Sensors
Wiener Linien Austria
rolandzeiner/wiener-linien-austria · vv2.3.0
HACSCloud polling
Home Assistant integration for Vienna public transport departures (Wiener Linien)
In Apple Home through HomeKit Bridge
What HomeKit Bridge makes of each kind of entity this integration creates, read from its source code. A device only gets the ones that apply to it.
| Entity | Shows up as | Note |
|---|---|---|
binary_sensor | Sensor (motion, contact, leak, smoke…) | |
sensor | Sensor (temperature, humidity, air quality…) |
How it connects
Cloud polling
Goes through the maker’s cloud, asking it for updates every so often. Needs the internet and an account.
Details
| Installs (analytics) | 60 (0.01%) |
|---|---|
| GitHub stars | 23 |
| Latest version | v2.3.0 (2026-10-21) |
| Set up in the UI | Yes |
| Maintainers | @rolandzeiner |
| License | MIT |
Limitations from the README
- Wiener Linien stops only. Departure boards, and a route's start and destination, use stops from the Wiener Linien stop list. A station served only by the S-Bahn can't be picked.
- S-Bahn shows timetable times, not live ones. There is no live data for the S-Bahn, so a departure board can't show delays, cancellations or platform changes for it, and a late train leaves the board at its planned time. On a route, S-Bahn and train rides keep their timetable times too.
- No S-Bahn between Praterstern and Hauptbahnhof until the end of October 2027. ÖBB has closed this stretch for construction since 7 September 2026, so Wien Mitte, Rennweg and Quartier Belvedere have no S-Bahn lines to pick, and routes don't use it. The lines return to the picker once trains run there again. Regional …
- The card's last pick stays on that device. It's saved in the browser, not in Home Assistant, so a phone and a wall tablet each remember their own. Two route cards without a route on the same device share that pick.
- Routes are experimental and stop to stop. Start and destination are stops, not addresses, and the trip planner decides the walking between platforms.
- Live times on routes come from the departure boards. The trip planner sends none, so a ride gets its live time from /monitor, which lists about the next hour. Rides more than about an hour away stay on the timetable. /monitor has no arrival times, so a ride's arrival moves by its departure delay.
- Static catalogue refreshes weekly. Brand-new stops may take up to a week to appear in search.
- Arrival times on the trail are estimates. They add the timetable's travel time to the departure's live time, so a delay the vehicle picks up further down the line isn't in them. They're usually within a minute or two; the far end of a long tram or bus line can be off by a few minutes, because its timetable changes …
- Stops-ahead is best-effort. Short-turn services may show the full scheduled path. Replacement buses (SEV) and unscheduled detours produce no panel, the row stays as it is, with no chevron.
In ReReHome
Whatever HomeKit Bridge shares reaches Apple Home as normal HomeKit accessories behind your Home Assistant bridge, so ReReHome shows and controls them like any other.
Bridges get their own settings page listing the accessories behind them.
