I think you can look up those device ids.
They're pretty low compared with my new ones, lol.
So you have six 18770's and one 20304.
edit: maybe it's the device id no.
One is the mfr model, I think.
Any time I leave my Z-Stick paired after clearing a ghost I get massive issues with my Z-Wave network (whether powered on or not). That anecdote could be completely wrong regarding your issues, but you may want to try excluding it to see if it clears up any of your issues.
2 Likes
un pairing the z wave stick seems like low hanging fruit. I'll do that first and see what happens. I admittedly did have it unplugged for a while, but have never unpaired it. Setting up simplicity studio is a PITA so I didn't want to risk having to re-set that up again.
Yep. Exactly the same reason that I had left mine paired in order for me to give you that advice. However, I started noticing problems pretty rapidly, and then they went away pretty rapidly after I excluded it.
feeling pretty dumb, can't figure out how to exclude it, there are no buttons on it
Thanks all, I'll give this a go for a while with the stick excluded. If it freezes up again I'll start looking into my GE/Jascos. I appreciate you all, I'll update this as it develops in case others have the same problem!
3 Likes
Sounds good. Let us know in a day or two if things have stabilized.
I would also recommend going to Settings Zwave and pull up the Zwave logs. Let it run for a bit and see if there is a device that is spamming the network more than others. You are looking for constant updates from a device. I have had a few devices over the years do this and they have gone in the trash.
2 Likes
Yeah, also, the bad GE/Jascos are the old ones; not sure of specifics.
If someone wants to look up those Jasco device IDs this is where I look: https://devices.zwave-js.io/
First you have to convert the decimal number from HE to hex, you can just use google "12343 in hex". Then you search on that site above typing the hex in this format 0xHHHH where HHHH is the hex string padded with leading 0's to be 4 bytes.
3 Likes
I am having the exact same problem and have been fighting it for weeks. I have no idea why my zwave is very very sluggish and I have to reboot the hub several times a week. I am at a loss myself. I haven't changed anything other than firmware versions and it was stable for a long time.
Well, the zooz stick wasn't the problem. I froze up twice over the weekend. Going to start by disabling. I converted everything I could to LR (basically some battery powered contact sensors and temp sensors I have in my freezer) and removed some older Aeon labs devices that are quirky somtimes, not sure what else to do except start removing devices 1 at a time and let it sit a week or so, starting with my remaining jascos & homeseers
One weird thing to add - scenes that are triggered by a switch still work when the z-wave is frozen, just seems that scenes that FIRE z-wave devices won't trigger. Examples of 3 things that work or don't work when I'm "frozen"
- I go in my storage room (which has poor light) and flip on my zooz z-wave switch manually. Well, my goveen light strip that is all around the room DOES turn on. So that zooz switch is reporting back and firing.
- if I click my "basement lights off" button my tablet, that same zooz switch will not respond.
- If sunset arrives, none of my z wave switches respond to the trigger that turns certain outside lights on at this time.
So weird. I would expect NOTHING z-wave to work, but it just seems that rules that control z-wave devices stop working.
Again - nothing amiss in the logs.
Sounds like inbound comms work but outbound (from hub to devices) is what stops working. This has been an issue that has come up a few times recently.
I believe it is just one possible outcome of the radio getting overwhelmed.
Can you post the red/blue topology map from the z-wave details page?
Looks pretty sparse for some nodes.
The 100+ ignore, those are Long Range
I was most interested in the 01, which is the hub. It mostly looks OK but all the devices with red in 01 means those devices do not see the hub as a neighbor, so they will not try direct routes. Further, some of those devices only show blue in 1-2 other devices meaning they have very few route options. Might not be related to your issue at all but may be causing other issues. Could even be causing excess re-routing, which can lead to performance issues.
1 Like
Silly question(s), as I am learning things just by following the thread. Is the "1##" ID range reserved for LR?
Second, if the above is yes, does that mean that the two above (and to the left of) 100 are NOT LR and have no connectivity to anything? Would that not be an issue as well? (The two I am talking about are AF and 80)
Correct and correct, and those two nodes I do not see in the screenshots above.
Those two nodes could be new failed pairings or something.
Overall mesh looks pretty sparse. Surprised by the number of devices that do not see the hub. That is probably causing a lot of extra stress. Also looks like its almost 50/50 sensors to repeating devices.
@fleetmack is it possible the hubs location is causing signal interference?
1 Like
