I've been having an issue recently that I think I have narrowed down to Lutron/Hubitat. It seems that when I'm controlling scenes, or multiple lutron dimmers at once it is printing an exceedingly long delay before the action occurs. It generally does occur, but may take 15 seconds. At the same time if I utilize Google Assistant to issue the command, I frequently get a 'having trouble reaching Hubitat' message. Looking at my logs I'm not seeing any errors. It appears that that once the action shows in the logs it happens reasonably quickly, but there is often a sizeable delay before it shows in the logs.
It seems, with limited testing, that controlling an individual Lutron device is happening at a normal pace.
For my Lutron devices I only use Lutron scenes as then all I have to do is send the single button command from Hubitat and then the Lutron hub takes care of all my Lutron devices e.g. I have a “Goodnight” scene setup on Lutron that will turn off lights, turn off fans that are not needed and then dim other lights to be used as nightlights.
Just switched to including Lutron scenes in my Hubitat scenes to try and sped things up (I have a few Hue bulbs in the scenes as well). That's actually what gave away the issues. Since instead of agressive popcorning as the lights come on now the whole Lutron scene is delayed.
As a separate, much more minor issue I'd be curious of best practices for integrating hue like that, to minimize that popcorn effect, but truly it's secondary to the massive delay I'm now getting and the google warning.
