I started using this feature for a number of reasons but after a short amount of time, the condition would show a "?" instead of the expected time. When this happens, the condition stop working. How would someone go about preventing the malfunctions or is there another way to test a device's state of a period of time?
I would suggest sharing a screenshot of your rule and the output from "Logs" (with all logging enabled, of course), when this problem happens. There may be clues there. I have not heard of this happening before so don't have any ideas offhand.
Any chance this is an IRIS V1 device?
No. I do not have any IRIS devices. Fibaro motion sensors Ecolink garage door sensors are the devices I'm having issues with.
I reported similar behavior but thought it was limited to IRIS V1 devices. You may want to submit to bravenel. He said they may look into it and perhaps could get more attention since it's not V1 related in your case.
The first condition is all the sensors in home while the zone sensor includes the same sensors in the first condition. There's probably a better way that does not involve Time Since Event
I'm not sure if there is still a still a question here; if so, I'd again suggest sharing the suggested log entries. That seems like it should work.
This is an actual occurrence of the feature malfunctioning by not keeping the time. So, since the time is not being tracked, the rule condition is now nullified.
My suggestion if you're using a condition that is likely to exceed the event history stored for the device (which is what Rule Machine checks for here; it does not track anything itself) is to find another way to do it. Keeping similar logic, you could have another rule that triggers on this device event that sets a hub variable to the current time, then use that in a similar comparison instead. Or you could probably simplify the logic in this rule a bit by setting a hub variable, even just a boolean, to a specific value if the door stays closed for more than 15 minutes, which it seems is the only threshold you care about (or just skip the hub variable entirely and set Private Boolean on this rule since you aren't using it for anything else and it's already there).
Sometimes, it's also possible to re-write these rules and trigger with the "time since" device instead, though that would require some thought, whereas either of the two above options are pretty simple. Other alternatives would be increasing the history for this device (on the device detail page) so this is less likely to happen in the first place, or figuring out why it's generating so many events if this is not an expected number.
Thank you for the awesome response with gives options to my dilemma. I did attempt saving time and then compare the difference but ran into complications in how to properly compare the date and time. One rabbit hole involved conversions before and after calculations. It's not as easy like Webcore when I was using smartthings.
Webcore is also available on Hubitat (built in now, but either option works) if you prefer.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
