My Abode security system is connected to Hubitat. The "connection" consists of the Hubitat being able to read and set the mode (Away, Home, etc.) and the Hubitat being able to read only the activities that post to the Abode timeline.
To use the security system motion sensors to trigger lights in HE, motion needs to trigger an entry on the Abode timeline. However, when the security system mode is standby or home, the motion sensors don't trigger a timeline report. To resolve for this, and since the Abode has its own CUE automations, I set up a CUE automation to fire each time the motion sensor is triggered.
The problem is the Hubitat rule will only trigger the first time the motion sensor reports. After that HE does not see a change, so the rule won't trigger again. So I added an action to the Cue automation, which writes to the timeline. But there was alot of inconsistency in the Abode timeline reporting - sometimes the motion sensor reported first, sometimes the CUE action reported first. Since my setting is for HE to leave the lights on for 2 minutes, I set up Abode to end the CUE action after 1 minute (smallest Abode increment). That creates a distinct entry in the timeline 1 minute after the motion trigger. This seems to consistently send the unique motion trigger signal to HE, but I was wondering if there is a:
a. more elegant, streamlined (and hopefully quicker) way to do this using the Abode motion sensors?
b. way to make the lights stay on in HE as long as the Abode system is sending motion signals? Currently the lights go off after 2 minutes, even if there was another timeline entry trigger at 1 min 30 seconds.