Z-Wave JS failure #3234
Comments
|
Seems ok now with 9.0.1 |
|
@ablyes can you set your addon logs to debug and then paste the results here? CC @AlCalzone |
|
This is mine |
|
Honestly this last log looks like the recovery mechanism is working as intended, although it isn't successful. The controller stops responding completely and after 3 attempts of sending, followed by 3 attempts of restarting the stick without success, the driver gives up. Afterwards zwave-js-server should restart the driver (not sure if it does here?), which reopens the serial port, hopefully causing the stick to respond again. |
|
I have the same issue after i updated to 0.1.93 this morning. After a while the driver does manage to start, but within a minute, the whole thing happens again. |
|
Which controller do you have? Which firmware version (if 700/800 series)? |
|
I'm using an Aeotec Gen5, running on: Z-wave JS UI: 2.0.1 |
|
Which path are you accessing it through? |
|
I had the same issue with this version. Here is the path i'm using :
|
|
Similar scenario here.. stopped working recently, similar logs. It all starts well and good, but then just hangs. My hardware reports Aeotec Z-Stick Gen5 (ZW090) - UZB Device: ttyACM0 - /dev/serial/by-id/usb-0658_0200_01FFFFFF-FFFF-FFFF-FFFF-160316112940-if00, s/n: 01FFFFFF-FFFF-FFFF-FFFF-160316112940 - 0658:0200 Debug log tail: |
I'm connecting trough: /dev/serial/by-id/usb-0658_0200-if00 My aeotec Gen5 stick is the old regular version (not Gen5+), running on v1.1. I found there was a firmware update at aeotec: https://aeotec.freshdesk.com/support/solutions/articles/6000252294-z-stick-gen5-v1-02-firmware-update I upgraded my stick 10 minutes ago via my Windows machine (it was quite a hassle to get the driver and the upgrade working). but since then no crashes yet... fingers crossed! |
|
This company is doing bullshit, not devices. |
The Z-Wave JS UI add-on and the Z-Wave JS official add-on are not compatible to be run at the same time. If you run both at the same time they will compete for the serial port and problems may arise. |
|
According to hassio-addons/addon-zwave-js-ui#584 this is likely to be an issue with VMs. Some 500 series controllers reconnect to USB when being restarted (soft-reset). Some VMs require specific configuration to be able to handle this, otherwise the connection to the controller gets lost. The proper solution would be to configure the VM correctly (whatever correct is), the easy solution is disabling soft-reset. Previous versions tried to auto-detect whether a controller would come back after soft-resetting and remember this info, but this feature had false negatives, so it was removed in |
|
We disable soft-reset if we detect a VM in the add-on. |
|
What's the indication that the affected users in this issue are using VMs? |
Not 100% sure but the lack of If the controller did receive and handle the That and the users in the linked issue having very similar problems with soft-reset. |
I found that post, but disabling the soft-reset didn't work. (for me at least)
A bit later i found out that i had Z-Wave JS not running; so i am only using Z-Wave JS UI. For me the firmware upgrade to v1.2 did the trick, it's still up and running. |
|
I'm running HAOS. I'm pretty sure that means it's all running in VMs. Still seeing a soft reset in my logs. |
I double-checked - that codepath only gets executed if soft-reset is not disabled (or if you are using a 700+ series controller) |
|
Was able to see earlier in the log where it talks about detecting VMs.. [09:59:35] INFO: Both 'network_key' and 's0_legacy_key' are set and match. All ok. I'm unable to find a place to disable soft-reset.. I'm not using Z-Wave JS UI, just the zwave_js integration along with the core_zwave_js add-on. Any pointers? I'm coming up empty on my search. Is it possible because of the state I'm in (things won't start all the way), that UI isn't available? |
|
Hi. Same issue with dying Z-wave. Home Assistant 2023.9.3 UZB |
|
I have the same issue.. |
|
Rolled back to 0.1.92 to see if that helped. It did not. Rolled back to 0.1.90 (the next backup I had) and it is working again. Looks like a long list of changes in 0.1.91.. two sound like they could be the culprit here. I'm guessing these releases came in rapid succession which is why I didn't get 0.1.91 installed automatically. |
Do you have driver logs? That stick should be on the list of sticks that are never soft-reset. |
|
Same issue here. RPI with Z-wave HAT. Reverted to HA 2023.6.3 + 0.1.93 still problem. Sorry if the HA version is irrelevant here, noob here. Just thought I could chip in some info that the same happened with a HAT that isn't USB-connected. |
|
Do you have more complete driver logs @jenscollin ? |
|
Just updated the HA Core again thinking that it had nothing to do with it. However the combo 2023.9.3 and 0.1.84 it still fails over and over again. I'm thinking that HA Core is more involved than I though. A load of these... then suddenly, "New client" and all hell breaks loose. Then it starts over after a few minutes. How do I download the whole log, I just get partials that I understand are hard to make something by. |
https://www.home-assistant.io/integrations/zwave_js#how-to-access-the-z-wave-logs - keep the window open.
That should support soft-reset. At least my 2016 variant does. |
|
Issue is solved for me with Version 0.1.97 and Home Assistant 2023.10.3. Z-Wave.Me USB Stick ZME_UZB1 on Proxmox VM. |
so I noticed that there is a trend where this is happening to users with dead nodes, so I thought to install PC Controller 5 and see if I could manually wipe some of these nodes out. I found something odd on my zwave stick in that two nodes (51 and 55) are neighbors of each other, but neither can be marked as failed, and if I attempt to poll them for information, either one will lock up the stick and make it unresponsive, even in PC Controller 5. I have no idea how to force these nodes to go away but I think that would clear up my issues. It's also strange to me that this only became a problem after upgrading from 0.1.87 to 0.1.97. after deleting a few dead nodes, the behavior ends up the same though, Zwave JS just reboots repeatedly. oops* uploaded wrong log. this is the correct one: |
Because your controller is becoming unresponsive and Z-Wave JS now tries to handle this by restarting it, instead of just continuing and risking a few more nodes to be incorrectly marked as "dead". The latest update increased the timeout for this from 10 to 30 seconds - seems this is still not enough. |
i haven't tried to see how long it takes for the stick to recover, but can check. is there a way to force the client to ignore nodes? eg a setting to "never poll nodes [51,55] |
|
I ran into a same issue, after upgrading firmware on USB controller & issue went away. Here is the Aeotec link |
I'd love to try this but for some reason the instructions on this page do not work on my system. the firmware upgrade software cannot find the com port for the device (despite it working for backing up the stick in another application also from Aeotec), thus I cannot upgrade the firmware. I'm trying to get my hands on another windows PC to attempt but have not found one yet. I also filed a support request with Aeotec for this but not sure that will be fruitful |
Well... let's just say this wasn't supposed to break anything, aside from users having to disable soft-reset. But I didn't anticipate just how broken almost all Z-Wave controller firmwares are. |
so, great news, I borrowed a windows machine for 15 minutes today, updated the firmware on my stick, and then things are working swimmingly again. 1.02 on the Gen5 Aeotec stick seems to make this problem disappear specifically on |
This worked for me as well. Thanks for the tip! Environment:
|
|
FYI, before everyone moves away from the Gen5 stick - I released another driver version yesterday which should help with the remaining issues: https://github.com/zwave-js/node-zwave-js/releases/tag/v12.2.0 |
|
I have updated to latest version of Z-Wave JS UI and it stopped working now. The Aeotec Stick Gen 5 is not recognized nor the entities in it. As stated in my previous comment, I have the latest firmware installed following this tutorial
After the update of the add-on, are there any recommended steps for those who have updated the firmware in the Aeotec Stick Gen 5? |
|
Here you find some logs of a Zwave 7gen Stick of aeotec with firmware 7.19.4. Accessing serial port by id doesn't work at all (Zwave JS and Zwave JS UI). Forwarding serial port with ser2net seams to work at the beginning, until it ends up in the same problem. Testet this morning with all the latest versions available. zwavejs_2023-10-19 - using ser2net.log |
|
@pachiclana unplug and replug the stick, disable soft-reset in the options, make sure you have the correct port selected. |
|
@sofa74surfer Like the last time I looked at the logs, your stick suddenly stops communicating without any indication why. Here's where it happens in the ser2net logs: I suspect there's either
As far as I can see, this is not related to the Z-Wave JS updates, as the problem happens randomly without Z-Wave JS interfering. Or does it work if you roll back? |
|
@AlCalzone, it works now. I just disabled the soft-reset option, restarted the add-on and it worked. Thanks for the advice! |
|
Same here, Have HA on a VMWARE esxi 6.7 u3 with passthrough USB and with the soft reset on it did not connect to the bus, The stick i have is a Aeotec Zwave Gen5 ZW090 firmware v1.2 After disabling the soft reset function it started working again. |
|
I may have a stupid question : |
Well only thing i did was update everything go into the zwave JS UI click the cogwheel (settings) open the Z-Wave options and disable Soft reset there and save, Restart Z-Wave JS and it should be fine. |
|
after upgrade to 2.2.3, ZWAVE stopped working, changed the ZWAVE integration to point from ws://core-zwave-js:3000 to ws://a0d7b954-zwavejs2mqtt:3000 and its working one. Before 10/14 ws://localhost:3000 was working fine How can I know what is correct setting for ZWAVE integration? |
Z-Wave is hardly dead. Although it is true that some technology is being pushed noisily out to general less tech savvy consumers, like ZigBee, Wi-Fi and promises they will all work together because of things like Matter. |
|
Upgrading my controller (gen5) and then grabbed the latest of zwave-js-ui and hass and it's been fixed for me (so far). I tried everything before upgrading the firmware and the system would eventually crash but after taking the plunge and upgrading it yesterday (took 10 minutes) everything has been smooth since then. For more context, i did have four dead nodes which I've since removed, that will probably help the system run better too and prevent future problems. |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
|
This Issue isn't resolved for my Aeotec Z-Stick 7. it's dead since over 3 month, i buyed a new one, but it also din't work. Tried id on a second machine and it doesn't work at all. Downgraded the Stick, but this also not works. Same Issue "Failed to execute controller command after 1/3 attempts." all the time. It stopped working somewhere in September 23 with a update of HA or Zwave. |
|
Same here on my Aeotec Z-Stick 5. I haven’t been able to update HA or Zwave since September. None of the fixes listed have helped. Anytime a new update comes out, I update to see if it has been resolved, but end up having to revert to a backup. what info can I provide to help with this? |
|
For completeness, i'm still seeing recovery fail occasionally (Aeotec Gen5+ on HA Yellow and latest versions of HA). I'm running Zwave JS UI now but the controller recovery is sounding similar. I last saw this on the 27th December in the middle of the night. But the controller tries to soft reset. The main problem being it then thinks its responsive again. It isnt. All zwave reporting and control just ceases yet appears fine (i.e not dead in the status etc. Its like everything is just frozen). If i then change something like the inclusion timeout in JSUI and hit save, the controller immediately comes back to life and the trafffic goes crazy while all the nodes on the network update their parameters etc - like you would expect if soft restart was successful. Latest snippet (sorry, debug wasnt on as i thought this was related to interview/cometz, but /i think its wider now) This will go on forever until I manually take action. The last time it happened above, it was 4AM - at least 5 hours later I noticed my 60 node network was not functioning. The nodes dont show as unavailable in timeline/logbook, their temp etc readings just stay the same and flatlined. |
|
@cadwizzard AFAIK you need a newer version of node-zwave-js, but the latest addon version doesn't come with that yet. |
|
Which addon are you referring to? Latest official addon is up to date: #3351 |
and others
Describe the issue you are experiencing
Since the last version of home assitant
Home Assistant 2023.9.3
Supervisor 2023.09.2
Operating System 10.5
Interface utilisateur : 20230911.0 - latest
Z-Wave JS Current version: 0.1.93
My Z-Wave devices are not working. I have this error in the logs:
What type of installation are you running?
Home Assistant Supervised
Which operating system are you running on?
Home Assistant Operating System
Which add-on are you reporting an issue with?
Z-Wave JS
What is the version of the add-on?
0.1.93
Steps to reproduce the issue
System Health information
Message in french : Aucune correction n'est actuellement disponible
-> no correction
Anything in the Supervisor logs that might be useful for us?
No response
Anything in the add-on logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: