Skip to content

Added parameter time to search for a specific trip time. #11235

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.

Sign up for GitHub

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

Merged
merged 2 commits into from
Feb 3, 2020
Merged

Added parameter time to search for a specific trip time. #11235

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ee8d29f
Added parameter time to search for a specific trip time.
gurbyz Nov 20, 2019
9cce8e9
Apply suggestions from code review
gurbyz Nov 20, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 24 additions & 1 deletion source/_integrations/nederlandse_spoorwegen.markdown
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,6 +28,10 @@ sensor:
from: Gn
to: Mt
via: Zl
- name: 'AlmereBuiten-Duivendrecht-the-08h06m-train'
from: Almb
to: Dvd
time: '08:06:00'
```

{% configuration %}
Expand Down Expand Up @@ -60,8 +64,27 @@ routes:
description: Optional other station you wish to visit in between.
required: false
type: string
time:
description: Optional time to search for a specific train.
required: false
type: time
{% endconfiguration %}

The data are coming from [Nederlandse Spoorwegen](https://www.ns.nl/).
### Station codes

Station codes must be used and can be looked up [here](https://nl.wikipedia.org/wiki/Lijst_van_spoorwegstations_in_Nederland).

### Searching a specific train vs. the next train

The default behavior (without configuration variable `time`) gives you the information about the *next* train that fits the criteria (`from`, `to`, `via`).
When using the configuration variable `time`, you can search for a specific train.
This is convenient when searching for the next train doesn't give you enough time to base an automation on.
E.g., when you normally take the 08h06m train and want to get information about this train, but there is another train
that's departing just minutes before your train, your time window to warn you on a delay might be too small.

Using `time` only updates the route sensor during a time window around the chosen time.
Outside this window, the route sensor's state is `unknown`.
The window is from half an hour before the chosen time until half an hour after the chosen time.
In this way, you can have multiple routes with specific trains before hitting the FUP threshold for using NS API.

The data are coming from [Nederlandse Spoorwegen](https://www.ns.nl/).