core icon indicating copy to clipboard operation
core copied to clipboard

Traccar integration

Open Rothammel opened this issue 2 years ago • 2 comments

The problem

automatically created traccar devices have no unique ID's

This entity ('device_tracker.gps_sim800l_proto') does not have a unique ID, therefore its settings cannot be managed from the UI. See the [documentation](https://www.home-assistant.io/faq/unique_id) for more detail.

What version of Home Assistant Core has the issue?

Home Assistant 2023.1.7 Supervisor 2023.01.1 Operating System 9.5 Frontend 20230110.0 - latest

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Traccar

Link to integration documentation on our website

https://www.home-assistant.io/integrations/traccar/

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

Rothammel avatar Feb 01 '23 15:02 Rothammel

Hey there @ludeeus, mind taking a look at this issue as it has been labeled with an integration (traccar) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of traccar can trigger bot actions by commenting:

  • @home-assistant close Closes the issue.
  • @home-assistant rename Awesome new title Change the title of the issue.
  • @home-assistant reopen Reopen the issue.
  • @home-assistant unassign traccar Removes the current integration label and assignees on the issue, add the integration domain after the command.

(message by CodeOwnersMention)


traccar documentation traccar source (message by IssueLinks)

home-assistant[bot] avatar Feb 01 '23 15:02 home-assistant[bot]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.