C7 Intermittently Hangs on Z-Wave

Hello,
I migrated from a very stable ~50 device z-wave network on ST G2 in late December because of cloud issues and dislike of the new app/where that platform was going and the enthusiastic community here.

My last 4-5 months have been rough. My C7, now at 2.2.7.122 has issues where commands on the z-wave radio just don’t seem to go through, it’s like the z-wave radio intermittently hangs. I can see where Webcore or Homebridge send the commands, but my z-wave radio seems to sometimes ignore commands. Nothing I do seems to improve it.

I’ve shut down all power/voltage/temp monitoring on my Inovelli Red and Zooz devices to relieve network congestion.

Hard power down, remove power for 30 seconds seems to help for some time, but within a few days commands just don’t register. The hub is responsive from the web side, but my z-wave side seems to “freeze-up” and it’s not always the same device that hangs, it can be almost any device on the network.

Issues are especially evident when I have homebridge send a “good-night” sequence to shut 20-30 lights/switches off, lock doors, etc.. Sometimes 2-10 random devices just don’t shut down, but wait a second, send a command to that device again, or log into the HE web interface and it will shut down that device.

I’m really struggling here. I reached out to support, who after a couple of emails referred my email to the engineering team, then closed the ticket.

  • A Z-Wave mesh of 45 devices that grew and was stable in ST G2 for ~3 years
  • I do see many Re-Routes/New Routes in my logs on the C7
  • My PER’s are all 0, but after a couple of days but I rebooted 12 hours ago.
    I’ll see 3-4 devices with 2-5 PER errors every few days.
  • I predominantly run Webcore and Homebridge (Tonesto 2.X) and some other apps to mirror lights / RGBW strips
  • RTTI’s are all low but for a couple of devices on the fringe of my network
  • Security is none for the vast majority of devices, I do have a Schlage lock and 3 leak sensors running S0, and a 4 devices running S2

This instability has gone beyond simple debug, my setup is just unstable and I’m at a loss on trying to figure it out.

This has caused me to lose trust in the device. ST G2 had it’s faults with cloud servers being down, but my C7 is worse on a much more frequent basis.

I really want this to be successful, but I’m at a loss on this one. Open to ideas and trying things,

Thanks everyone,
Jonathan

Can you post screenshots of your z-wave details page?

The details I’m looking for are routes, speeds, RTT, LWR RSSI, etc

Bryan,
Thanks for looking. I rebooted this morning after a firmware update, so I understand if this isn't super useful to you. I can give it some time to build history/traffic so the stats are more useful and repost in 24-48 hours...

Thank you sir,
Jonathan

I'll assume the table below is useless without some more time and post it again after 24-36 hours or runtime.

Node Stats
0x07 (007) PER: 0, RTT Avg: ms, LWR RSSI:
Neighbors: 16, Route Changes: 0
0x09 (009) PER: 0, RTT Avg: ms, LWR RSSI:
Neighbors: 17, Route Changes: 0
0x0A (010) PER: 0, RTT Avg: ms, LWR RSSI:
Neighbors: 6, Route Changes: 0
0x0B (011) PER: 0, RTT Avg: ms, LWR RSSI:
Neighbors: 17, Route Changes: 0
0x0C (012) PER: 0, RTT Avg: ms, LWR RSSI:
Neighbors: 22, Route Changes: 0
0x0E (014) PER: 0, RTT Avg: ms, LWR RSSI:
Neighbors: 18, Route Changes: 0
0x10 (016) PER: 0, RTT Avg: ms, LWR RSSI: 7dB
Neighbors: 15, Route Changes: 0
0x11 (017) PER: 0, RTT Avg: ms, LWR RSSI:
Neighbors: 30, Route Changes: 0
0x12 (018) PER: 0, RTT Avg: ms, LWR RSSI: -3dB
Neighbors: 37, Route Changes: 0
0x14 (020) PER: 0, RTT Avg: ms, LWR RSSI:
Neighbors: 20, Route Changes: 0
0x1C (028) PER: 0, RTT Avg: ms, LWR RSSI:
Neighbors: 39, Route Changes: 0
0x1D (029) PER: 0, RTT Avg: ms, LWR RSSI:
Neighbors: 21, Route Changes: 0
0x23 (035) PER: 0, RTT Avg: ms, LWR RSSI:
Neighbors: 8, Route Changes: 0
0x26 (038) PER: 0, RTT Avg: ms, LWR RSSI:
Neighbors: 22, Route Changes: 0
0x29 (041) PER: 0, RTT Avg: ms, LWR RSSI:
Neighbors: 6, Route Changes: 0
0x2A (042) PER: 0, RTT Avg: ms, LWR RSSI:
Neighbors: 26, Route Changes: 0
0x2E (046) PER: 0, RTT Avg: ms, LWR RSSI:
Neighbors: 17, Route Changes: 0
0x2F (047) PER: 0, RTT Avg: ms, LWR RSSI:
Neighbors: 24, Route Changes: 0
0x30 (048) PER: 0, RTT Avg: ms, LWR RSSI:
Neighbors: 15, Route Changes: 0
0x31 (049) PER: 0, RTT Avg: ms, LWR RSSI:
Neighbors: 25, Route Changes: 0
0x32 (050) PER: 0, RTT Avg: ms, LWR RSSI:
Neighbors: 28, Route Changes: 0
0x33 (051) PER: 0, RTT Avg: ms, LWR RSSI:
Neighbors: 5, Route Changes: 0
0x34 (052) PER: 0, RTT Avg: ms, LWR RSSI:
Neighbors: 24, Route Changes: 0
0x37 (055) PER: 0, RTT Avg: ms, LWR RSSI:
Neighbors: 18, Route Changes: 0
0x38 (056) PER: 0, RTT Avg: ms, LWR RSSI:
Neighbors: 14, Route Changes: 0
0x3A (058) PER: 0, RTT Avg: ms, LWR RSSI:
Neighbors: 15, Route Changes: 0
0x42 (066) PER: 0, RTT Avg: ms, LWR RSSI:
Neighbors: 13, Route Changes: 0
0x43 (067) PER: 0, RTT Avg: ms, LWR RSSI:
Neighbors: 10, Route Changes: 0
0x45 (069) PER: 0, RTT Avg: 1ms, LWR RSSI: 2dB
Neighbors: 17, Route Changes: 1
0x46 (070) PER: 0, RTT Avg: ms, LWR RSSI:
Neighbors: 7, Route Changes: 0
0x49 (073) PER: 0, RTT Avg: ms, LWR RSSI:
Neighbors: 14, Route Changes: 0
0x4A (074) PER: 0, RTT Avg: ms, LWR RSSI:
Neighbors: 4, Route Changes: 0
0x4B (075) PER: 0, RTT Avg: ms, LWR RSSI:
Neighbors: 3, Route Changes: 0
0x4C (076) PER: 0, RTT Avg: ms, LWR RSSI:
Neighbors: 3, Route Changes: 0
0x4D (077) PER: 0, RTT Avg: ms, LWR RSSI:
Neighbors: 28, Route Changes: 0
0x50 (080) PER: 0, RTT Avg: ms, LWR RSSI:
Neighbors: 33, Route Changes: 0
0x51 (081) PER: 0, RTT Avg: ms, LWR RSSI:
Neighbors: 5, Route Changes: 0
0x57 (087) PER: 0, RTT Avg: ms, LWR RSSI:
Neighbors: 31, Route Changes: 0
0x60 (096) PER: 0, RTT Avg: ms, LWR RSSI:
Neighbors: 6, Route Changes: 0
0x61 (097) PER: 0, RTT Avg: ms, LWR RSSI:
Neighbors: 11, Route Changes: 0
0x64 (100) PER: 0, RTT Avg: 2ms, LWR RSSI: 13dB
Neighbors: 17, Route Changes: 1
0x72 (114) PER: 0, RTT Avg: ms, LWR RSSI:
Neighbors: 8, Route Changes: 0
0x73 (115) PER: 0, RTT Avg: ms, LWR RSSI:
Neighbors: 7, Route Changes: 0
0x74 (116) PER: 0, RTT Avg: ms, LWR RSSI:
Neighbors: 10, Route Changes: 0
0x75 (117) PER: 0, RTT Avg: ms, LWR RSSI:
Neighbors: 11, Route Changes: 0
1 Like

