Transitous Departures smart home integration, free and open source
Nearby public transport departures on the Gladys dashboard, powered by Transitous.
Published by tomgermany
- Devices
- Version 3.3.0
- Requires Gladys >=5.2.0
- ★ 0
You need:
Gladys Assistent > Version 5.2
External Integration Transitous Depatures
Internet Access for Your Gladys Assistant Installation
You get:
You'll receive an external integration for Galdys Assistant. This integration automatically displays the next 6 public transportation departures in a clear, easy-to-read widget—from buses to trains, ferries, and cable cars. All of this within a configurable radius around your home.
Example:
Result: For each of the six tiles, the nearest stop is first determined once. That is, the nearest bus stop, nearest ferry, and nearest rail stop. The next departure from that stop is then displayed. This means: If there is only one stop within your search radius, you will see the next six departures. If multiple stops are found, they are displayed using color coding.
Configuration
-
Install the external integration either through Gladys Assistant (recommended) or in Gladys Assistant with direct access to GitHub.
-
After Installation check that Integration is running.
-
Open your Dashboard and go into Edit Modus and there add the new Widget. Select this Integration Widget.
-
When adding the widget to your dashboard, you’ll need some information:
a.) Your geolocation as the starting point (or choose location from Gladys Assistant)
5.) The diameter of the search radius.
6.) The refresh interval in 10-minute increments.
7.) A unique identifier for API access at https://transitous.org/. This identifier must be unique—for example, an email address or website. It is stored by the integration only in the configuration field there. The integration neither retrieves nor documents this identifier. Everything remains with you. Transitous.org uses this identifier to manage the load on its IT infrastructure. Keep in mind the data provider when setting this. We recommend 30 minutes.
- After filling out this information, save it and place the widget where you want it.
Specifically: Either select your Galdys house or enter a geolocation of your choice. Below that, you can define three search radii in metres. This means that bus stops will be searched for within these radii. The individual radii are added together. If radius 1 is set to 300 metres and you enter 200 metres for radius 2, then radius 2 will have a search radius of 500 metres:
In the lower section, you can then choose to reschedule the time display. The time currently shown is the time today when Gladys Assistant starts. Using the drop-down menu, you can reschedule the display by the number of days you wish; for example, 14:00 plus 1 day = tomorrow at 14:00. The time is always based on when the application starts. They then set the interval at which the new departure times are retrieved. In consideration of the provider, Transitous, we ask that you do not set this to less than 30 minutes. Finally, Transitous asks for a ‘connoisseur’; we do not store this (except in the configuration field) and do not use it. It is used exclusively by Transitous:
Operation
In the top image, you will see a button. This displays the three search areas you have selected, and with each click you move up and then down through these search areas.
The results are initially displayed in the top six tiles. These show: an icon representing the mode of transport (bus, train, aeroplane, ferry, etc.). Below that, the departure time and the destination station.
Each mode of transport has its own colour. Special transport services such as ferries, cable cars, as well as call-a-taxi and Moonliner services, are shown in grey. Cancelled or disrupted journeys are shown in red.
At the bottom of the screen, you will see a list of the stops found. These initially show the stop name, followed by the route number (also colour-coded), the distance from your current location and, where available, the type of vehicle.
Troubleshooting
The integration logs everything it does: check the integration logs from the
Gladys UI (or docker logs on the host) with LOG_LEVEL=debug for the full
detail.
Configuration settings
These are the settings Transitous Departures asks for in its configuration screen in Gladys.
| Setting | Type | Required | Description |
|---|---|---|---|
| Widget setup information | section | No | Before adding the widget to your dashboard, determine the coordinates of your chosen location. You need latitude and longitude in decimal format, for example 49.350 and 8.690. When adding the widget, you can then configure the search radius, number of departures and refresh interval. The default search radius is 2,000 metres. Timetable data: Transitous. Information about data sources and attribution: https://transitous.org/sources/ |
How to install Transitous Departures in Gladys
- In Gladys, open Integrations: Transitous Departures appears in the catalog, next to the native integrations, with a community badge.
- Click Install. Gladys pulls the Docker image (
ghcr.io/tomgermany/gladys-transitous-departures:3.3.0), starts it in a sandbox isolated from the core, and generates the integration's interface (devices, discovery and configuration). - Open the Configuration screen of the integration, fill in the settings, and save.
- You can also install it directly from its repository URL: https://github.com/tomgermany/gladys-transitous-departures.
Transitous Departures requires Gladys >=5.2.0. The catalog inside Gladys refreshes every hour, so a new version becomes available at most one hour after its release.
Not running Gladys yet? It is free and open source: follow the installation guide to get started.
About external integrations
Transitous Departures is an external integration: a community integration packaged as a Docker container and published on GitHub, that Gladys installs in one click and runs in a sandbox isolated from its core. It is published and maintained by tomgermany, not by the Gladys core team.
- Browse all integrations, native and community
- Build and publish your own external integration
- Source code on GitHub — source of this documentation