-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pymodbus error still occurs with Docker-based HA and v1.13.1 #753
Comments
I got the error too, I had to delete it, install 1.13.0 then restart. Then re configure the integration. |
Mind trying v1.13.2b1? |
1.13.2b1 starts, but I get this error...Error reading registers. Type: RegisterType.HOLDING; start: 31000; count: 91; slave: 196 from tcp://192.168.2.235:502: Exception Response(131, 3, IllegalAddress) With the 1.13.0 the registers were working no problem |
OK great, that's something different. Mind opening a new ticket, and include your inverter model and manager version? The inverter is successfully talking to us, it just doesn't like the register we're reading. That's proabably because we don't support your inverter firmware version, or you need to select it in the advaned settings. |
Actually, leaving open until this is released as a non-beta version. |
Adding to this -> I'm using Home Assistant Green and also get the pymodbus error
Using H3 inverter |
This should be fixed in v1.13.2. |
Hi @canton7. In my environment it works. Thank you for the quick fix. Best regards, A. |
Version of the custom_component
v1.13.1
HA Version
2025.1.4 docker image
Configuration
nothing special
Describe the bug
After updating to v1.13.1 foxess_modbus didn't start anymore. Downgrading to v1.13.0 also did not help.
After checking the HA logs and the vendoring PR, I downgraded the pymodbus version inside the home assistant docker container to 3.6.9 and kept the integration at v1.13.0 - both seems to be necessary to not run into the issue, with v1.13.1 and the system pymodbus at 3.6.9 I still run into the issue. Too tired to debug further today.
Looks like just vendoring doesn't help if a newer pymodbus is installed in /usr/local/lib/python3.13/site-packages (as it is inside the docker container).
Debug log
The text was updated successfully, but these errors were encountered: