Problems with ModBus migration from ioBroker

Configuration
1

Hello, I would like to query my Froling P5 pellet heater from Home Assistant via ModBus TCP. What works great in ioBroker unfortunately doesn’t work in Home Assistant. Do I have to pay attention to anything about the addresses?
image

image
image1755×315 23 KB

In iobroker - it works.

And now Home Assistant:

modbus:
  - name: Heizung
    type: tcp
    host: 192.168.178.150
    port: 502
    sensors:
      - name: Brennstofflager
        slave: 1
        address: 31901
        input_type: input
      - name: Brennstofflager_test
        slave: 1
        address: 2001
        input_type: input

The two IDs are the one that works in ioBroker and the 2001 is according to Froling

2024-11-19 15:46:51.832 DEBUG (MainThread) [homeassistant.components.modbus.modbus] Pymodbus: Heizung: Error: device: 1 address: 31901 -> Modbus Error: [Connection] Not connected[AsyncModbusTcpClient 192.168.178.150:502]
2024-11-19 15:46:51.832 DEBUG (MainThread) [homeassistant.components.modbus.modbus] Pymodbus: Heizung: Error: device: 1 address: 2001 -> Modbus Error: [Connection] Not connected[AsyncModbusTcpClient 192.168.178.150:502]
2

That looks like it should be 32001?

However it is this bit that is not connecting:

3

hey, i fixed it with my loxone device. In Loxone there is no problem to read the modbus