[Solved] All Z-Wave Switches Stopped Reporting Current State

🛎️ Get Help
21

No, there have been other similar cases but I never connected the dots to think about the association being blown up.

You can just try configure on other drivers as well to see if it fixes it, some do the lifeline association and some do not.

You can also use this driver/tool: [RELEASE] Z-Wave Universal Device Scanner . You just switch to that driver temporarily and it has a special command button to set the association. You do not need to run any of the other commands there (but they wont hurt anything either if you want to try it out).

When you switch back to your regular driver just run configure again on the normal driver.

If you have any battery devices impacted you would need to wake the device manually then press the command button ~2-3 seconds later.

1 Like
22

Let us know if the lifeline repair also fixed your other devices. Really curious to confirm for sure if that was the actual issue. Very strange and I have no idea how it could have happened.

1 Like
23

Will do. I will try this evening and update the thread.

24

Well...Darn. I tried it on a Zooz ZEN32 and a GE (Jasco) Smart Motion Switch. No effect. He problem persists.

ZEN32:

image
image1923×1116 486 KB

Jasco Z-Wave Motion Switch:

image
image1257×808 158 KB

25

It may be worth mentioning, on the ZEN32, I tried configuring with both the System Driver as well as the Community Driver linked on the Zooz website.

26

Did you run the "Lifeline Association" command button with my scanner driver? That is the one I know for sure will fix it. I don't see anything about lifeline in the second screenshot

On your first screenshot I can see your lifeline is screwed up.
image

I am guessing you somehow set one of those USB sticks your paired as the lifeline for every single device.... Just checked, you sure did, here is your lifeline, so the devices are/were sending their reports to this node:

image
image910×51 21.6 KB

:point_down: :point_down:

1 Like
27

Yah. Don't I feel sheepish. You said that. I screwed it up.

On both on both the ZEN32 and the Jasco Z-Wave Motion Switch, I changed back you your driver. I set the Lifeline Association to Single Channel. Hit configure. Switched it back to the original driver. Hit configure. Waited a minute. Everything worked like you said it would :grin:

Thanks for tolerating the amateur hour over here.

2 Likes
28

Awesome!
I have no idea how you managed to set the USB stick as the lifeline, something in PC Controller I am sure. Lesson is not to click random things in PC Controller :face_with_raised_eyebrow:

3 Likes
29

Ok. For the good of the broader Hubitat community, I am going to put my ignorance on full display, with the hope that it may assist someone else in the future :laughing:. As you read this, bear in mind, while today I'm a Z-Wave amateur, when I first started a few years ago, I REALLY didn't know what I was doing.

As you pointed out, I had four ghost nodes on my network. One "GENERIC_TYPE SWITCH_BINARY" and three "SPECIFIC_TYPE PC_CONTROLLER". I could not figure out how to get one particular "SPECIFIC_TYPE PC_CONTROLLER" removed from my network. The others removed exactly as described on the Ghost Node Removal instructions.

After seeing your comment, I popped the Z-Wave stick back into my computer to do some more investigating. When I selected that device within the ZWaveControllerUI app and clicked "Is Failed", it would not go to "Failed" status, therefore I could not remove. I looked closer.

It didn't fail because it was still communicating on my Z-Wave network.

Given that I have had to manually remove a Z-Wave stick from my network several times before, I assumed that is what this device represented.

I found the "fingerprint mfr: "008B", prod:"5441"". After some googling, I found this:

XL1050 – Z-Wave Alliance Product Catalog

At some point, years ago (when I was much dumber), I added my thermostat to my network (clearly, I had forgotten this). At the time, I didn't understand that this was a controller or that it joined this Hubitat Z-Wave network as a secondary controller. I was able to remove it via the normal exclusion process.

Now we know why, of the multiple Z-Wave networks in my home, only this one was affected. There is a part I still don't understand. Why now and why only physical switches? Maybe we will never know. Maybe it doesn't really matter. If we could get to the bottom of it, it might assist in keeping me or someone else from making another bonehead move like this in the future.

3 Likes
30

Interesting, I have seen another thermostat that was a controller as well. I think we found instructions on how to join it as a node instead of a controller and got it working for the person.

I guess at some point recently that thermostat decided it was going to be in charge and set all the switches lifeline association to itself...

2 Likes
31

New lifeline troubleshooting process will start with:

  1. Do you have a Z-Wave thermostat? :wink:
2 Likes
32

Last update: I had a chance, this morning, to address every device with a known issue on this Z-Wave network. The fixes are as follows:

All devices are back to working as expected

Thank you again @jtp10181 for the attention and assistance.

4 Likes
33

This thread is marked as solved because re-establishing lifeline as described by @jtp10181 solved the issues described by @user2315