A device is permanently "not_home" - but the integration writes same records into DB

[ildar170975]

Here is a "states" table for some "device_tracker".
It is always not_home.
Check the "attributes_id" column - these are same attributes.

Believe these attributes are these:

Why the integration is writing smth into DB when it is not needed?

[mudape]

Don't know about the records
Note that apple watch can't be tracked by wifi as its not directly connected to your network

In version 2.2.0 a coordinator is used, did that change anyting?

[ildar170975]

@mudape
Thanks for the feedback!
I will start monitoring & report then.

[ildar170975]

@mudape
Test with some iPhone which can be home / not_home:

These records have same attributes_id (i.e. same attributes).
The last column is a converted last_updated.
HA was restarted 3 times - yellow rows correspond to these moments.
Seems that the entity was marked as "updated" on HA startup - even with same content (state & attributes); probably this is how HA works.

Result: I do not see a behaviour described in the 1st post.
In the 1st post there were same records with different last_updated and HA was NOT restarted during a period with many repeated consecutive records.
Closing the issue.
But will keep monitoring anyway.

Data from DB were taken by DBBrowser for SQLite.

[ildar170975]

@mudape

Note that apple watch can't be tracked by wifi as its not directly connected to your network

Strange, when I installed iPhoneDetect 1st time (2021?) - noticed that it reported home for apple watch.