-
-
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
After renaming a device it starts to report as undefined. #4626
Comments
I was looking for the opposite a few days ago. Renaming the device changes the name of the entities (this is my expected behavior). There should be a dialog like in home assistant renaming system if we want to rename the entities too. |
Isn't that exactly what is expected? For some sensors it works (home assistant recognizes the new name) but for some others it just doesn't work because the explained behavior |
The new api allows to specify wether to also update Home Assistant entity IDs, see https://github.com/Koenkk/zigbee2mqtt.io/blob/new_api/docs/information/mqtt_topics_and_message_structure.md#device |
Thanks @Koenkk, for now I repaired the decides and they picked the new name (in hassio they also have the new name, but they use the Mac as id). I'll check the new api if I get a chance |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days |
What happened
After renaming certain devices they stopped working.
They are all aqara devices. I renamed them using hassio integration. After renaming if I check the logs I can see errors about undefined devices popping everytime I activate one of the renamed devices.
Xiaomi button and a ikea bulb renames without problem, but the rest of aqara devices suffer from this problem.
What did you expect to happen
To rename them and still work
How to reproduce it (minimal and precise)
Debug info
Will post later this info
Zigbee2MQTT version:
Adapter hardware: CC2531, CC2530, CC26X2R1, CC1352P-2, Conbee II
Adapter firmware version:
The text was updated successfully, but these errors were encountered: