ZWave Issues with Warranty Hub

[user2574]

I upgraded to a C8 Hub in January from my C7. I had all kinds of Zigbee Issues for months, and it was finally resolved by Hubitat with a replacement hub. It fixed my Zigbee issues 100%, everything worked solid.

Shortly after, I started getting ZWave issues. I will have all ZWave devices no longer respond every few days, or even every day. A reboot does not fix it. I get no logs in this state.

One of two things can fix it (temporarily):

1. Change Region to US-908.4 Mhz, 916 Mhz --> When done, I am still on US-LR (not the non LR region). However, usually devices work again after
2. Disable ZWave and Re-Enable. Works sometimes, but not others.

One sure way to break it is to just reboot the hub. Zwave will usually not work after a reboot until I change region or disable/Enable.

My ZWave was solid on the C7, Solid on my first C8, and then has had issues since the Warranty hub replacement. Original migration of ZWave to the Warranty hub had no issues, everything worked at first, started having issues by the end of the week.

I feel the Warranty hub has a ZWave issue.

I believe the ZWave Long Range update was actually released just after I got the hub. I don't know if that is the issue, but I cannot turn off Long Range (if I change region to NOT LR it always ends up back on LR. I don't know if it is my hub only or that is how it is working on all hubs, but I cannot change to the non LR region.

I can't help but assume the hub is bad (again). I have not had a stable system since I left the C7 in January of this year due to first Zigbee issues (WAS a hub defect) and now ZWave. Getting really old.

Edit: Zwave Repair does nothing, all nodes fail repair in this state.

[672southmain]

What firmware version? There have been several updates since January.

Like you, I had no Z-Wave issues on my C-7. Unlike you, I have had absolutely no Z-Wave issues on my C-8, which I got when it came out.

Have you turned in a warranty support case on the replacement hub?

[csteele]

I hate to ask the dumb question but since this is a Migration (C-7 to second C-8), is that original C-7 powered off? Your symptoms have an "interference" sound to them.

If it's not powered off, did you reset the C-7's ZWave radio?

[user2574]

I did put in a case just now. I do not see any firmware version showing on Zwave Details, nor an update button for firmware. Where is that hidden? I don't see anything in hub details either.

[hydro311]

For the ZW freq thing, that's normal -- the 8/8P will always use the option with LR (even though you can seemingly select the plain option). The plain option is used by C7 and below.

Unfortunately, that selection menu isn't dynamic by hub type -- it's understandably confusing.

ETA -- the LR selection doesn't hurt/affect anything if you don't want to use LR, but there's no way to actually turn off or disable LR on the 8/8P

[user2574]

So I guess it just "resets" the same frequency when I toggle this and ZWave starts working again? Not sure why that works to fix the issue for a bit.

[hydro311]

Sorry, that I don't know.

[user2574]

The C7 and the original C8 have been powered off. I did boot up the bad C8 once after migration to save my Webcore pistons, since I forgot to pause Webcore and it failed migration. I booted the old C8, it, turned off ZWave and ZigBee, saved a backup of the pistons, and shut down.

Then I went back to the current C8, restored my pistons from the file on the new Webcore install. I don't think that one boot up would have changed anything, ZWave was working when I got done with that when back on the warranty hub.

[csteele]

@user2574

The C7 and the original C8 have been powered off.

Excellent.. to my "ears" the situation where the ZWave Radio reinitializes would seem to put it as #1 to your mesh but over time, the "other #1" worms its way back. Clearly something else is going on, but that's my reason for asking.

To add to the diagnostic pool of clues, you could power off the C-8 and power on the C-7. If ZWave works then there's one more clue to suggest the C-8 is having a problem. That's assuming you didn't reset the C-7, ever.

[user2574]

@csteele

you could power off the C-8 and power on the C-7

I think I reset the C7, not sure. I would need to use it for a day or so to even know if ZWave had an issue there... it is so far out of date though, I wouldn't want to go there. I wouldn't expect any Zigbee stuff to work though.

[csteele]

I'm not suggesting a permanent rewind back to the C-7, just a 30-60 min test to see if just turning it one, (while the C-7 is off) will allow it to control ZWave devices without any special effort. It should still be the Controller (if you didn't reset).

The same would be true of your old C-8, yea, Zigbee would be back to failing, but does ZWave just burst back to life?

When you got the replacement C-8, did you re-migrate using the C-7 cloud backup? or did you create a C-8 cloud backup of the defective hub to push to the new C-8? I'm thinking that another re-migrate might result in a better outcome. You'd want to take a cloud backup of your C-8 before trying that, of course, so you'd have some ability to rewind back to "now".

