New EG4 Gridboss Supported?

[NylonDiamond]

Do you know if the new EG4 GridBoss is supported? Maybe I'm using the wrong protocol. I only see the protocol for the 18k. I'm using this adapter and getting the following error:

INFO:.transport_base[transport.0]:get registers (0): Registry_Type.INPUT - 0 to 39 (40)
DEBUG:pymodbus.logging:Current transaction state - TRANSACTION_COMPLETE
DEBUG:pymodbus.logging:Running transaction 7
DEBUG:pymodbus.logging:SEND: 0x1 0x4 0x0 0x0 0x0 0x28 0xf0 0x14
DEBUG:pymodbus.logging:Resetting frame - Current Frame in buffer -
DEBUG:pymodbus.logging:Changing state to IDLE - Last Frame End - None Current Time stamp - 1752989830.937242
DEBUG:pymodbus.logging:New Transaction state "SENDING"
DEBUG:pymodbus.logging:Changing transaction state from "SENDING" to "WAITING FOR REPLY"
DEBUG:pymodbus.logging:No response received, Expected 85 bytes Received 0 bytes !!!!
DEBUG:pymodbus.logging:Changing transaction state from "WAITING FOR REPLY" to "PROCESSING REPLY"
DEBUG:pymodbus.logging:RECV:
DEBUG:pymodbus.logging:Processing:
DEBUG:pymodbus.logging:Getting transaction 0
DEBUG:pymodbus.logging:Changing transaction state from "PROCESSING REPLY" to "TRANSACTION_COMPLETE"
ERROR:.transport_base[transport.0]:<bound method ModbusException.__str__ of ModbusIOException('[Input/Output] No Response received from the remote slave/Unable to decode response')>

Here is my config:

[general]
log_level = DEBUG

[transport.0] #name must be unique, ie: transport.modbus
#logging level for transport
log_level = DEBUG

#rs485 / modbus device
#protocol config files are located in protocols/
protocol_version = eg4_v58
analyze_protocol = false
write = false

#in
#was unit
address = 1
port = /dev/ttyUSB0
baudrate = 19200

#modbus tcp/tls/udp example
#host = 192.168.0.7
#port = 502
#override protocol reader
#transport = modbus_tcp

#the 'transport' that we want to share this with
bridge = transport.1

manufacturer = EG4
model = GRIDBOSS
#optional; leave blank to autofetch serial from device
serial_number =

read_interval = 10


[transport.1]
#connect mqtt
transport=mqtt
host = 172.16.43.222
port = 1883
user = mqqt_user
pass = mypass
base_topic = home/inverter/
error_topic = /error
json = false
discovery_enabled = true
discovery_topic = homeassistant

[HotNoob]

At a glance, could be incorrect address, wiring, baud, or lastly protocol. Modbus addresses often overlap so you are likely to see something if the protocol is different. I haven't run into the gridboss one yet, but if you can get the modbus communication documentation from eg4, it's not too difficult to add into ppg.

…

On Sun, Jul 20, 2025, 12:51 a.m. Jesse Skelton ***@***.***> wrote: *NylonDiamond* created an issue (HotNoob/PythonProtocolGateway#103) <#103> Do you know if the new EG4 GridBoss is supported? Maybe I'm using the wrong protocol. I only see the protocol for the 18k. I'm using this adapter and getting the following error: INFO:.transport_base[transport.0]:get registers (0): Registry_Type.INPUT - 0 to 39 (40) DEBUG:pymodbus.logging:Current transaction state - TRANSACTION_COMPLETE DEBUG:pymodbus.logging:Running transaction 7 DEBUG:pymodbus.logging:SEND: 0x1 0x4 0x0 0x0 0x0 0x28 0xf0 0x14 DEBUG:pymodbus.logging:Resetting frame - Current Frame in buffer - DEBUG:pymodbus.logging:Changing state to IDLE - Last Frame End - None Current Time stamp - 1752989830.937242 DEBUG:pymodbus.logging:New Transaction state "SENDING" DEBUG:pymodbus.logging:Changing transaction state from "SENDING" to "WAITING FOR REPLY" DEBUG:pymodbus.logging:No response received, Expected 85 bytes Received 0 bytes !!!! DEBUG:pymodbus.logging:Changing transaction state from "WAITING FOR REPLY" to "PROCESSING REPLY" DEBUG:pymodbus.logging:RECV: DEBUG:pymodbus.logging:Processing: DEBUG:pymodbus.logging:Getting transaction 0 DEBUG:pymodbus.logging:Changing transaction state from "PROCESSING REPLY" to "TRANSACTION_COMPLETE" ERROR:.transport_base[transport.0]:<bound method ModbusException.__str__ of ModbusIOException('[Input/Output] No Response received from the remote slave/Unable to decode response')> Here is my config: [general] log_level = DEBUG [transport.0] #name must be unique, ie: transport.modbus #logging level for transport log_level = DEBUG #rs485 / modbus device #protocol config files are located in protocols/ protocol_version = eg4_v58 analyze_protocol = false write = false #in #was unit address = 1 port = /dev/ttyUSB0 baudrate = 19200 #modbus tcp/tls/udp example #host = 192.168.0.7 #port = 502 #override protocol reader #transport = modbus_tcp #the 'transport' that we want to share this with bridge = transport.1 manufacturer = EG4 model = GRIDBOSS #optional; leave blank to autofetch serial from device serial_number = read_interval = 10 [transport.1] #connect mqtt transport=mqtt host = 172.16.43.222 port = 1883 user = mqqt_user pass = mypass base_topic = home/inverter/ error_topic = /error json = false discovery_enabled = true discovery_topic = homeassistant — Reply to this email directly, view it on GitHub <#103>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAQUIMOUQO33SYODLUQDJJL3JMU5VAVCNFSM6AAAAACB5OYZ5WVHI2DSMVQWIX3LMV43ASLTON2WKOZTGI2DMMBRHEYDQMI> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[NylonDiamond]

Thanks for the advice.

According to this forum post, EG4 responded with, "We currently do not have the Modbus available for the Gridboss. Unfortunately, I don’t have specific information regarding the reason for its unavailability. However, once it is approved for release to the public, we will notify everyone." (That was 2 months ago..)

According to this repo, the gridboss's INV485 port doesn't seem to function.
However, also according to this repo, it is possible to wire GridBOSS to RS485 via the dongle port (HDMI). I'm going to do that and see if I can communicate with it.

[HotNoob]

i've put in a request to eg4. it would be ideal to have official documentation... never know.

otherwise reverse engineering works. i'm assuming that is what was done with the linked repo...
it could be added to ppg if it takes too long.

[HotNoob]

v1.1.11 branch
90104f1

from that linked repo; wrote it for ppg.
https://github.com/galets/eg4-modbus-monitor/tree/master

100% completely untested.

protocol_version=eg4_gridboss_re

---

if someone with a gridboss wants todo a registry dump; i can test on my end... and maybe a little bit of extra reverse engineering. if i have some time to blow ;)

