Z-Wave JS 0.1.59 Update Brakes
kjake opened this issue · comments
The problem
I had Z-Wave JS 0.1.58 installed and allowed the update to 0.1.59. After update, Z-Wave JS no longer appears to work and there are errors.
I have rebooted the hardware, and I have confirmed that the Z-Wave JS add-on is running.
I was able to revert to the back-up taken before the 0.1.59 upgrade and it is running again as 0.1.58.
I am using a Zooz ZST10-700 on a Rpi4 and have 4 z-wave Sensative door/window strips being monitored.
What version of Home Assistant Core has the issue?
core-2022.5.5
What was the last working version of Home Assistant Core?
core-2022.5.5
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Z-Wave JS
Link to integration documentation on our website
https://www.home-assistant.io/integrations/zwave_js
Diagnostics information
config_entry-zwave_js-05f59a6cc3b271c5424377e9dce04593.json.txt
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Could not fetch stats for core_zwave_js: Container addon_core_zwave_js is not running
Config entry 'Z-Wave JS' for zwave_js integration not ready yet: Cannot connect to host core-zwave-js:3000 ssl:default [Connect call failed ('172.30.33.3', 3000)]; Retrying in background
Failed to connect: Cannot connect to host core-zwave-js:3000 ssl:default [Connect call failed ('172.30.33.3', 3000)]Additional information
No response
Hey there @home-assistant/z-wave, mind taking a look at this issue as it has been labeled with an integration (zwave_js) you are listed as a code owner for? Thanks!
(message by CodeOwnersMention)
zwave_js documentation
zwave_js source
(message by IssueLinks)
I had the exact same issue as the original poster. I just started using Home Assistant (HA OS) and as soon as I updated to 1.59 Zwave completely broke. I reverted to the 1.58 backup and things are working again.
Error from log:
`Logger: homeassistant.components.zwave_js
Source: components/zwave_js/init.py:518
Integration: Z-Wave JS (documentation, issues)
First occurred: 7:50:04 PM (1 occurrences)
Last logged: 7:50:04 PM
Failed to connect: Cannot connect to host core-zwave-js:3000 ssl:default [Connect call failed ('172.30.33.0', 3000)]`
I have the exact same issue, however I'm using the UZB-stick. I have reverted back to previous version, but it's still broken with the same error. Have tried rebooting and powercycling to no avail
Edit:
Restored to the 57-version and my Zwave network is back up again, thank goodness.
Same issue. Can anyone point me to a link /documentation to revert back to 1.58?
I am having the same issue on core 2022.5.5, HA OS 8.1, and supervisor 2022.05.3 with a generic Z-Wave to USB stick. Reverted to 1.58 and everything works.
Same here, reverted to 0.1.58 and Im back up and running.
@tommyk2 Go into Settings > Addons, Backups & Supervisor > Backups and mine had a partial backup prior to the Z-wave JS upgrade.
Same issue. Reverted back and working again.
Same issue. Reverted to 0.1.58 and restarted and my network is back up.
I found after updating and everything stopped working an error in my log about these two files.
/etc/cont-init.d/config.sh
/etc/cont-init.d/structure.sh
Took me a few attempts to get logged into the docker instance and run chmod - this seems to have fixed if for me...
docker exec -it addon_core_zwave_js /bin/bash
bash-5.1# chmod +x /etc/cont-init.d/config.sh
bash-5.1# chmod +x /etc/cont-init.d/structure.sh
Can somebody please tell zwave JS to not break my stuff...?
Also a real changelog wouldn't hurt.
s6-supervise zwave_js (child): fatal: unable to exec run: Permission denied
FFS.... reverting to 0.1.58
How do you revert to 1.58? Sorry, new to HA, basic Rpi4 install
How do you revert to 1.58? Sorry, new to HA, basic Rpi4 install
@mikem30303 Please read the thread as someone has already answered this question.
Go into Settings > Addons, Backups & Supervisor > Backups and mine had a partial backup prior to the Z-wave JS upgrade
I'm having the same issue (AEOTEC Z-Wave USB Stick (Gen5+) I Have rolled back to 1.58
Thank you thank you thank you!!! @cydia2020
works well after upgrading to 0.1.60
I tried upgrading to 0.1.60, but still get the originally reported error (and issues). "Failed to connect: Cannot connect to host core-zwave-js:3000 ssl:default [Connect call failed ('172.30.33.3', 3000)]" If that error is showing the IP... it's just flat out wrong.
I tried upgrading to 0.1.60, but still get the originally reported error (and issues). "Failed to connect: Cannot connect to host core-zwave-js:3000 ssl:default [Connect call failed ('172.30.33.3', 3000)]" If that error is showing the IP... it's just flat out wrong.
That's the IP address of the docker container that Z-Wave JS is running on, try reloading the integration or restarting the machine.
That is NOT the IP address of the docker container... I'm not running in a docker container... and the IP address is outside of my IP address range (172.16.x.x). I'm running on Home Assistant OS / Supervisor (so no docker). And I find it very interesting the original poster had the SAME IP address in their error.
That is NOT the IP address of the docker container... I'm not running in a docker container... and the IP address is outside of my IP address range (172.16.x.x). I'm running on Home Assistant OS / Supervisor (so no docker). And I find it very interesting the original poster had the SAME IP address in their error.
Hi there. HAOS runs add-ons and even core things, like Supervisor, in Docker. That IP is a private range local to your HAOS installation and refers to the zwave_js add-on container, but there is a problem with it getting started appropriately with .159; I haven't tested .160 yet. This sort of communication happens in the background and your average HA user isn't really meant to know about it.
Hi all,
This is on me, apologies for the mess this has created. Thanks to another issue home-assistant/addons#2494 I was able to find the root cause which was a change in the build system (this was not reflected in the change logs because it has to do with the base images that we use to build addons, not zwave js itself). I did test the addon before I submitted the PR, and ran into this same issue, but because I didn’t touch any of the files listed in the failure logs, I assumed I had created the permissions issue when transferring the files from my repo to my HA server, and once I resolved it locally I moved on. That was clearly a very poor assumption.
The fix has been merged and resolved in 0.1.60
So... I just updated to 0.1.60... the problem still persists. Same error. Reverting to 0.1.58 again.
So... I just updated to 0.1.60... the problem still persists. Same error. Reverting to 0.1.58 again.
If you could provide some logs that'd be appreciated.
I just re-upgraded to 1.6 again. It did, once again, break with the same issue as before. Before gathering more than the aforementioned central log with the unable to connect error, I attempted to reload the addon (no effect)... and then decided to do a full restart of the entire HASS OS host. After a full reboot, the problem went away... so not sure what is going on with that... the upgrade didn't (for me) happen seemlessly, but a full reboot resolved it.
Thanks @raman325. Confirming that 0.1.60 is working. I did have to wait a bit longer than expected, but the Integration eventually went back to normal, and logs from the add-on looked normal as well.
Can confirm that 0.1.60 still threw the same error after update. But a full reboot of the system brought everything back online. Thank you for the fast work devs!
i am having this issue since this morning after updating core to 2022.6.6
Unfortunatly restore from backup didn't work