Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Swiss public transport not generating unique IDs: only one entity is present #107073

Closed
dopsi opened this issue Jan 4, 2024 · 2 comments · Fixed by #107087
Closed

Swiss public transport not generating unique IDs: only one entity is present #107073

dopsi opened this issue Jan 4, 2024 · 2 comments · Fixed by #107087

Comments

@dopsi
Copy link

dopsi commented Jan 4, 2024

The problem

Both when using the new UI and the YAML configuration for the integration, the first entry gets properly created (with a sensor) but the second one only shows up in the entries but does not have an entity associated.

What version of Home Assistant Core has the issue?

2024.1.0

What was the last working version of Home Assistant Core?

2023.12.4

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Swiss public transport

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

sensor:
  - name: lausanne_geneve
    platform: swiss_public_transport
    from: "Lausanne"
    to: "Genève"
  - name: geneve_lausanne
    platform: swiss_public_transport
    from: "Genève"
    to: "Lausanne"

Anything in the logs that might be useful for us?

2024-01-04 10:04:12.476 ERROR (MainThread) [homeassistant.components.sensor] Platform swiss_public_transport does not generate unique IDs. ID None_departure already exists - ignoring sensor.epfl_to_preverenges_departure
2024-01-04 10:04:12.481 ERROR (MainThread) [homeassistant.components.sensor] Platform swiss_public_transport does not generate unique IDs. ID None_departure already exists - ignoring sensor.epfl_to_preverenges_departure

Additional information

No response

@home-assistant
Copy link

home-assistant bot commented Jan 4, 2024

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

Code owner commands

Code owners of swiss_public_transport can trigger bot actions by commenting:

  • @home-assistant close Closes the issue.
  • @home-assistant rename Awesome new title Renames the issue.
  • @home-assistant reopen Reopen the issue.
  • @home-assistant unassign swiss_public_transport Removes the current integration label and assignees on the issue, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


swiss_public_transport documentation
swiss_public_transport source
(message by IssueLinks)

@miaucl
Copy link
Contributor

miaucl commented Jan 4, 2024

There is a pull request pending fixing the missing unique ids for the newly added devices.

miaucl added a commit to miaucl/ha that referenced this issue Jan 6, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Feb 11, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants