Modbus integration not working reliably with HA Core 2024.4.1

[nilremgithub]

The modbus integration has stopped working with the latest HA update. The log shows:

Logger: homeassistant.components.modbus.modbus
Source: components/modbus/modbus.py:383
integration: Modbus (documentation, issues)
First occurred: 11:51:50 (1 occurrences)
Last logged: 11:51:50

modbus solis communication closed

[Paulholloway]

No issues observed here (and mine normally breaks quickly).
Do you have the latest version?

[nilremgithub]

Thanks for letting me know. I will check the code I have added.

[nilremgithub]

It seems other people are experiencing the same issue. It seems to be related to the 2024.4.1 upgrade.
See: home-assistant/core#115040

[fboundy]

It seems other people are experiencing the same issue. It seems to be related to the 2024.4.1 upgrade. See: home-assistant/core#115040

Thanks - I've subscribed to updated to that issue so will monitor it. It does look like its an issue with Core

[fboundy]

A number of issues are now documented in home-assistant/core#115236.

I'm not sure which, if any, relate to issues with the Solis inverter. If you are able to debug log the issue and submit it then that would be helpful but the guy who looks after this on HA is somewhat lacking in social skills so be warned!

[spetrie13]

3.13.2 Using Solax for inverter communication. Noted in logs also was getting 107A issues on writing to Inverter causing modbus issues. Changed inverter config in pv_opt from 5500W to 5000W so hopefully that will limit charge to 100A limit of inverter.

…

On Mon, 8 Apr 2024, 23:15 fboundy, ***@***.***> wrote: A number of issues are now documented in home-assistant/core#115236 <home-assistant/core#115236>. I'm not sure which, if any, relate to issues with the Solis inverter. If you are able to debug log the issue and submit it then that would be helpful but the guy who looks after this on HA is somewhat lacking in social skills so be warned! — Reply to this email directly, view it on GitHub <#24 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AYRF457DNHSIWDPJPHHRSV3Y4MJGHAVCNFSM6AAAAABF2LG4QWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBTG4ZTAOBWG4> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[Richardvdw01]

My modbus problems still persist after Bump pymodbus v3.6.7 #115279
Looking at the logs, it seems that the modbus connection keeps getting lost. This makes several entities unavailable at the frontend.
When rolling back to 2024.3.3 everything works flawless.
Here is the latest log when upgrading to 2024.5.3:

Pymodbus fail.docx

[nilremgithub]

I am not experiencing any issues. However I added the following to the top of the solis.yaml file under the port setting to address the original concern and haven't removed it.

delay: 5

message_wait_milliseconds: 100
timeout: 5

[Richardvdw01]

Thank you @ nilremgithub, Adding the delay resolved the issue. It looks like the new Pymodbus is too fast for the serial connection.

[fboundy]

Please feel free the update the GitHub repo with a Pull Request incorporating this

…

On 16 May 2024 at 09:59 +0100, Richardvdw01 ***@***.***>, wrote: Thank you @ nilremgithub, Adding the delay resolved the issue. It looks like the new Pymodbus is too fast for the serial connection. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: ***@***.***>