Z-wave JS stopped working. Most of my home out of order... Here we go again

aruffell · September 30, 2021, 8:27pm

Here you can read more about those keys and the changes happening:

home-assistant/addons/blob/c1bc77b9ae87f56bb6a142eabe7294499ab72ec9/zwave_js/DOCS.md

# Home Assistant Add-on: Z-Wave JS

## Installation

Follow these steps to get the add-on installed on your system:

1. Navigate in your Home Assistant frontend to **Supervisor** -> **Add-on Store**.
2. Find the "Z-Wave JS" add-on and click it.
3. Click on the "INSTALL" button.

## How to use

The add-on needs to know where your Z-Wave stick can be found, and therefore,
you'll need to configure the add-on to point to the right device.

If you're using Home Assistant you may find the correct value for this on the
`Supervisor -> System -> Host system -> Hardware` page. It is recommended
to use a "by-id" path to the device if one exists, as it is not subject to
change if other devices are added to the system.

This file has been truncated. show original

TurtleBlitz · September 30, 2021, 10:09pm

Tried v0.1.44 and got this error on the integration page

“Retrying setup: Cannot connect to host core-zwave-js:3000 ssl:default [Connect call failed (‘172.30.33.0’, 3000)]”

Did a full restart and everything is working! Good work

diederik-maes · October 1, 2021, 12:15pm

Upgraded this morning to 0.1.44 and everything stopped working again.
I rolled back to 0.1.42 and will now await another release that hopefully will be stable again.

diederik-maes · October 4, 2021, 11:25am

Tried now with 0.1.45 and still same problem.
Anybody who found the solution? All the keys in config seem correct.
Meanwhile I will roll back to 0.1.42

diederik-maes · October 4, 2021, 11:40am

FYI, a reboot seems to have fixed it.
For now 0.1.45 seems to be working correctly.

kalach · October 5, 2021, 11:24am

Same here with 0.1.41, had to do full restore. The partial back up restoring did not work. Even now with each update from 0.1.42 till 0.1.45 I am loosing some devices and have to re-interview them, so I do not have fully operational network and have to do manual fixing.

mm523 · November 17, 2021, 6:38am

I’m on 0.1.47 and I still keep having to restart Z-Wave JS multiple times per day. The entire thing is just junk, I’m utterly floored that this is the new integration. I was using whatever the default was about a year ago and had zero problems. Nothing but trouble with this. It’s borderline useless. And I really wish it wasn’t in JS, there’s a good reason the entire software industry has been shifting to languages like Go. JS is a weakly typed nightmare, you should never write anything critical in JS. Ever.

firstof9 · November 17, 2021, 8:00pm

Provide some logs for troubleshooting assistance, in a new thread as not to hijack this one.

mwav3 · November 18, 2021, 1:53am

Developed by Google. I’m sure our privacy and security were their top priorities. What could possibly go wrong…

finity · November 18, 2021, 2:27am

I’m sure there are lots of people who would disagree.

Including me.

mm523 · November 18, 2021, 6:38pm

It’s entirely open source there isn’t crap in there somehow mining your data. That’s sheer paranoia and ignorance. Enterprises wouldn’t be using it everywhere if that weren’t the case. Also, the point is about strong, static typing in general, and that JS is godawful garbage. The exact language doesn’t even really matter. Of course that’s not necessarily even the cause of any problem here, but damn I wish people would stop embracing terrible languages and practices.

mm523 · November 18, 2021, 6:41pm

You’re welcome to disagree. Unfortunately, your disagreement doesn’t make it function correctly. This kind of thing isn’t a matter of opinion, it doesn’t work much of the time as evidenced by many people’s experiences in this thread.

finity · November 18, 2021, 9:11pm

and that is a completely subjective opinion based on some peoples experiences in one thread in one forum.

and most of the people in this thread eventually ended up getting things working fine after the new release with the bugs fixed and/or fixing the user errors (security key issues).

I didn’t switch for a long time because I didn’t feel it was production ready. I had been running test installs of zwavejs2mqtt in Docker outside of HA (I don’t use Supervisor) to test things and getting things ready for a smooth transition once I decided to do it. I finally did this weekend and I haven’t had any real issues…especially ones that would make me say that the entire thing is junk and completely useless. Hyperbole much?

and yet you still haven’t provided any additional information to help us to help you figure out why your system is junk and mine (and many others) isn’t.

Do you actually want help or not?

sparkydave · November 18, 2021, 9:26pm

On the other hand my ZWave network is rock solid. The only issues I’ve ever had have been with very old (~7 years or so) devices letting me down, but my newer ones are brilliant.

BebeMischa · November 18, 2021, 9:51pm

May I just say, that I’m distancing myself from all the discussion after my last entry in this (my) topic?

My frustration was only about breaking changes, which made me mad for a second and I wish, this will be done differently.
But in all means not about the allover reliability of the Z-wave JS integration. Well, since the changes are applied and I found out, how to react correctly on my side, Z-wave works like a charm here. Until the next breaking update, but it works like a Swiss watch.

I’m, even with the volcanic explosions, I can have, when things break, VERY happy with the work, the developers have done to give a free of charge possibility to run an automated household, which for a big part relies on Z-wave, by name Z-wave JS in particular.

So please, do not misuse my tread for frustrations of different kind, create your own.

Thanks very much.

mwav3 · November 18, 2021, 10:11pm

The root cause of the issue that started this thread was the update for the zwavejs addon came out a day or two before the Home Assistant release, and both required an update at the same time due to changes around the security keys in zwavejs. That had nothing to do with the language the program was written in. Independently managed but codependent software projects have this happen all the time, regardless of the programming language used to develop the software. Yes it affected a lot of people, and they posted about it (you will notice almost all posts a day or two apart). Sure, it was a mistake to release it early, but it was promptly fixed.

I would not make inferences about the whole project being “borderline useless” over this one incident though.

WillS · November 27, 2021, 6:58pm

I may have had Zwave JS on auto-update when I noticed an issue in what was likely 0.1.47 and devices started to not respond. I couldn’t even turn one of the dimmers off manually. But with a family member staying here after a stroke, the HVAC quitting, my laptop crashing, etc, I’ve had other priorities to visit. Now today, I tried upgrading to 0.1.149 with many reboots/restarts and have a core-Zwave-JS 3000 error, so I’ve restored back to a 10-10-2021 full backup and am back to 0.1.37 and core-2021.7.4

I am concerned that I will have to make a big leap in many areas at some point, and all of the tweaks and partial fixes noted in this thread will have to be trialed and recovered from when some percentage of them are no longer effective or appropriate.

My current configuration works fine for what I need it, and while I plan to grow and become much more creative, stability is a key feature that drew me from openHAB to Home Assistant in recent months, and I hope that continues to be a key feature moving forward.