Other "damage" from the migration to Z-Wave JS were:
Two 800 series LR devices (in LR mode) that went into Pending state in Z-Wave Details. Both devices were battery powered sleepy devices that when woken up would successfully signal the hub (per Z-WaveJS logs) but the hub said timed out when trying to respond.
One 800 Series (Leviton) in mesh mode that lost it's S2 security settings. The device did respond to direct hub control within the device's own page but quit participating in any app based manipulation (eg Switch bindings, Google Home, etc...). Excluding and re-including the device in mesh mode again with security fixed the problem. Note: Leviton 800 series do not support LR mode.
It took quite a while (an hour-ish?) and several rounds of waking up all sleepy devices (other than the two mentioned above that had to be re-added) to get the hub back in working order.
Did you wake them, or did you just mean that they were sending events to the hub? Waking up is a specific Z-Wave process, and it is normal for at least secure devices not to fully function until then.
You can actually change the post location by editing the topic title...click on the pencil next to your title and you can change the location of the post.
Either leaving it here or moving it is fine, totally up to you. Obviously more people will see it in the normal categories.
Did you wake them, or did you just mean that they were sending events to the hub? Waking up is a specific Z-Wave process, and it is normal for at least secure devices not to fully function until then.
I am referring to the formal wake-up Z-Wave process using the device's "wake up" button sequence.
