I have HAOS running in a VirtualBox guest on a Linux host. I have four identical Enbrighton in-wall toggle switches, all working fine. However, I recently noticed that one of the four has a red bar in the security column in the JS Z-Wave UI.
I can’t be certain, but I believe that has changed since installation. I know security is not really critical for this device, but I’d love to know why. I also notice that in the FW column, three show FW: v5.54 SDK: v6.81.3 but the on is missing the SDK entry.
I downloaded the .otz file from Jasco, and have tried updating the firmware to the same version, but it always just times out, never going about what looks like 0,04%. I also have the .otz file for the previous 5.53 firmware, but am a bit shy of trying that without confirmation that doing that and then upgrading again to 5.54 would help any. (As far as I remember, all four switches had 5.54 when I first got them a few years ago.
I assume I could remove and then re-add the switch, but I’d really like to avoid that because it took me many many tries to originally get it added. (It’s phyically out in the garage, and my network access is not very good there, even though the device itself seems to connect fine to the other Z-wave devices in the house.
Thanks for any explanation for the difference, and for suggestions on how to resolve it.
That doesn’t seem likely, as security level is established at inclusion. It can’t be changed without excluding the device and including it again AFAIK,
It seems more likely that you are misremembering than the device has downgraded firmware without your involvement.
You can know for sure by checking the communication stats for the device. Based on your firmware upgrade experience I would assume there is a problem, as a mains powered device with good communications should progress ok. You can look at the network map to see how many hops there are to it, more hops will slow it down, especially if a slower device is in the path.
One option is to remove the switch and temporarily power it closer to the controller. That should improve the inclusion and firmware upgrade. Once you move the device back, you’ll likely have to heal it. If the network is really bad, you may have to move/heal in steps.
I can believe it was always this way and I just never noticed, but why would this one have gotten added differently from the others? (Yes, I know there is no good answer to that.) The firmware shows the same version, is just doesn’t show the SDK for that one switch.
The network graph shows a direct connection between the controller and the switch, with -99 dBm. Link statistics for 10 iterations all succeeded but latency was 50 min, 2270 max, and 556 avg. I can try moving a controlled plug-in outlt via extension core to a point midway between the controller and the switch, and see if re-mapping will help, but I don’t expect much. I suppose temporarily moving the switch is possible, but it would be a royal pain.
I’ll report back tomorrow - too late to play with this tonight. (US Eastern time)
If there is any communication error during S2 Security bootstrapping, the secure inclusion is aborted and the inclusion reverts to insecure. You probably received a warning but might have not noticed or forgotten.
For the same reason, maybe the query for the SDK version failed and so it’s unknown. You could try a re-interview, if there are communication problems that could make it worse.
-99 dBm signal strength is barely better than no signal at all. If it was in that state during inclusion, it’s not a surprise the security bootstrapping might have failed. I’m surprised the switch works at all.
The noise floor of a 500-series controller is around -94 dBm, -100 dBm for 700-series and min -110 dBm for 800-series. So for most controllers that signal strength is practically noise.
Definitely strange. The other switch in the garage seems to have been included correctly, and works as well as the problem one, but it does show S2 security level.
Moving the plug-in outlet to various locations didn’t help any, it was never “close enough” to change the map.
However, I did manage (no idea why or how) to re-load the firmware for the switch, and now it does show the SDK for the firmware, but still not secure. At this point, it doesn’t seem I have much choice but to find a time to physically move the switch to be closer to the controller. Hopefully I can get to it before the thread gets locked for old-age.
