Modbus sensors - Unique ID and Device support

surfer2100 · October 17, 2024, 7:40am

Hi everyone,
I just switched to Modbus for one of my integrations and ran across the same issue.
I’ve opened an issue for this, as I’ve not seen one being created so far:

github.com/home-assistant/core

Create Modbus Devices for each listed connection point in Modbus configuration

opened 07:38AM - 17 Oct 24 UTC

rschoell

integration: modbus

### The problem I've recently switched my Keba integration from the internal in…tegration (based on unreliable UDP protocol) to Modbus TCP. So far this is far more stable and controllable, as TCP is stateful protocol. One thing that bothers me (and others: https://community.home-assistant.io/t/modbus-sensors-unique-id-and-device-support/373428) is, that we create a "device" in yaml, under which we place binary_sensors, sensors, switches, ... If you then look in Settings - Devices, it only lists the sensors as entities, but does not list the "main" device. It would be cumbersome to have some correction of this. My config looks like this: ``` - name: KEBAP30 delay: 5 timeout: 5 type: tcp host: 192.168.1.102 # your callbox IP address goes here port: 502 sensors: # Lesbare Sensoren - name: KebaP30_charging_state address: 1000 scan_interval: 30 data_type: uint32 unique_id: KebaP30_charging_state - name: KebaP30_cable_state address: 1004 scan_interval: 30 data_type: uint32 unique_id: KebaP30_cable_state ``` I would expect to see - Device = KebaP30 - Sensor: sensor.KebaP30_charging_state - Sensor: sensor.KebaP30_cable_state I cannot fix this myself, but hope that you'll help the community and me. Many thanks. ### What version of Home Assistant Core has the issue? core-2024.10.1 ### What was the last working version of Home Assistant Core? _No response_ ### 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 _No response_ ### Example YAML snippet ```yaml - name: KEBAP30 delay: 5 timeout: 5 type: tcp host: 192.168.1.102 # your callbox IP address goes here port: 502 sensors: # Lesbare Sensoren - name: KebaP30_charging_state address: 1000 scan_interval: 30 data_type: uint32 unique_id: KebaP30_charging_state - name: KebaP30_cable_state address: 1004 scan_interval: 30 data_type: uint32 unique_id: KebaP30_cable_state ``` ### Anything in the logs that might be useful for us? _No response_ ### Additional information _No response_

Hope this get’s some drive on fixing this. In MQTT this is also possible with the addition of some lines per sensor, but in Modbus this should be far easier, based on the “main” device being created for the connection info’s.