Possible sensor/switch issue with Zen16 v3.30 firmware?

Hi Zooz!

Since it just became available to update via JS in Home Assistant a couple/few hours ago, I updated my 800LR Z16 to 3.30 (from 3.20). My 3 sensors have forever been happily configured as #7/Contact Sensors (each monitoring dumb wired reed sensors), but now after the update, all 3 sensors show as “Unavailable”.

The relays are all working fine. Claude helped me troubleshoot a lot of stuff, but nothing is shaking those Unavailable states loose…

With Claude’s help, I confirmed that the Associations (Lifeline) is confirmed intact, the Z16’s Node status has been “Alive” throughout, and I verified that all of the Z16’s configuration parameters are properly set. I tried resending the parameters, tried every possible type & manner of refresh and restart for both the device, Z-Wave JS, and HA itself.

As I physically cycled each sensor’s door, Claude confirmed that the S1/S2/S3 input reports (Notification CC) never fired — there was no timestamp movement on the corresponding entities.

I did try rolling back to 3.20, but the Unavailable states still persisted there too.

Since I have so darn many automations tied to this Z16 (paired LR), I’m dreading the thought of having to exclude/re-include, so I’m really hoping there’s something I can do instead of that nuclear option… I’d be grateful for any ideas - many thanks in advance!

Cheers, Chris

I ended up going nuclear and did the whole exclude / re-include dance (and I stayed on 3.30)… TLDR, that seems to have fixed it - everything is back to working well in the limited testing I’ve done, so hopefully that continues :crossed_fingers:

This was my first foray into a device swap like this with HA’s ZW JS, and I had an unanticipated scare with a couple duplicated device entries (the old one was unexpectedly sticking around after exclusion and then I had 2 new ones for the 2 re-includes I had to do [2nd one to set up Contact Senors])… As I was going nuts trying to figure out some way to get rid of those 2 devices and all their pesky entities, I realized they all were just suddenly gone – JS (or something else within HA) must’ve just swept them out after a bit of a delay.

Well, don’t question a miracle, I guess! With those gone, I was easily able to rename the sensor & relay entity IDs back to the original ones, and then everything dropped right back into place with automations, scripts, etc. Whew!

Whenever the next Z16 fw update rolls out, I think I’ll wait a while before pulling the trigger :sweat_smile:

1 Like

Early Adopter Syndrome? :grinning_face_with_smiling_eyes:
Glad it worked out in the end…

1 Like

For what it’s worth, I updated my Zen 16 devices to 3.30 without issues. I was using the ZBox though (although that shouldn’t really matter).