Sudden HA exodus trough ModBus

jakob.tewes · March 20, 2025, 6:32pm

Heyhey team ModBus ,

ran into an issue, that kills my Home Assistant with ModBus.
I got a PV installation with a ModBus Smartmeter SDM630v2.
Those i integrated via this config:

modbus:
  - name: modbus_1
    type: serial
    port: /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0
    baudrate: 19200
#    baudrate: 9600
    bytesize: 8
    method: rtu
    parity: N
    stopbits: 1
    delay: 0
    message_wait_milliseconds: 45
    timeout: 5
    sensors:
## SM1
      - name: sdm630_01_phase_1_line_to_neutral_volts
        unique_id: sdm630_01_phase_1_line_to_neutral_volts
        slave: 1
        address: 0
        input_type: input
        precision: 2
        data_type: float32
        unit_of_measurement: V
        device_class: voltage
        state_class: measurement
      - name: sdm630_01_phase_2_line_to_neutral_volts
        unique_id: sdm630_01_phase_2_line_to_neutral_volts
        slave: 1
        address: 2
        input_type: input
        precision: 2
        data_type: float32
        unit_of_measurement: V
        device_class: voltage
        state_class: measurement
....

Now for the second time in a few days my HA doesn´t come up anymore. Logs (set ModBus to debug) is full of this:

