Bus Stop
On your display
Bus Stop shows the next departure of your bus line right on your clock, including live delays.
- Topic
- Miscellaneous
- Includes
- Script
Runs on
- Runs on 32×8 (TC001 & DIY) 32×8 (TC001 & DIY) version
- Runs on 52×16 (TC002)
- Does not run on 32×8 with AWTRIX 3 (TC001 & DIY) Made for AWTRIX NG.
Choose your display in the next step.
Script description
Bus Stop shows the next departure of your bus or tram line right on your clock, including live delays.
The top row shows the scheduled departure time, followed by the delay: +X in red when the vehicle is late, +0 in green when it's on time. The bottom row scrolls the line number and its destination. Cancelled trips are shown in red. A bus stop icon (yellow H on a stop pole) sits on the left, or you can use any icon from the AWTRIX Hub instead.
Timetable and live data come from the nationwide DELFI database via efa.vrr.de. It's free, needs no API key and covers buses, trams and subways all over Germany. Times are converted to your local time automatically.
Settings
- Stop: town and stop name, e.g. "Gelsenkirchen Wissenschaftspark". Adding the town makes sure the right stop is found.
- Line: the line number, e.g. 302 or NE12.
- Direction (optional): part of the destination name. Both directions usually share the same stop, so use this to see only one of them. Leave it empty to show the next departure either way.
- Refresh: how often departures are updated (default 60 s).
- Icon (optional): an AWTRIX Hub icon name. Leave it empty for the built-in bus stop icon.
Press the middle button to refresh right away.
To watch both directions or several lines, install the app more than once with different settings.
Requires an Ulanzi TC002 (52×16 display).
Sign in to view and copy the code of this script.
Discussion 10
Ask a question, suggest a change or share how you use it.
Newest first
that was fast, thanks! i will try to get it work tomorrow and report...
Ok its works, I have to change some settings for my region so I have to use efavvs.de/vvs/ like on my tc002. I have just one subway line i wanna see. Sometimes after a departure, --:-- and a no departure text comes up. Then 5min later all is fine. Our Subway comes every 10min. I played with the settings but this "hickup" repeats...
The issue likely doesn't lie with the app's logic, but rather with the number of departures being loaded. The app only retrieves the next 6 departures for the entire stop (covering all lines and both directions). Your filter—applied by line and direction—only takes effect after this data is fetched. If your subway train has just departed, the next one might be the 7th (or later) in the sequence, meaning it falls outside the initial set of 6; consequently, the app finds no match and displays "--:--". Once earlier departures drop off the list, your train shifts into view. This aligns with the ~5-minute delay you’ve observed. I have uploaded a new version.
ok installed the ne script. Same "problem" , but u mentioned both directions. If i don't set a direction, it works fine. btw. at the subway stop running 3 different lines so 6 departures should be fine. If u wanna try my region settings let me know. Both directions,not what I wanted, but for now a good workaround. Edit: Tryed my TC001 subway station on my tc002, same problem. Normaly my TC002 is sett a station with only one subway line.
It works perfectly for me—also only in one direction. But I’ll double-check it. Edit: updated! The filter checks whether your specified direction text appears in the trip's destination name. Without the actual data, I cannot determine why it sometimes fails. Possible reasons include variations in how a destination is spelled for certain trips, "short-turn" trips with a different final destination, or instances where the destination name appears in a different part of the response. For this reason, I have created a diagnostic version. If the line is found but the direction filter excludes everything, the display will show—instead of "--:--"—exactly what I need to see: "No match for 'yourText'. Seen: <destinations for the line>." Otherwise, everything functions just as it does in version 2.4
Now the --:-- No match found text and Seen :other Direction comes like you wrote. If its easier for you try my settings, change script line 69 to: "https://efa.vvs.de/vvs/standard/XML_DM_REQUEST?outputFormat=rapidJSON&mode=direct&useRealtime=1&useAllStops=1&" Then set Stop to: Stuttgart SSB Zentrum , Line to: U12 , Direction to: Remseck Neckargröningen Hope this helps... Thanks!
More scripts in Miscellaneous
Something wrong with this script? Report it.
Have an idea?
Sign in to ask questions and join the conversation.