Update: we've hit 1000 integrations, here are the next 1000 🚀

When I opened this topic at the end of July, the store had a handful of external integrations. Today, Gladys has 1069 integrations (1043 in the store + 26 native), and the initial list is almost exhausted. Thank you to all the contributors, it’s incredible what has happened in three months :clap:

We therefore need the next steps. I have prepared a list of the next 1000 integrations, ranked by priority, with a small note for each explaining why it is there. All are feasible today with the external integrations framework and the SDK: we can start right away.

:page_facing_up: The complete list (CSV): Gladys Assistant next 1000 integrations + energy contracts (09/11/2026) · GitHub

How the list was built

  • Real Home Assistant usage data: 724,000 active installations, 1420 integrations. I cross-referenced these figures with the store to keep only what we are missing. 267 lines have a real HA installation number to measure demand.
  • Other catalogs: HACS, Homey, Jeedom, ioBroker, openHAB. None publish a ranking, so here it’s an indication of presence, not a figure.
  • What is specific to Gladys: energy contracts, AI and voice providers, calendars, and very French needs (Linky, Voltalis, pools, transport, school ENTs
).
  • No duplicates with the store or with Gladys’ native features (music, thermostat, energy tracking
).

For each integration, the CSV provides: the store category, the Gladys type (device, provider, ai, tts, calendar, communication, weather), the possible capability (energy_contracts, music
), local or cloud, the countries concerned, the priority (P1 / P2 / P3), the number of Home Assistant installations and a note.

Distribution: 72 in P1, 240 in P2, 688 in P3. 297 work locally.


Suggested batches (P1)

As last time, I suggest batches. These are just suggestions: take what speaks to you, especially if you have the hardware or contract at home.

Batch A: Energy Contracts (France, Europe, North America), with the energy_contracts capability

  • France: EDF Zen Flex (Sobriety days announced the day before), CRE gas reference price, real off-peak hours of the PRM (Enedis HC meridian reform), Ekwateur, Engie, solar buyback rates (OA EDF, SEG, EEG)
  • Europe: Luminus, Fluvius / ORES / Sibelga capacity tariff, aWATTar, Octopus Energy Deutschland, §14a EnWG network tariffs, ElCom (tariffs of all Swiss municipalities), Norwegian network tariffs with power steps, Norgespris / StrĂžmstĂžtte, easyEnergy, Essent, Datadis (Spain)
  • North America: OpenEI URDB (tariffs of ~3,700 American providers), Green Button Connect, Ontario tariffs (OEB), PG&E

:warning: Catalog or integration? A static grid (fixed prices, revised on a known date) goes into the catalogue energy-contracts, not in an integration. The integration is justified when a dynamic calendar (spot prices, signaled days, peak events), delegated pricing (virtual battery, Norwegian state aid) or customer account data is required. I have listed separately 62 static grid providers (Mint, Vattenfall, local authorities, SaskPower, SMUD
) to be proposed directly to the catalogue: Gladys Assistant next 1000 integrations + energy contracts (09/11/2026) · GitHub

Lot B: AI and Voice

  • Model providers (type ai): Ollama (to run the assistant 100% locally; the current Ollama integration is of type device), LM Studio, OpenRouter (300+ models with a single key), Groq, Scaleway Generative APIs, and OVHcloud AI Endpoints (hosted in France)
  • Voice (type tts): Piper (local, French voices), Wyoming gateway (to connect any text-to-speech server), Google Translate TTS, OpenAI TTS, Google Cloud TTS

Lot C: Calendars (type calendar)
Google Calendar via native API (read and write: 43,000 HA installations), Outlook / Exchange, iCloud with a login assistant, Airbnb / Booking.com for vacation rentals (tenant arrivals and departures in the calendar, to control heating and door lock codes from scenes).

Lot D: Heating, Hot Water, and Energy
MyElectricalData, Voltalis, Aldes, myVAILLANT, Remeha / Baxi / Chappée, EMS-ESP (Bosch / Buderus locally), Mysa (baseboard thermostats, very popular in Quebec), Tesla Powerwall locally.

Lot E: Major Names Still Missing
Denon / Marantz (26,000 HA installations), HEOS, Arlo, Paradox, BTicino MyHOME, Grohe Sense, TeslaMate, Xiaomi Home extended to sensors, plugs, and gateways (the current one only manages vacuum cleaners), Xiaomi / Roborock vacuum cleaner map.

Lot F: Daily Life
Local task and shopping lists (43,000 HA installations), Navitia (most French public transportation networks), RTM Marseille, Deutsche Bahn, National Rail, Waze, Forest Weather (fire risk), Enedis Outage Info, WAQI, MeteoSwiss, Blue Riiot, iopool, YunoHost, Mail and Packages, Signal, message broadcasting on Google speakers.

Lot G: Network and Gateways
OpenThread Border Router (controlled by its API), ESPresense (room-by-room presence), OpenMQTTGateway / Theengs (Bluetooth sensors decoded by an ESP32 and published in MQTT).[details=“The 72 P1 integrations, in order”]

