-
Notifications
You must be signed in to change notification settings - Fork 4
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
ERROR (MainThread) [homeassistant] Error doing job: Exception in callback SerialTransport._read_ready() #22
Comments
@slivorezka are there any error logs before that? The error you pasted is an internal error from homeassistant and not from the integration. Also, what string did you use for the USB device path? Did you mount this device in your docker container? |
Also, I've installed the Must Inverter integration manually and looks like it works fine for the time being Thanks! |
A little bit more info about this bug and how to fix it. There is an issue https://community.home-assistant.io/t/error-doing-job/290384
And after some time I have very slow HA instance. Reload can fix it but later (few hrs) this issue will come back. My
|
I join the problem. I have a similar behavior, after starting the integration everything works well for a while, from 5 minutes to an hour, after which the readings stop changing, and the ON itself starts to slow down very much, only a complete reboot of the ON helps, restarting the integration does not help. (or rather it helps, but not always). Below is part of the log with errors. 2024-05-02 09:39:39.553 INFO (MainThread) [homeassistant.setup] Setting up must_inverter 2024-05-02 09:41:55.994 WARNING (MainThread) [custom_components.must_inverter] wrong number of registers read at address 10101, expected 24, got 12 2024-05-02 09:42:06.234 WARNING (MainThread) [custom_components.must_inverter] wrong number of registers read at address 20000, expected 17, got 21 2024-05-02 09:46:56.001 WARNING (MainThread) [custom_components.must_inverter] wrong number of registers read at address 10101, expected 24, got 12 2024-05-02 09:47:06.267 WARNING (MainThread) [custom_components.must_inverter] wrong number of registers read at address 20000, expected 17, got 21 2024-05-02 10:04:04.051 ERROR (MainThread) [custom_components.must_inverter] error reading modbus data at address 15201 2024-05-02 10:04:14.205 ERROR (MainThread) [custom_components.must_inverter] error reading modbus data at address 20101 |
@devastatoralexey I added a new config to allow changing the scan interval in the latest version. Can you change it to something like 30 seconds and see if the error stops or takes longer to happen? This integration is my first experience with modbus, I'm not familiar with what could cause that. |
I tried the new version. I changed the parameters many times, both up and down. When the interval increases, it works a little longer, but still freezes and stops taking readings. After which the entire smart home server begins to slow down. Only rebooting the integration or server helps. I can’t connect to the proprietary Wifi USB plug at all. Not on any port. I scanned all its open ports, but none of them connect. There is another software "https://solar-assistant.io/shop/products/software" I tried it, everything works with it, there are no freezes, which means the problem is still with the integration. I will continue experimenting with the parameters. Thank you for your work. Perhaps the work of this person will help you: add: (20-05-2024) Регистратор: custom_components.must_inverter error reading modbus data at address 20000 |
I have a similar behavior. All freezing. scan interval 30s not help. And cpu host machine 100% |
System Health details
System Information
Home Assistant Community Store
Home Assistant Cloud
Home Assistant Supervisor
Dashboards
Recorder
Checklist
Describe the issue
The installation process of this integration was fine.
But after a few mins I've noticed some lagging of HA in general. See more detail in the Debug logs section.
My MUST inverter has this name: Must 3000W 24V 60A (PV18-3024VPM)
Reproduction steps
Debug logs
Diagnostics dump
No response
The text was updated successfully, but these errors were encountered: