Core: 17track default entity names not changed [seventeentrack]

Created on 16 Jan 2019  路  6Comments  路  Source: home-assistant/core

Home Assistant release with the issue: 0.85.1

Last working Home Assistant release (if known):

Operating environment (Hass.io/Docker/Windows/etc.): Centos 7 non docker

Component/platform: 17track

Description of problem:
Despite being on 0.85.1 my entity names are not changing save for a new entity that has appeared because it is newly tracked. I'm still seeing "sensor.17track".

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

- platform: seventeentrack
  username: !secret 17track_user
  password: !secret 17track_pass

Traceback (if applicable):


Additional information:
I've verified the contents of my /usr/lib/python3.5/site-packages/homeassistant/components/sensor/seventeentrack.py, and they match what is latest in Github for 0.85.1.

seventeentrack

Most helpful comment

Someone should make an entity registry manager.

All 6 comments

I've tried purging my sensor states from sql delete from states WHERE entity_id like "%17track%"; removing the sensor from hass, restarting, and then re-adding, but same result.

screen shot 2019-01-15 at 10 37 56 pm

[aneisch@nuc-nuc ~]$ sudo find / -name seventeentrack.py 
/usr/lib/python3.5/site-packages/homeassistant/components/sensor/seventeentrack.py
[aneisch@nuc-nuc ~]$ 

^^ This file contains the latest changes

@bachya any ideas?

This is likely because your entity registry has the old names. Open /config/.storage/core.entity_registry, delete any existing 17track.net entities, restart HASS, and see if that fixes your issue.

This did indeed resolve the issue. Does something need to be done to allow for the proper migration of these names at large? I guess to take it one step further: I see that some of my old packages are still present in the core.entity_registry file. Is there a mechanism to prune this file?

Great question; @balloob, is there a mechanism in place for this?

Someone should make an entity registry manager.

The suggested workaround worked and the long term fix is out of scope for this issue. Thanks @bachya!

Was this page helpful?
0 / 5 - 0 ratings

Related issues

TheZoker picture TheZoker  路  3Comments

neonandu picture neonandu  路  3Comments

sogeniusio picture sogeniusio  路  3Comments

moskovskiy82 picture moskovskiy82  路  3Comments

arangates picture arangates  路  3Comments