I recall reading that thread. And I looked it over again, but didn't see conclusive proof that there is a bug or something in this app.
It doesn't seem to affect everyone, there are only a few complaints about this, not some widespread thing like today's ever popular topic - Zwave issues.
So I wonder what is different about yours (and a few others) Lutron installation. Again that brings me back to something unique to your installation like network issues, or maybe some other hub slowdown problem or another app consuming resources.
Have you ever done a "hub statistics" and see if something is chewing up hub resources?
Yep, that is exactly how I have the two devices I show above are handled. I even put the button controller screenshot above to prove that is what I am doing.
I believe this same question was pasted in the following thread, but not sure if @Eric.C.Miller ever successfully tested the two SmartBridge Pro concept...
Here are the Device Stats for the last 5 minutes. I made sure to go use the Picos during that time as well.
Device Stats enabled: true
Device stats start time: 1607980589348
Device stats total run time: 365787
device id 34 runcount 43 total runtime 640 average run time 14.8837209302
device id 1005 runcount 5 total runtime 60 average run time 12
device id 1153 runcount 24 total runtime 13302 average run time 554.25
device id 1154 runcount 11 total runtime 19 average run time 1.7272727273
device id 1004 runcount 6 total runtime 136 average run time 22.6666666667
device id 10 runcount 18 total runtime 71 average run time 3.9444444444
device id 24 runcount 10 total runtime 116 average run time 11.6 (this device is controlled by a Pico)
device id 25 runcount 8 total runtime 131 average run time 16.375 (this device is controlled by a Pico)
device id 169 runcount 3 total runtime 48 average run time 16
device id 292 runcount 5 total runtime 15 average run time 3
device id 258 runcount 4 total runtime 44 average run time 11
device id 769 runcount 16 total runtime 337 average run time 21.0625
device id 260 runcount 12 total runtime 75 average run time 6.25
device id 1008 runcount 3 total runtime 109 average run time 36.3333333333
device id 1011 runcount 1 total runtime 8 average run time 8
device id 1009 runcount 1 total runtime 20 average run time 20
App Stats enabled: true
App stats start time: 1607980589355
App stats total run time: 365790
app id 115 runcount 11 total runtime 171 average run time 15.5454545455
app id 965 runcount 38 total runtime 8389 average run time 220.7631578947
app id 967 runcount 3 total runtime 135 average run time 45
app id 4 runcount 36 total runtime 626 average run time 17.3888888889
app id 904 runcount 9 total runtime 481 average run time 53.4444444444
app id 109 runcount 5 total runtime 112 average run time 22.4
app id 108 runcount 5 total runtime 121 average run time 24.2
app id 747 runcount 8 total runtime 7961 average run time 995.125
app id 577 runcount 4 total runtime 347 average run time 86.75
app id 5 runcount 1 total runtime 6 average run time 6
app id 5 runcount 22 total runtime 184 average run time 8.3636363636
app id 612 runcount 4 total runtime 820 average run time 205
app id 613 runcount 4 total runtime 935 average run time 233.75
app id 483 runcount 1 total runtime 264 average run time 264
1153 is an Amazon Echo Flex.
965 is a Somfy Shade
747 throws back an error.
Ok so acknowledge that these devices are eating resources, but I do have to point out that his problem started way before any of these devices entered my mesh. The problem is about 1yre old and these devices are only 1 month old (approx).
I would see if you can somehow optimize these apps, or maybe pause the app or device just to see what happens.
I recognize that you have had issues with this before adding these devices, but you can never quite tell if they might be making it worse unless you try a few things.
The stuff you labeled as Lutron was only 11 and 16 milliseconds, so there is no appreciable delay in that particular part of the code.
What is the app ID of your Lutron hub? You can browse to the app itself and see the ID in the address bar of the browser.
I will ask again though, what does your home network look like? Are the Hubitat and Lutron hubs on the same network switch or router? They have reserved addresses? What brand/model is your networking equipment?
I have mine on a TP link too, so that is probably a good sign. Different device, but far as I know no known issues like there seems to be with Netgear and maybe a couple others.
Ok, those apps that are reporting high usage is the Ecobee Suite Manager and the Amazon Echo, both Cloud devices which generally talk way too much). Just added that one last week. But yes, I can pause it for now to see if there is any change.
Could this be a setting or an old version I'm working with on the Lutron hub? I know there aren't many user accessible settings on that thing, however, the more I think about this, the more I think it HAS to be a problem with the Lutron hub and not HE. Everything running through HE including the Lutron stuff works instantly. Its only when I need to send and return at the same tim e through the Lutron hub do I run into issues.
The only thing I see in the Lutron app is on the Settings > Help and it lists version 7.4.2.The Lutron app itself from on the Android Play Store is at also 7.4.2, so I don't know if the hub firmware has a version we can see or not?
Might be worth calling Lutron to see if they can tell if your hub is updated.
I don't have logging turned on, but otherwise looks the same as your screenshot. I was mainly wondering if one of the apps in your screenshot above that had the high times was Lutron. But it looks decent. In fact 17ms runtime is pretty good all things considered.
I would (without any other way to tell) concur with this conclusion. The Hubitat side of things seems to be good far as the Lutron stuff goes. I would try that longer test, but if the Lutron app, devices, and so on are all sub 100 milliseconds (WAY less actually), I doubt Hubitat is the problem here.