Yea, you are right.. I need more of that data filled out..

One more thought - 2.2.7 has improved z-wave drivers for "Plus" versions of dimmers / switches. I find my system works better with these "plus" drivers dimmers / switches than the old ones (at least I think it does and it probably wouldn't hurt to give them a try). You may need to manually switch over.

So, for example, if your devices are the "Z-Wave Plus" version and you see it using a driver like "Generic Z-Wave CentralScene Dimmer", switch the driver to "Generic Z-Wave Plus Scene Dimmer" (note the new drivers have the word "Scene" in their names where the old ones said "CentralScene"). Similarly "Generic Z-Wave CentralScene Switch" becomes "Generic Z-Wave Plus Scene Switch". You'll know your devices are the "plus" version if the "inClusters" listed on their web page (in the Data area) has a 0x5E.

@bcopeland, @jvm33,

I appreciate everything here. Thank you so much.

  1. Z-Wave Info below with some time under it's belt
  2. I had a glitch last night where I can see my homebridge (Tonesto) App told my lock to lock at 10:24 PM, yet the lock never seemed to get the command. Send the command again at 10:38 PM via the same app and the lock responded within a second.
    (Detailed Post in the homebridge thread as I work to debug:
    [RELEASE] Homebridge Hubitat v2.0)

Sorry for the long logs posted as tables in here. If there's a better way to share these, please let me know...

-Jonathan

1 Like

Which node is your lock and what model / driver is it using?

That's a lot of route changes.

One more question.. Is your lock using S2 or S0 ?

Hi Bryan,
The lock is 0x57 (087) (Schlage) and sadly it's running S0 -it's an older model).
JD

RSSI: -9 dB.

:-1:

1 Like

@JasonJoel and yet that node is 15-17' in direct line of sight to the deadbolt...

It is also not zwave plus. As such you may need to do a few repairs on that node to encourage it to choose a better route to the hub.

Not sure if the routing improvements included in 2.2.7 apply to non-plus nodes. Maybe Bryan will correct me on that though.

1 Like

My understanding is repairs do nothing for battery operated devices, but Bryan is the expert...
Thank you and thank everyone for trying to troubleshoot. It is so much appreciated.

Not on a C-5. But you have a C-7, don't you?

It should..

FLiRS (LSS) devices like your lock can be repaired normally.. Non-listening battery devices get updated Node Neighbors / routing updates every 14 wakeups (1 week for most devices)..

Now this device being non-plus, do you have good beaming capable mains powered repeaters nearby?

3 Likes

Hi,
I have a Aeotec 7-Series Extender on mains about 6' from the doorway with the deadbolt. The spec. sheet says its beaming compatible...

On that same note, my routing doesn't show it taking any hops at all:
Routing shows: 01 -> 57 40kbps

Also, it's not always this device that gives me grief of being intermittent. I'm also not opposed to throwing some $ at it and buying the upgraded z-wave board for the lock (or replacing it altogether).

https://products.z-wavealliance.org/products/3699/pics

-Jonathan