home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
72.72k stars 30.45k forks source link

Nederlandse_spoorwegen time gets incorrect train #103549

Closed Waylikemark closed 8 months ago

Waylikemark commented 11 months ago

The problem

I’ve created an sensor which polls the train from Roermond to Heerlen of 09:10 to send me a notification in case there are any delay’s. But the sensor always pulls the information about the train of 09:00, which even isn’t a direct train and requires a hop.

What version of Home Assistant Core has the issue?

core-2023.11.1

What was the last working version of Home Assistant Core?

Never

What type of installation are you running?

Home Assistant OS

Integration causing the issue

nederlandse_spoorwegen

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

Snippet from configuration.yaml:
      - name: "Roermond-Heerlen (muv zondag)"
        from: Rm
        to: Hrl
        time: "09:10:00"

Anything in the logs that might be useful for us?

No response

Additional information

No response

home-assistant[bot] commented 11 months ago

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

Code owner commands Code owners of `nederlandse_spoorwegen` 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 nederlandse_spoorwegen` Removes the current integration label and assignees on the issue, add the integration domain after the command.

(message by CodeOwnersMention)


nederlandse_spoorwegen documentation nederlandse_spoorwegen source (message by IssueLinks)

issue-triage-workflows[bot] commented 8 months ago

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.