Presence Trigger Stopped Working

I have a couple of simple presence trigger-based rules to switch my HVAC into "Away" mode when I leave the house (and regular program when I return), because the occupancy sensors in my thermostat (Ecobee) often don't register that I've left for almost an hour, needlessly continuing to run the HVAC.

Those presence-based rules were running just fine for about a month. Not perfect every time, but I would say at about 98%. Then I left for my other home for just over a month. I returned to this home a few days ago and the presence-based triggers weren't triggering anymore. I left & returned home maybe 6-8 times over the past few days - no presence triggering at all.

I checked the app to ensure the geofence was active, and that it knew where I was - whether inside or outside the geofence - and that all was working. My iPhone was also fine - no issues with location services or anything like that which might prevent the geofence from knowing my location. I rebooted my iPhone anyway. I then updated my hub with the latest platform version. Still no resolution. Finally, yesterday, I thought I'd check the rules themselves even though nothing had changed, and then clicked the button to "Run Actions" just to make sure. The rule ran successfully, sending me the notification that "I left the house" and then switching my thermostat to Away mode. But, suprisingly, after manually running that rule, the presence triggers immediately started working again...perfectly (I've been in/out of my home about four times since and every depart/arrival event triggered its corresponding rule).

Just wondering if anyone has any ideas as to why it took me manually running the rule for the presence trigger to start working again. Seems odd that, if the presence trigger hasn't triggered for 4-5 weeks, it just stops functioning, and that the only way to wake it back up again is to manually run a rule that utilizes a presence trigger.

I wonder if the DB maintenance procedure would have freed up 'something' that was keeping the triggers from running.

Does running a rule trigger the DB Maintenance procedure, or does that happen with a reboot and/or nightly? Because the presence triggers weren't working for several days, including after I ran a platform update which obviously reboots the hub.

They're continuing to work reliably now. I have each departure/arrival event send me a notification - my intent was to monitor the functionality of the geofence until I felt confident it was working reliably. However, after this unexpected "interruption" I guess I'll leave the notifications active, or I wouldn't otherwise know if the presence triggers stop working again. :neutral_face:

1 Like

It's a manual only operation. As far as I know, platform updates would not trigger it nor would just running a rule. For triggers to fail the system would have to ignore the hardware event OR it's already being handled so don't process a 'duplicate'. I don't think the first one is likely. The database keeps track of such things. One possibility is that the power went out while the presence event was being handled and it was never marked as 'completed' so after power up booting it was stuck thinking presence events were happening so anything new could be discarded until they finished. That 'completion' only happened when you manually ran the rule, much much later. THIS IS ONLY speculation.

The DB maintenance is Settings->Reboot, check Advanced options will give you a check box to rebuild the DB.