Skip to content

Document 'name' config parameter in rejseplanen #10243

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
fabaff merged 5 commits into from
Aug 27, 2019
Merged

Document 'name' config parameter in rejseplanen #10243

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
9a1ec53
Document 'name' config parameter in rejseplanen
KennethLavrsen Aug 27, 2019
bf1ae84
An example where policy and common sense clash
KennethLavrsen Aug 27, 2019
c678382
:pencil2: Tweak
klaasnicolaas Aug 27, 2019
7d899a0
Adjust default
fabaff Aug 27, 2019
3de44eb
Fix sample
fabaff Aug 27, 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
6 changes: 6 additions & 0 deletions source/_components/rejseplanen.markdown
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -53,6 +53,11 @@ stop_id:
description: The ID of the public transport stop.
required: true
type: string
name:
description: "The name of the sensor. Entity ID for the sensor will be created based on this name. E.g., Glostrup St becomes `sensor.glostrup_st`. It's optional but recommended if you define more than one sensor."
required: false
type: string
default: "Next departure"
route:
description: List of route names.
required: false
Expand Down Expand Up @@ -105,6 +110,7 @@ A more extensive example on how to use this sensor:
# Example configuration.yaml entry
sensor:
- platform: rejseplanen
name: 'Elmegade 350S'
stop_id: '000045740'
route: 'Bus 350S'
direction:
Expand Down