Exactly. I don’t know what fixed it but it is.
Hi @eulogious, how did you edit them in ‘core.entity_registry’ ?
I see them in ‘states’ but can’t find them in the ‘_registry’ file…
Sorry to thread hijack, but it seems to be semi-broken for me too, though I can’t for the life of me figure it out.
We used Google Maps integration. It was still picking up my wife’s phone location but not mine. So I deleted known_devices and restarted HA, after which it picked up my wife’s phone, but now not mine at all. I’ve verified that location is shared with my HA google account, and if I log on with that account I can see the location in google maps. But whatever I do, HA will not create a device entry for it. I even had my wife unshare hers to be sure it wasn’t a “one device” deal, but hers works fine, and not mine.
Ideas?
Same problem here not able to get any new devices in home assistant. Not the native iOS app tracer of Life360. Nothing appears in the list of devices. I sat 3 hours yesterday going back and forth but could not figure out why? 
For me it’s totally unclear how the new device tracker is supposed to work. I want to ping local IP adresses, but the device trackers aren’t working anymore.
What is the correct way to use the ping platform device tracker now? Is the known devices file history from now on?
1 Like
Be very, very, very careful editing any of the core.* files. One character off is enough to make it so that home assistant will not start. Also make sure that you have another way to edit files if home assistant won’t start, and have a way to restart home assistant with home assistant not working. I run my hassio in a docker container on a debian vm, so I can just edit the files from docker if needed. I also have the IDE addon still running because it will work if home assistant is down/not running. I had an extra ‘,’ in the file and that prevented home assistant from starting. Luckily I have other ways to get to the files and to start home assistant, so no big deal. Be careful. With that being said, the files are located at .storage. I just edited the file and then rebooted.
Good luck.
I will say that the only device tracker I had issues with was owntracks. I use the IOS app for location tracking as well, and I had no issues with it, just owntracks. It looks like the IOS app was part of “phase one” of the device tracker migration effort, but I had no issues with it.
I had a similar issue and found that I had left the configuration.yaml settings in.
device_tracker:
- platform: gpslogger
Once I removed that and rebooted HA I stopped and restarted the GPSLogger app.
It then started working and I had a new device in my GPSLogger integration section.
Just wanted to bump that this worked for me with the current Hassio version …
device_tracker:
- platform: xfinity
host: 192.168.5.1
interval_seconds: 10
consider_home: 180
new_device_defaults:
track_new_devices: true
That is, contrary to the current Hassio instructions, removing the ‘username’ and ‘password’ requirments worked for me to get my Xfinity connecting,tracking and auto-generating ‘known_devices.yaml’.
The current Home Assistant documentation only lists host as an option for that platform, nothing about username or password