WARNING (MainThread) [custom_components.must_inverter] wrong number of registers read at address *, expected *, got * #47
Comments
|
I couldn't find any code paths that would lead to this, I added that warning as a sanity check and it should never happen. I guess it's some bug on pymodbus,o n newer versions of it they added a check on their side that throws an exception when it happens |
In other words, can I ignore the warnings? |
|
New logs: 2024-11-22 16:14:51.974 DEBUG (MainThread) [custom_components.must_inverter] reading modbus data 2024-11-22 16:15:17.984 ERROR (MainThread) [custom_components.must_inverter] error reading modbus data at address 10101 2024-11-22 16:15:17.985 DEBUG (MainThread) [custom_components.must_inverter] reading modbus data from 15201 to 15221 (21) 2024-11-22 16:15:17.985 INFO (MainThread) [custom_components.must_inverter] modbus client is not connected, trying to reconnect 2024-11-22 16:15:22.107 DEBUG (MainThread) [custom_components.must_inverter] reading modbus data from 20000 to 20016 (17) |
Yes, they should be harmless. I saw your other issue on the repo, it might be somewhat related to that. I would recommend increasing the scan interval configuration to something more moderate. |
But scan interval in default value... I'm try set: 30 / 60 / 180 / 300 but I see problem again and again... 😓 |
System Health details
System Information
Home Assistant Community Store
Home Assistant Cloud
Home Assistant Supervisor
Dashboards
Recorder
Checklist
Describe the issue
From time to time the problem "wrong number of registers read at address *, expected *, got *" appears consistently, while all sensors continue to work and display data.
In this ticket I give an example of the case with "WARNING (MainThread) [custom_components.must_inverter] wrong number of registers read at address 20000, expected 17, got 21" , but if you look at the history - the problem was also with other registers.
The problem cannot be reproduced by force; it appears randomly.
I didn’t notice any connections: the problem can appear at 9 pm,
5 am or 12 noon. In this case, no manipulations are performed: no one reconfigures anything in Home Assistant and no one touches the inverter.
The following messages appear in the HA log:
This error occurred in custom integration.
Logger: custom_components.must_inverter
Source: custom_components/must_inverter/init.py:243
integration: Must Inverter (documentation, problems)
First message: November 17, 2024 at 00:53:21 (25 messages)
Last message: November 17, 2024 at 11:29:46 pm
wrong number of registers read at address 15201, expected 21, got 24
wrong number of registers read at address 20000, expected 17, got 21
wrong number of registers read at address 20101,
expected 114, got 17
wrong number of registers read at address 20101, expected 114, got 21
wrong number of registers read at address 10101, expected 24, got 79
USB or Serial device path: /dev/ttyUSB0
Baud rate: 19200
Parity (‘E’ven, ‘O’dd or ‘N’one): N
Stop bits (1, 1.5, 2): 1
Byte size (7, 8): 8
The server used is Windows Server, on which the VMware Workstation Pro 17.5 virtual machine is installed for Home Assistant. Every time you turn on the virtual machine, the specified USB device is automatically forwarded to VmWare.
Reproduction steps
The problem cannot be reproduced by force; it appears randomly.
I didn’t notice any connections: the problem can appear at 9 pm, 5 am or 12 noon. In this case, no manipulations are performed: no one reconfigures anything in Home Assistant and no one touches the inverter.
Debug logs
Diagnostics dump
This error occurred in custom integration.
Logger: custom_components.must_inverter
Source: custom_components/must_inverter/init.py:243
integration: Must Inverter (documentation, problems)
First message: November 17, 2024 at 00:53:21 (25 messages)
Last message: November 17, 2024 at 11:29:46 pm
wrong number of registers read at address 15201, expected 21, got 24
wrong number of registers read at address 20000, expected 17, got 21
wrong number of registers read at address 20101,
expected 114, got 17
wrong number of registers read at address 20101, expected 114, got 21
wrong number of registers read at address 10101, expected 24, got 79
The text was updated successfully, but these errors were encountered: