Nmap tracks too long

Configuration
1

here is my log:
2019-05-28 20:11:10 WARNING (MainThread) [homeassistant.components.device_tracker] Updating device list from nmap_tracker took longer than the scheduled scan interval 0:00:12
2019-05-28 20:11:23 WARNING (MainThread) [homeassistant.components.device_tracker] Updating device list from nmap_tracker took longer than the scheduled scan interval 0:00:12
2019-05-28 20:11:36 WARNING (MainThread) [homeassistant.components.device_tracker] Updating device list from nmap_tracker took longer than the scheduled scan interval 0:00:12
2019-05-28 20:11:49 WARNING (MainThread) [homeassistant.components.device_tracker] Updating device list from nmap_tracker took longer than the scheduled scan interval 0:00:12
2019-05-28 20:12:02 WARNING (MainThread) [homeassistant.components.device_tracker] Updating device list from nmap_tracker took longer than the scheduled scan interval 0:00:12
2019-05-28 20:12:28 WARNING (MainThread) [homeassistant.components.device_tracker] Updating device list from nmap_tracker took longer than the scheduled scan interval 0:00:12
2019-05-28 20:12:41 WARNING (MainThread) [homeassistant.components.device_tracker] Updating device list from nmap_tracker took longer than the scheduled scan interval 0:00:12
2019-05-28 20:12:54 WARNING (MainThread) [homeassistant.components.device_tracker] Updating device list from nmap_tracker took longer than the scheduled scan interval 0:00:12
2019-05-28 20:13:07 WARNING (MainThread) [homeassistant.components.device_tracker] Updating device list from nmap_tracker took longer than the scheduled scan interval 0:00:12
2019-05-28 20:13:20 WARNING (MainThread) [homeassistant.components.device_tracker] Updating device list from nmap_tracker took longer than the scheduled scan interval 0:00:12
2019-05-28 20:13:33 WARNING (MainThread) [homeassistant.components.device_tracker] Updating device list from nmap_tracker took longer than the scheduled scan interval 0:00:12

help.i think that i did mess something :confused:

2

Hi,
I had the same.

i solved it with this:

device_tracker:
  - platform: nmap_tracker
    home_interval: 3
    interval_seconds: 20
    hosts: <your host>

It’s interval_seconds you want to toy with to make it work without errors.

Nmap is still not very reliable so i would suggest a combination with owntracks or something like that.
I use nmap to trigger stuff when i come home, and owntracks for when i leave.

Hope this helps, i’m not very good at this but i have recieved alot of help here so i try to help as much as i can :slight_smile:

3

i had it configured but slightly diffriend values that you propose:

device_tracker:
  - platform: nmap_tracker
    hosts: 192.168.0.0/16
##    exclude: 192.168.2.222,192.168.2.44,192.168.2.212
    interval_seconds: 120
    consider_home: 240
    track_new_devices: true

and this error never show up before.
since 2 days it pop up in logs many times in short periods.

4

Ok, but when using /16 as you do, there are many adresses to check for the program.
consider configuring a /24 scan or as precise as you can.

Other than that i’m not sure what the reason is for this sudden errors.
Perhaps you have expanded with other components that steals resources from your setup so nmap isn’t going as fast as before?