This is a quick run after you enable it and watch the stats.
3 Likes
I wish the device/app id are hyperlink so you can go directly to that device/app. Hard to track down which device it is just from the ID.
1 Like
You can always go to http://[hubIP]/device/edit/[deviceID#]
Not that hard
http://[HubIP]/device/edit/[DeviceID]
http://[HubIP]/installedapp/configure/[AppID]
This is a diagnostic tool. Probably not even supported. At this point its better than nothing. I also don't think its something you would run all the time, just enable it to capture some data and then disable it again.
2 Likes
Found this jewel while skimming some black hat onion forums....
Advanced HTTPS Configuration
http://HUB-IP/hub/advanced/certificate
You can insert your own SSL certs here
7 Likes
Just as an FYI on this feature
1 Like
Whatever
I was posting for the sake of others.... who might not be as technically inclined
1 Like
Updated with HTTPS, Zwave Repair, and latest backup URL.
Keep 'em coming!
Finally a way to spot the high flyers in terms of resource usage (and potentially solve the mystery of why some hubs slow down and others don't). It may have taken two years but the kimono has finally been opened... Thank you HE!
Cursory takeaways after a very brief app stats run time of 1094770:
App with highest average runtime (4X that of the next highest), highest total runtime (and 3rd highest runcount): Hub WatchDog. I guess the Schroedinger's Cat phenomenon appiles here. Time to look away...
Other apparent hotspots:
App with highest runcount: HubConnect, no surprise. Runner up: WebCoRE. But amazingly, since it runs the bulk of my automations, the 2nd lowest average runtime of the 30 apps tracked during this interval.
Device with highest runcount and 2nd highest average and total runtimes: Iharyadi's Environment Sensor (my favorite Temp/Humidity/Lux sensor and great Xiamoi parent router). Genuine surprise here. I have two of these.
Device with next highest runcount (and highest total and average runtime) Zooz Powerstrip. No shock there (pun intended).
Time to start some rigorous observations.
Guessing the time is in milliseconds. Looks like the sleep number app is my biggest hog.
Device Stats enabled: true
Device stats start time: 1599067459576
Device stats total run time: 1357779
device id 549 runcount 21 total runtime 164 average run time 7.8095238095
device id 1250 runcount 38 total runtime 276 average run time 7.2631578947
device id 1058 runcount 45 total runtime 2043 average run time 45.4
device id 807 runcount 23 total runtime 206 average run time 8.9565217391
device id 244 runcount 51 total runtime 2627 average run time 51.5098039216
device id 245 runcount 51 total runtime 2648 average run time 51.9215686275
device id 246 runcount 51 total runtime 2768 average run time 54.2745098039
device id 37 runcount 3 total runtime 18 average run time 6
device id 1249 runcount 10 total runtime 81 average run time 8.1
device id 806 runcount 23 total runtime 174 average run time 7.5652173913
device id 1218 runcount 97 total runtime 611 average run time 6.2989690722
device id 1219 runcount 97 total runtime 558 average run time 5.7525773196
device id 1220 runcount 97 total runtime 530 average run time 5.4639175258
device id 1221 runcount 97 total runtime 483 average run time 4.9793814433
device id 1222 runcount 97 total runtime 498 average run time 5.1340206186
device id 1223 runcount 97 total runtime 461 average run time 4.7525773196
device id 1224 runcount 97 total runtime 443 average run time 4.5670103093
device id 1225 runcount 97 total runtime 459 average run time 4.7319587629
device id 906 runcount 2 total runtime 69 average run time 34.5
device id 920 runcount 18 total runtime 86 average run time 4.7777777778
device id 916 runcount 36 total runtime 1548 average run time 43
device id 193 runcount 2 total runtime 41 average run time 20.5
device id 76 runcount 14 total runtime 140 average run time 10
device id 239 runcount 10 total runtime 236 average run time 23.6
device id 69 runcount 1 total runtime 17 average run time 17
device id 770 runcount 2 total runtime 7 average run time 3.5
device id 531 runcount 2 total runtime 84 average run time 42
device id 529 runcount 2 total runtime 87 average run time 43.5
device id 34 runcount 2 total runtime 100 average run time 50
App Stats enabled: true
App stats start time: 1599067459580
App stats total run time: 1357782
app id 993 runcount 37 total runtime 1178 average run time 31.8378378378
app id 929 runcount 40 total runtime 1074 average run time 26.85
app id 1192 runcount 47 total runtime 9966 average run time 212.0425531915
app id 205 runcount 46 total runtime 12062 average run time 262.2173913043
app id 1060 runcount 7 total runtime 515 average run time 73.5714285714
app id 1031 runcount 20 total runtime 1842 average run time 92.1
app id 367 runcount 50 total runtime 1218 average run time 24.36
app id 17 runcount 37 total runtime 395 average run time 10.6756756757
app id 147 runcount 5 total runtime 872 average run time 174.4
app id 1065 runcount 25 total runtime 26532 average run time 1061.28
app id 273 runcount 2 total runtime 162 average run time 81
app id 1126 runcount 18 total runtime 2516 average run time 139.7777777778
app id 1204 runcount 2 total runtime 92 average run time 46
app id 514 runcount 2 total runtime 112 average run time 56
app id 1203 runcount 1 total runtime 30 average run time 30
1065 is the SleepNumber App
Looks like the only slow stuff is the web based stuff which I expected.
I expect it was running a test while stats were on. I would hope 5 seconds would be the longest thing running (I’m assuming synchronously). It didn’t show up for me, but wasn’t running a test at the time. I only ran it for a minute.
Yes, the picture may certainly look different over a longer observation period. Hence the need to go about this in some kind of structured fashion. It's great to have the ability to see what levers can be pulled and compare the outcomes.
1 Like
I'm sure someone will come up with some sort way to prettify it into an app.
Relative to my post above, these were my high flyers:
App stats total run time: 1094770
Apps:
runcount 78 total runtime 202420 average run time 2595.1282051282 << Hub Watchdog
runcount 202 total runtime 10063 average run time 49.8168316832 << HubConnect (ST Client)
Devices:
runcount 78 total runtime 1565 average run time 20.0641025641 << Environment sensor
runcount 60 total runtime 2256 average run time 37.6 << Zooz Powerstrip
Also: Memory GREEN 481476
Looking forward to seeing what I can tune here, now that I easily gauge my progress.
I'd turn down the frequency rate on Hub Watchdog until you start having problems. Mine runs every 3 hours.
I wonder why your power strip is so much higher avg run time than mine.
device id 1218 runcount 97 total runtime 611 average run time 6.2989690722
device id 1219 runcount 97 total runtime 558 average run time 5.7525773196
device id 1220 runcount 97 total runtime 530 average run time 5.4639175258
device id 1221 runcount 97 total runtime 483 average run time 4.9793814433
device id 1222 runcount 97 total runtime 498 average run time 5.1340206186
device id 1223 runcount 97 total runtime 461 average run time 4.7525773196
device id 1224 runcount 97 total runtime 443 average run time 4.5670103093
device id 1225 runcount 97 total runtime 459 average run time 4.7319587629
Fast is good for making pretty graphs but if it impacts your hub you're kinda shooting yourself in the foot.
Lol, for sure. That jumped out at me like a sore thumb... but probably with a granularity of minutes rather than hours. Actually I'm going to disable it entirely for a while to see what kind of uptime the latest firmware can provide. I only started using it when the need for some kind of objective measurement of the progressive slowdown phenomenon became critical, last Fall.
Yea I only ramp it up to minute increments when I'm troubleshooting something. I keep it at 3 hours so I can still watch if it starts trending up. .142 has been stable for me. Haven't had to reboot and not currently trending up in delay.
