Extended warranty is for hardware failures. Your case is not indicative of a hardware failure, and replacing the hub is unlikely to fix the issue you are dealing with. However, we are sending you a replacement hub. Please be on the lookout for emails confirming the shipping of your replacement.
I saw your post on another thread so jumping back in here. Have you updated to the most recent platform? Go to your network settings and turn off the periodic bonjour restart. Not sure if it will make any difference.
Also after the hub has been up for at least 12 hours, go to the Logs > App Stats / Device Stats pages. Turn on all the display settings and it should be sorted by % of busy by default.
Post a screenshot of the top dozen or so, including the stats at the top, should fit in one screenshot.
Oh also go to the past logs and filter by error logs, post a screenshot of recent errors, then do the same for warn logs.
Thanks for the follow-up! I am up to date (2.3.9.193) and turned off bonjour restart, fingers crossed!
There were a few shades I changed drivers yesterday that broke some rules which I have since fixed this morning.
Nothing seems out of order there 
I say this with true appreciation for your help... I think I have tried everything. Literally sat in front of logs (z wave and regular) for 2+ hours trying to find out what it could be. Tearing the three leftover hairs on my head out!
Are you still seeing this?
Not so much. Of my 100+ deviecs, 90% have less than 1 reroute, 10% have 2-10, and a couple devices have 20+. One is my lock which others have posted has many reroutes but doesnt impact mesh, another is a devices that is pretty isolated in the attic.
That seems normal for 24hr+ of uptime.
The alternate power supplies you tried, they were at least 2A? The Pro comes with a 2A supply.
The only other things I can think to try would be:
- Get a zniffer setup, to absolutely determine if there is some sort of excessive z-wave traffic clogging the radio or not. You have to re-flash a USB stick with a special firmware.
- Reset the radio and test a clean radio. If you have hub protect you could run a cloud backup before resetting and then turn off the automatic backup. This would in theory allow you to go back to how you were before but it is risky.
- Buy another hub on Amazon, test clean hub with a few devices. If no issues migrate to new hub and test. If it does not work out you have 30 days to send it back.
In process of doing #3, migrating back to my C7. I had processing issues and some far out devices had trouble connecting, so if I hub mesh it and use the processing power of the C8 pro for all the rules/internet devices, I should be OK. I saw another thread that proposed that maybe something with all the devices connecting directly causes issues with a heavier load on the hub's antenna? May try to get a zniffer setup to see If I can help others.
Thank you for all the help!
Seems unlikely, there are some regulars on here with a very large number of devices and I remember when the C8 first came out all the people showing off how many devices had direct connections. Its not like it maintains an active connection with all the devices, not like a Wifi signal. It is not really a "connection", it is a route. When the device is not active there is nothing transmitting between the hub and device, for all the hub knows the device is offline. Having a device route through another node does not take any strain off the hub. The hub still has to receive and process any transmissions whether it comes directly from the node or via an intermediate hop. The z-wave radio is still aware of and keeps track of all z-wave nodes. Zigbee I think is a little different because the radio really only pays attention to the directly connected nodes, that is maybe where someone got the idea.
To follow up, splitting to two hubs seems to have solved the issue. I dont know why it works, but I have increased from 80% commands working to closer to 99%. My original intent was to slowly move everything back to the C7 and let the C8 Pro run all the rules and internet connections. But after I moved all the FLIR shades and battery devices over, everything is markedly more stable.
There are still lost commands but its so few and far between, I can completely accept it. I still have a high number of redirects for my lock, mostly from the hub that has all the FLIR devices. That doesnt translate to any functionality lost.
Maybe if I get bored one day, or if it becomes less stable, I may try completely moving back to the C7 like my original plan.
My guess is that it was mostly the blinds for whatever reason. I have 4 locks on my mesh with no issues. High route changes for FLIRS seems to be normal at this point for all the z-wave details pages I have seen. I think every time the hub tries a command cold (and usually fails) and then retries with the beam first it is counting it as a route change.
You may noticed reduced battery life on any sensors that are further out, as they probably do not have any repeaters to use. Any low activity sensors I would definitely consider moving back to the main hub.
Quick sidebar question:
What is FLIRS?
I thought it was a thermal imagining system.
Didn't think that was applicable to lock devices.
(I did a search: all I saw was thermal imaging stuff.)
Thanks.
Basically any battery device that needs to Receive commands that require immediate action will be FLiRS. Locks, Thermostats, and Blinds are the most common. Sensors only send commands typically, so it is not needed for most battery devices.
Found this: https://www.intin.no/wp-content/uploads/2020/02/zwaveflirs.pdf
Googles AI Overview is pretty good too:
Z-Wave's FLiRS (Frequently Listening Routing Slave) technology allows battery-powered devices to have long battery life while still responding quickly to commands. FLiRS works by having devices alternate between sleep mode and a partially awake mode, where they listen for a wake-up signal from a controller or other device. When a device receives the wake-up signal, it fully wakes up and can communicate with the controller.
Here's how FLiRS works:
Wake-up signal A controller or other device sends a special beam signal to wake up a FLiRS device.
Partial wake The FLiRS device listens for the wake-up signal at a rate of once to four times per second.
Full wake When the FLiRS device receives the wake-up signal, it fully wakes up and can communicate with the controller.
Sleep If the FLiRS device doesn't hear a wake-up signal, it goes back to sleep mode.
FLiRS devices include battery-powered devices like door locks, thermostats, and window blinds. A good Z-Wave network design ensures that a beaming device is always near a FLiRS device.
3 Likes
It just doesnt explain why the issues seem to only happen on a c8 pro, not the c7. I still have some issues, just less frequent. If there was a way to migrate connections to the c7, I would probably test it. Just too much work given thats its much more stable.
Good idea about the battery devices, thanks for the advice. So far they are actually closer than the original hub.
