I initially received an error when trying to switch to ZWJS (ZWaveJS installation is invalid). Reverted to the prior build, updated again, and was able to make the switch.
I also updated Z-Wave firmware and have a few devices that don't seem to have survived the move. The vast majority of my other devices (mostly switches and shades) work great.
Zooz ZEN31 LED controller (built-in driver). I have one that works, another that doesn't
Zooz ZEN37 remote (community driver, I honestly can't remember what the built-in is)
Zooz ZSE41 contact sensor (using community driver, but built-in is the same result)
Aeotec trisensor (community; was able to get it to update once manually)
Zooz ZSE40 sensor (community)
Fibaro Flood Sensor (built-in)
Looking at the z-wave logs (which seem way more useful and easy to read!), I see activity from these devices.
I reverted back to Z/IP and these seem to be back and functioning again (haven't had a chance to test them all yet though)
For the devices that don't work, post two screenshots of the Z-Wave Settings for each device from the Z-Wave Settings page:
When your system is using z/ip gateway
When your system is using ZWaveJS
I want to make sure that the ZWave security settings are exactly the same. And if they are not, each of those devices can be re-interviewed to fix the situation under ZWaveJS.
Yes, I tried to wake the battery devices and they didn't report status.
I'll switch back to ZWJS and try again, and take screenshots. Some of the devices show activity in the last column but none showed a route.
I did see activity (e.g. motion reports, button presses on the remote) in the zwave logs but nothing registered on the drivers. I didn't get as far as to test if the drivers received an event to process.
That usually means that ZWJS did not complete its device interview. Messages are probably not being handed off to the driver. There is a way to manually re-trigger the interview for individual devices but it has not been posted publicly, it is supposed to work itself out without it and should not be needed.
I have the same thing happening. Battery-powered sensors show a recent “last message” but nothing in the logs and status “pending”. It’s been about 6 hours now.
It is a little early yet to be getting to worried but i am seeing this as well. All 4 of my zen 34 remote switches are refusing to do anythingn the zwave page shows activity in the last message column, but nothing is happening and they are staying pensing. I was able to get most of the other devices to move forward and conplete the interview process. Going to give it another day to start working.
Same here. Had to back out of using zwavejs because all of my Zen37 button remotes were marked as unknown and did not work. Also all my levitation switches set up with S2 were saying S2 unauthenticated. The Zen11 multi-sensors seemed to be listed oddly too. Like all the LR devices had issues. Wasn't in the mood to try to fix things.
I was able to get almost everything back either be forcing re-interviewing, or rejoining. I left it on ZWJS overnight.
I'm left with one fibaro flood sensor which initially reports values on joining but no updates, and a ZSE40 and ZSE41 that I couldn't get to work. I didn't try rejoining the 40/41 and have now reverted to z/ip.
I was able to get about half of my offending Ring Gen2 contact sensors and a Aeotec aerq sensor connected. Just had to push the button on them.
Then Zen34 Remote switches, 3 Ring Gen2 Contact sensors, and the Zooz ZSE43 Tilt/Shock sensor is being a pain.
I also noticed that it looks like my Inovelli Red FAn controller device changed it's stuff. It is showing connected with S0_Legacy as shown below instead of S2.
I found that just leaving things running overnight, 3 of the 5 motion sensors successfully cleared the pending status. Two still haven't. I'll try the reinterview link if the lazy way (just waiting) isn't enough.
Ok so after waiting 24 hours I took more drastic steps.
I was able to trigger something to happen with the Ringe Gen2 contact sensors by triggering the tamper alert on the remaining contact sensors. Not sure if there is anything special to that or if all of the other stuff related to then Zen34 switches just got things in a good state for those to work, but they did.
The Zooze Zen34 remote switches wouldn't connect no matter what i did. I tried @jtp10181 suggestion above. I tried re-Interviewing the devices. I could always see activity hitting the Zwave Log. It just never worked. I finally just excluded and repaired them. Not the best way for users but it does work.
Then Zen34 required a repair as well. I did find documentation about how to trigger it to wake up, but i am not sure if that was doing anything. I finally removed it and repaired it and everything seems good now.
If you migrate to ZW-JS and a device is not working at all, and/or the security info is wrong on the z-wave details page, use the endpoint to force a re-interview.
Seems like the command was doing something - I got a webpage saying "done".
Though I ended up excluding/including my Monoprice 15902 PIR sensors anyway: Four sensors purchased at the same time reporting different combinations of device class & security during the ZWJS migration.
For anyone with the same issue: During inclusion the Z-wave process seems to force a generic driver. As soon as it was included I changed the driver to the "Zooz 4 in 1 Sensor New" driver, saved, then proceeded with a couple of rounds of "configure" and device "wake" till I saw battery or tamper readouts start to populate. If they didn't run on AAA batteries I would dump them However the good news is that, they now include and exclude rapidly and did so at distance from the hub!
With respect to including z-wave devices, can anyone tell me if the inclusion process includes an initial configuration using the default driver? I can't be sure as I didn't attempt replication, but hitting configure with the system chosen driver seemed to cause the sensor to become unresponsive.
GoControl WA00Z1 remote switches were eventually coaxed out of "pending" status by repeated attempts to turn switches on and off but are now workings as normal.
