For whatever reason, I opened the Z-Wave details page to look at a ZSE44 LR temp and humidity sensor. Lo and behold, I noticed that it wasn't shown as paired LR.
Okay, maybe somehow I screwed up months ago, right? So, before I exclude and factory reset and redo as LR, I notice MASSIVE amounts of missing devices on the details page. These devices include in-wall line powered switches. Entire rooms.
The device page shows ~145 real devices. The Z-Wave details page ~66!
I have no idea when this started. I did go back and forth from Zip to ZWJS a couple times, and I think there may have been a cloud restore thrown in mix, along with some other restores. This was when I was having problems with ZWJS, but again, I have no idea when this started.
Did I miss something as far as developments go? When things are going well, I don't pay as much attention as I should - hence the ZWJS kerfuffle.
Since moving back to ZIP, neither of my Zen17s show up in the Details table. They are both LR, but all my other LR devices show up.
It's consistently reproducible, as I've had to bounce temporarily back to JS a few times for some maintenance stuff (the Details table is complete on JS).
Since both Z17s work fine on ZIP (they have issues on JS), I just live with it
Going back and forth, as I've said before, hasn't been trivial for me. Several devices didn't make the transition to zip, as I recall. Had to factory reset, etc, as I recall. This is an order of magnitude difference though.
@bcopeland wants the content of a json file. Too big to cut and paste text. Safari probably not formatting it in an easy to read form. Did a bunch of cut and paste images.
I don't feel like spend endless hours on this stuff.
After switching to ZWJS, I managed to get the ZSE41s to behave properly by hitting the device button 4 times in several different ways. Remove battery, etc. I found that if the blue light stays on a little longer, the 'change' occurs, ie, on wake up, the sensor doesn't report 'open' when it is actually closed. I did all 7 sensors in the house. I was optimistic. A hub reboot wipes out that progress, or 'change'.
The driver says I have 2.20 device firmware. There's a 2.3 version that I'll try, although it's possible it's already there, just not reported on the driver.
Now, I have to remember how to upgrade the firmware, lol.
edit: Well, the 2.3 update is in my firmware files, so I must've updated it already:
Highly unlikely the device firmware would fix this. Something in ZWJS is getting out of sync causing the reporting to be backwards. I believe this was a much larger issue early on, have not seen any other reports of it recently.
You could try forcing a reinterview on one of them and see if it helps.
Force a re-interview, endpoint ## below is the decimal node number.
/hub/zwave2/reinterview?node=##
After you run that, then manually wake the device with the button press.
Click the Z-Wave button 4 times quickly to wake the sensor up manually.
The LED indicator will flash once to confirm the device is awake. During wake-up, the sensor turns the Z-Wave radio on for one minute to receive communication from the hub.
If you keep the zwave logs open it should cause a bunch of activity, thats about the only way to verify that it actually did the interview.
Yes. That fixes it. Again, until the next reboot.
Next steps? lol.
edit: locking on the next one-no state change, werong sequence?
edit2: refresh gets the next one reporting state change, but problem still exists. If I open the door, press 4 times on button, and get a long blue light, problem goes away. Again, until the next reboot. There is activity on the z-wave logs, but it goes by quickly. I didn't save a file. Wouldn't know what I'd be looking at anyway.
edit3: That's not working, as I thought it was. Oh, well. Back to zip, unless I want doors and window to report OPEN every 12 hours.
.. Can you PM me a screenshot of your z-wave details page?