# Integration Type HA Installations
1 Piper TTS tts 54 879*
2 Wyoming TTS (gateway) tts 54 879*
3 Local task and shopping lists provider 43 735
4 Google Calendar calendar 43 466
5 OpenThread Border Router device 39 865
6 Denon / Marantz AVR device 26 075
7 Google Translate TTS tts 533 200**
8 Denon HEOS device 18 420
9 Ollama (local AI provider) ai 13 686
10 Google Assistant SDK (broadcast) communication 12 479
11 Waze Travel Time device 10 932
12 Apple iCloud Calendar calendar 5 871
13 World Air Quality Index (WAQI) device 4 853
14 ESPresense device 3 759
15 OpenRouter ai 3 075
16 Tesla Powerwall (local) device 2 138
17 Google Cloud Text-to-Speech tts 2 059
18 Signal (signal-cli) communication 957
19 easyEnergy provider (energy_contracts) 364
20 Nettleie (Elvia, Tensio, Lede
) provider (energy_contracts) 159
21 Essent device (energy_contracts) 37
22 OVHcloud AI Endpoints ai 16
23 EDF Zen Flex provider (energy_contracts) –
24 Reference gas prices (CRE) provider (energy_contracts) –
25 Engie France device (energy_contracts) –
26 Enedis off-peak hours (HC meridian) provider (energy_contracts) –
27 Ekwateur device (energy_contracts) –
28 Luminus device (energy_contracts) –
29 Fluvius / ORES / Sibelga capacity tariff provider (energy_contracts) –
30 aWATTar provider (energy_contracts) –
31 Octopus Energy Deutschland device (energy_contracts) –
32 Network charges §14a EnWG Module 3 provider (energy_contracts) –
33 ElCom – Swiss electricity tariffs provider (energy_contracts) –
34 Datadis device –
35 Strþmstþtte / Norgespris provider (energy_contracts) –
36 OpenEI Utility Rate Database (URDB) provider (energy_contracts) –
37 Green Button Connect device –
38 Ontario electricity rates (OEB) provider (energy_contracts) –
39 PG&E provider (energy_contracts) –
40 Solar buyback tariffs (OA EDF, SEG UK, EEG
) provider (energy_contracts) –
41 LM Studio ai –
42 Scaleway Generative APIs ai –
43 Groq ai –
44 OpenAI TTS tts –
45 Outlook / Exchange (calendar type) calendar –
46 Airbnb / Booking.com (seasonal rental) calendar –
47 MyElectricalData device –
48 Voltalis device –
49 myVAILLANT device –
50 Remeha / Baxi / ChappĂ©e (BDR Thermea) device –
51 EMS-ESP (Bosch, Buderus, Junkers locally) device –
52 Aldes (InspirAIR, T.One) device
53 BTicino MyHOME (OpenWebNet) device –
54 Arlo device –
55 Paradox (PAI) device –
56 Grohe Sense / Blue device –
57 Blue Riiot (Blue Connect) device –
58 iopool device –
59 YunoHost device –
60 OpenMQTTGateway / Theengs device –
61 TeslaMate device –
62 Navitia (French transport networks) device –
63 RTM Marseille device –
64 Deutsche Bahn device –
65 National Rail (Darwin) device –
66 MeteoSwiss weather –
67 MĂ©tĂ©o des forĂȘts (fire risk) device –
68 Info coupures Enedis device –
69 Mail and Packages device –
70 Mysa device –
71 Xiaomi Cloud Map Extractor provider –
72 Xiaomi Home (sensors, plugs, gateways) device –

* Wyoming protocol number overall, shared by these two lines.
** Enabled by default in HA, so inflated number. It is classified as if it had 20,000 installations.
« – » : no equivalent in Home Assistant (integration specific to Gladys, or only present in HACS / Homey / Jeedom).
[/details]


How to contribute

  • Announce yourself here before starting, to avoid two people doing the same integration.
  • Prefer the local when possible, and reuse existing Node libraries.
  • Start from the template repository with the Node SDK, then publish by adding the GitHub topic gladys-assistant-integration to your public repository: the integration will appear automatically in the store.
  • Do you know an integration missing from the list, or an energy provider from your country? Let me know here, I will complete the CSV.

Your turn :muscle:

And we’re off again!!! haha :stuck_out_tongue:

By the way, you mentioned Denon / Marantz, but the integration already exists!

Claude must have missed it :smiley:

@Will_71 Could you import this list into your tool? :slight_smile:

On the subject of energy contracts, there is real work to be done to integrate either external integration contracts (for dynamic contracts), or via the energy-contracts repo for static contracts.

I have put in this post a list of contracts to be integrated statically.

Currently, 3 people have write access to this repo: @cicoub13, @bertrandda and me.

If anyone wants to become the “energy contracts guy”, I can give write access to this repo as well :slight_smile: Let me know if you wish to do so!

@guim31 could you maybe post your automated messages in the other topic? And we’ll keep this topic for discussion? :slight_smile:

Yes, I’ll take care of it tonight

@Will_71 I noticed something, the illustrations of your integrations are still in the old version of Gladys (design v4), even for integrations released two weeks ago

Example: Intégration domotique TaM Montpellier, gratuite et open source | Gladys Assistant

I might not be fully awake yet, but I don’t really understand the v4 design for my illustrations.
What’s the problem?

Got it, I’ll put the bookings and summaries in thread 10385, as before :slight_smile:

Your integration screenshots are from Gladys v4, not v5:

In v5, it would look like this:

I’m talking about these files: gladys-tam-montpellier/docs/assets at main · William-De71/gladys-tam-montpellier · GitHub

Ok I understand. Thanks I’ll take care of it tonight.