Recently Spotted is not set after addon start

[chas-iot]

After addon start, the Recently Spotted is not set until the phone goes out of WiFi range and comes back. However, the Minutes Ago is updating.

[chas-iot]

After more specific testing.
The main display state of the Thing is in an indeterminate state '...' until the 'Minutes ago last seen' exceeds 10 Minutes (which is the 'Time window' I use in the configuration). When the minutes exceeds 10, then the state becomes INACTIVE and when the phone is spotted again, the state becomes ACTIVE. If the phone is present, then the minutes keeps updating to mostly 0 and 1 but the main state remains ...
This happens both after a full gateway restart and also after disabling and enabling the addon.

[flatsiedatsie]

I think this is by design. If the system reboots, I don't want the addon to report a phone as 'gone' even though it might just not have re-discovered it yet. By being in an indeterminate state, no rules either way are triggered (I hope).

[chas-iot]

My issue is that, after an adapter restart, I have to take the phone off the network and then put it back on the network before it registers as active.
So what I'd like to see is that when the minutes are updated and less than the Time Window and the device state is indeterminate, then the device state is set to ACTIVE.

[flatsiedatsie]

I understand, but that's not an option. The adapter doesn't know it restarted. It just knows that it hasn't seen your phone yet. It should find it naturally after a little while (if it doesn't, that indeed is an issue). While it's indeterminate, your rules should (in theory) not be triggered.

Imagine the situation where your phone isn't present, but the adapter assumes it is for the first ten minutes after a restart. That could create strange situations. For example, if you're on holiday, but your home thinks you're present, and unlocks the door anyway, or turns on the heater. It's just not safe.