[Solved] Z-Wave Failed - DEAD

[bravenel]

@srwhite

I have the Z-Wave repeater side of the Iris plugs using a custom driver I wrote for SmartThings and ported to HE. All that does is a periodic health check to spot any that fall offline.

These will mess up your mesh no matter what driver you use. Remove them to start.

@srwhite

Those include 5 locks, a Zooz 4-in-1 sensor, an Aeon 6-in-1 sensor, and an Aeon Energy Meter G5 securely joined.

Remove and then rejoin the Zooz and Aeon sensors, and the Aeon Energy Meter. Be sure to rejoin as non-secure.

@srwhite

I disagree with that assertion. Those that have the upgraded firmware 0x20082010 are rock solid as repeaters. The issue that Hubitat and Smartthings has, is that during pairing, the hub fails to set Association Group #1 to the ID of the hub. This causes the Z-Wave module to believe it's fallen off the mesh. Once Group 1 is set, you can pull reports, MSR, etc. from the plug, and they remain connected and stable.

This is not what we are observing. If you have a lot of powered Z-Wave devices, you shouldn't need any repeaters. Humor me, remove them, see if it helps.

@srwhite

I won't rule out force removed devices as being an issue. Hubitat is unable to pair my Schlage BE469 deadbolts. This led to a few "phantom" devices that had to be removed during my numerous attempts. But that was a while ago. It looks like the Z-Wave stack failed around 2:37am last night. Looking at logs, that appears to be the last message received from any devices.

You could well have a very hosed up mesh due to a combination of all of these factors. Our next release will have a number of Z-Wave improvements, including with respect to ghost nodes. My suggestion would be to wait for that, or to rebuild your Z-Wave from scratch, with no Iris repeaters, only secure Z-Wave for locks, and no custom drivers. Follow the guide here: How to Build Your Z-Wave Mesh.