pymodbus returned isError True

[brendan-pike]

I have the latest firmware & code here.

In logs I do get these errors:
Pymodbus: SungrowSHx: Error: device: 1 address: 5740 -> pymodbus returned isError True
Pymodbus: SungrowSHx: Error: device: 1 address: 5741 -> pymodbus returned isError True
Pymodbus: SungrowSHx: Error: device: 1 address: 5742 -> pymodbus returned isError True
Pymodbus: SungrowSHx: Error: device: 1 address: 5743 -> pymodbus returned isError True
Pymodbus: SungrowSHx: Error: device: 1 address: 5745 -> pymodbus returned isError True

Is it adequate to simply remove the refences form the dashboard or is more action require?

I have a LAN connected SH10RS / SUNSTONE-H_01011.02.59 and can provide more detail if required.

Thank you

ps. as a side note the dashboard scenes did not load correctly until I manually edited them,

[Gnarfoz]

Removing them from the dashboard won't be enough. If these are not working on your inverter, you'll have to remove the relevant sensors from the modbus_sungrow.yaml file. They're related to the smart energy meter (DTSU666), do you have that installed?

Also, which scenes? What did you edit? (Better to make separate issues for separate problems.)

[tahlers93]

Hey, i have the same errors:
Pymodbus: SungrowSHx: Error: device: 1 address: 13030 -> pymodbus returned isError True Pymodbus: SungrowSHx: Error: device: 1 address: 13031 -> pymodbus returned isError True Pymodbus: SungrowSHx: Error: device: 1 address: 13032 -> pymodbus returned isError True Pymodbus: SungrowSHx: Error: device: 1 address: 13033 -> pymodbus returned isError True Pymodbus: SungrowSHx: Error: device: 1 address: 13001 -> pymodbus returned isError True

I'm using the energy meter DTSU666-20 and have the latest firmware (updatet end of the last week). Because i'm using evcc and i had problems, when home assistant and evcc connect directly to my pv, i've connected home assistant to the modbus relay of evcc.

Could this be the problem?

[brendan-pike]

Thanks, I don't use the DTSU666 so I've just removed those references.

As suggested I'll raise separate tickets where needed, unfortunately I may have to revert back to the legacy code for now. I'm using this node-red script which worked quite well but I'm struggling to get it working with the v2 here.

[Gnarfoz]

I'm using the energy meter DTSU666-20 and have the latest firmware (updatet end of the last week). Because i'm using evcc and i had problems, when home assistant and evcc connect directly to my pv, i've connected home assistant to the modbus relay of evcc.

Could this be the problem?

Probably not. But you haven't described the rest of your setup at all. Which inverter? Is it using a WiNet-S dongle?
Also, you're referring to completely different registers (13xxx instead of 574x). So it's kind of not "the same error".
"pymodbus returned isError True" just means "there was an error reading address X" and doesn't convey any further information.

[Gnarfoz]

I'm using this node-red script which worked quite well but I'm struggling to get it working with the v2 here.

I've added a comment to guysqr/node-red-ha-solar-management#5, maybe that can help you (or the author) get on the right track.

[tahlers93]

I'm using the energy meter DTSU666-20 and have the latest firmware (updatet end of the last week). Because i'm using evcc and i had problems, when home assistant and evcc connect directly to my pv, i've connected home assistant to the modbus relay of evcc.
Could this be the problem?

Probably not. But you haven't described the rest of your setup at all. Which inverter? Is it using a WiNet-S dongle? Also, you're referring to completely different registers (13xxx instead of 574x). So it's kind of not "the same error". "pymodbus returned isError True" just means "there was an error reading address X" and doesn't convey any further information.

Here my setup:
SH10RT-20
SBR096
DTSU666-20
WiNet-S

[Gnarfoz]

Is your evcc talking to the WiNet-S or to the LAN port of the SH10RT?

[tahlers93]

To the WiNet-S

[Gnarfoz]

Are the registers available on the LAN port of the SH10RT?

[tahlers93]

I'll have to test it soon and let you know how it goes.

[fredrikekre]

FWIW, basically every registered errored for me (SH10RT) when using the WiNet-S module but once I started using the LAN port everything worked flawlessly.

[mkaiser]

@tahlers93

To the WiNet-S

to avoid confusion:

Is your WiNet-S using WLAN or did you connect an Ethernet cable to the WiNetS?

[Gnarfoz]

Doesn't really make a difference regarding registers, does it? Only polling frequency?

[Tr1n0va]

Hi, I'm getting similar errors. What should I do?

Logger: homeassistant.components.modbus
Quelle: components/modbus/modbus.py:310
Integration: Modbus (Dokumentation, Probleme)
Erstmals aufgetreten: 15:14:57 (762 Vorkommnisse)
Zuletzt protokolliert: 20:33:10

Pymodbus: SungrowSHx: Error: device: 1 address: 5722 -> pymodbus returned isError True
Pymodbus: SungrowSHx: Error: device: 1 address: 5723 -> pymodbus returned isError True
Pymodbus: SungrowSHx: Error: device: 1 address: 5724 -> pymodbus returned isError True
Pymodbus: SungrowSHx: Error: device: 1 address: 2612 -> pymodbus returned isError True
Pymodbus: SungrowSHx: Error: device: 1 address: 2628 -> pymodbus returned isError True

[fredrikekre]

Is your WiNet-S using WLAN or did you connect an Ethernet cable to the WiNetS?

Ethernet. Note that increasing timeouts etc didn't work either.