Device tracker not working after upgrade to Hassio 0.94

Installation Home Assistant OS
1

I had my iphones configure in known devices

fran_iphone:
hide_if_away: false
icon:
mac: B0:19:C6:88:39:E2
name: Fran-iPhone
picture: /local/Fran.jpg
track: true

lucilles_iphone:
hide_if_away: false
icon:
mac: B0:19:C6:31:FB:27
name: Lucilles-iPhone
picture: /local/Lucille.jpg
track: true

and a device tracker section in the config yaml

device_tracker:

  • platform: xfinity
    host: 192.168.x.x
    interval_seconds: 10
    consider_home: 180
    new_device_defaults:
    track_new_devices: true

  • platform: nmap_tracker
    hosts:

since upgrading to 0.94 hassio is not updating their locations. How do I fix this?

2

Please see the banner at the top and the How to help us help you guide on how to correctly format the code in your post.

3

I guess this is what you are wanting. I’m really not sure.

Known_devices. yaml

image

configuration.yaml

image

4

No, they are screen shots. While they do show indentation they do not make it easy for us to help you by copying and pasting corrections. What we would like you to do (please) is format your pasted config as outlined in point 11 of the link Tinkerer posted, How to help us help you - or How to ask a good question

1 Like
5

With update 0.94 device tracking was overhauled.
known_devices I believe is no longer used (not sure if it is used for partially still).

When I upgraded I had duplicates of all my devices.
I fixed it by doing the following:

Rename known_devices.yaml to known_devices.yaml.backup.
Restart Home Assistant.
Depending on what program you use for Device Tracking, you’ll need to re-establing the link.
I am using mobile_app on the Ariela app - this now shows up on the integration screen.
I checked and corrected the entityID in integrations, and everything is back to normal.

Hopefully my experience can help point you in the correct direction.
I can’t say your situation is the same, but what I found might help you figure it out!

DeadEnd

2 Likes
6

OK, I’ll try again, I copied and pasted from my text editor. The web page is changing what I past, removing the spacing

Know_devices
fran_iphone:
hide_if_away: false
icon:
mac: B0:19:C6:88:39:E2
name: Fran-iPhone
picture: /local/Fran.jpg
track: true

lucilles_iphone:
hide_if_away: false
icon:
mac: B0:19:C6:31:FB:27
name: Lucilles-iPhone
picture: /local/Lucille.jpg
track: true

Configuration yaml

device_tracker:

  • platform: xfinity
    host: 192.168.5.1
    interval_seconds: 10
    consider_home: 180
    new_device_defaults:
    track_new_devices: true

  • platform: nmap_tracker
    hosts:

    • 192.168.5.23
    • 192.168.5.18
      home_interval: 10
7

I figured it out. Here it is again.

Configuration yaml

  `device_tracker:
      - platform: xfinity
        host: 192.168.5.1
        interval_seconds: 10
        consider_home: 180
        new_device_defaults:
          track_new_devices: true
          
      - platform: nmap_tracker
        hosts:
        - 192.168.5.23
        - 192.168.5.18
        home_interval: 10`

known_devices yaml

fran_iphone:
  hide_if_away: false
  icon:
  mac: B0:19:C6:88:39:E2
  name: Fran-iPhone
  picture: /local/Fran.jpg
  track: true
  
lucilles_iphone:
  hide_if_away: false
  icon:
  mac: B0:19:C6:31:FB:27
  name: Lucilles-iPhone
  picture: /local/Lucille.jpg
  track: true
8

OK, Thanks, Mine actually started working today with me changing anything. But I will take a shot wt what you did.

9

renaming known_devices made the locations disappear. Had to put he known_device yaml back in

10

Same issue here. Tracking is now broken in 94 along with WINK.

Known entries show wink devices, but show them as unavailable.
Our phones are not showing up at all.

11

Release notes are your friend:

Comment from the release page that might be relevant:

They are overhauling how the device trackers work. If you upgraded to 94.0, I would just move forward and convert to the new way of doing things since the legacy way is going away. Yes, this was a pain as I had to change several of my node-red flows, but once done it’s done and there shouldn’t be too many more “growing pains”. My $.02

1 Like
12

I tried removing my tracker and started over. It appeared to work but now getting JsonparseException errors.

I really need another HA setup just for upgrade testing since the config checker thought it was safe to upgrade!

13

I would love to, but it is unclear to me how to do that.

1 Like
14

By any chance have you tried this. Some said it works but config check fails for me so had to remark out:

Discovery

Discovery has been mordernized thanks to @Kane610 and with the input from @Jc2k. Each integration is now able to specify how they can be discovered in their manifest, and the new zeroconf and ssdp integrations will do the rest. The new discovery is non-obtrusive: no devices are set up without approval by the user. Instead, you will need to approve each discovered integration. You can find them in the discovered section of the integrations page in the config. Only a handful of integrations have been migrated to the new approach in this release: Hue, LIFX, Deconz, TrÄdfri, Axis, ESPHome, HomeKit Controller.

The new discovery is now part of the default config. If you are not using the default config, add ssdp: and zeroconf: to your configuration.yaml.

15

What devices are showing under the “states” section under the developer tools? Most likely the name changed, that’s all. That’s what happened to me and my owntracks devices, it added a _2 to the entitiy id. I ended up renaming the devices back to the original names that it had before the upgrade and all is working now. Changing it back was not trivial for me because whenever I tried to rename it, it said I already had an entity with that name. So I had to go into the core.entity_registry file and renamed the new entity in the actual file. This was the only way I could change it. I changed the name because of my OCD, not because it needed to be done.

So you have 2 approaches you can do, either change you code to reflect the new names given to the devices after the upgrade (could be easy depending on how much code you have to change), or change the entity back to it’s original name (could be difficult, just depends on your setup and what entity still “exist”).

16

My config says I am using the default config and I don’t need any of integrations listed. So I have not tried them

17

All my devices still show with their original names. All my tracking devices are showing up and I haven’t changed anything.

18

my devices are no longer there in states.

persistent_notification.invalid_config

I am thinking I need to downgrade and try again

19

Yea it just threw up errors for me.
I am about to go back to 93 then try again.
If still the same, will wait till they get 94 more stable
aka 94.2

20

Well then I would say if it ain’t broke, don’t fix it.