-
Notifications
You must be signed in to change notification settings - Fork 99
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proposal: Allow changing names through UI for MQTT Discovery #30
Comments
I'm also involved in zigbee2mqtt and this is something that has also bother me. Using HA MQTT discovery mechanism, zigbee2mqtt can already expose any supported paired device in HA upon successful pairing. This is great for users. Unfortunately the only manual step remaining is device naming that requires editing in zigbee2mqtt device database file in order to do the name mapping in zigbee2mqtt and save HA the trouble. I've imagined possible integrations:
|
I think that this can easily be solved by allowing MQTT devices to specify a unique ID. That way they will end up in the Entity Registry and you can use the normal frontend flow for renaming entities. The zigbee2mqtt project will be able to use Zigbee device serial numbers for unique IDs. (this won't solve the services etc that @dgomes mentioned, but I think that is out of scope of the current discussion (and its own platform is probably best solution)) |
Thanks @dgomes, @OttoWinter and @balloob. |
Proposal
Allow for a method to change names of entities through the UI just like with
unique_id
for MQTT Discovery componentUse Case
There is development for a drop in replacement of
xiaomi_aqara
usingCC2531
stick to save some round trips and avoid the proprietary gateway. Currently there is https://github.com/Koenkk/zigbee2mqtt for the actual functionality using Home Assistant discovery setup, coupled with https://github.com/danielwelch/hassio-zigbee2mqtt hassio addon.Current state
Configuration of devices names can be done either:
As
xiaomi_aqara
already has Discovery through the gateway andunique_id
is allowed, would be nice to have the same forzigbee2mqtt
.The text was updated successfully, but these errors were encountered: