I started with a C7 and have migrated to a C8Pro. I have always had spotty Z-Wave. Sometimes things work fine and I get quick responses. Other times things are very slow (more than a min for a device to respond to a command from the device page on the hub). I feel like I have a great spread of wired devices (almost all Zooz) in plastic electrical boxes so my mesh should be good. I have replaced a chatty T-stat and stopped using thermostat controller because of the volume of traffic that was adding (see my other posts about that) to see if any of that would help.
There's an awful lot of route changes on some of those devices, but I guess that depends on how long the hub has been up to accumulate that number.
Also some low RSSI readings, is the hub well placed centrally or are they just distant devices?
Is there a reason for using S2 Authenticated inclusion on the motion sensors as the usual advice is include without security except for locks, alarms and garage doors etc? I'm not sure how much impact that will cause but imagine there'll be a lot more traffic.
If you dont need the temp to within 0.5 deg I would bump that to 10, If you are not using the lux to a fine degree, I would bump that to at least 25. Motion clear delay could be bumped to 30 unless you find it impacts your automations. Set the Group 1 reporting to Notifications Only (this cuts messages in half).
Your locks seem to have a high message count. Do you have a lot of automations relating to the locks that you are sending them a lot of commands?
What is the Device Monitor app doing? Is it possibly sending a lot of refresh commands?
Maybe turn on debug logging for the Garage lock, then go to Logs > Scheduled Jobs and find the "LogsOff" schedule for that device and delete it. This way debug logging will stay on.
Lets see what turns on up there, we will see if the device is being very chatty for some reason.
Deadbolt Garage is the least used deadbolt and the farthest lock from the hub. I have enabled debug logging and deleted the job to disable it. How long would you like me to wait before posting it? Here is just a simple unlock and lock using the device page:
I was just thinking to check it over a day and see if there is any unusual activity. Just doing some quick math based on about 3 messages per event, looks like around 4 activations per day which I guess is not unreasonable if the lock was used daily.
Every time the hub has to send a command to a lock it will send a first try, which usually fails, then it sends a FLIRS wake beam which will jam up the mesh for up to 60 seconds. The device will wake up then they can talk. This happens for each lock if you are commanding multiple at a time.
So, if you are doing refreshes via Device Monitor and Device Activity Check you may want to par that down to just one app. I know that DAC will only refresh if the device looks to be inactive, not sure what the other app does.
I have 4 z-wave locks on my mesh as well, when I first added them I did have some struggles but after learning more about how they work and impact the mesh I have dialed them in over time.
Oh also if you are wanting to command multiple locks at once, I would recommend using the system mirror app with a lock mirror. It is like making a lock group, you mirror a virtual lock to multiple locks and the app will select which devices need to be commands, do them one at a time and it will also try them more than once.
Sorry looking at the stats again, I am leaning more towards the ZSE40's causing the issues. Not only do they have a lot of route changes but also a lot of errors. The locks are normal to see route changes and yours do not have the errors like the motion sensors do.
The errors could be corrupted messages getting rejected do to the S2 error checking.
Do you have the antenna on the C8 both perpendicular to the ground? That is how they work best.
Are the ZSE40 in any sort of positions or mounting that could be causing interference?
I will check the Mirror app for deadbolt locking. I am using auto lock now to lock them after time so there should not be more than 1 or 2 unlocked when mode would change to away and a lock any unlocked deadbolt would be triggered via a basic rule. I also have Reliable Locks app sitting in front of rules or dashboard usage of the locks (I will not put that in front of the Mirror app).
C8 Pro factory antennas are straight up and down in relation to the horizon. I would not think the mounting is an issue for the Motion sensors. They are mostly in a room corner at the ceiling junction with the wall. Wood studs and drywall construction (house built in 1986)
Living Room - line of sight (same height as the hub) 18'
Dining room - line of sight 20'
Flex - 3 2x4s and two pieces of drywall 21' (right next to the dining room one)
Garage - Several walls - guessing 45'
Laundry - Several walls - guessing 32'
Kitchen - below the hub through one wall 4'
Yeah not a bad idea. Can see if the changes to the ZSE40s has made a difference or not.
Lock does not look bad, nothing out of the ordinary based on your rules I assume. Just be aware with the locks every time you see a "refresh()" or "lock()" command in those logs the hub is probably sending the FLIRS beam which I explained above. But it should only have an impact for 30-90 seconds if the device responds.
