Zwave docker update and "unavailable" status

Configuration Z-Wave
1

Hi there,
on my home assistant setup, I’m using zwave-js in a dedicated docker container.

Everytime I update the docker (stop / remove / delete image / pull new image) my sensors change state to unavailable.

This is understandable, but due to the fact that update are more or less weekly , prevent me to understand which sensors don’t change state for long term , using the “last changed” attribute.

Is there a way to “manually” pause/unpause the communication preventing the system to make sensors “unavailable” ?

2

The entities become unavailable whenever connection is lost to the z-wave js server, which of course occurs when you upgrade the server. No, it’s not possible to avoid this.

3

Why weekly? They don’t release weekly and even if they did it is not necessary. Maybe monthly with HA updates but definitely not weekly.

4

I usually stop home assistant container before updating zwavejs in docker.

That should stop it from showing unavailable in the logs.

Update
It wont show unavailable in the device’s history when you update zwavejsui while home assistant is shut down, but “last changed” will be when home assistant was restarted, so may not solve what issue you are trying to fix.

5

Using last changed is problematic as it resets whenever you restart HA. There are other ways to accomplish your objective that avoid this issue. Post your code that breaks.

2 Likes
6
7

Mmm … never tried this before … I’ll let you know.

8

MMmm … what do you mean ?

9

Commits are not releases so why bother. Even with release why bother unless beneficial/needed feature, security patch, or Required for HA update?

1 Like
10

I use to update my docker container anytime seems to be a relevant update that solve some issue.
In the fact , zwave-js v12 was initially a big pain in the ass.

But this isn’t the point … don’t you agree ?
I wonder if there is a way to bypass this.

11

Instead of using the LATEST tag in your docker run command, use a specific version.

12

The problem is if you dont update zwavejsui’s container, it will stop working when you update home assistant due an incompatible zwavejs server. This is a frequent “breaking change”, including this latest November release.

So, unless you use mqtt (which is stable and doesn’t need updates much, if ever), you are basically forced to keep updating zwavejsui when you update home assistant.

13

You quoted it but did you read it?

“ why bother unless… Required for HA update?”

HA is monthly update at best. OP is doing update with every commit. Thats crazy and useless

14

Yes, i read you put that. My point was that your forced to do updates to zwavejs frequently to keep zwavejs compatible with home assistant. To me, monthly is still frequently to have to update this, but we may have a different opinion on frequently.

But i agree you don’t need to always update each new zwavejs commit

2 Likes
15

Or even every monthly build of HA… I’ve been recently pulling back on the frequency of updating to find a good comfy fit. Looks like I’m going to be settling on quarterly unless I have something breaking… Then it’s settle in with a gallon of coffee and an audio book for a couple hours on a Saturday morning. :wink:

2 Likes
16

Yeah quarterly would definitely be nice. Zwavejs updates have caused me the most issues out of all my programs- by issues i mean something breaks on an update to the point my wife notices and is not happy. The annoying thing is many times things work fine at first, but would break after i leave on a trip for a week. Then there is another zwavejs release shortly after to fix the bug. I haven’t bought a new z wave device in months, and would like to just leave it alone, but this frequent incompatible zwavejs server breaking change forces my hand to update.

I just make sure to only update if I’ll be home for at least a week, and also look at the github issues before updating. I never have issues with my zigbee2mqtt updates. It’s gotten to the point ive considered just ditching the zwavejs integration and using the mqtt part of zwavejsui instead. Mqtt would avoid zwavejs server breaking changes, but changing now would be a lot of work. I know you have a lot more devices then me, so that would take a lot of pots of coffee if you did that. :slight_smile:

1 Like
17

I don’t know if the HEB has that much coffee in stock, sir.

1 Like
18

What issues.

Zwavejs has never caused me problems.
I had zwave problems, specifically related to range, caused by devices but never zwavejs as primary cause.

19

Glad you never had problems with it, but just look at the release history and issues on Github

This one in particular was a release on 10/5 of this year that fixed the bug released in the version on 9/29

This was another fun one I dealt with - my entire zwave network crashed

That happened at least with one other update. Some updates just cause individual devices of mine to break, but there have been numerous times I’ve needed to roll back after an update.

To clarify, I really like the zwavejsui program and interface, I just don’t like how its updates frequently break things, and I don’t like how I am forced to update it to deal with Home Assistant breaking changes for the zwavejs server compatibility issue. I cringe every time I have to update this program.

20

Yep, that why I only update HA + Zwave 3x a year. And never to a .0 release and only after surfing this message board to see if things are stable.

2 Likes