Rocket Launches smart home integration, free and open source
Upcoming rocket launches worldwide: countdown, liftoff, results and delays for your scenes.
Published by guim31
- Devices
- Version 1.0.0
- Requires Gladys >=5.1.0
- ★ 0
Upcoming rocket launches from around the world in Gladys: SpaceX, Arianespace, ULA, Rocket Lab, ISRO, JAXA, Chinese launchers… The data comes from Launch Library 2, the free and open database of The Space Devs, updated by its community in real time.
What it does
- A Next launch device: name, date in your local time, hours left, status, provider, rocket, launch site, live webcast, "launch today", and the last launch with its result.
- One more device per filter you choose (SpaceX, Kourou, Ariane 6…), with the same features.
- A Rocket launches dashboard widget: countdown to the next launch and the five next ones.
- Four scene triggers: launch soon, liftoff, launch result, launch postponed.
- Two scene actions that return a sentence ready to send or to say aloud.
Requirements
- Gladys Assistant 5.1 or later (5.2 for the details panel of the widget).
- Internet access from Gladys. No account, no key: Launch Library 2 is free for personal use.
Configuration
- Install the integration, then open its Configuration tab.
- Choose the language of the texts: device and feature names, text values and scene sentences (French by default). Names are set when a device is created: to rename them, delete and re-add the device.
- Optionally type filters (see below), then save.
- In the Discovery tab, add the Next launch device, and the device of each filter.
The Check button reads Launch Library 2 again at once and shows the next launch, the number of launches of each filter and the requests left this hour.
Filters
Up to five, separated by commas. A filter matches the launches whose provider, rocket, mission,
launch site or country contains the text, without case or accents: SpaceX, Arianespace, ISRO,
Ariane 6, Starship, Starlink, Vandenberg. A few usual names are understood too: Kourou
(Guiana Space Centre), Florida, California, Baikonur, China, India, Japan, Europe
(Arianespace, ESA, Avio). Codes of three characters or less match whole words: a country code
(US, CN, GF), a provider code (ULA, SpX) or a rocket (H3).
Each filter adds a device named "Next launch · <filter>". Changing the text of a filter creates a new device: delete the old one from Gladys.
Devices
All features are read only.
| Feature | Value |
|---|---|
| Launch | Rocket and mission, as Launch Library 2 names them: "Falcon 9 Block 5 | Starlink Group 15-15" |
| Launch date | As precise as it is known: "Mon, Oct 19 · 12:30", "~12:30" for a time known to the hour, a day, "October 2026", "Q4 2026" |
| Hours until launch | Whole hours before the date (No Earlier Than), 0 when it is reached |
| Launches within 7 days | Upcoming launches of the device in the next 7 days |
| Launch status | Go, To be confirmed, To be determined, On hold |
| Launch provider, Rocket, Launch site | From Launch Library 2 |
| Webcast live | 1 while the official webcast is live |
| Launch today | 1 when the next launch is today (when its day is known) |
| Last launch, Last launch result | The last launch that left the ground, and its outcome: In flight, Success, Failure, Partial failure |
The next launch is the first one that has not left the ground yet. Launch dates are often "No Earlier Than": a launch planned for "October 2026" is dated the first day of the month.
Dashboard widget
Rocket launches shows the countdown to the next launch, the number of launches within 7 days and the five next launches with their date, provider and status. Tap a launch to read its mission. The Device setting limits it to the launches of a filter; empty, it shows every launch.
Scene triggers
Each trigger asks for a device: "Next launch" for every launch in the world, or the device of a filter. A launch matching several devices fires once per device, so a scene runs once.
- Launch soon: 5, 15 or 30 minutes, 1, 2 or 24 hours before a launch whose time is known to the minute and whose status is Go or To be confirmed. A launch that moves fires again at its new time.
- Liftoff: when Launch Library 2 reports the rocket in flight, usually within 10 minutes.
- Launch result: success, failure or partial failure (filter optional), with the failure reason (in English).
- Launch postponed: a launch planned within 48 hours moves 15 minutes or more later ("New date"), or is put on hold ("On hold").
Every trigger passes on a sentence ready to send, the launch, mission, rocket, provider, site, date and status, and its own details (minutes before, result, previous date, delay).
Scene actions
- Read the next launch: a sentence such as "Next launch: Falcon 9 Block 5 | Bandwagon 5 (SpaceX), from Cape Canaveral SFS, FL, USA, Mon, Oct 19 · 12:30. Status: Go.", and the launch, provider, site, date, hours left (-1 when none) and status.
- Read the next launches: one sentence listing the next 1 to 5 launches with their date.
Both accept an optional device to keep to a filter.
Scene examples
- Launch soon (Next launch · Kourou, 15 minutes before) → send the sentence of the trigger to your phone.
- Liftoff (Next launch · SpaceX) → turn the living room light blue, then say the sentence on the speaker.
- Every morning at 8:00 → Read the next launches (3) → send the sentence in a message.
Troubleshooting
- Nothing in the devices: Launch Library 2 has not been read yet. Press Check: it shows the error, if any.
- "Request limit reached": Launch Library 2 allows 15 requests per hour without an account, and answers 429 beyond. The integration waits the time announced and reads again on its own. Avoid pressing Check many times in a row: it uses 2 requests each time.
- A filter matches nothing: press Check to see how many launches each filter matches. A filter only sees the next 40 launches in the world, about one or two months.
- Set
LOG_LEVEL=debugon the container to see each reading.
Limits
- Launch Library 2 is free and anonymous but limited to 15 requests per hour: the integration reads the upcoming launches every 30 minutes, every 10 minutes from an hour before a launch until its outcome is known, and the last launches every 2 hours: 2 to 7 requests an hour. Its own margin is 12 per hour.
- Liftoff and results are seen at the next reading: up to 10 minutes late.
- The data is the one of the Launch Library 2 community: a date may change at the last minute, a result may be published hours later.
- The webcast links are not available in this mode of the API: only the "live" flag.
- This integration is not affiliated with The Space Devs nor with any launch provider.
Credits
Launch data: Launch Library 2 by The Space Devs. Integration by guim31, under the Apache 2.0 license.
Configuration settings
These are the settings Rocket Launches asks for in its configuration screen in Gladys.
| Setting | Type | Required | Description |
|---|---|---|---|
| How it works | section | No | Launches come from Launch Library 2 by The Space Devs, a free database without an account, limited to 15 requests per hour: the integration reads it every 30 minutes, every 10 minutes around a launch. Dates are shown in the Gladys time zone. |
| Language of the texts | select | No | Language of the device and feature names, of the text values and of the scene sentences. Names are set when a device is created: to rename them, delete and re-add the device. |
| Filters (one device each) | string | No | Up to 5, separated by commas: a provider (SpaceX, Arianespace, ISRO), a rocket (Ariane 6, Starship), a site (Kourou, Florida, Baikonur) or a country code (US, CN). Each filter adds a "Next launch" device of its own. |
How to install Rocket Launches in Gladys
- In Gladys, open Integrations: Rocket Launches appears in the catalog, next to the native integrations, with a community badge.
- Click Install. Gladys pulls the Docker image (
ghcr.io/guim31/gladys-launch-library:1.0.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/guim31/gladys-launch-library.
Rocket Launches requires Gladys >=5.1.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
Rocket Launches 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 guim31, 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