-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Renaming devices in Z2m breaks Z2m > mqtt > Home Assistant topic trigger #4452
Comments
@ciotlosm did you set the "Update Home Assistant entity ID" in the UI to true? Because if so this is expected behaviour. |
@Koenkk nope, I did not, I just renamed the Friendly Name. Example:
|
Fixed in latest dev (together with some other fixes). Can you confirm? |
Doesn't seem to be fixed, mqtt topic still changes to friendly name instead of using id.
|
That is expected, but Zigbee2MQTT will now update the discovery information in Home Assistant. |
Tested button actions (after rename) and it does seem to work. For me personally I would have better liked mqtt topics to be using the ID, as the ID is used in Home Assistant automations and Friendly Name can have white space or special characters that are made for display, not much for machine interpretation. But this is a personal view. |
Was this ever fixed? I am having an issue of devices showing as hidden in HA after they have been renamed. |
What happened
Steps
Problem
Seems for some reason the device queues in Home Assistant for the entities are expecting the ID to be used, but the queues coming from Z2m are no using friendly names.
What did you expect to happen
I was hoping that the change won't break my integration.
How to reproduce it (minimal and precise)
Check: Configuration → Devices → .. Search for it .. → MQTT Info and see topics use IDs
Temporary solution: Use Terminal add-on to go into
/share/zigbee2mqtt/
and emptydevices.yaml
and then restart the add-onDebug info
Zigbee2MQTT version: 1.14.4-dev (bbc7c7d)
Adapter hardware: CC26X2R1 (zzh!)
Adapter firmware version:
The text was updated successfully, but these errors were encountered: