Deprecated alias BaseTrackerEntity

[larronni]

The deprecated alias BaseTrackerEntity was used from iphonedetect. It will be removed in HA Core 2027.6. Use homeassistant.components.device_tracker.BaseTrackerEntity instead, please report it to the author of the 'iphonedetect' custom integration

[Dan1jel]

Due to (what i assume) dead repo, i started using ARPscan instead. No offense to iphonedetect, its been my choice for so many years, but i need to have something that works now.

After some searching, i found ARPscan and have my hopes for that to be more updated/activity.

Only posting it here to help others to maybe have things going asap, or at least until this repo is updated.

https://github.com/cyberjunky/home-assistant-arpscan_tracker

Edit: looks good but having issue with ARP to track our phones... Wish iPhonedetect would be updated to continue the use of this great app.

[breakthestatic]

ARP tracking isn't nearly as accurate, since the ARP table gets cached and takes time to clear after a device actually leaves the network. This integration performs regular polling, so it puts a bit more strain on the devices themselves, but is exactly as precise as the polling interval. Another interesting thing with this integration is that it uses mDNS to get around issues w/ iOS ignoring regular ping requests and occasionally sleeping during other types of polling (e.g. snmp).

[Dan1jel]

ARP tracking isn't nearly as accurate, since the ARP table gets cached and takes time to clear after a device actually leaves the network. This integration performs regular polling, so it puts a bit more strain on the devices themselves, but is exactly as precise as the polling interval. Another interesting thing with this integration is that it uses mDNS to get around issues w/ iOS ignoring regular ping requests and occasionally sleeping during other types of polling (e.g. snmp).

Yea i did notice that when i tried it, thought i found something that could be instead until an update came... But no its not as accurate.

I hade to roll back to previous update to maintain my automations.

[breakthestatic]

The deprecation warning is slightly annoying, but the incorrect zone calculations (from using the old, deprecated base class) are much more detrimental if you use zone state (count) for anything or trying out the new in_zones state attributes.

Hopefully my PR gets merged and then we can all be fully up and running again.

[Dan1jel]

The deprecation warning is slightly annoying, but the incorrect zone calculations (from using the old, deprecated base class) are much more detrimental if you use zone state (count) for anything or trying out the new in_zones state attributes.

Hopefully my PR gets merged and then we can all be fully up and running again.

Maybe a stupid question, but now i have trigger "if home Is less then 0" and ".. more then 0", how should i use "in_zone"?

[breakthestatic]

Maybe a stupid question, but now i have trigger "if home Is less then 0" and ".. more then 0", how should i use "in_zone"?

If you have existing zone conditions for greater than 0/less than 1, functionality should remain the same (with the exception of the bug regarding incorrect zone counts for persons using this device tracker). I personally haven't thought up specific use-cases for the new in_zones functionality, but I'm sure there's some neat things that can be done w/ it. I just simply care about the number of people in my home, and the way this integration handles home/not_home doesn't work with the new pattern introduced in 2026.7 (without my PR or equivalent changes).

[Dan1jel]

Maybe a stupid question, but now i have trigger "if home Is less then 0" and ".. more then 0", how should i use "in_zone"?

If you have existing zone conditions for greater than 0/less than 1, functionality should remain the same (with the exception of the bug regarding incorrect zone counts for persons using this device tracker). I personally haven't thought up specific use-cases for the new in_zones functionality, but I'm sure there's some neat things that can be done w/ it. I just simply care about the number of people in my home, and the way this integration handles home/not_home doesn't work with the new pattern introduced in 2026.7 (without my PR or equivalent changes).

Thanks for the replies and maybe helping other along the way.

I do think there is a bug in 2026.7 where it shows incorrectly despide how many is home (in my example, 2 where home but zone.home says 0).

So i might wait until a fix is out for that. Im controlling privacy settings for my camera, and i got alot of notifications/constantly video recordings due to my HA is not recognizing anyone home.

I did see several other PR that have not been approved from 1 year ago, so i really do hope that this is not att dead/left project.

[breakthestatic]

I do think there is a bug in 2026.7 where it shows incorrectly despide how many is home (in my example, 2 where home but zone.home says 0).

Yes, that's the bug caused (at least partially) by this integration. In 2026.7, a zone's state (count) is controlled by a new state attribute (the aforementioned in_zones list). For most trackers, in_zones is working correctly. However, the device trackers created by iphonedetect use a (now) invalid method of reporting tracker state. The PR I opened earlier today fixes the zone count logic by refactoring the "type" of tracker this integration creates, which corrects the in_zones calculation and in turn fixes the zone count. You can see the changes for the PR at #164. I've also published a release in my fork (https://github.com/breakthestatic/iphonedetect), which I'm personally using until the PR gets merged. Be warned - if you do use my fork, it can be a bit tricky getting it installed without uninstalling mudape's original one since they conflict in HACS. I first deleted the original integration, added my fork as a custom repository, and then installed it once visible in HACS. By doing this though, there's a decent chance the device trackers created by the original integration could be deleted (requiring recreation after installing the forked copy).

[danieletorelli]

@breakthestatic Thank you for working on the fix. I installed that in my HomeAssistant 2026.7 and I can confirm it works.

Your fork was relatively easy to install if you follow those steps:

(Assuming you have this integration installed and configured - do not uninstall it or delete your configuration before)

1. Install https://github.com/breakthestatic/iphonedetect as custom repository
2. Search for "iphonedetect" in HACS and you will find two integrations
3. Install https://github.com/breakthestatic/iphonedetect integration while keeping the old one installed. This will effectively replace the integration code by downloading the version 2.5.0-beta.1 reusing the configuration data of the old integration, since the data in hacs.json stayed the same
4. Restart HomeAssistant to make the change effective
5. Go back to HACS and uninstall the old integration without deleting your configuration and do not restart HomeAssistant yet
6. Reinstall https://github.com/breakthestatic/iphonedetect integration again with version 2.5.0-beta.1
7. Restart HomeAssistant to make the change effective

Meanwhile, @mudape could you please let us know if you are planning to merge the fix in here or if there's any other thing preventing it at the moment?

[Dan1jel]

@breakthestatic Thank you for working on the fix. I installed that in my HomeAssistant 2026.7 and I can confirm it works.

Your fork was relatively easy to install if you follow those steps:

(Assuming you have this integration installed and configured - do not uninstall it or delete your configuration before)

1. Install https://github.com/breakthestatic/iphonedetect as custom repository
2. Search for "iphonedetect" in HACS and you will find two integrations
3. Install https://github.com/breakthestatic/iphonedetect integration while keeping the old one installed. This will effectively replace the integration code by downloading the version 2.5.0-beta.1 reusing the configuration data of the old integration, since the data in hacs.json stayed the same
4. Restart HomeAssistant to make the change effective
5. Go back to HACS and uninstall the old integration without deleting your configuration and do not restart HomeAssistant yet
6. Reinstall https://github.com/breakthestatic/iphonedetect integration again with version 2.5.0-beta.1
7. Restart HomeAssistant to make the change effective

Meanwhile, @mudape could you please let us know if you are planning to merge the fix in here or if there's any other thing preventing it at the moment?

Great guide! I have done as you did, but cant confirm until someone comes home. Thank you @breakthestatic for taking you time and also fixing this. If @mudape is maybe leaving this, you could maybe continue on your repo 🙏

Edit: can confirm that this works for me also!