-
-
Notifications
You must be signed in to change notification settings - Fork 202
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
9.27.0 Docker won't start on Aeotec Z-Stick Gen5+ #3997
Comments
I get the same error on 9.27:
But it goes away and things work as expected when I go back to 9.26 |
Same issue on USB STICK ZOOZ ZST10 S 700: |
Same here, and I needed to roll-back to restore working ZWave at home. This is what I have as the error message in the UI:
|
Same error here... reverted to 9.26.0 and my system is back up |
Also pulled sha256:6d36abbe92f950a6324cdfcc88e6a4fae7d08b91eca90454b5887c1885a399c2 since it was newer, did not work. Rolled back to 9.26. |
Also rolled back to 9.26. |
same, this update killed my system and have to rebuild. using a nortek zwave stick. |
Same for me. Same situation . Docker under Unraid. Rolled back to 9.26.0 up and running again |
same. looks like it doesn't like |
Same here. Reverting to 9.26.0 and everything is working back as before. SiliconLab / Usb Controller / 700/800 Series : https://devices.zwave-js.io/?jumpTo=0x0000:0x0004:0x0004:0.0 |
I think this should get fixed by #4000 - at least I could access my stick in Docker on that branch. |
9.27.1 should fix this |
Can confirm this fixed the problem on my end. Thank you. |
Works for me, thanks for the quick turnaround |
So fast, Thanks for everything 🙇 |
9.27.1 worked for me! Thanks! |
Checklist
Deploy method
Docker
Z-Wave JS UI version
9.27.0.f3c4ac5
ZwaveJS version
14.3.1
Describe the bug
After upgrading to the 9.27.0 docker image, it is failing to start. Rebooted the box, unplugged/replugged the dongle, nothing works
To Reproduce
Upgrade from 9.26.0 -> 9.27.0
Expected behavior
it starts up.
Additional context
Downgrading to 9.26.0 and it starts right up.
Log output isn't super helpful, even on "Silly"
The text was updated successfully, but these errors were encountered: