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

My ov info is not retrieving any info anymore #42

Open
pvklink opened this issue Sep 20, 2023 · 2 comments
Open

My ov info is not retrieving any info anymore #42

pvklink opened this issue Sep 20, 2023 · 2 comments

Comments

@pvklink
Copy link

pvklink commented Sep 20, 2023

Hi, i have ov info working for months.
But since two days my ovapi-TRAM-info does not work anymore
I use a raspberry 4b, latest os, 64 bits
OV plugin version = '1.4.2'
and using the ov info within homeassistant, latest beta docker
error i got is unknown in the lovelace ui for my ov entities.

my sensor.yaml which i include with: sensor: !include sensor.yaml in configuration.yaml

<sensor.yaml>
`- platform: ovapi
name: Tram_17_x
stop_code: 5615
route_code: 32005616
show_future_departures: 4

  • platform: ovapi
    name: Tram_17_y
    stop_code: 5615
    route_code: 32005615
    show_future_departures: 4
  • platform: nederlandse_spoorwegen
    api_key: d232349be07644d88c243c9bf3c8672b
    routes:
    • name: Denhaag CS-Utrecht
      from: Gvc
      to: Ut
    • name: Rijswijk CS-Denhaag CS
      from: Rsw
      to: Gvc
      `
@GitHubxtsnl
Copy link

it may be possible the transportation provider changed the stop_code or route_code. so you should redo the lookup procedure to find the new and updated stop- and/or route_code.

@pvklink
Copy link
Author

pvklink commented Jan 25, 2024

yes, that did the trick, thanks @GitHubxtsnl

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants