I control my Systemair ventilation system over modbus. It gives me more than 100 entities that I am not able to connect to a Device. My wish for Christmas is Modbus device(s). in Home Assistant. 
Yep, would be great to have similar capability as device map in MQTT, right?
That would be amazing!
fully agree I have the same issue but for BACNET, in the end I have used the climate-template via HACS to get it working… but I needed to add lots of ugly code due to the way HA handles a few things
That’s something very needed.
I’m running 250 entities via modbus integration and they belong to 9 electricity meters, having entities grouped by which meter they belong to will help a lot
1 Like
Any news?? It’s incredible that such an important protocol to connect devices is so limited…
2 Likes
I also ran in to the very same problem: “device:” is not allowed in Modbus-configuration.
I’d love to have my four base devices combined and NOT have horrible long modbus.yaml nor the clumsy dashboard configuration by gathering entities one by one, while the values are, after all, gathered from the same device.
You can point the area that sensor belongs to (not marked in the example), but not the device itself.
To make it clear, this marked out part is something what I need:
- name: "BP SE Sensor battery alarm"
unique_id: bpse_batt_alarm
slave: 30
address: 0
input_type: discrete_input
device_class: battery
# device:
# identifiers: ["bpse_30"]
# manufacturer: "Carel"
# model: "BP SE Sensor"
# name: "BP SE Sensor 30"