All ZWave devices disappeared

[aamann]

Last night all my Z-Wave devices stopped responding. Checking the hub’s Z-Wave details, the list of devices is completely empty (and yes, Z-Wave is enabled).

Any way to fix this or has the radio died (any way to confirm that?)

[aaiyar]

@aamann

Any way to fix this

Power down the hub. Wait 30 seconds. Then power it back up again.

Note: power down != reboot

[aamann]

Thank you! You just saved me heart from major palpitations!

[rlithgow1]

What do your logs say at the time you lost the z-wave radio? Any indications of what might have caused it?

What does your z-wave details page look like?

[aamann]

I don’t know the exact time when it stopped responding but going back through the logs I can find this:

sys:12023-02-13 20:41:36.037warnZ-Wave Network responded with Busy message.

[rlithgow1]

Anything surrounding that? Post your z-wave details page in it's entirety

[aamann]

These couple messages around it - then nothing for a couple of minutes in either direction:

Here is the Z-Wave details page (in chunks, sorry, printing to create a PDF does only print a small subsection):

I have yet to manage to get the repeater (0x25) back to being active which would improve the network significantly…

[aaiyar]

Nothing egregiously wrong with your z-wave network, outside of 0x25 possibly being a ghost node. You should try to confirm that it is not a ghost.

However, multiple devices have multi-hop routes. That's not great vis-a-vis response time.

[aamann]

The topology would be much better if 0x25 would come back online - it's a repeater up in the attic in the midle of the house…

[aaiyar]

You should consider excluding it, and re-including it.

[rlithgow1]

In addition to what @aaiyar says about excluding/including, I would also re pair everything you have (except door locks and garage openers) without encryption. It creates unnecessary overhead on the mesh and really isn't needed. It would certainly improve things for you. Overall though your mesh looks good.

[coreystup]

To respectfully disagree with @rlithgow1 , if you aren't using motion lighting or don't need instantaneous response, I would leave S2 devices on S2. Especially with all many as you have on 40 kbps links. The additional CRC checksum in data transmission is worth it, IMO. I pair all my devices that support S2 with it enabled and I have no issues.

But I'm in the minority here.

[aamann]

The repeater satrted to show up again - as a new device. Now I have a ghost device at the old address that does not want to delete (not to worried about that other than my OCD…). The mesh is slowly starting to optimize around the repeater. When all is done, all S3 devices should be back on 100kbps links and I didn't have any issues with that for a couple of years so I'm going to leave them as-is (not using motion lighting).

Thanks for everyone's help - things are back up and running and humming along nicely. I'm just glad this happened while I was a home so I actually could reboot the hub…

[aaiyar]

@aamann

Now I have a ghost device at the old address that does not want to delete (not to worried about that other than my OCD…).

This is going to be an issue. Power down the repeater (so the hub cannot reach it). Then remove the ghost. Then shut the hub down, plug in the repeater, and power everything back up again.