HERE Travel Time smart home integration, free and open source
Travel times with live traffic from HERE: car, truck, transit, delay, scenes, widgets.
Published by William-De71
- Devices
- Version 0.1.0
- Requires Gladys >=5.3.0
- ★ 0
Overview
This integration follows your usual trips — home to work, school, the airport — with the travel times of HERE. For each trip it gives the travel time with live traffic, the delay caused by the traffic, the distance and the main roads, or the lines and times by public transport, and it can start your scenes when the traffic gets worse or the route changes.
- Each trip becomes a device: travel time, time without traffic and traffic delay (car, truck, scooter / motorcycle), distance, main roads or lines.
- Six travel modes: car (with or without live traffic), truck, scooter / motorcycle, bicycle, walking, public transport (lines, changes, first departure, real-time delay).
- Trips are read only on their days and hours, so that the requests stay within the free monthly usage of HERE.
- Scene triggers: the route of a trip changes, the monthly budget is almost used, HERE refuses the API key. Scene actions: compute a route now, read a trip now.
- Three dashboard widgets: the travel times of the trips, one trip, the requests of the month.
The image above is a generated illustration, not a screenshot. Not affiliated with HERE; not tested with a real API key yet.
Prerequisites
- Gladys Assistant 5.3.0 or later.
- A HERE API key (free within the monthly usage below):
- Create an account on platform.here.com ("Sign up"). New accounts are on the Base plan: HERE asks for a payment method during the sign-up, and only bills what goes beyond the free usage.
- Open the Access Manager from the launcher (top right), tab Apps, then Register new app; give it a name ("Gladys") and press Register.
- In the app, tab Credentials, choose API Keys then Create API key, and copy the key (an app holds two keys at most).
- The timezone of Gladys set correctly (Settings > System): the hours of the trips are read in it.
- To use "home" as a place: the location of your house set in Settings > Houses. The integration asks for the location permission at install time for this.
Cost. HERE counts one transaction per request and gives, each month on the Base plan, a free usage per request type (HERE pricing, read on 26 October 2026):
| Request type | Free a month | Then, per 1,000 |
|---|---|---|
| Car with live traffic ("Time-aware routing") | 5,000 | USD 2.92 |
| Car without traffic, bicycle, walking ("Routing") | 30,000 | USD 0.88 |
| Truck | 5,000 | USD 2.92 |
| Scooter / motorcycle | 5,000 | USD 2.92 |
| Public transport | 5,000 | USD 2.92 |
| Geocoding (an address turned into coordinates, once) | 30,000 | USD 0.88 |
A car trip read every 15 minutes from 6:00 to 21:00, Monday to Friday, uses about 1,300 requests a month. The integration keeps by default to 90 % of each free usage and reads the trips less often rather than going over. The free usage belongs to the HERE account: other apps of the account count too.
Configuration
The trips are not typed as JSON: each one is a small form, behind the buttons at the bottom of the configuration page.
| Field or button | Description |
|---|---|
| HERE API key | Required. Kept secret by Gladys, never shown again nor written to the logs. |
| Default interval | Minutes between two readings of a trip without its own interval (5 to 240, 15 by default). |
| Default delay threshold | Traffic delay, in minutes, from which a trip shows in red in the widgets (orange from 3 minutes). 10 by default. |
| Monthly budget | Share of the free usage of each request type the integration may spend. 90 by default; above 100, HERE bills the extra requests. |
| Language of the texts | Feature names, route texts, scene summaries, messages of the buttons, language asked from HERE. Choose it before adding your devices: a device keeps the feature names it is created with. |
| Add a trip | Name, from, to, travel mode, live traffic (car), avoid tolls / motorways / ferries, days, hours ("6-10, 16-20", empty: 6-21), own interval and threshold. The places are checked at once. |
| Edit a trip | The trip by its name or number (#2); only the fields you fill in change. 0 brings the interval or the threshold back to the default. |
| Remove a trip | The trip by its name or number. Its device stays in Gladys until you delete it. |
| List the trips | Each trip with its schedule, the requests it plans, its last reading and its last error, and the requests of the month. |
| Test the API key | Computes a short walk in Paris from coordinates (one "Routing" request) and says what to fix when HERE refuses the key. |
From and to accept:
- an address or a place name ("Gare Part-Dieu, Lyon"): HERE turns it into coordinates once (one geocoding request), then the integration keeps them;
- coordinates "latitude, longitude", such as
45.7640, 4.8357(no geocoding); - home (or
maison,domicile,zuhause,casa,hogar): the first house of Gladys that has a location; - @name: the house of Gladys with this name, such as
@Chalet.
Usage
Trips
- Paste the API key and press Test the API key.
- Press Add a trip for each usual trip. The answer shows the places as HERE understood them: check them. A car trip on weekdays from 6:00 to 21:00 every 15 minutes is the default: change the days and the hours to what you need.
- The first reading comes within a minute when the trip is in its hours. Outside its hours, the trip keeps its last reading.
A car trip uses live traffic by default. Turn Live traffic (car) off for a trip whose delay does not matter: it then counts in the 30,000 free "Routing" requests instead of the 5,000 "Time-aware routing" ones. A scooter / motorcycle trip uses motorways unless Avoid motorways is checked.
Devices
Open the Discover tab and add the trips you want. Each device has:
- Travel time with traffic (minutes; "Travel time" without live traffic). By public transport: door to door, from the first departure on foot to the arrival, waits included;
- Travel time without traffic and Traffic delay (minutes; trips with live traffic);
- Distance (km) and Route: the main roads (such as "A6, A7"), or by public transport the lines and the times (such as "Bus C1 → Métro B · 07:49–08:16").
The values follow the readings of the trip; Gladys keeps their history.
Dashboard widgets
- Travel times: the trips with travel time, distance and roads or lines, a badge with the delay (green, orange from 3 minutes, red from the threshold of the trip; by public transport, the time of the first departure, or the real-time delay announced), a link to the route on HERE WeGo, and Refresh all.
- Trip: one trip, chosen among the devices: up to four tiles, route, times by public transport, last reading, Refresh.
- HERE requests: one gauge per request type used (five at most), what the trips plan a month, the state of the key.
A refresh button spends one request per trip, none for a trip read less than a minute ago.
Scenes
Triggers of the integration:
- The route of a trip changes: at a scheduled reading, the fastest route goes by other roads (or other lines) than at the previous one. Variables: name, route, previous route, travel time, delay, distance, summary sentence.
- The monthly budget is almost used: a request type reaches 80 %, then 100 % of its budget (once each a month).
- HERE refuses the API key: once, until a request works again; the summary says what to fix.
For a threshold ("the delay goes above 10 minutes", "the travel time goes above 40 minutes"), use the device trigger of Gladys on the feature of the trip.
Actions: Compute a route (any two places, now) and Read a trip now (also outside its hours). Both return the travel time, the time without traffic, the delay, the distance, the route, the departure and arrival times and a summary sentence such as "Work: 38 min, 14 min of traffic, 11.8 km via M6, A6." to send in a message.
Examples:
- When the traffic delay of "Work" goes above 10 minutes → send the summary of the trip.
- Every weekday at 7:15 → read "Office (transit)" now → send
{{0.0.summary}}(lines, first departure, changes, delay) to the household. - When the route of "Airport" changes → send a message: an accident or a closed road on the usual way.
Transport
The integration uses the servers of HERE (cloud): the coordinates of your trips are sent to HERE at each reading, and an address once when it is geocoded, with your API key in the request. The trips are kept in the Gladys configuration; the last readings, the request counter and the geocoded addresses are kept in the /data volume of the integration.
Troubleshooting
- "HERE refuses the API key":
API_KEY_INVALID— copy the key again from the Credentials tab of the app (a deleted or disabled key is refused too);API_KEY_MISSING— no key reached HERE;FORBIDDEN— the key is valid but not allowed to use the service: check that the account is on the Base plan (payment method entered) and that the app is enabled. The integration tries again every hour, and at once after Test the API key or a new key. - "HERE does not know the address": add the town and the country, or type coordinates.
- A trip has no reading: check its days and hours with List the trips (the timezone shown must be yours), and its last error.
noRouteFound,couldNotMatchOrigin,couldNotMatchDestination: no road for this mode near a place (move the point to a street);noCoverage,noStationsFound: no public transport data around the places. - Readings rarer than the interval: "stretched … to stay within the budget" in List the trips means the trips of that request type plan more than the budget; reduce the hours, the trips or the interval, or raise the budget.
- "The requests of the month are used": the budget of that request type is reached; the trips concerned wait for the next month (UTC). HERE's own count on platform.here.com is the reference.
- 429: HERE limits the requests of the key; the integration waits 15 minutes.
- To report a problem, give the versions of Gladys and of the integration, the text of List the trips (hide your addresses if you wish) and the logs of the integration (Settings → Supervision). Never paste your API key.
Configuration settings
These are the settings HERE Travel Time asks for in its configuration screen in Gladys.
| Setting | Type | Required | Description |
|---|---|---|---|
| HERE Travel Time | section | No | How it works: 1. Create a free account on platform.here.com (Base plan: a payment method is asked, the free usage is not billed), register an app in the Access Manager, create an API key in its Credentials tab and paste it below. 2. Declare each trip with “Add a trip”: from, to, travel mode, days and hours. 3. In the Discover tab, add the trip: it becomes a device (travel time, traffic delay, distance, route). 4. Add the widgets and use the scenes. Cost: one request per reading. Free each month: 5,000 by car with traffic, truck, scooter and public transport; 30,000 by car without traffic, bicycle and walking; 30,000 geocodings (once per address). By default the integration stays within 90 % and stretches the intervals. The places are sent to HERE. |
| HERE API key | secret | Yes | An API key of an app of your HERE platform account (Access Manager → Apps → your app → Credentials → API Keys). Sent to HERE only, never shown again. |
| Default interval (minutes) | number | No | How often a trip without its own interval is read, within its hours (5 to 240). |
| Default delay threshold (minutes) | number | No | From this traffic delay, a trip without its own threshold shows in red in the widgets (orange from 3 minutes). |
| Monthly budget (% of the free usage) | number | No | Share of the free monthly usage of each request type the integration may spend: 90 keeps a margin (HERE counts the other apps of the account too). Above 100, HERE bills the extra requests. |
| Language of the texts | select | No | Feature names, route texts, scene summaries, messages of the buttons and the language asked from HERE. Automatic: the language of your dashboard once a widget has been shown, guessed from the timezone of Gladys before that. |
How to install HERE Travel Time in Gladys
- In Gladys, open Integrations: HERE Travel Time appears in the catalog, next to the native integrations, with a community badge.
- Click Install. Gladys pulls the Docker image (
ghcr.io/william-de71/gladys-here-travel-time:0.1.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/William-De71/gladys-here-travel-time.
HERE Travel Time requires Gladys >=5.3.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
HERE Travel Time 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 William-De71, 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