This integration provides information about next departures for different public transport types like Bus, Subway, Tram etc.
The Public Transport Departures integration uses EFA (Elektronische Fahrplanauskunft) endpoints as data source. This endpoints are maintained by different federal states (Bundesländern) and/or municipalities.
There is a list of known endpoints (will be updated continuously with each release)
Important
If more EFA endpoints are known to you, please write me a short messge or create a new issue and provide API URL. After a check I will add them to supported API's.
| Name | Supports real time |
|---|---|
| General | |
| General EFA | No |
| Baden-Württemberg | |
| Freiburger Verkehrs AG (VAG) | To check |
| Donau-Iller-Nahverkehrsverbund (DING) | YES |
| Nahverkehrsgesellschaft Baden-Württemberg (nvbw) | To check |
| Verkehrsverbund Rhein-Neckar (VRN) | To check |
| Verkehrs- und Tarifverbund Stuttgart (VVS) | To check |
| Bayern | |
| MoBY (Bahnland Bayern) | Yes |
| Regensburger Verkehrsverbund (RVV) | No |
| Verkehrsverbund Großraum Nürnberg (VGN) | No |
| Mecklenburg-Vorpommern | |
| Verkehrsgesellschaft Mecklenburg-Vorpommern mbH (VMV) | To check |
| Niedersachsen | |
| Vehrkehrsverbund Region Braunschweig (VRB) | To check |
| Nordrhein-Westfalen | |
| Aachener Verkehrsverbund | No |
| Der WestfalenTarif | To check |
| Verkehrsverbund Rhein-Ruhr (VRR) | Yes |
| Rheinland-Pfalz | |
| Rolph.de | To check |
| Sachsen | |
| Der Verkehrsverbund Oberelbe/Mittelsachsen (VVO/VMS) | Yes |
- Using the tool of choice open the folder for your HA configuration (where you find
configuration.yaml). - If you do not have a
custom_componentsfolder there, you need to create it. - In the
custom_componentsfolder create a new folder calledha_departures. - Download all the files from the
custom_components/ha_departures/folder in this repository. - Place the files you downloaded in the new folder you created in
step 3. - Restart Home Assistant
The configuration of integration is made via Home Assistant GUI
- Open
Settings/Devices & services - Click on
Add Integrationbutton - Search for
Public Transport Departures - Click on integration to start configuration dialog
Step 1 - Choose the API endpoint and enter stop name
In this step
ha-departuresintegration will search for all locations matching provided stop name. Please select one of them from the list
You will get list of connections provided by the API for selected stop Select all connection(s) you are interesting in and click on
OK
Choose a name for your new hub
Warning
No duplicate names are allowed!
After submit a new Hub will be created incl. new sensor(s) for each connection you selected in previous step:
You can any time add or remove connections to existing hub's (stop locations)
Just click on ⚙️ icon, select or deselct the connections and click on OK, Integration will remove obsolete and add new connections to the integration.
Documentation of this card please s. repository
Add a custom template sensor in your configuration.yaml
sensor:
- platform: template
sensors:
furth_197:
friendly_name: 'Fürth Hauptbahnhof - Bus 179 - Fürth Süd(time only)'
value_template: "{{ (as_datetime(states('sensor.furth_hauptbahnhof_bus_179_furth_sud'))).strftime('%H:%m') }}"Add entity (or entites) card to your Dashboars(don't forget to reload yaml before)
type: entities
entities:
- entity: sensor.furth_197
name: Fürth Hauptbahnhof - Bus 179 - Fürth Süd
icon: mdi:busYou can use other cards like time-bar-card to visualize remaining time to the next departure. card yaml configuration:
type: custom:timer-bar-card
name: Abfahrten Fürth-Hbf
invert: true
entities:
- entity: sensor.furth_hauptbahnhof_u_bahn_u1_furth_hardhohe
bar_width: 30%
name: U1 - Hardhöhe
guess_mode: true
end_time:
state: true
- entity: sensor.furth_hauptbahnhof_bus_179_furth_sud
bar_width: 30%
name: 179 - Fürth Süd
guess_mode: true
end_time:
state: trueIf you enjoy my work or find it useful: