Border Wait Times Canada/US Smart-Home-Integration, kostenlos und Open Source

Unofficial. Canada / U.S. border wait times (CBSA, CBP), each way.

• Veröffentlicht von LM1LC3N7
• Geräte
• Version 0.1.2
• Erfordert Gladys >=5.1.0
• ★ 0

Auf GitHub ansehenAlle Integrationen

Info

Die Dokumentation dieser Integration wird von ihrem Autor geschrieben und ist bisher nur auf Englisch verfügbar.

Unofficial integration, not affiliated with the Canada Border Services Agency (CBSA) nor with U.S. Customs and Border Protection (CBP). It reads the wait times at the land border crossings between Canada and the United States, both ways, from the open data of both agencies: no account, no key.

• To Canada: the CBSA file (bwt-eng.csv, and bwt-fra.csv for the French names), travellers and commercial vehicles.
• To the U.S.: the CBP feed (bwt.cbp.gov), passenger vehicles, NEXUS and Ready Lane lanes, commercial vehicles and FAST lanes. Only the Canadian border is kept.

Read-only: nothing is ever sent to the agencies but GET requests. Tried against the real CBSA and CBP files on 29 October 2026; the module has not been used yet in a real Gladys install by a traveller: tell us what you see.

The times shown are estimates published by the agencies, for information only: they can change quickly and do not replace the official information.

Setup

1. Install the integration, pick the language of the names and the read interval (10 to 60 minutes, 15 by default), then save.
2. The first read starts at once (or an interval after the previous one when the container just restarted). Open the Discovery tab: each crossing shows up at most twice, one device per direction ("To Canada: …" and "To the U.S.: …").
3. Create the crossings you care about.

What you get

Device	Feature	Unit
To Canada	Travellers wait	min
To Canada	Commercial vehicles wait	min
To the U.S.	Passenger vehicles wait	min
To the U.S.	NEXUS wait	min
To the U.S.	Ready Lane wait	min
To the U.S.	Commercial vehicles wait	min
To the U.S.	FAST wait	min
Both	Status	text

A lane the crossing does not have simply never gets a value.

• "No Delay" (CBSA) is 0 minutes: a zero wait announced by the agency. At CBP, the number of minutes given is published as it is, whether the lane says "delay" or "no delay" (the real feed gives "no delay" with 0, 1 or 5 minutes).
• "Closed", "Not Applicable", "--", "Lanes Closed", "Update Pending", "N/A" or an unknown text are never published as a number: the Status feature says it ("Closed", "Lanes closed", "Update pending at the source", "Not applicable to this crossing", "No reading published by the source", "Unreadable value: nothing published").
• The status also gives the time of the reading: the CBSA one with its zone (e.g. 2026-10-29 16:40 EDT), the CBP one in the local time of the port.

Freshness

• Each reading is published once (deduplicated on the time given by the source, kept in /data): a scene "wait below X minutes" fires on a new reading, not at every read.
• A reading older than 2 hours (age counted as below) is never published; the status becomes "Stale reading (over 2 h)" with its time. The age is counted from the server Date header (CBSA) or the local time of the port (CBP).
• The CBP feed gives the time of each port: when it no longer moves for over 2 hours, nothing of it is published and the status becomes "Source silent for over 2 h: nothing published".
• CBP types the time zone by hand (an "EST" shows up in October): it is not used. Each port has its time zone (from its CBP district: Eastern, Central, Mountain, Pacific, Alaska; an unknown district takes the zone whose offset matches the feed time against the Date header): local times become exact instants, changes of time included, the day before when they are later than the time of the port.
• Changes of time: in March, a reading from before the jump keeps its real age. In November, the hour from 1 to 2 am happens twice: a reading time in that hour, never seen before, is taken as the first of the two (the older): a reading older than 2 hours is never taken for a fresh one, at the price, once a year, of a fresh reading of that hour left out. A time that follows a reading already published for the same lane is taken as the second: the new reading is published.
• A port of an unknown district (none today: the 30 ports of the feed have their district) may be in several zones around a change of time, in March as in November: the oldest possible reading is kept; never a stale reading published, a few fresh readings of those hours left out. The zones guessed are kept and narrowed read after read.
• A port whose time is more than 2 hours from the server Date header (a feed served from a cache, a frozen port) publishes nothing; so does the whole feed when its latest time is.
• Gladys keeps the last value published of a feature: when a wait is no longer known, the Status feature says it, not the value.

A scene "wait below X minutes"

In a scene, pick the Device state change trigger, the wait feature you want and the condition "lower than X". It fires on the first fresh reading below X.

Pace and sources

