Modbus failing after upgrade to 2023.9.0

[34by151]

The problem

Upgraded from 2023.8.4 to 2023.9.0

After upgrade
Core connects to 2 modbus servers via rtuovertcp
After aprox 5mins all registers become unavailable

Modbus has been rock solid up to this version

Restored 2023.8.4 and modbus has returned to normal

What version of Home Assistant Core has the issue?

2023.9.0

What was the last working version of Home Assistant Core?

2023.8.4

What type of installation are you running?

Home Assistant Supervised

Integration causing the issue

modbustcp

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant]

Hey there @adamchengtkc, @janiversen, @vzahradnik, mind taking a look at this issue as it has been labeled with an integration (modbus) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of modbus can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign modbus Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

modbus documentation
modbus source
_{^{(message by IssueLinks)}}

[janiversen]

Please add debug log as pr documentation otherwise it is impossible to see what happens.

and of course configuration.yaml

we have seen issues earlier when timeout was too fast.

[34by151]

Hey there @adamchengtkc, @janiversen, @vzahradnik, mind taking a look at this issue as it has been labeled with an integration (modbus) you are listed as a code owner for? Thanks!

Code owner commands
(message by CodeOwnersMention)

modbus documentation modbus source (message by IssueLinks)

Debug logs lost when I restored the backup and reverted to 2023.8.4
I will clone vm and run in an isolated environment
After that I redo the upgrade and get the logs

Will see if I can get that done tomorrow and post the logs

[sagitt]

Same problem to me, i using it with alfa sinapsi and elmogway2

[janiversen]

And same response, please follow our guidelines, otherwise it makes no sense to open an issue.

[FuL75]

Same here, looks like it wotks for one hour after reboot and then this:
2023-09-07 14:44:41.965 ERROR (SyncWorker_0) [homeassistant.components.modbus.modbus] Pymodbus: VMC_HUB: Modbus Error: [Input/Output] Modbus Error: [Invalid Message] No response received, expected at least 8 bytes (0 received)

[FuL75]

my timeout was default one (5 secs), worked fine till 2023.8.4. Now I've tried to increase to 30 secs.
Let's see if it solves the issue.

[janiversen]

And none of you care follow the guidelines, and post a debug log. Without a debug log it is impossible to help.

"No response received" is often related to a too short timeout, but can be a number of other causes.

You need to make a small configuration.yaml, no custom components, run it with debug as pr modbus documentation, and post the configuration.yaml and the log here. Before that is posted no investigation will take place.

[janiversen]

And just for reference, my production system using tcp have been running for 24 hours without any error (I updated yesterday, hence 24 hours).

[0xa51f]

configuration yaml:

• name: hub1
  type: tcp
  delay: 5
  timeout: 5
  host: 192.168.X.X
  port: 502
  sensors:
  • name: Grid Power
    unit_of_measurement: "W"
    device_class: power
    data_type: int16
    slave: 30
    address: 2600
    lazy_error_count: 1

debug log:

home-assistant_2023-09-07T18-40-04.154Z.log