2025-03-20 19:07:33.355 DEBUG (MainThread) [pymodbus.logging] Connecting to /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0:0.
2025-03-20 19:07:33.355 DEBUG (MainThread) [pymodbus.logging] Connecting comm
2025-03-20 19:07:35.730 DEBUG (MainThread) [pymodbus.logging] Connected to comm
2025-03-20 19:07:35.754 INFO (MainThread) [homeassistant.components.modbus.modbus] modbus modbus_1 communication open
2025-03-20 19:07:35.773 DEBUG (MainThread) [pymodbus.logging] recv: 0x1 0x4 0x0 0x34 0x0 0x2 0x30 0x5 0x1 0x4 0x4 0x42 0x15 0xac 0xa0 0x83 0x40 0x1 0x4 0x0 0x34 0x0 0x2 0x30 0x5 0x1 0x4 0x4 0x42 0x75 0x18 0xd0 0xf5
2025-03-20 19:07:35.774 DEBUG (MainThread) [pymodbus.logging] Processing: 0x1 0x4 0x0 0x34 0x0 0x2 0x30 0x5 0x1 0x4 0x4 0x42 0x15 0xac 0xa0 0x83 0x40 0x1 0x4 0x0 0x34 0x0 0x2 0x30 0x5 0x1 0x4 0x4 0x42 0x75 0x18 0xd
2025-03-20 19:07:35.774 DEBUG (MainThread) [pymodbus.logging] Frame check failed, possible garbage after frame, testing..
2025-03-20 19:07:35.774 DEBUG (MainThread) [pymodbus.logging] Frame check failed, possible garbage after frame, testing..
2025-03-20 19:07:35.774 DEBUG (MainThread) [pymodbus.logging] Frame check failed, possible garbage after frame, testing..
2025-03-20 19:07:35.775 DEBUG (MainThread) [pymodbus.logging] Frame check failed, possible garbage after frame, testing..
2025-03-20 19:07:35.775 DEBUG (MainThread) [pymodbus.logging] Frame check failed, possible garbage after frame, testing..
2025-03-20 19:07:35.775 DEBUG (MainThread) [pymodbus.logging] Frame check failed, possible garbage after frame, testing..
2025-03-20 19:07:35.775 DEBUG (MainThread) [pymodbus.logging] Frame check failed, possible garbage after frame, testing..
2025-03-20 19:07:35.775 DEBUG (MainThread) [pymodbus.logging] Frame check failed, possible garbage after frame, testing..
2025-03-20 19:07:35.776 DEBUG (MainThread) [pymodbus.logging] Frame check failed, possible garbage after frame, testing..
2025-03-20 19:07:35.776 DEBUG (MainThread) [pymodbus.logging] Frame check failed, possible garbage after frame, testing..
2025-03-20 19:07:35.776 DEBUG (MainThread) [pymodbus.logging] Frame check failed, possible garbage after frame, testing..
2025-03-20 19:07:35.776 DEBUG (MainThread) [pymodbus.logging] Frame check failed, possible garbage after frame, testing..
2025-03-20 19:07:35.776 DEBUG (MainThread) [pymodbus.logging] Frame check failed, possible garbage after frame, testing..
2025-03-20 19:07:35.776 DEBUG (MainThread) [pymodbus.logging] Frame check failed, possible garbage after frame, testing..
2025-03-20 19:07:35.777 DEBUG (MainThread) [pymodbus.logging] Frame check failed, possible garbage after frame, testing..
2025-03-20 19:07:35.777 DEBUG (MainThread) [pymodbus.logging] Frame check failed, possible garbage after frame, testing..
2025-03-20 19:07:35.777 DEBUG (MainThread) [pymodbus.logging] Frame check failed, possible garbage after frame, testing..
2025-03-20 19:07:35.777 DEBUG (MainThread) [pymodbus.logging] Frame check failed, possible garbage after frame, testing..
2025-03-20 19:07:35.777 DEBUG (MainThread) [pymodbus.logging] Frame check failed, possible garbage after frame, testing..
2025-03-20 19:07:35.778 DEBUG (MainThread) [pymodbus.logging] Frame check failed, possible garbage after frame, testing..
2025-03-20 19:07:35.778 DEBUG (MainThread) [pymodbus.logging] Frame check failed, possible garbage after frame, testing..
2025-03-20 19:07:35.778 DEBUG (MainThread) [pymodbus.logging] Frame check failed, possible garbage after frame, testing..
2025-03-20 19:07:35.780 DEBUG (MainThread) [pymodbus.logging] Frame check failed, possible garbage after frame, testing..
2025-03-20 19:07:35.780 DEBUG (MainThread) [pymodbus.logging] Frame check failed, possible garbage after frame, testing..
2025-03-20 19:07:35.780 DEBUG (MainThread) [pymodbus.logging] Frame check failed, possible garbage after frame, testing..
2025-03-20 19:07:35.781 DEBUG (MainThread) [pymodbus.logging] Frame check failed, possible garbage after frame, testing..
2025-03-20 19:07:35.781 DEBUG (MainThread) [pymodbus.logging] decoded PDU function_code(4 sub -1) -> ReadInputRegistersResponse(dev_id=0, transaction_id=0, address=0, count=0, bits=[], registers=[], status=1)
2025-03-20 19:07:35.781 DEBUG (MainThread) [pymodbus.logging] Frame advanced, resetting header!!
2025-03-20 19:07:35.781 DEBUG (MainThread) [pymodbus.logging] recv, unused data waiting for next packet: 0x1 0x4 0x4 0x42 0x15 0xac 0xa0 0x83 0x40 0x1 0x4 0x0 0x34 0x0 0x2 0x30 0x5 0x1 0x4 0x4 0x42 0x75 0x18 0xd0 0
2025-03-20 19:07:35.955 DEBUG (MainThread) [pymodbus.logging] recv: 0x1 0x4 0x0 0x34 0x0 0x2 0x30 0x5 0x1 0x4 0x4 0x42 0x18 0x8a 0xe0 0x9 0x13 old_data: 0x1 0x4 0x4 0x42 0x15 0xac 0xa0 0x83 0x40 0x1 0x4 0x0 0x34 0x
2025-03-20 19:07:35.956 DEBUG (MainThread) [pymodbus.logging] Processing: 0x1 0x4 0x4 0x42 0x15 0xac 0xa0 0x83 0x40 0x1 0x4 0x0 0x34 0x0 0x2 0x30 0x5 0x1 0x4 0x4 0x42 0x75 0x18 0xd0 0xf5 0xba 0x1 0x4 0x0 0x34 0x0 0
2025-03-20 19:07:35.956 DEBUG (MainThread) [pymodbus.logging] Frame check failed, possible garbage after frame, testing..
2025-03-20 19:07:35.956 DEBUG (MainThread) [pymodbus.logging] Frame check failed, possible garbage after frame, testing..
2025-03-20 19:07:35.956 DEBUG (MainThread) [pymodbus.logging] Frame check failed, possible garbage after frame, testing..