• One read every N minutes (10 to 60), never more often for the same source: saving the form, a reconnection, the Discovery tab, a device created or a restart start no read (the time of the last attempt is written to /data before each read). Exceptions: an interval shortened in the form makes the next read due sooner (at the new length after the last one, at the earliest); a read cut by a save or a reconnection resumes a minute later, for the sources it had not asked yet only (a source asked, even cut, waits for its interval); a restart while /data could not be read or written reads at once.
• A device created gets at once the fresh readings already in memory (no read); renaming or moving a device sends nothing again.
• One request at a time: the English CBSA file, the French one (only when the language is French, for the names), then CBP. Each request is bounded to 20 seconds and in size (256 KB for the CBSA, 4 MB for CBP).
• The CBSA gets back the If-None-Match / If-Modified-Since headers it offers; CBP offers none.
• User-Agent: gladys-attente-frontiere/<version> (+repository address).
• A 429 or 5xx answer pauses that source (5 minutes doubled at each failure, Retry-After honoured, between 60 seconds and 6 hours), kept across a restart. The other source is still read. The French CBSA file (same server) is not asked when the English one was just refused or is paused.
• The French names of the CBSA never block anything: without them, the English names are used.

Status of the integration

"Connected" as soon as at least one of the two sources was read at its last attempt (CBP counts only while its feed still moves). After a restart, before the next read: "connected" when a source was read fine within the interval (kept in /data), else "Waiting for the first read (in N min)"; the device statuses stay as already shown. The message says, per source, what is wrong: unreachable, no answer in time, paused after a 429 or a 5xx, unexpected format, frozen or late feed; and also an interval replaced (out of 10-60 minutes), a /data unreadable (set aside under another name) or not writable, values put off to the next read (Gladys accepts 300 states a minute, the module sends 250 at most over a rolling minute; beyond, the values put off come first the next time, in turn).

Data and licences

• Contains information licensed under the Open Government Licence – Canada (CBSA, dataset "Current Border Wait Times").
• The CBP data is a work of the United States government, in the public domain.
• No personal data is read nor kept.

Konfigurationseinstellungen

Diese Einstellungen fragt Border Wait Times Canada/US in seinem Konfigurationsbildschirm in Gladys ab.

Einstellung	Typ	Pflichtfeld	Beschreibung
Border wait times	section	Nein	Open data of the Canada Border Services Agency (to Canada) and of U.S. Customs and Border Protection (to the U.S.): no account, no key. Unofficial integration, not affiliated with either agency. The waits are estimates of the agencies, updated about every hour, shown as they publish them: a reading older than 2 hours is never published. After saving, open the Discovery tab and create the crossings you want: one device per crossing and direction.
Language of the names	select	Nein	Language of the device names given in Discovery and of the status texts. The French names of the crossings come from the CBSA; the CBP names are English only.
Read every (minutes)	number	Nein	Time between two reads of the sources, from 10 to 60 minutes. The agencies update their data about every hour.

So installierst du Border Wait Times Canada/US in Gladys

1. Öffne in Gladys Integrationen: Border Wait Times Canada/US erscheint im Katalog neben den nativen Integrationen, mit einem Community-Badge.
2. Klicke auf Installieren. Gladys lädt das Docker-Image (ghcr.io/lm1lc3n7/gladys-attente-frontiere:0.1.2) herunter, startet es in einer vom Kern isolierten Sandbox und erzeugt die Oberfläche der Integration (Geräte, Erkennung und Konfiguration).
3. Öffne den Bildschirm Konfiguration der Integration, fülle die Einstellungen aus und speichere.
4. Du kannst sie auch direkt über die URL ihres Repositorys installieren: https://github.com/LM1LC3N7/gladys-attente-frontiere.

Border Wait Times Canada/US benötigt Gladys >=5.1.0. Der Katalog in Gladys wird stündlich aktualisiert, eine neue Version ist also spätestens eine Stunde nach ihrer Veröffentlichung verfügbar.

Du nutzt Gladys noch nicht? Es ist kostenlos und Open Source: folge der Installationsanleitung, um loszulegen.

Über externe Integrationen

Border Wait Times Canada/US ist eine externe Integration: eine Community-Integration, die als Docker-Container verpackt und auf GitHub veröffentlicht wird. Gladys installiert sie mit einem Klick und führt sie in einer vom Kern isolierten Sandbox aus. Sie wird von LM1LC3N7 veröffentlicht und gepflegt, nicht vom Gladys-Kernteam.

• Alle Integrationen durchsuchen, native und aus der Community
• Deine eigene externe Integration bauen und veröffentlichen
• Quellcode auf GitHub — Quelle dieser Dokumentation

Abonniere den Newsletter von Gladys Assistant

Ein paar E-Mails im Monat zu neuen Releases und Neuigkeiten aus dem Projekt. Verschickt von Pierre-Gilles Leymarie, dem Gründer des Projekts. Jederzeit abbestellbar 🙂