17Track.net


#61

Same question, didn’t find the solution to display each sensor created by package ID :confused:


#62

Hello ! Thank you for this component ! Perfect time ! :slight_smile:
However, like others, it’s complicated to manage each package in a view. Is it possible to put entities in a sub domain (eg. sensor.17track.*) ?
I have the same error than above:
Entity id already exists: sensor.XXXXXX. Platform seventeentrack does not generate unique IDs

Thank you again !


#63

@marcb and @minims see https://github.com/home-assistant/home-assistant/issues/18840 - there is a PR already merged adding more “sane” entity names.


#64

Hi, having the same error every 10 minutes,

Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/homeassistant/helpers/entity_platform.py", line 343, in _async_add_entity
    raise HomeAssistantError(msg)
homeassistant.exceptions.HomeAssistantError: Entity id already exists: sensor.un591019467cn. Platform seventeentrack does not generate unique IDs

#65

@maxandersen - It’s great thanks.
Can you also please make a UI to show all packages in a table like this:
https://github.com/tr1plus/ha-aftership (including the last update date) ?


#66

Having it all in one sensor would work too and is easily manageable especially if one is planning to display it in a table like what is used in https://github.com/custom-components/sensor.aftership/blob/master/custom_components/sensor/aftership.py
I am using it already with a custom:list-card - works beautifully


#67

Hi all – FYI, this PR adds the desired functionality mentioned by several people above (e.g., a JSON attribute that shows packages for each summary sensor):


#68

I’m using Hass on Ubuntu (not Hass.io) and I don’t have 17track component in Integration Panel. I’d like to manage my tracking numbers like in #14 post. Any suggestions how to do it?


#69

Since this is a sensor platform and not a standalone component, you won’t see anything in the Integrations Panel. You’ll need to follow the documentation and modify your configuration.yaml file.