As HA no longer works i tried deactivating the SDM Meters and removed all the configured sensors. Unfortunately this does not solve the thing. Its definitely modbus as removing the modbus config…you know

jakob.tewes · March 20, 2025, 7:15pm

Expected behavior when unplugging the ModBus USB Adaptor:

2025-03-20 20:13:46.897 ERROR (MainThread) [homeassistant.components.modbus.modbus] Pymodbus: modbus_1: Error: device: 1 address: 0 -> Modbus Error: [Connection] Not connected[AsyncModbusSerialClient /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0:0]
2025-03-20 20:13:46.945 DEBUG (MainThread) [homeassistant.components.modbus.modbus] Pymodbus: modbus_1: Error: device: 1 address: 2 -> Modbus Error: [Connection] Not connected[AsyncModbusSerialClient /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0:0]
2025-03-20 20:13:47.007 DEBUG (MainThread) [homeassistant.components.modbus.modbus] Pymodbus: modbus_1: Error: device: 1 address: 4 -> Modbus Error: [Connection] Not connected[AsyncModbusSerialClient /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0:0]
2025-03-20 20:13:47.057 DEBUG (MainThread) [homeassistant.components.modbus.modbus] Pymodbus: modbus_1: Error: device: 1 address: 6 -> Modbus Error: [Connection] Not connected[AsyncModbusSerialClient /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0:0]
2025-03-20 20:13:47.104 DEBUG (MainThread) [homeassistant.components.modbus.modbus] Pymodbus: modbus_1: Error: device: 1 address: 8 -> Modbus Error: [Connection] Not connected[AsyncModbusSerialClient /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0:0]
2025-03-20 20:13:47.152 DEBUG (MainThread) [homeassistant.components.modbus.modbus] Pymodbus: modbus_1: Error: device: 1 address: 10 -> Modbus Error: [Connection] Not connected[AsyncModbusSerialClient /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0:0]

jakob.tewes · March 20, 2025, 7:19pm

This is the “less debug” messages:

2025-03-20 20:19:14.118 ERROR (MainThread) [homeassistant] Error doing job: Exception in callback SerialTransport.intern_read_ready() (None)
Traceback (most recent call last):
  File "/usr/local/lib/python3.13/asyncio/events.py", line 89, in _run
    self._context.run(self._callback, *self._args)
    ~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/pymodbus/transport/serialtransport.py", line 134, in intern_read_ready
    self.intern_protocol.data_received(data)  # type: ignore[attr-defined]
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^
  File "/usr/local/lib/python3.13/site-packages/pymodbus/transport/transport.py", line 304, in data_received
    self.datagram_received(data, None)
    ~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/pymodbus/transport/transport.py", line 338, in datagram_received
    cut = self.callback_data(self.recv_buffer, addr=addr)
  File "/usr/local/lib/python3.13/site-packages/pymodbus/transaction/transaction.py", line 183, in callback_data
    self.response_future.set_result(pdu)
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^
asyncio.exceptions.InvalidStateError: invalid state

wintermute11 · April 7, 2025, 5:28pm

Exactly same situation here !
SDM630 modbus, HA freezes after 1-2 days.
Did you solve it ?

Edit: i have rtuovertcp. And we are not alone:

github.com/home-assistant/core

Modbus value spike issues since last update (2025.2.x) : values mixed from wrong sensor

opened 02:50PM - 09 Feb 25 UTC

neuhausj

integration: modbus