todo a dump via ppg:
run once with this under modbus transport.

analyze_protocol = true
analyze_protocol_save_load = true

it'll save it as "input_registry.json" and "holding_registry.json"

or any modbus dump will do.

[josuealuna]

I just got my stand-alone gridboss installed (no inverter). I would need someone to ELI5 since I don't even know what ppg is, but I'm very interested in getting this into my HA setup

[Tmaxxrox97]

v1.1.11 branch 90104f1

from that linked repo; wrote it for ppg. https://github.com/galets/eg4-modbus-monitor/tree/master

100% completely untested.

protocol_version=eg4_gridboss_re

if someone with a gridboss wants todo a registry dump; i can test on my end... and maybe a little bit of extra reverse engineering. if i have some time to blow ;)

todo a dump via ppg: run once with this under modbus transport.

analyze_protocol = true
analyze_protocol_save_load = true

it'll save it as "input_registry.json" and "holding_registry.json"

or any modbus dump will do.

@HotNoob are there detailed instructions on how to create a modbus dump through PPG? I tried the following config file in both a v1.1.11 and a v1.1.10 docker container and based on the logs it never does the analysis/save. Is Docker the issue and I should try it as a script instead?
Additionally, where are the files supposed to be saved? Assuming I missed the log output, I looked in all the folders contained in the app directory as well as the root directory in the docker container but didn't see them.

At first glance the protocol files work. Some values appear to be scaled incorrectly but I can work on adjusting those.

[general]
log_level = DEBUG

[transport.0] #name must be unique, ie: transport.modbus
#logging level for transport
log_level = DEBUG

#rs485 / modbus device
#protocol config files are located in protocols/
protocol_version = eg4_gridboss_re
analyze_protocol = true
analyze_protocol_save_load = true
write = false

#in
#was unit
address = 1
port = /dev/ttyUSB0
baudrate = 19200

#modbus tcp/tls/udp example
#host = 192.168.0.7
#port = 502
#override protocol reader
transport = modbus_rtu

#the 'transport' that we want to share this with
bridge = transport.1

manufacturer = EG4
model = GRIDBOSS
#optional; leave blank to autofetch serial from device
serial_number =

read_interval = 10


[transport.1]
#connect mqtt
transport=mqtt
host = {{ my_host }}
port = {{ host_port }}
user = {{ mqqt_user }}
pass = {{ mypass }}
base_topic = home/inverter/
error_topic = /error
json = false
discovery_enabled = true
discovery_topic = homeassistant

[HotNoob]

cool, glad it's working. adjusting the units shouldn't be too hard ;)
ty for testing.

---

i've never done it in docker before :P

docker cp {container name}:/input_registry.json ./input_registry.json

in theory it should appear in the working directory of the script.

alternatively, something like modpoll should work for dumping

apt install modpoll
modpoll -m rtu -b 19200 -p none -s 1 -a 1 -t 3 -r 1 -c 1000 /dev/ttyUSB0 > input_registers.txt
modpoll -m rtu -b 19200 -p none -s 1 -a 1 -t 4 -r 1 -c 1000 /dev/ttyUSB0 > holding_registers.txt

[Tmaxxrox97]

@HotNoob is there a good way to send you the modbus dumps? I'd prefer to not upload them here since they have serial number data in them.

[HotNoob]

@Tmaxxrox97
you can email me at hotnoob@hotnoob.com