What if any is there a limit on how many rule machine rules you can have I have about 25 rules and as of late the rules are firing as they were before any suggestions on what to look for.
Thank you
I'm sure there's some theoretical limit related to the database they're stored in, but that would likely be in the tens of thousands at a minimum, so the practical answer to your question is "no." 
To troubleshoot, you'll need to provide more information if you want help, otherwise you could be dealing with a device problem, a rule problem, or some combination. This document may help you get started:
1 Like
I can't make out what the problem is as described. Could you give a little more info?
Before what? Do you mean they are still fine, or there's now a problem?
If you're having a problem, it's not due to the number of rules. My current Rule Machine rule count is 104, but it used to be more and there still wasn't a problem.
I had them firing fine then recently I added HomeKit intergration through hubitat and limited only cameras to homebridge, and i started noticing that some of the rules that are motion based are misbehaving I will have to go through them and see if I can find a common issue.
You mean you are using the motion sensor capabilies of HomeKit Secure Video in your rules? What does misbehaving entail?
Wait, what? Why? Use Homebridge or use the built-in HomeKit integration. Don't use both.
Not using HomeKit for any rules only using hubitat, I have restrictions of some of the rules. Here’s an example of a simple rule it should not turn the lights off after the restricted time. Should it. So sometimes it works fine and others it will shut the light off even when the restriction says it shouldn’t it. I may have something incorrect here,. Not sure
The light will still turn off, if the trigger turned the light on before the required expression was True, and the sensor went inactive after the required expression was False, because your rule says to wait for the motion sensor to become inactive, which it will regardless of the restriction. Your required expression cannot stop the motion sensor from changing to an inactive state.
I'd use a conditional action here and include the required expression range with a cancel and exit rule, else wait for event. But others can probably offer a better way to do it.
I tried using my cameras for triggering lights, but it got complicated when the lights would turn off and the camera took that as motion activity. There may have been a way to deal with that, but I turned back to using the dedicated motion sensors for lighting triggers.
FWIW
I have well over 100 with no issues.
I will give that a try Thanks for the input
You could also turn on this Required Expression option
Your rule will only trigger between Sunset and Sunrise but will cancel your Wait and keep the light on if it become later than Sunrise
1 Like
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
