You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The following code limits devices to one entity on an endpoint depending on if the Zigbee device type and HA domain match.
This has caused issues in the past (with config entities, but will also apply to normal entities). It's a remnant of when clusters were limited to one entity. The implementation also isn't ideal in the first place (comparing Zigbee devie type with HA domain).
A migration for the unique IDs will also need to happen in Home Assistant Core if we change this.
Alternatively, we could try and leave the unique ID of the matching entity the same and just add the others with a the cluster id suffix, like done for unmatched entities.
The text was updated successfully, but these errors were encountered:
Issue
The following code limits devices to one entity on an endpoint depending on if the Zigbee device type and HA domain match.
This has caused issues in the past (with config entities, but will also apply to normal entities). It's a remnant of when clusters were limited to one entity. The implementation also isn't ideal in the first place (comparing Zigbee devie type with HA domain).
zha/zha/application/discovery.py
Lines 521 to 530 in 77e4094
Migration
A migration for the unique IDs will also need to happen in Home Assistant Core if we change this.
Alternatively, we could try and leave the unique ID of the matching entity the same and just add the others with a the cluster id suffix, like done for unmatched entities.
The text was updated successfully, but these errors were encountered: