What is the last HA version with working modbus?

Installation
1

When did they do large breaking changes to modbus?
2025.2.1 definitely does not work. “Upgraded” from 2023.3 and modbus is dead on this version. Works for 1-2 hours, after that get spam of the following messages in log:

Feb 08 20:12:22 ubuntu-phablet hass[18271]: 2025-02-08 20:12:22.591 ERROR (MainThread) [pymodbus.logging] Exception response 131 / 0
Feb 08 20:12:22 ubuntu-phablet hass[18271]: 2025-02-08 20:12:22.594 ERROR (MainThread) [pymodbus.logging] Exception response 131 / 0
Feb 08 20:12:22 ubuntu-phablet hass[18271]: 2025-02-08 20:12:22.597 ERROR (MainThread) [pymodbus.logging] Exception response 131 / 0
Feb 08 20:12:22 ubuntu-phablet hass[18271]: 2025-02-08 20:12:22.604 ERROR (MainThread) [pymodbus.logging] Exception response 131 / 0
Feb 08 20:12:22 ubuntu-phablet hass[18271]: 2025-02-08 20:12:22.607 ERROR (MainThread) [pymodbus.logging] Exception response 131 / 0
Feb 08 20:12:22 ubuntu-phablet hass[18271]: 2025-02-08 20:12:22.609 ERROR (MainThread) [pymodbus.logging] Exception response 131 / 0
Feb 08 20:12:22 ubuntu-phablet hass[18271]: 2025-02-08 20:12:22.612 ERROR (MainThread) [pymodbus.logging] Exception response 131 / 0

And of course all the modbus entities go to “unknown”. Real fun.

Restart, and everything okay again for 2 hours or so. Then just blows up again.
While I could schedule a restart job for HA to restart every couple hours, I’d rather find a version that works. I used this software to automate a bunch of my climate controls at home, and I don’t want to move it anywhere.
I use a venv, so no issues with any auto upgrade shenanigans - can deploy any version.

Do I just go back to 2023.3 or is there something newer where they didn’t blow up modbus support?

2

Looks like modus is still supported. When was it working for you? When did it break?

3

Well you cant expect two years of updates to be not breaking anything. You should revisit the modbus integration page and check if your code is still syntactically correct or you can use the modbus proxy addon.

2 Likes
4

Did you read the post?

5

There is absolutely nothing wrong with my configuration.

I checked the logs and it’s about 3-4 hours that something happens to the modbus component and it crashes so that it only gives “Exception response 131 / 0” to every query.

A problem with the configuration will not make it work fine for 3-4 hours and then die, and a restart would not fix it every time in that case.

Only thing that changed was that slave is now default 1 instead of 0, and I updated that, but no difference.

And hey, I do expect every update to break everything! That’s why I am running a VENV. Because even if you do not update in docker, they push you random updates from their server to the supervisor, that you can not opt out of, which is not only a huge security risk, but it also eventually bricks your install completely.

But the fact that you should expect the very core components (modbus is one) to break every time you update says quite a bit about this project.

Oh btw, tell all those people here:

That their configuration is wrong and they should expect modbus to be completely messed up.

At least I now know that it should work in 2024.12.5, and that’s what I will be installing and keeping for the next few years.

6

Tried 2024.12.5, it’s also broken there, and breaks even faster.