-
-
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
All devices are lost after Z2M update #23235
Comments
The same here What did you expect to happen? How to reproduce it (minimal and precise) Zigbee2MQTT version Adapter firmware version Adapter Setup Debug log |
Same. Rollback done. |
Have same issue rolled back also |
Same here ! Full rollback running. What is strange is that the duplication of entities occurs after a full restart of HA and not just after the update to 1.39.0. This is a severe issue and 1.39.0 deployment should be aborted if you want my opinion. Edit: the full restor have restored the entities. |
I confirm the trigger is the restart of HA on my side too. |
Same issue here, double sensors and entities. They even remain double after restoring..... also all devices are offline. Can only control when directly go to zigbeetomqtt |
Same here, had to roll back to 1.38.0. Will not update again until this is solved. |
1 similar comment
Same here, had to roll back to 1.38.0. Will not update again until this is solved. |
Had same issue updating today to 1.39.0. Rolling back to 1.38.0 |
I have same issue; How do you rollback zigbee2mqtt? |
@kefrens in home assistant settings> system> backups |
Hello have same issue. rollback 1.38 ok |
In my case rollback to 1.38 did not restore devices to Z2M.
|
@paavokurkela , did you restart HA? |
I have to do a full restore and not only a rollback on Z2M 1.38 |
Same here, full restore needed |
@raphmur Yes I did. I also tried full restore from backup. That restored entities on HA but Z2M devices did not restore. |
Could you:
See this on how to enable debug logging. |
@Koenkk thank you for looking on this. As I restored my system I currently have 1.38 installed. Please note that this very same problem existed already earlier. I believe it was from 1.37 to 1.38 and it was first time this problem happened to me. Please find infos requested below: Couple devices paired to 1.38![]() Devices gone 1.39![]() HA version:![]() configuration.yaml (with debugs enabled)
Add-on config screen (credentials hidden)![]() log (1.38 with two Ikea lights paired)
log (startup during upgrade process to 1.39 and all devices lost)
|
hi guys I had same issue 😞 too but I manage myself by taking time to remove the old entities (without _2) then renaming all the entities by removing the "_2" (+/- 10 devices with 4 entity each) 💪 But I struggle with how to remove the zigbee2mqtt_bridge entities, if someone how it is possible? 🆘 |
Hello @Koenkk , Is there any chance to have a fix in the 1.39.1 release (#23221) ? |
@paavokurkela in the 1.38.0 log I see
See this on how to enable debug logging. |
@Koenkk thank you for your request. While gathering logs you requested I found out that devices are gone every time I just simply restart Z2M, no even update needed. Please see log I was able to catch for you below: Something I want to point out is that while I tried to store log.txt under /homeassistant/zigbee2mqtt/log/%TIMESTAMP% nothing was stored there. Also as log below says: Hope this leads us to right direction.
|
I noticed that in Z2M MQTT parameters, the base topic which was "zigbee2mqtt" before upgrade was renamed to "zigbee2mqttHA" after upgrade. I reproduced two times the problem (thanks to ha backups) and give up try to upgrade ! Later, I also tried a third upgrade positioning Related to #23294 Hope it will help |
@lecourtb probably you have set |
I have the same issue, I cant update to 1.39 without break my devices and automations because devices duplicate with suffix '_2' |
That was effectively the case ( |
Same issue here. |
Has anyone with this issue upgraded to |
Tested and issue is still persisting |
You should take a look at #23294 . Enjoy! |
Yes it is ! Thanks |
Rename base topic to zigbee2mqtt works for me. Thank you. |
I got my system back to working state. I deleted z2m completely as well all files and folders. This or that my system works again. |
Renaming base_topic to zigbee2mqtt and installing yhe 1.19.1 resolves the issue for me. |
Removing the |
For me doesn't work as well. In the config of Zigbee2MQTT I have as well: But it still creates all entities with a '_2' |
Responding to myself.
|
Thanks a lot @kefrens This solved my issue finally. They need to match the addon base_topic and mqtt site. |
Anyone noticing that triggers somehow are named differently after the latest update? I get a lot of uknown triggers suddenly after updating. |
What happened?
After add-on update on Home Assistant, all the devices are lost from Z2M and Homa Assistant (no devices listed under MQTT instance)
Restoring a backup restores devices on Home Assistant but not on Z2M. Same issue happened to me also with earlier update, unfortunately I don't have any details on that. Log is literally empty.
What did you expect to happen?
No response
How to reproduce it (minimal and precise)
Update Z2M
Zigbee2MQTT version
1.38.0-1
Adapter firmware version
20230507
Adapter
Slaesh
Setup
Add-on under HA on Intel Nuc
Debug log
No response
The text was updated successfully, but these errors were encountered: