Hello, I’m trying to understand why my Mobile Companion on Android sometimes fires two states (home, not_home) within milliseconds - effectively triggering two main automations I have, one for when I’m leaving/away from home and one for when I come back. The bad news is that such behavior is random, as I have not yet found a way to reproduce it systematically.
Here is an example where area changes happened within 0.001s:
| entity_id | state | last_changed |
|---|---|---|
| device_tracker.oneplus_8t | home | 2026-04-04T23:20:00.000Z |
| device_tracker.oneplus_8t | not_home | 2026-04-04T23:24:04.196Z |
| device_tracker.oneplus_8t | home | 2026-04-04T23:24:04.197Z |
| device_tracker.oneplus_8t | not_home | 2026-04-04T23:24:29.155Z |
On the case of this specific logs here - home > not_home > home > not_home - the correct execution should have been a simpler home > not_home, after leaving the configured area/home (defined with approx 0.5mi / 800mt).
Instead it fired a quick not_home, home when I was still well within the boundaries of my home; I was just firing up the engine of my truck.
I noticed similar behavior on opposite direction, in other words when I come back: hot_home > home > not_home > home where the two in the mid (home > not_home) get fired within milliseconds.
Any idea where to look ?
Unsure if it’s a bug or something