[user2574]

I posted today, and opened the case, because ZWave is dying within an hour now after I get it back up.

It failed somwhere in this log recently.

dev:4842024-07-22 01:28:28.950 PMinfoseqNo: 127, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: 100 kbs

dev:572024-07-22 01:28:28.849 PMinfoseqNo: 121, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: 40 kbs, rssi: [-77 dBm, N/A, N/A, N/A, N/A], Ack channel: 1, Transmit channel: 1

dev:572024-07-22 01:25:13.865 PMinfoseqNo: 121, routeChanged: false, transmissionTime: 2ms, repeaters: None, speed: 40 kbs

dev:572024-07-22 01:25:13.764 PMinfoseqNo: 114, routeChanged: false, transmissionTime: 2ms, repeaters: None, speed: 40 kbs, rssi: [-77 dBm, N/A, N/A, N/A, N/A], Ack channel: 1, Transmit channel: 1

dev:572024-07-22 01:23:52.257 PMinfoseqNo: 114, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: 40 kbs

dev:3612024-07-22 01:23:03.050 PMinfoseqNo: 112, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: 100 kbs, rssi: [-77 dBm, N/A, N/A, N/A, N/A], Ack channel: 0, Transmit channel: 0

dev:3612024-07-22 01:21:58.140 PMinfoseqNo: 112, routeChanged: true, transmissionTime: 1ms, repeaters: None, speed: 100 kbs

dev:3612024-07-22 01:21:57.939 PMinfoseqNo: 111, routeChanged: true, transmissionTime: 1ms, repeaters: None, speed: 100 kbs, rssi: [-78 dBm, N/A, N/A, N/A, N/A], Ack channel: 0, Transmit channel: 0

dev:2024-07-22 01:21:01.569 PMinfoseqNo: 111, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: Unknown

dev:572024-07-22 01:18:31.315 PMinfoseqNo: 110, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: 40 kbs, rssi: [-77 dBm, N/A, N/A, N/A, N/A], Ack channel: 1, Transmit channel: 1

dev:572024-07-22 01:18:31.114 PMinfoseqNo: 109, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: 40 kbs, rssi: [-77 dBm, N/A, N/A, N/A, N/A], Ack channel: 1, Transmit channel: 1

[user2574]

What is this device with no device ID?

dev:4052024-07-22 01:34:59.815 PMinfoseqNo: 132, routeChanged: true, transmissionTime: 1ms, repeaters: None, speed: 100 kbs, rssi: [-85 dBm, N/A, N/A, N/A, N/A], Ack channel: 0, Transmit channel: 0

dev:2024-07-22 01:34:46.239 PMinfoseqNo: 132, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: Unknown

dev:4842024-07-22 01:32:49.777 PMinfoseqNo: 127, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: 100 kbs, rssi: [-85 dBm, N/A, N/A, N/A, N/A], Ack channel: 0, Transmit channel: 0

dev:4842024-07-22 01:28:28.950 PMinfoseqNo: 127, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: 100 kbs

dev:572024-07-22 01:28:28.849 PMinfoseqNo: 121, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: 40 kbs, rssi: [-77 dBm, N/A, N/A, N/A, N/A], Ack channel: 1, Transmit channel: 1

dev:572024-07-22 01:25:13.865 PMinfoseqNo: 121, routeChanged: false, transmissionTime: 2ms, repeaters: None, speed: 40 kbs

dev:572024-07-22 01:25:13.764 PMinfoseqNo: 114, routeChanged: false, transmissionTime: 2ms, repeaters: None, speed: 40 kbs, rssi: [-77 dBm, N/A, N/A, N/A, N/A], Ack channel: 1, Transmit channel: 1

dev:572024-07-22 01:23:52.257 PMinfoseqNo: 114, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: 40 kbs

dev:3612024-07-22 01:23:03.050 PMinfoseqNo: 112, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: 100 kbs, rssi: [-77 dBm, N/A, N/A, N/A, N/A], Ack channel: 0, Transmit channel: 0

dev:3612024-07-22 01:21:58.140 PMinfoseqNo: 112, routeChanged: true, transmissionTime: 1ms, repeaters: None, speed: 100 kbs

dev:3612024-07-22 01:21:57.939 PMinfoseqNo: 111, routeChanged: true, transmissionTime: 1ms, repeaters: None, speed: 100 kbs, rssi: [-78 dBm, N/A, N/A, N/A, N/A], Ack channel: 0, Transmit channel: 0

