HA 2025.1.4 broke my Modbus entities

Configuration
1

HA 2024.12.x worked flawless, but since I upgraded to 2025.1.4 all my modbus entities are unavailable.

This is my configuration:

  - name: Smartlogger3000A
    type: tcp
    host: 192.168.X.YY
    port: 502
    sensors:
      - name: total_generated_energy
        address: 40560
        data_type: uint32
        scale: 0.1
        precision: 2
        unit_of_measurement: kWh
        device_class: energy
        state_class: total_increasing
      - name: daily_generated_energy
        address: 40562
        data_type: uint32
        scale: 0.1
        precision: 1
        unit_of_measurement: kWh
        device_class: energy
        state_class: total_increasing
      - name: active_power
        address: 40525
        data_type: int32
        scale: 0.001
        precision: 2
        unit_of_measurement: kW
        device_class: power
        state_class: measurement
      - name: phase_a_current
        address: 40572
        data_type: int16
        unit_of_measurement: A
        device_class: current
        state_class: measurement
      - name: phase_b_current
        address: 40573
        data_type: int16
        unit_of_measurement: A
        device_class: current
        state_class: measurement
      - name: phase_c_current
        address: 40574
        data_type: int16
        unit_of_measurement: A
        device_class: current
        state_class: measurement

This is the error:

Pymodbus: Smartlogger3000A: Error: device: 1 address: 40560 → Exception Response(131, 3, IllegalValue)

This error unfortunatly tells me nothing…

Does anyone have a suggestion how to fix this please? :frowning:

2

Hi.

I encountered this problem earlier.
I thought the update also broke the work.
I restored from a backup copy and modbus worked.
I decided to update again.
After the update it started working.
Everything works now 2025.1.4

3

Interesting!

I got it working by adding slave: 0 to my devices. Apparently 0 was the default value before 2025 but 2025.1 changes this to 1 without mentioning it in the release notes…

4

Thanks for the solution.

Classic HA. If you don’t want your things to break run it in venv (in docker they push you supervisor upgrades in the background without the ability to opt out, which eventually just bricks your install), and never update it unless you need to for something new to work.

Went from having these ballaches every other month to once every 2-3 years when I decide to update it.