0.107.6 broke Device Tracker

Since the update to 0.107.6 last night my all my device tracker devices go offline after about 30 minutes or so. If I rollback to 0.107.5 they work as expected.

I get the same Device Tracker error in the logs for both 0.107.5 & 0.107.6. This is only affecting normal ethernet tracking via my router as Bluetooth tracking still works.

image

image

image

Here is my NMAP settings which have not changed for years

  - platform: nmap_tracker
    hosts: 192.168.0.1/24
    home_interval: 10
    track_new_devices: true
    consider_home: 300
  

All instances of “hide_if_away:” has also been removed from known_devices.yaml.

Anyone else experiencing the same ?

Had exactly the same issue!!
Solved it by removing

home_interval: 10

And adding instead:

interval_seconds: 60

Don’t know what changed but it looks like that home_interval which is in minutes as per doc is now in seconds… so device_tracker runs every 10s and has no time to finish before the next run

Well it seems that you just need to adjust interval_seconds (no need to remove home_interval ) to your needs as the default value (12s) is too short in 107.6. I’ve searched which PR could changes that but did not find something

Thanks for that - just added interval_seconds: 60 to my config and will update to 0.107.6 and monitor over night whilst I WFH.

It did not work here to just add interval_secondes: 60. So I’m currently reviewing the doc to find the best settings. May have to open an issue on Github

It’s not perfect but they don’t go offline like they were doing. 0.107.7 update didn’t reference this so guess an issue needs to be raised.

If you want to add informations or logs, issue raised here: https://github.com/home-assistant/core/issues/33281

1 Like

Just woke up after nights and mine has failed again. Might roll back and stay at 0.107.5 for the moment

Thanks for raising the issue. Think you have added all I could add as well.

same issue here. Any documentation on how to easily rollback on HA Core (hassio) on a RPi

ha core update --version 0.107.5

Running 0.107.5 for a few days and I still get the odd hit using interval_seconds: 60 changing it to 15 seconds seems to stabilise it - stable 7 hours since


  - platform: nmap_tracker
    hosts: 192.168.0.1/24
    #home_interval: 10
    interval_seconds: 15 #60
    track_new_devices: false
    consider_home: 300

Any news around this getting fixed in the next deployment?

There are no known maintainer for the Nmap integration… so I don’t think it will be solved in the next couple of releases

1 Like

I have 2 HA’s running. Pi4 is the main one and my old Pi3B+ is used for adguard and as a zizbee bridge. Pi3 is running 107.7 and the device tracker on that is working fine with a few test devices to track and has been for days. I tried updating the Pi4 again last night and device tracker worked for about 12 hours before failing again - back to 107.5.

Wonder if it is the amount of devices that it is tracking that is causing the issue?

There were no logs on the Pi4 when it failed as well.