My house isn't very large. Nothing could be over ~40 feet from the hub. I have issues with devices much closer than that.
Busy zwave network could cause it but thats usually a failed pair which you said you don't have or power reporting spamming.
Note: I believe the only non plus things I have are 5 door locks.
I mentioned non plus because they don't report status updates.
Yep. That's exactly why I have a box of about 20-30 non-plus switches in the basement on my junk table. 
I think S0 is more chatty than S2 also.
Looks like I have 8 S0 devices (not sure why my loft multi-sensor is S0--I thought it was S2).
19 "none"
1 "S2 Access Control" (Door lock) plus, of course, the hub itself.
35 "S2 Authenticated"
It may be S2 and just joined as S0. You'll need to rejoin it to get it to connect as S2 since that is done during the pairing process.
Have you checked your hub stats? There may be a clue there...
http://hubitat.local/hub/stats
http://hubitat.local/hub/enableStats
http://hubitat.local/hub/disableStats
Enable stats and let them run for a few minutes then pull up the first link to view the stats. Disable them when you're done.
You can use these links by replacing the app id or device id to take you to the offending app.
http://hubitat.local/installedapp/configure/APPIDHERE
http://hubitat.local/device/edit/DEVICEIDHERE
2 Likes
Device Stats enabled: true
Device stats start time: 1601922767885
Device stats total run time: 132008
device id 77 runcount 10 total runtime 59 average run time 5.9
device id 1185 runcount 2 total runtime 18 average run time 9
device id 1985 runcount 4 total runtime 123 average run time 30.75
device id 1281 runcount 4 total runtime 44 average run time 11
device id 1857 runcount 4 total runtime 75 average run time 18.75
device id 2498 runcount 1 total runtime 23 average run time 23
device id 2691 runcount 4 total runtime 59 average run time 14.75
device id 2243 runcount 4 total runtime 105 average run time 26.25
device id 388 runcount 4 total runtime 80 average run time 20
device id 329 runcount 4 total runtime 36 average run time 9
device id 1825 runcount 4 total runtime 45 average run time 11.25
device id 1762 runcount 4 total runtime 45 average run time 11.25
device id 1314 runcount 4 total runtime 43 average run time 10.75
device id 1378 runcount 4 total runtime 95 average run time 23.75
device id 610 runcount 2 total runtime 1612 average run time 806
device id 652 runcount 11 total runtime 65 average run time 5.9090909091
device id 1729 runcount 2 total runtime 22 average run time 11
device id 1409 runcount 2 total runtime 36 average run time 18
device id 1921 runcount 3 total runtime 40 average run time 13.3333333333
device id 1793 runcount 2 total runtime 20 average run time 10
device id 1794 runcount 2 total runtime 31 average run time 15.5
device id 2051 runcount 1 total runtime 26 average run time 26
device id 2179 runcount 1 total runtime 11 average run time 11
device id 2437 runcount 1 total runtime 10 average run time 10
device id 2629 runcount 1 total runtime 10 average run time 10
device id 326 runcount 2 total runtime 30 average run time 15
device id 327 runcount 2 total runtime 36 average run time 18
device id 394 runcount 2 total runtime 20 average run time 10
device id 395 runcount 2 total runtime 54 average run time 27
device id 2081 runcount 3 total runtime 137 average run time 45.6666666667
device id 389 runcount 2 total runtime 263 average run time 131.5
device id 1313 runcount 2 total runtime 25 average run time 12.5
device id 1505 runcount 2 total runtime 29 average run time 14.5
device id 1889 runcount 1 total runtime 7 average run time 7
device id 1377 runcount 2 total runtime 35 average run time 17.5
device id 1697 runcount 1 total runtime 7 average run time 7
device id 418 runcount 2 total runtime 15 average run time 7.5
device id 2274 runcount 2 total runtime 37 average run time 18.5
device id 2659 runcount 2 total runtime 115 average run time 57.5
device id 419 runcount 2 total runtime 53 average run time 26.5
device id 1253 runcount 2 total runtime 22 average run time 11
device id 1254 runcount 2 total runtime 26 average run time 13
device id 1092 runcount 3 total runtime 78 average run time 26
device id 2369 runcount 2 total runtime 53 average run time 26.5
App Stats enabled: true
App stats start time: 1601922767889
App stats total run time: 132022
app id 195 runcount 13 total runtime 454 average run time 34.9230769231
app id 1 runcount 14 total runtime 1954 average run time 139.5714285714
app id 1456 runcount 5 total runtime 173 average run time 34.6
app id 376 runcount 40 total runtime 3692 average run time 92.3
app id 37 runcount 2 total runtime 67 average run time 33.5
app id 1058 runcount 1 total runtime 802 average run time 802
app id 396 runcount 42 total runtime 2898 average run time 69
app id 421 runcount 84 total runtime 5242 average run time 62.4047619048
app id 1155 runcount 83 total runtime 5259 average run time 63.3614457831
app id 737 runcount 1 total runtime 1269 average run time 1269
app id 398 runcount 1 total runtime 56 average run time 56
app id 391 runcount 1 total runtime 66 average run time 66
Nothing looks terrible but what are these two devices and app? Assuming cloud devices by the times.
Dev 610 - Group: All Inside Lights
Dev 689 - Garage Ceiling Light Parent (GE/Jasco Motion Sensor/Dimmer, JasonJoel's driver)
App 737: aaTestApp ("On: Group: All Inside Lights")
The stats page is interesting--what do the various things mean (so I know what to watch for)?
What about 389?
Device Stats enabled: true
true means stat collection is running false means its disabled
Device stats start time: 1601922767885
This is what time stat collection started in some funky way I cant decipher but the hub knows what it means.
Device stats total run time: 132008
This is how long the stat collection has been running.
device id 77 runcount 10 total runtime 59 average run time 5.9
Device ID number is the device that it is talking about
Runcount is how many times that device has been triggered during the collection
total runtime is time in milliseconds that all of the runtimes added up to.
average runtime is the average runtime for each triggered execution on the device.
Same goes for the app stats but for apps.
And, after that was done, the following did NOT turn on (after a refresh to to make sure the status was right):
Basement Ceiling Lights
Basement Room Ceiling Light
Dining Room Lights
Fireplace Ceiling Lights
Guest Bedroom Closet Light
Kitchen Ceiling Fan Lights
Laundry Room Light
Loft Lamp
Note: I typo'd -- I meant 389, not 689.
If you spaced out the on triggers does it complete?
This rule turns off about 150 devices.
1 Like
In that specific case, I ran the "least likely" to work well method.
But, when I do them about 3-5 at a time, spaced out, with refreshes, I still have some that don't behave. I had 2-4 this morning, I believe. My "Set At Home" app runs when I disarm and several lights were off (I didn't do a thorough audit--I just drove it again to get things in shape).
I'd take out those refreshes. That's a lot of commands all at once. I'd also enable group on/off optimization so it isn't sending on's or off unnecessarily. Clump devices into groups of 5 or 6. Leave out ones you are doing specialized things to like setting dimmer/fades and such.
Those refreshes actually seem to help more than hurt.
The hub seems to not properly track status all the time, so it thinks things are on or off when they are the opposite.
I added those to help make sure the status is correct before sending the commands because, otherwise, things were not acting right even more frequently.
As you can see, I tried to put delays in there to space those refreshes out--and to allow them to complete before taking actions.
