#Zen76 associations
1 messages · Page 1 of 1 (latest)
Hmm that contains less information than I had hoped. Can you make a driver log on level debug (https://zwave-js.github.io/zwave-js-ui/#/troubleshooting/generating-logs?id=driver-logs) and while that is running, re-interview both switches (one after the other)?
Node 42 Debug driver log: https://hastebin.com/share/atamixiqey.yaml
Node 46 Debug driver log: https://hastebin.com/share/yubumumeco.yaml
ohh I think I may know what's wrong
Those devices support the newest version of the (Multi channel Association CC. This makes it so the driver checks if the target node's security class is one of the sending node's security classes.
In your case both are insecure, but the check doesn't consider no security. So that check is negative, although the association should be allowed.
I could reproduce:
https://github.com/zwave-js/node-zwave-js/pull/6011
should be fixed in the next version of node-zwave-js
awesome, thank you
Thanks, very helpful. I saw same thing this week trying to add association for Zooz zen34 dimmer
I started off trying to add a zen34 which is what led me to try to just do 2 zen76's together, to take the whole sleeping device out of the equation. My setup is old and the no security is a remnant of that and the fact I live in the middle of nowhere, I'm not worried about someone sniffing zwave packets.
Same. Hoping minimize potential issues with no security. I tried with some other switches and had hit or miss results I couldn’t make sense of. Ultimately was able to (slowly) set it up with zwave pc controller - excellent reminder how much I appreciate nice interface and ease of use in zwavejs
Just noting I'm likely encountering the same issue
Happened on my Zen34
Which I then tested with my Zen77's
I use no security on these since they're just lights
Just @me if you need additional logs from me
issue is already fixed and released. it all depends on the release being picked up
Did this make it into the the latest release? I'm still having the same error
zwave-js: 11.5.0
home id: 4056066524
home hex: 0xf1c2a9dc```
did a docker compose pull about an hour ago
I forgot to merge. The fix is in 11.5.1, which Z-UI will pick up tomorrow morning
right on, just making sure. Thanks
I didn't see it in the release notes was the only reason I was wondering
will this allow s2 authenticated switches to associate with s2 unauthenticated plugs?
or is that just something that isn't possible
This is allowed in one direction, if
- the source switch has both authenticated and Unauthenticated
- and it supports association cc v4 and/Or multi channel association v3, where it is required to learn the target's security classes before sending a command
In practice you'll probably have to try it out
that's what i was aiming for, as the switch inside my garage is a zen71 700 series added in s2 authenticated, but the plugin module that runs the relay to open my garage door is only s2 unauthenticated
so my goal is to have the switch be able to open the door via association by turning on the switch that runs the relay, so i can open it from the other side of the garage from where the actual button is
but when i tried this late last year it wouldn't work. it's entirely possible i had set it up wrong though
i can (and have) set it up to work via scene control, but i'd like to be able to have it work if HA is down so associations would be more bulletproof
i'm also planning to eventually replace that with two ZEN32s so i can have control of the light too via both sides of the garage, but that's a different discussion for another day since i don't have those in place right now
it should work if you re-include the zen71 with unauthenticated. there's not really an upside to having authenticated, unless you have reasons not to be sure you're including the correct device (e.g. if you suspect an attacker trying to sneak a device into your network)
the only difference is that you're entering a PIN and the device gets a different key
how can i add it as unauth? i asked zooz support and they said it can only run as s2 auth but not s2 unauth
if there's a way to do it though i'm open to that
let me check
when I scan the QR code on mine, it says that it will request both Auth and Unauth
so it's just a matter of unchecking Authenticated when including. In HA this is hidden behind "How do you want to add your device" in the add device dialog
not sure right now if SmartStart lets you choose
but you definitely can in Z-Wave JS UI
this worked. I just removed the check for s2 auth and kept unauth and now I have an s2 unauth zen71