dev:2024-07-22 01:21:01.569 PMinfoseqNo: 111, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: Unknown

dev:572024-07-22 01:18:31.315 PMinfoseqNo: 110, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: 40 kbs, rssi: [-77 dBm, N/A, N/A, N/A, N/A], Ack channel: 1, Transmit channel: 1

dev:572024-07-22 01:18:31.114 PMinfoseqNo: 109, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: 40 kbs, rssi: [-77 dBm, N/A, N/A, N/A, N/A], Ack channel: 1, Transmit channel: 1

It brings me to "device Missing" Page from the log instead of a device

[rlithgow1]

Can you post your z-wave details page in it's entirety? Use windows snip..

[bobbles]

@user2574

What is this device with no device ID?

It could be a ghost I suppose.
Do you have any zwave devices in your zwave details page with no routes?
Maybe post it here for people to have a perusal over.

EDIT: What the post says above.......

[user2574]

[user2574]

Zwave is turning of in minutes now, the problem is much worse today.

I have been rebooting the hub, so I just did a shutdown to get a full power cycle. ZWave did not work when hub was back up. I also now have Hub Load Sever warning, and I have not had that issue before. Got ZWave working with disable/reenable, then it cut out right after.

I did the update settings things and just got it back again, it will not last long. Hub Load Sever is not going away, this is now a new issue

Edit: Hub Load Severe went away about 5 minutes after the power cycle

[jtp10181]

How is your C8 being powered? Sorry if this was asked before but I did not see it.
If not the OE supplied power block, you need to test with that for a baseline.

@jtp10181

Z-Wave Issues

For partial or total loss of Z-Wave control (radio seems dead), before doing anything else please shut down the hub from settings and unplug for 30 seconds, then re-plug to boot back up. This will allow the radios to fully power down and restart. A regular reboot only restarts the platform and not the radio hardware.

Z-Wave Details Page Docs: Z-Wave Details | Hubitat Documentation

• How is Hub being powered? Supplied power block or other (explain)
  • PoE power (with splitter) is known to cause major Z-Wave issues on the C-8 hub.
  • See this post for detailed write up on PoE testing: PoE and the C8 (with extensive testing)
• Provide screenshots showing entire Z-Wave details Page
• Provide screenshot of Z-Wave Topology Map (red/blue squares)

---

Also, all of those nodes with the "Discover" button need to be removed.

@danabw

Simple first steps - try these first

1. If a Discover button appears for a partially included device, selecting that button can allow a device to successfully complete joining the Z-Wave mesh.
2. Shut down the hub and restart it to force restarting of the Z-Wave radio - this can help w/ghost issues:
   -- a. Shut down your hub from the Settings menu.
   -- b. Then pull the USB power plug (recommended to do at the wall connection, not at the hub as the hub connection can be a little fragile, at least on some C-7 hubs) to completely remove power from your hub after it's shut down.
   -- c. Wait 30s
   -- d. Plug the hub in again.

Using the hub's built-in ghost removal tools
Below is a detailed summary from @jtp10181 of best way to use the hubs built-in ghost removal tools. Try these tools first before trying Ghost removal with a UZB stick:

• Click Refresh on the device ONCE, wait for the page to refresh. The Remove button should then appear. Click Remove ONCE. Again, wait. May want to have logs open while doing this as well.
• Sometimes it takes multiple tries of the Refresh button to get the Remove button to appear. Try to be patient and NOT click Refresh furiously. If you start getting "Zwave busy" error messages in your logs, power down and reboot again.
• It is common for it to take multiple tries at the Refresh/Remove buttons to remove a ghost, give it at least five or six attempts before assuming it's not going to work. Shutting down/restarting between successful removals can also help.

[user2574]

I removed my Ghosts. I did a 30+ second power cycle, and the Hub came back without ZWave working.

Disable/Enable did not fix it. I dId the change region and update settings trick and it got it working again for now.

I am at least the same place, or worse, where I was in this morning. Nothing has helped.

[jtp10181]

@jtp10181

How is your C8 being powered? Sorry if this was asked before but I did not see it.
If not the OE supplied power block, you need to test with that for a baseline.

@jtp10181

Z-Wave Issues

• How is Hub being powered? Supplied power block or other (explain)
  • PoE power (with splitter) is known to cause major Z-Wave issues on the C-8 hub.
  • See this post for detailed write up on PoE testing: PoE and the C8 (with extensive testing)