This AM I did my first attempt at ZwaveJS Switchover. I followed same general procedure from mavrrick58:
So I updated my hub to latest firmware And then hit the switch ZwaveJS.... waited for reboot.
After reboot... I wait. The hub was really slow and sluggish.. ok, going thru the conversion I think. But after 30 mins, zwave was still completely dead. all devices were pending, and 2 out of my 5 S2 LR devices were 'unknown' security. Just switching around tabs was painful... with page loads taking several seconds to complete.
I waited another 30 mins. no dice. So I did a reboot. Hub did better after this, a few devices got routes, and the sluggish page loads disappeared. I am noting here, I don't think I've seen anyone describe this behavior on the first boot or if its to be expected.
I used the re-interview node link and got the S2 devices back. One was stubborn and took multiple tries, most of the other AC powered mesh devices showed up, with exception of my leviton ZW4SF fan controller. That controller has known occasional lockups which I've posted on... I tried the manual paddle switch and it was DOA also.. so a quick airgap brought that device back online.
I don't get an option for zwave firmware upgrade.. I'm looking for a confirmation here that 7.18 is the right version. I've reread the discussions but confused myself on whtehr I do or don't need an upgrade post ZwaveJS. (or the pause of 7.22 is still effect even for zwavejs and I'm good?)
OK so last are the battery devices. I've got two Zooz ZSE40s that I can't get online. I've waved like a madman in front of them and tried reinterview many times... I can't get them to show up. I even airgapped them (pulled the batteries and reinserted) and tried a reinterview.
Re-searching through all the posts here, looks like others had issues with ZSE40 and ZWAVEJS.. but maybe they are old news. Is this a known no-go?
I can go the exclude/include route for these two devices if that's required.. but wanted to check if this is a no go before I pull more hair out.
Shut down hub, unplug power for 1 minute, power back up. That will clear the z-wave radio. See if that works. (Rebooting on it's own doesn't clear the radio)
A good suggestion and I should have tried that first, but no dice. Full power down/remove... power back up... several madman motions in from of the sensors and reinterview attempts, but no go.
2.4.4 is rumored to have significant JS work in it, so I would at least wait for that.
I was an early JS adopter and was happy on it for quite a while, but then some JS update ~late summer really trashed it for me. I'm not planning to try it again until there is widespread agreement things are smooth. I go back once in a while to check the issues not working for me, and they are still present. Fortunately, going back to ZIP is always smooth for me, so I'll likely try JS again when the 2.4.4 beta lands.
2.4.4 is not in beta yet, but hopefully sometime soon.
Basically says "Hi" to devices and grabs their deets so they can communicate w/your hub.
Jeff said: "The interview endpoint is something specific for ZWJS. ...sends a bunch of discovery requests out to the device to learn about all of its capabilities and command classes. The endpoint is just to force it to do that again, to see if it helps with some of the reported issues."
SO I go to Zooz site and grab the manual for the ZSE40, I see a reference to manually waking up the sensor. I go and pull the manual, and see this:
The sensor’s wake-up interval is set to 12
hours by default to save battery life. You
can change the wake-up interval using
your controller’s advanced settings if
available.
During wake-up, the sensor receives
communication from the hub (setting
updates or network information). Long
wake-up interval will not affect how
often the sensor reports motion and
other values to your gateway controller.
MANUAL WAKE-UP
Press and release the Z-Wave button
once to wake the device up. The LED
indicator will flash once (blue or orange).
You may need to wake the sensor up
manually IF:
1. It doesn’t fully configure during set-up
(values are not displayed or errors
pop up in your hub’s interface).
2. You change advanced settings for the
sensor and want them to update
The Zwave button! Ohh, thats the paperclip hole on the ZSE40.
Press and release the Z-Wave button
once to wake the device up. The LED
indicator will flash once (blue or orange).
So a quick jab with a paperclip... get a red flash... reinterviewed and hello ZSE40. Duplicated this on the other ZSE40... right back online.
So waving like a madman (although therapeutic for me) might 'wake' the sensor... but perhaps not all the low level comm sync with base are active (they are on their 12 hour schedule)... until you jab it with a paperclip.
So far that seems to have done it... both are back online and functioning.