### The problem Hello, I updated my HA last week (from 2025.1.x to 2025.2.1) an…d since then I have issue with my Modbus sensor which record erroneous spikes. It matches the update of the pyModbus library as well. It used to work flawlessly but now I have regular issues. What I noticed is that I am getting erroneous value, for example room temperature jumping multiple degrees or flowsensor jumping from 0 to a value for just 1 frame. It looks like this value is the answer from another request. **This only happens when the Modbus telegram is sent again after 3sec (probably due to timeout).** Is there a way to avoid sending this new telegram after timeout ? (I am polling values each 10s anyway) Before / after HA update: <img width="948" alt="Image" src="https://github.com/user-attachments/assets/f2958fc5-189e-4ebd-a34d-0a34fab6bf04" /> Errors over 2h: <img width="948" alt="Image" src="https://github.com/user-attachments/assets/82f9eb8a-97de-4d35-b475-5ddbebb30008" /> Now the interesting part: this spikes are only generated when the request is repeated. Here are 2 examples: * 30°C could well be the temperature from the "Retour condensateur" <img width="1913" alt="Image" src="https://github.com/user-attachments/assets/41dd3a32-0936-42f3-a8a2-0e381f7316d7" /> * 32°C could well be the temperature from the "Ballon" <img width="1911" alt="Image" src="https://github.com/user-attachments/assets/49f7bb52-d0a5-473e-9319-d7de6384a9b4" /> A few other examples: <img width="747" alt="Image" src="https://github.com/user-attachments/assets/bd6b7983-65e9-43f9-bbf3-985f9d304a9c" /> <img width="748" alt="Image" src="https://github.com/user-attachments/assets/b7224127-415a-4786-9551-d530951f565f" /> <img width="748" alt="Image" src="https://github.com/user-attachments/assets/7ddb0347-0557-47a4-ae31-fcbecf19c479" /> ### What version of Home Assistant Core has the issue? core-2025.2.1 ### What was the last working version of Home Assistant Core? core-2025.1.x ### What type of installation are you running? Home Assistant OS ### Integration causing the issue Modbus ### Link to integration documentation on our website https://www.home-assistant.io/integrations/modbus/ ### Diagnostics information It looks like as soon as a Modbus frame is repeated (due to timeout), the next Modbus telegram is taken as answer. This leads to value mixing between MB sensors. The sequence of Modbus frame seems to be off. A first approach would be to disable the Modbus timeout and wait for the next polling. ### Example YAML snippet ```yaml """yaml # Read info from PAC modbus: - name: PAC type: tcp host: 192.168.1.23 port: 502 sensors: - name: Température extérieure slave: 1 address: 1003 input_type: holding unit_of_measurement: °C state_class: measurement scale: 0.1 offset: 0 precision: 1 scan_interval: 10 - name: Température départ condensateur slave: 1 address: 1004 input_type: holding unit_of_measurement: °C state_class: measurement scale: 0.1 offset: 0 precision: 1 scan_interval: 10 - name: Température retour condensateur slave: 1 address: 1005 input_type: holding unit_of_measurement: °C state_class: measurement scale: 0.1 offset: 0 precision: 1 scan_interval: 10 - name: Débit capteur slave: 1 address: 1020 input_type: holding unit_of_measurement: l/min state_class: measurement scale: 0.1 offset: 0 precision: 1 scan_interval: 10 - name: Température ballon slave: 1 address: 1100 input_type: holding unit_of_measurement: °C state_class: measurement scale: 0.1 offset: 0 precision: 1 scan_interval: 10 - name: PAC Temp Z1 appartement slave: 1 address: 1111 input_type: holding unit_of_measurement: °C state_class: measurement scale: 0.1 offset: 0 precision: 1 scan_interval: 10 - name: PAC Temp Z2 Culte RdC slave: 1 address: 1121 input_type: holding unit_of_measurement: °C state_class: measurement scale: 0.1 offset: 0 precision: 1 scan_interval: 10 - name: PAC Temp Z3 Culte sous-sol 1er slave: 1 address: 1131 input_type: holding unit_of_measurement: °C state_class: measurement scale: 0.1 offset: 0 precision: 1 scan_interval: 10 - name: PAC Temp Z4 salle fête slave: 1 address: 1141 input_type: holding unit_of_measurement: °C state_class: measurement scale: 0.1 offset: 0 precision: 1 scan_interval: 10 - name: PAC état slave: 1 address: 102 input_type: holding state_class: measurement scale: 1 offset: 0 precision: 0 scan_interval: 10 switches: - name: Appartement slave: 1 address: 6011 command_on: 1 command_off: 4 write_type: holding verify: - name: Salle culte slave: 1 address: 6012 command_on: 1 command_off: 4 write_type: holding verify: - name: Sous-sol slave: 1 address: 6013 command_on: 1 command_off: 4 write_type: holding verify: - name: Salle fête slave: 1 address: 6014 command_on: 1 command_off: 4 write_type: holding verify:""" ``` ### Anything in the logs that might be useful for us? ```txt Log covering both event (14:48:15 and 14:50:27): 2025-02-09 14:48:10.910 DEBUG (MainThread) [pymodbus.logging] Frame advanced, resetting header!! 2025-02-09 14:48:10.910 DEBUG (MainThread) [pymodbus.logging] send: 0x1d 0xf 0x0 0x0 0x0 0x6 0x1 0x3 0x4 0x4c 0x0 0x1 2025-02-09 14:48:13.911 DEBUG (MainThread) [pymodbus.logging] send: 0x1d 0xf 0x0 0x0 0x0 0x6 0x1 0x3 0x4 0x4c 0x0 0x1 2025-02-09 14:48:14.377 DEBUG (MainThread) [pymodbus.logging] recv: 0x1d 0xf 0x0 0x0 0x0 0x5 0x1 0x3 0x2 0x1 0x40 old_data: addr=None 2025-02-09 14:48:14.378 DEBUG (MainThread) [pymodbus.logging] Processing: 0x1d 0xf 0x0 0x0 0x0 0x5 0x1 0x3 0x2 0x1 0x40 2025-02-09 14:48:14.378 DEBUG (MainThread) [pymodbus.logging] decoded PDU function_code(3 sub -1) -> ReadHoldingRegistersResponse(dev_id=0, transaction_id=0, address=0, count=0, bits=[], registers=[320], status=1) 2025-02-09 14:50:22.693 DEBUG (MainThread) [pymodbus.logging] Frame advanced, resetting header!! 2025-02-09 14:50:22.693 DEBUG (MainThread) [pymodbus.logging] send: 0x1d 0xb0 0x0 0x0 0x0 0x6 0x1 0x3 0x3 0xed 0x0 0x1 2025-02-09 14:50:25.695 DEBUG (MainThread) [pymodbus.logging] send: 0x1d 0xb0 0x0 0x0 0x0 0x6 0x1 0x3 0x3 0xed 0x0 0x1 2025-02-09 14:50:26.708 DEBUG (MainThread) [pymodbus.logging] recv: 0x1d 0xb0 0x0 0x0 0x0 0x5 0x1 0x3 0x2 0x1 0x2c old_data: addr=None 2025-02-09 14:50:26.708 DEBUG (MainThread) [pymodbus.logging] Processing: 0x1d 0xb0 0x0 0x0 0x0 0x5 0x1 0x3 0x2 0x1 0x2c 2025-02-09 14:50:26.708 DEBUG (MainThread) [pymodbus.logging] decoded PDU function_code(3 sub -1) -> ReadHoldingRegistersResponse(dev_id=0, transaction_id=0, address=0, count=0, bits=[], registers=[300], status=1) ``` ### Additional information Full log attached covering both events: [home-assistant_modbus_2025-02-09T14-25-35.079Z.log](https://github.com/user-attachments/files/18724847/home-assistant_modbus_2025-02-09T14-25-35.079Z.log)

jakob.tewes · April 7, 2025, 7:00pm

No real “fix”. Suspecting concurring devices with same ModBus Device ID. Disconnected the unwanted one and didn´t come back.

Nevertheless I was shocked how bad the ModBus error handling is, that no one replied ever and that this could break whole HA. A shame…