Modbus entities unavailable at first configuration

Configuration
1

I just set up modbus to my heatpump, and it seems like the integration itself is up. And I have created some sensor entities. But they are all unavailable. In the lo it looks like the connection is done ok, and I see no failures. It suggests that there is just nothing to read. Or am a reading the debug log correctly?

Configuration:

name: ctc
type: tcp
host: 192.168.1.248
port: 502
delay: 2

sensors:
  - name: "ctc_hot_water_temperature"
    unit_of_measurement: "°C"
    address: 62003
    scan_interval: 60
    #slave: 1
    #data_type: integer
    scale: 0.1
    input_type: holding

Debug log:

2024-11-13 22:55:41.925 DEBUG (MainThread) [pymodbus.logging] Connecting to 192.168.1.248:502.
2024-11-13 22:55:41.925 DEBUG (MainThread) [pymodbus.logging] Connecting comm
2024-11-13 22:55:41.929 DEBUG (MainThread) [pymodbus.logging] Connected to comm
2024-11-13 22:55:41.929 DEBUG (MainThread) [pymodbus.logging] Resetting frame - Current Frame in buffer - 
2024-11-13 22:55:41.933 DEBUG (MainThread) [pymodbus.logging] -> transport: received eof
2024-11-13 22:55:41.934 DEBUG (MainThread) [pymodbus.logging] Connection lost comm due to None
2024-11-13 22:55:41.934 DEBUG (MainThread) [pymodbus.logging] callback_disconnected called: None
2024-11-13 22:55:41.934 DEBUG (MainThread) [pymodbus.logging] Wait comm 100.0 ms before reconnecting.
2

The slave address is required, and the slave address station number and the device setting address station number need to be the same in order to communicate

1 Like
3

Thanks! I was able to find the issue with the help of another post.

But now I have this other issue, the modbus entities sometimes for no apparent reason go unavailable, often when I reloaded other config changes. And then Im not really sure how to get them back again, but they tend to jump back overnight.

Anyone know why this is happening? Screenshot of the history explorer with some of the entities

image
image2007×645 96 KB