This thread is unrelated to slowdown of hubs, but an attempt to get speedy rules
If it's one thing that we notice, it's walking into a dark room, and waiting for the lights to turn on. So frustrating. Then I read this:
After reading Bruce's post about RM's runtime overhead, it got me thinking. All my lighting rules were in Rule Machine. I had also previously created my own zone motion sensors (in rule machine) and then developed large lighting rules in Rule Machine, so all my lighting logic went through Rule Machine effectively twice. I've not been happy with the snappiness of the rules for motion. So, I created a test by using the inbuilt Motion Lighting app to turn on the lights. I then logged the data and compared the results (simultaneously).
My tests results show that Rule Machine is nearly a 1.2 seconds slower than Motion lighting. The Rule machine logic is going through rule machine twice, (once: my own zone motion controller rule, and two: the Rule Machine lighting rule itself) so it's probably not a fair comparison, and since the Motion Lighting app gets to the gate first, it's getting through the gate much earlier (which may then also slow down the Rule machine processing).
So, what I've done is use Motion Lighting simply for turning on the light quickly, and disabling all other Motion Lighting commands for off (via selecting all modes for disable off). I'm turning off the lights via my normal Rule Machine rule for that room.
I plan to do this for all my lighting rules - using the inbuilt Motion Lighting app for quickly turning on the lights, and nothing else. Alternatively, if anyone can put together a tiny/speedy lighting app that only turns on lights via a few selectable motion sensors, that might work too.
Hope this helps.