-
-
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
Update to 1.42.0, Now zigbee-herdsman cannot find Sonoff dongle. #25007
Comments
same issue here, zigbee2MQTT doesn't restart with the same error
|
I got it to work after moving the configuration folder under the new addon_configs folder. /homeasssistant/zigbee2mqtt => /root/addon_configs/[randomstring]_zigbee2mqtt/zigbee2mqtt |
ok got it, have to move the zigbee configuration file in addon_config to make it work properly |
Note I read the migration step, but since the example is for supervisor and there were no addon_configs directory in the homeassistant directory, I didn't check with the terminal in the rootdir and incorrectly assumed it was only for supervisor installation. |
@will0913 have you also lost almost all the device associations? |
@jocel1 , No, I still have all my devices. p.s. I have the homeassistant OS vm |
Thanks! I think I understand why, it's because I disabled as well with the migration the legacy api |
Moving the folder as described didn't change anything, even after a full home assistant restart. Found the destination folder and ran: EDIT: That moved it into zigbee2mqtt/zigbee2mqtt, so I corrected that and it did start sucessfully, but everything is showing "Entity not found". |
contents of my zigbee2mqtt folder: Could it result from missing database.db? |
it is not work, still the same error: |
@espe20 , Are you able to locate your zigbee2mqtt folder?
|
Yes I am able and I found it also move it to location and still without luck. Is HA restart needed? |
I made a restore backup and lost all config :( I see addon create a config when expected by release info |
Same issue here with "Home Assistant Operating System", however, with a "slae.sh_cc2652rb_stick" Starting Zigbee2MQTT without watchdog. |
I had the same issue after updating. Moving a copy (full overwrite) from the old directory to the new one worked. Be sure to stop zigbee2mqtt before doing the process.
After that you can delete/cleanup the old directory. I'll do it a few days later. |
also on my HAOS after clean install of new addon with ver 1.42 can't start it again with errors in previous comments. I downgraded to 1.41 and fetch backup of z2m from HA backup file and then it runns again with old config but can't run ui because of EDIT: |
I had the same problem, just downgraded to 1.40.2-1 |
Strange thing. I don't have zigbee2mqtt in config folder but in share folder... I still did not update to latest z2m version because of this mess but I wonder what would happen in my case... |
When I reverted to 1.40.2 it deleted the new folder that I copied over. I restored from a backup, but apparently the backup doesn't backup the database because all of my 40+ devices are still gone. |
I did the update yesterday and lost all devices as well. |
Please see zigbee2mqtt/hassio-zigbee2mqtt#664 (comment) |
I had troubles starting plug-in because of data_path setting of ver 1.42.0-1 after new installation. Once upgraded to 1.42.0-2 data_path issue was solved but plugin was still crushing during start becasue of firmware and deprecated ezsp drivers. I have upgraded firmware of my Sonoff dongle E to the latest version and finally started the plugin using ember drivers. Added several devises. They were gone ! after restart. default data_path option still points to config/zigbee2mqtt . What is finally right place and correct settings ? |
What happened?
Everything was working perfectly. When the update to 1.42.0 completed, starting Zigbee2MQTT addon now fails, results in:
The device still shows up as expected:
Restarting home assistant and restarting the host machine still result in the same error message on startup attempt.
What did you expect to happen?
I expected that it would continue functioning normally as it did prior to the update.
How to reproduce it (minimal and precise)
Not sure, but my configuration.yaml:
Zigbee2MQTT version
1.24.0
Adapter firmware version
cannot access
Adapter
ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus
Setup
Home Assistant as a VM on a Proxmox box on X86-64 Thinkpad
Debug log
The text was updated successfully, but these errors were encountered: