Power glitched, yesterday, now I have this....

[ewkearns]

Any sage ideas on how to fix this with the least anxiety?

Tried: Rescan and Optimize with no luck....

[thymer]

Any sage ideas on how to fix this with the least anxiety?

Tried: Rescan and Optimize with no luck....

Did you try turning the breaker off to that switch, wait a sec, turn it back on?

[ewkearns]

That is my next thing to try..... though it has never helped, before.... when I lose a node.

[thymer]

That is my next thing to try..... though it has never helped, before.... when I lose a node.

It's about 50% for me although haven't had that issue in ages. That doesn't work and remove/add doesn't... time for a new one

[ewkearns]

I'm hoping some of the "you should never have to remove and add" folks will weigh in, here....

Here's a bit more from the log:

[RJS]

I had something similar happen during a power outage. I had to delete several nodes and re-add them. Since then I bought a UPS and use BLUPS plugin. I wrote an event to gracefully shut down the hometroller when the UPS gets below a certain level.

I should perform a live test on that but I'm hesitant. If it doesn't work, I may lose some z-wave nodes again. Mmmmm maybe for the test, instead of performing a shutdown, I could just play a mp3 file and test the shutdown operation separately.

- Robert

[macromark]

Any sage ideas on how to fix this with the least anxiety?

Tried: Rescan and Optimize with no luck....

Not a lot of info to go on here. Which version of HomeSeer and the Z-Wave plug-in are you using? What brand/model of switch is this? Which Z-Wave interface do you have?

Try a connectivity test and see if the node can be reached. If it can't, power-cycle or "air gap" the switch then try the connectivity test again. Does the switch have a number of neighbors?

[ewkearns]

Not a lot of info to go on here. Which version of HomeSeer and the Z-Wave plug-in are you using? What brand/model of switch is this? Which Z-Wave interface do you have?

Try a connectivity test and see if the node can be reached. If it can't, power-cycle or "air gap" the switch then try the connectivity test again. Does the switch have a number of neighbors?

HS3 Pro Edition 3.0.0.171 (Windows) (Will update as soon as I can figure out what is wrong with the updater.)
Z-Wave 3.0.1.2
Jasco On/Off Switch
Z-Net

Power Cycle has no effect, can't "Test Connectivity" or "Audit"
"Optimize" is as posted
9 Neighbors, Including direct

Note that the HS computer is on an UPS, so, no glitch there.... only the switch, itself. I've seen this happen since HS2 with a different computer and different Z-Wave hardware...

[Pete]

Power Cycle has no effect, can't "Test Connectivity" or "Audit" "Optimize" is as posted

This tells me that the node is dead. Remove it if you can and re associate it. My guess is that if you cannot remove it; then the node is dead.

Best then to quit spinning your wheels as dead is dead, replace the switch and maybe test the switch off line.

Sometimes when I have optimized the entire network and it misses stuff; an individual granular node scan does work better for me. I cannot say if this is the right way to do this; rather it is what I do.

I use my Leviton Remote Vizia RF remote to remove a node. Found out that any Z-Wave remote will do this with any Z-Wave node. I also assumed pairing was just one press with these devices and I tried multiple short presses and it would pair up right away.

It's a PITA. I configured my Z-Net devices one at a time using the RPi right next to the devices that I wanted to add or remove. That said I am currently testing a new Z-Wave + network with Z-Wave hot spares.

I also have paired one GE Z-Wave switch from some 40 feet away; which is the first time I have done this. It's a bit of a PITA but looks like you will have to move the Z-Net device to being close to the switch or maybe you can utilize wireless to do the pairing of the device?

If you do not see anything at the device level then my guess is that the device is just not working anymore.

It is odd that you see the node on a scan existing devices but not if you go directly to it. Here is what I see when I do the full scan of existing devices.
Maybe the glitch just messed with the device and database. Best still to try to remove it from the network close by the switch or to see if you can remove it.

Node: 19 Supports Class(es): SWITCH_MULTILEVEL, SWITCH_ALL, PROTECTION, POWERLEVEL, CONFIGURATION, VERSION_V2, MANUFACTURER_SPECIFIC, NODE_NAMING
Node 19 is Z-Wave version: Lib: 2.64 App: 3.16

Testing node connectivity on a network see:

Operational messages will appear here...
Obtaining a list of nodes to be contacted...
Node 19 (Node 19 Z-Wave Jasco Switch Multilevel Node 19) Successfully contacted.

[ewkearns]

Not a lot of info to go on here. Which version of HomeSeer and the Z-Wave plug-in are you using? What brand/model of switch is this? Which Z-Wave interface do you have?

Try a connectivity test and see if the node can be reached. If it can't, power-cycle or "air gap" the switch then try the connectivity test again. Does the switch have a number of neighbors?

See answers to questions.....

Bump!

[macromark]

See answers to questions.....

Bump!

Looks like a broken switch. If it is, all you can do is replace it.

[ewkearns]

I doubt it. Next week I'll try dragging the Z-Net out there to resurrect it.....

[ewkearns]

OK, I wanted to resurrect this issue. The problem was NOT, as I suspected, a broken z-wave node. I don't know what it was, because trying to troubleshoot z-wave, with the tools we have available, is like trying to see if the light went off in the refrigerator when you closed the door....

It appears that the zombie nodes I had and other non-performing nodes were taken care of by "Z-Health."

I'm not happy, because I don't understand WHAT happened, but I AM happy that it is resolved....