Updated to 2022.2 1 and 2 device tracker will not work

I have tried updating settings and removing nmap(logs say this is the issue) and have not been able to get the errors with device tracker to go away. Any help with this would be greatly appreciated as it totally breaks my presence/person detection and I will not be able to move to it without resolving this. Here is a shot of the log:

Logger: homeassistant.setup
Source: components/device_tracker/legacy.py:303
First occurred: 3:08:13 AM (1 occurrences)
Last logged: 3:08:13 AM

Error during setup of component device_tracker
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/setup.py", line 227, in _async_setup_component
    result = await task
  File "/usr/src/homeassistant/homeassistant/components/device_tracker/__init__.py", line 50, in async_setup
    await async_setup_legacy_integration(hass, config)
  File "/usr/src/homeassistant/homeassistant/components/device_tracker/legacy.py", line 158, in async_setup_integration
    legacy_platforms = await async_extract_config(hass, config)
  File "/usr/src/homeassistant/homeassistant/components/device_tracker/legacy.py", line 303, in async_extract_config
    raise ValueError(
ValueError: Unable to determine type for nmap_tracker: None
4 Likes

I also have the same problem! Did you manage to fix it?

Might suggest enabling debug logs and submitting an issue on the HA Core GitHub. Much discussion there.

I managed to fix it! I had an old device_tracker config in configuration.yaml file for the nmap tracker, but I saw there was also a configuration (duplicated?) added from the UI as described here
I’ve removed the config from the configuration file and restarted HA: the error was gone and the device tracker integration is working again!

11 Likes

Hi Liglo,
Had the same problem Thanks for sharing your fix!

I was working on it late last night and apparently missed a section of my device tracker in config.yaml when I deleted it. Your comment made me review it, and I got it! Thank you!

Legend! I had the same issue yesterday when I upgraded, reverted back as I thought it would be a long night trying to fix! Searched today and BOOM nice and easy :slight_smile: thank you!

Did exactly the same. Solved

Thank you, this helped me too.

Restarting worked for me too.