Ok … I turned on z-wave logging on all z-wave devices and i have that running now …
yes - i just hit that button ..running now … for last 20 min - so far, only INFO no errors or warnings …
There will be no errors or warnings. Feed those logs to an AI engine and use it to figure out how your zwave mesh is performing. The more you feed it, the better its analysis will be.
Personally, I’ve had a good experience using Gemini.
If you feel like trying it, I would be curious to know if this app surfaces any hints (it may not): hubitat/HubDiagnostics/README.md at main · hubitrep/hubitat · GitHub
In particular, check the Network, Health and Performance tabs (the Radio Capture tab also provides a means to capture and download the Z-Wave logs for feeding to your favourite LLM).
Well … things are looking up. Nothing really in the z-wave logs. After I removed the UZB stick - AND following Ricks instructions power down (again) the hub - let it sit … and restart … It was great all the remainder of yesterday and is perfectly fine this morning. Plus before I could NOT get lock code manager working with the new lock and now the lock responds fine and lock code manager works fine too.
Knock wood - let’s call this … good -
Oops - I forgot to add - AI did note one z-wave dimmer plug was chatting somewhat excessively … my wife complained a couple days ago it wasn’t dimming properly - it refused to go above 10 percent. So I swapped that out as a precaution - not sure that it was a CAUSE but I am not risking anything right now …
Was it a GE/Jasco switch?
No - it was a leviton z-wave dimmer plug
Thanks for the tip … I need to learn more about this program. It did find a failed z-wave entry for some z-wave shades i have been struggling with. After I “fixed” my problems I had to do an exclude and readd these shades … It seemed to work right - the z-wave settings no longer showed it … but hubitat hadn’t QUITE gotten rid of it … on reboot it appeared on the home page cause it wasn’t in a room - so i could delete it there … confusing I know suffice it to say it’s all good now and this does look like a tool worth learning.
Well - I spoke too soon. After working ok yesterday, this morning initially once again z-wave performance gone / non existant. Definitely good mesh, no ghosts, I ran z-wave logging last night I am about to feed that into AI. Hub light is on and green, but the hub / app itself was VERY slow / non responsive about an hour ago - but now the hub is accessible again (but z-wave still crappy).
AI summarized my z-wave logs as this …
Overall, the vast majority of your mesh looks beautifully healthy, but there are two notable entries to look at closely:
1. The Dynamic Routed Device: dev:712 (Highly Active) (zooz z-wave motion sensor)
On pages 1, 3, and 5, dev:712 is quite active. Looking closely at its routes, it is consistently bouncing between different multi-hop paths to get back to the hub:
-
It frequently routes via
repeaters: [0x3e, 0x15]at 100 kbps with a103mstransmission time. -
It occasionally drops down to
speed: 40 kbpsviarepeaters: [0x3e]with a144mstransmission time. -
Its entries show
routeChanged: truequite a few times.
What this means: routeChanged: true isn't a failure—it means the mesh is actively doing its job. Because dev:712 is likely a bit further away from the hub (indicated by it needing 1 or 2 repeaters), the Z-Wave stack is dynamically shifting paths to find the most efficient route. Its transmission times (around 100ms–140ms) are completely fine for a routed device, so as long as it isn't lagging in real-world performance, its behavior is normal and healthy.
2. The Slow Direct Device: dev:267 (zooz zen 04 plug -aways away from hub)
On pages 2 and 4, dev:267 shows up regularly.
-
It is hitting the hub with
repeaters: None(direct route). -
However, it registers a latency of
1021msto1022msand listsspeed: Unknown.
What this means: When a direct device takes over a full second to communicate and shows an unknown link speed, it usually means the hub is having to re-transmit the packet multiple times before it finally gets an acknowledgment (ACK).
-
If it's a battery-powered sensor: It might be sleeping right as a message finishes, or it's an older Z-Wave non-Plus device.
-
If it's a main-powered switch/plug: It might be positioned right on the physical fringe of your hub's direct RF range, causing packet drops that require retries.
Summary Checklist
-
dev:633Removal Success: The network is completely clear of the rapid-fire per-second clutter. Bandwidth is wide open. -
dev:712: Standard, healthy mesh routing behavior. Nothing to worry about. -
dev:267: This is the only device experiencing notable latency (1 second delay). If you notice this specific device ever being sluggish to respond on your dashboard, you might want to look into its placement or see if a nearby line-powered Z-Wave Plus device can act as a better repeating neighbor for it down the road.
Everything else in these logs—like dev:912, dev:62, and dev:1094—is operating flawlessly at a blazing fast 1ms direct speed!
Notthing jumps out to me in the logs.
Right now, I think my plan will be to shut down my c8 pro and reinstall my C7 which was just decommissioned in May. The changes to hubitat since i onboarded the C8 pro were …
- Added z-wave extender to help devices on my lower level (4800 sq ft house)
- Added 4 z-wave smartwings shades
- Replaced yale Z-wave door lock with newer one
I am going to add the z-wave extender AND the door lock to the c7 and run it for awhile see if it exhibits any issues. If not - then …. factory reset c8 pro and try migration over from scratch?
Sorry I closed this thread out hopefully hubitat staff will look at this
The silabs software using a z-wave stick allows direct access to the z-wave database.
Did you consider switching back to ZWave-JS ? I thought I read here somewhere that the logging is more detailed/useful with JS.
Yup. Sure is.
When I was in the early stages of these problems, I DID switch to JS … things got worse - I didn’t know why at the time (still don’t) but I got spooked.
I think there is either something wrong with the hub itself or related to the recent additions I had of 4 smartwing z-wave blinds and a new Z-wave lock. The thing that got me today is EVERYTHING on that C8 pro went to heck - no response for 1/2 hr or so then it came back but was sluggish. Nothing in the logs other than info or low impact stuff.
I have my old c7 hub back up and running now I am going to let this run for next several days and if it is fine, do a factory reset on the C8 and redo the migration and see what happens.
Thanks - I HAD seen that … I had made the adjustments they recommended. For now - on my redeployed C7 hub, I wont run those blinds or the new lock I added for a week or so … reduce the number of variables. Then just add one thing - wait a few days - and if ok, add another.