Most popular Home Assistant integrations → candidates for Gladys external integrations

The evening wave is out: four self-hosted software applications.

All tested on real software in Docker, not yet on a real Gladys installation. Your feedback is welcome :slight_smile:

The series stops here for now: I’m taking a break from new integrations. Feedback and corrections on those already published continue.

The small GCE batch (reserved for #436) is published: three integrations for GCE Electronics devices, at the request of @cce66 who will test them on real devices. They will arrive in the store at the next indexer run, and « Install from GitHub » already works with the link of each repository. All local, no cloud.

IPX800 V3 v0.1.1: GitHub - LM1LC3N7/gladys-ipx800-v3 · GitHub
Relays, inputs, and analog probes of the IPX800 V3, up to 3 devices. Relays are read-only except those you list; a command always sends a precise state (on or off), never a toggle. Ported from ha_ipx800v3 (MIT).

Eco-Devices RT2 v0.1.1: GitHub - LM1LC3N7/gladys-ecodevices-rt2 · GitHub
Counters, inputs, relays, X-4FP and X-THL pilot wires of the Eco-Devices RT2, up to 3 devices. Indexes are never published at 0 or decreasing. Teleinfo and clamp indexes await confirmation of their unit on a real device before being proposed. Based on pyecodevices_rt2 (MIT) and GCE documentation.

Eco-Devices ED3 v0.1.1: GitHub - LM1LC3N7/gladys-ecodevices-ed3 · GitHub
The 30 counters, clamps (power), voltage, relays, X-8R (read-only), and X-THL of the Eco-Devices 3, up to 3 devices. Same rule for indexes; counters powered by a clamp also await confirmation of their unit. Written based on GCE documentation and tools published by cce66 (MIT).

For all three: each device keeps its own devices (a device never controls another device), stopping an output is never blocked, and none have yet run on a real device. Your feedback is welcome in the GitHub issues.

Second wave of batch 19 (reserved for #434): the United States in open data. The five integrations will arrive at the store at the next indexer pass, and “Install from GitHub” already works with the link of each repository. None require an account or key, and all have been tested on the real services. A silent, outdated, or unreadable source is reported in the integration status: nothing is ever published as 0 instead of an unknown value.

CAISO v0.1.1: GitHub - LM1LC3N7/gladys-caiso · GitHub
The Californian electrical network: real-time wholesale prices by zone (NP15, SP15, ZP26), demand, renewable share, carbon intensity, and the alert level (Flex Alert, EEA 1 to 3) with a trigger. This is a wholesale price, not your rate. The published level is a minimum: an advisory that the integration does not recognize is cited in the status, and a return to “normal” is only announced if everything is recognized.

USGS v0.1.1: GitHub - LM1LC3N7/gladys-usgs-eau · GitHub
River and aquifer levels, flows, and temperatures from the USGS at your stations, in US or metric units. A measurement that is “dry,” “ice,” “below threshold”… is never published as a value; an estimated or provisional measurement is, and the status states it.

NDBC v0.1.1: GitHub - LM1LC3N7/gladys-ndbc · GitHub
The NOAA buoys and coastal stations: waves, wind, pressure, air and water temperatures, visibility, tide. A faulty station never blocks the others.

US Recalls v0.1.1: GitHub - LM1LC3N7/gladys-recalls-us · GitHub
US recalls: consumer products (CPSC), food and drugs (FDA), and vehicles (NHTSA, by brand, model, and year, or from a VIN that never leaves Gladys except to the official decoder), with a trigger and widget.

MBTA v0.1.1: GitHub - LM1LC3N7/gladys-mbta · GitHub
The next arrivals of Boston transport at your stops and line alerts. The next departure is displayed in dated text (“Red Line → Ashmont in 4 min (08:09)”) so that an outdated schedule never remains displayed, with an “imminent departure” trigger for scenes. MassDOT / MBTA data.

Your feedback is welcome in the GitHub issues.

Third and final wave of batch 19 (reserved for #434): North American devices controlled locally, without cloud or account. The five integrations will arrive in the store at the next indexer pass, and “Install from GitHub” already works with the link to each repository. None have yet run on a real device: they follow Home Assistant libraries and have been tested on fake devices. Your feedback with real hardware is welcome.

Hayward OmniLogic v0.1.1: GitHub - LM1LC3N7/gladys-omnilogic · GitHub
OmniLogic pool controllers via their local protocol: air and water temperatures, heating and setpoint, pumps (on, speed, power) and relays. Heating never turns on above the temperature ceiling you choose, even if the setpoint already in the controller is higher; stopping a pump or heater is never retained. Based on python-omnilogic-local (Apache-2.0).

Guardian (Elexa) v0.1.1: GitHub - LM1LC3N7/gladys-guardian · GitHub
The Guardian water shutoff valve and its leak detectors: valve state, leaks, temperatures, batteries. Closing is never retained and follows its valve if it changes address; opening is disabled by default and refused until a paired detector could be read. The local API has no password: keep the valve on a trusted network. Based on aioguardian.

IntelliFire v0.1.1: GitHub - LM1LC3N7/gladys-intellifire · GitHub
IntelliFire gas fireplaces (Heat & Glo, Heatilator, Majestic, Monessen, Quadra-Fire) via the local API of their Wi-Fi module: flame, pilot light, temperature, thermostat, timer, faults. “Turn off” always works and is retained until the flame is seen off; ignition, flame, fan, and setpoint are disabled by default, and ignition from Gladys always sets a timer. Based on intellifire4py.

GreenEye Monitor v0.1.1: GitHub - LM1LC3N7/gladys-greeneye · GitHub
The 32-channel energy monitor from Brultech (British Columbia), read-only: energy index (for Gladys energy tracking), power, current, voltage, pulse counters, and temperatures. An index is never published in decline or with a suspicious jump without your confirmation, and a counter that rolls over to zero is tracked without loss. Based on the Brultech packet format and siobrultech-protocols (MIT).

Modern Forms v0.1.1: GitHub - LM1LC3N7/gladys-modern-forms · GitHub
Modern Forms and WAC ceiling fans (generations 1 to 3): speed, rotation direction, breeze mode, light, and brightness. No setting is a switch, so “turn all on” never starts a fan; a stop is never abandoned on a fan failure or error. Based on aiomodernforms.

This message closes batch 19 (15 integrations in three waves: Canada, U.S. open data, then these local devices). Your feedback is welcome in the GitHub issues.

Updating my integrations to version 0.16 of the external integrations SDK, ready for Gladys 5.3. The new versions will arrive in the store at the next indexer run. There’s nothing to do: the update is sufficient.

What changes for you

  • Compatible with Gladys 5.3 periodic polling: none of these integrations are polled twice, they keep their own rhythm.
  • Each published feature is now checked by tests against the Gladys model (minimum, maximum, options…). It’s this control that found the bug below.

Fixed: devices rejected by Discovery

Five heating and air conditioning integrations published choice lists (mode, ventilation…) without minimum or maximum. Gladys then rejected the entire device, with „Minimum value: required field not provided by the integration“. This is fixed in Aprilaire 0.1.2, Fujitsu 0.1.2, Nexia 0.1.3, Rheem EcoNet 0.1.4 and Venstar 0.1.2 (and Toshiba AC 0.1.2, reported on GitHub). If you had tried one of them unsuccessfully: update it, then restart Discovery.

Updated integrations

  • ATAG, Roth Touchline, Genius Hub, MAX! Cube, LightwaveRF, airOS, Soma Connect, Somfy myLink, Vanderbilt SPC, Pure Energie, Sky Q, PJLink, Ruuvi Gateway, Iskra: 0.1.2; Remootio 0.1.3
  • P1 Monitor 0.1.4, Energieleser 0.1.3, Envertech 0.1.4, Hypontech 0.1.3, inexogy 0.1.3
  • Agua IOT 0.1.2, air-Q 0.1.3, Aircraft 0.1.2, BSB-LAN 0.3.2, Denon / Marantz 1.2.3
  • AirVisual 0.1.4, Ajax 0.1.4, Ambient Weather 0.1.3, Alfen 0.1.4, APsystems 0.1.5
  • Aquarea 0.1.3, Arcam 0.1.3, Autarco 0.1.3, Automower 0.1.6, Balboa 0.1.3

The others follow in waves of five. Having trouble after an update? Let us know here or in a repository issue.

Catch-up: fixes published between 25 and 31 October on my integrations had not been announced here, sorry. They are all already in the store: one update is enough. From now on, each batch update will have its message here.

Devices missing from Discovery (fixed)

Victron, Bosch Indego, Navimow, deCONZ and Automower were publishing choice lists without labels, and Gladys then refused the entire device. If Discovery showed nothing, you need to update and then restart it. Eedomus, Jeedom and Linn have received the same protection as a precaution.

Readings that never started (fixed)

On a new installation, Energieleser, Envertech, Hypontech, inexogy, Omnik and Zeversolar did not start their readings. This has been fixed since 25 October.

Energy meters: a jump is no longer counted without your consent

An aberrant value from a meter (a drop or an impossible jump) is retained until you confirm it. The accepted value now serves as a floor: a reading that is even lower, or that falls below an accepted jump, is also retained. This avoids a gap or a spike in the energy history.

Integrations concerned: Alfen, Autarco, E3/DC, Eco-Devices, EcoTracker, Energieleser, Envertech, homee, Hubitat, Hypontech, Imeon, Indevolt, inexogy, Iskra, NRGkick, Omnik, OpenEMS, OpenEVSE, P1 Monitor, Plugwise, Pure Energie, Rainforest Eagle, Sinapsi Alfa, Solakon, sonnen, Sungrow, YouLess and Zeversolar.

Hot water: ceiling at 65 °C

The hot water setpoint ceiling goes from 60 °C to 65 °C, and the default value is 65 °C. You can still set it lower, and the device limits still apply. Integrations concerned: Aquarea, ATAG, BSB-LAN, Compit, Genius Hub, homee, iDM, Lambda, my-PV, Rheem EcoNet, Stiebel Eltron and Waterkotte.

IntelliCenter: pool and spa ceiling

Heating is no longer started on a setpoint left above the ceiling, for example by the Pentair app. The ceiling is that of the pool in the configuration, or 40 °C for a spa. The integration states why it refuses.

MQTT: Qbus and PG LAB

  • Qbus: a very large message kept by the broker no longer causes the integration to crash (size limited to 2 MB).
  • PG LAB: a message of more than 8 KB received just at connection no longer cuts the integration as if the credentials were refused.

Having trouble after an update? Let us know here or in a repository issue.

New updates for my integrations, already published: they will arrive in the store at the next indexer run. One update is enough, there is nothing to redo.

Blue Current 0.1.3: « Stop Session » still works

Before, stopping a recharge was refused as long as the « Allow Commands » option was unchecked, which it is by default. This is no longer the case:

  • the stop goes through immediately, even if the option is unchecked and even if the station appears offline;
  • it is only refused if Gladys is not connected to Blue Current, or during a pause imposed by Blue Current after too many requests;
  • if you press « Start », « Unlock » or « Restart », then « Stop » before the station has responded, the first command is canceled: nothing goes after a stop.

Start, lock, unlock, and restart still require the option.

Migration to SDK 0.16 (wave 8)

Bang & Olufsen 0.1.3, BleBox 0.1.3, Blitzortung 0.1.2, Blue Current 0.1.3, Bluesound 0.1.2: compatible with Gladys 5.3 periodic polling, and each feature is verified by tests against the Gladys model. No issues on this side for these five.

Recent patches

  • Eco-Devices RT2 0.1.4 (pilot wire): on a zone that does not return a known mode, the message clearly states this, and a Stop or Anti-freeze sent to this zone is marked « sent, cannot be confirmed ».
  • Eco-Devices 3 (ED3) 0.2.1: readings are now verified on a real ED3 (thanks to the member who lent their responses), and an electricity meter that a pulse input can power is set aside in two more cases, to avoid mixing units.
  • Denon / Marantz 1.2.2: SDK 0.16, no visible change.

To know with Gladys 5.3.1

Gladys’ thermostat can now control pilot wire radiators and air conditioners. I check that my concerned integrations publish what is needed for this.

Having trouble after an update? Let us know here or in a repository issue.

I’m taking on 15 new integrations for batch 20. I checked today in @Will_71’s follow-up, in this thread (up to #453), in the store, in Gladys’s core, and on GitHub: none are announced or reserved by anyone else. If I’m wrong, let me know and I’ll remove them. Almost all work locally, and all rely on a library under MIT, Apache, or BSD license, or on the manufacturer’s documentation.

Climate and Energy

  • Atrea: Atrea dual-flow ventilation (RD5 regulation).
  • Systemair: Systemair SAVE ventilation (VTR, VSR, VSC), via the Modbus published by Systemair.
  • Buderus KM200: Buderus KM50, KM100, and KM200 gateways locally (heating, water heated to 65 °C).
  • MENNEKES AMTRON: AMTRON 4You and 4Business charging stations.
  • AirTouch 5: AirTouch 5 zoned ducted air conditioning.

Building and Access

  • JUNG HOME: JUNG HOME gateway (lights, shutters, outlets, thermostats).
  • Becker: Becker shutters and blinds via the CentralControl box.
  • LOQED: LOQED Touch lock; unlocking is disabled by default.
  • Akuvox: Akuvox intercoms; door opening is disabled by default.
  • Deako: Deako switches and dimmers.

Network, Sensors, and Lighting

  • QNAP QSW: QNAP switches (ports, PoE, temperature).
  • MySensors: MySensors home sensors, via a network gateway or MQTT.
  • Wiffi: stall.biz weather and air sensors (Weatherman, Rainyman…).
  • Switcher: Switcher water heaters, shutters, and outlets.
  • AiDot: AiDot Wi-Fi bulbs and lights, with the manufacturer’s official library.

I don’t have this equipment: the integrations will be tested on simulated devices, and feedback from those who have them will be invaluable. They use the latest SDK and are in French and English. I publish them in groups of five, with a summary here each time.

First wave of batch 20 (reserved for #454): climate and energy, locally. Four integrations are coming to the store at the next indexer pass, and “Install from GitHub” already works with the link of each repository. I don’t have this equipment: everything was tested on simulated devices based on the manufacturer’s documentation. Your feedback is precious if you have one.

Common rules: commands are disabled by default (a checkbox option), shutdown never depends on this option, it is kept and returned until the device confirms it, even after a Gladys restart. Only one connection to the device at a time.

Atrea v0.1.1: GitHub - LM1LC3N7/gladys-atrea · GitHub
The Atrea dual-flow ventilation with RD5 regulation, via its local web interface: mode, power, temperatures, alarms. Shutdown puts the central unit in manual mode and off, so the weekly program doesn’t restart it. No bypass or air flows yet (no reference documents these registers).

Systemair SAVE v0.1.1: GitHub - LM1LC3N7/gladys-systemair · GitHub
The Systemair SAVE units (VTR, VSR, VSC) via Systemair’s published Modbus TCP, with SAVE Connect or an RS485 gateway (EW11…): mode, temperatures, humidity, filter, alarms. Only two registers are written (level and mode). If the unit doesn’t allow manual shutdown, the integration states this instead of switching to low speed.

MENNEKES AMTRON v0.1.1: GitHub - LM1LC3N7/gladys-mennekes-amtron · GitHub
The AMTRON 4You and 4Business charging stations via Modbus TCP (MENNEKES doc 1.5): status, power, energy, current. Pause sets the station to 0 A and nothing can block it; restart and current adjustment are limited to 6–16 A, as stated in the manufacturer’s documentation. The station’s Modbus must be in read-write for commands.

AirTouch 5 v0.1.1: GitHub - LM1LC3N7/gladys-airtouch5 · GitHub
The AirTouch 5 zoned ducted air conditioning, via the local protocol published by Polyaire: air conditioners (on/off, mode, fan, setpoint) and zones (open/close, setpoint, temperature). Setpoints remain within the limits given by the console.

The fifth of the wave, Buderus KM200, is still awaiting a decision and will come later. Your feedback is welcome in the GitHub issues.

Fifth integration of the first wave of batch 20, announced at #455: it arrives in the store at the next indexer pass, and “Install from GitHub” already works with the repository link.

Buderus KM200 v0.1.1: GitHub - LM1LC3N7/gladys-bosch-thermostat · GitHub
Local Buderus KM50, KM100, and KM200 (and IVT) gateways, without cloud: temperatures, heating circuits, hot water, modes, and setpoints. The access code from the label and the password are only used to form the gateway key; they are never sent.

  • Modes and setpoints are disabled by default (a checkbox option); the room setpoint ranges from 5 to 30 °C, hot water is capped at 65 °C.
  • Choosing the “off” mode for a circuit does not depend on any option: it is kept and returned until the gateway responds.
  • Known limitation: RC300 and RC200 heating circuits do not have an “off” mode, so this version cannot turn off their heating from Gladys.
  • To communicate with the gateway, the integration presents itself as the Buderus application (header TeleHeater), as the reference library does; this is mentioned in the documentation.

I don’t have a KM gateway: everything was tested on a simulated gateway based on the reference library. If you have one, your feedback is very valuable, especially regarding the connection. Having trouble? Let me know here or in an issue on the repository.

Second batch of lot 20 (reserved for #454): building and access, locally. The five integrations arrive at the store on the next indexer pass, and “Install from GitHub” already works with the link of each repository. I don’t have this material: everything was tested on simulated devices based on the manufacturer’s documentation and the reference library. Your feedback is precious if you have one.

Common rules: turn off, stop, close, and lock are never retained and are returned until the device confirms them; opening a door or unlocking a lock is disabled by default and is never a switch (a button, behind a checkbox).

LOQED v0.1.1: GitHub - LM1LC3N7/gladys-loqed · GitHub
The LOQED Touch lock via the local API of its bridge: state (locked, open, night), battery. Lock always goes immediately. Unlock and open are two buttons disabled by default; open requires both options. The bridge notifications go through a small dedicated container and their signature is verified: a forged or replayed notification triggers nothing. You need to create the local API key in the LOQED application.

Becker v0.1.1: GitHub - LM1LC3N7/gladys-becker · GitHub
Becker shutters, blinds, screens, and sensors (sun, wind, rain) via the CentralControl CC31, CC41, or CC51 box: open, close, position, stop. A scene on multiple shutters sets them all. Nothing goes through the cloud.

Akuvox v0.1.1: GitHub - LM1LC3N7/gladys-akuvox · GitHub
Akuvox intercoms and access controls (E21V, R29…) via their local API: door relay status, an “open” button per relay (disabled by default, the device closes itself), scene triggers on openings, refused accesses, and calls. Codes and badges are never read. A relay in manual mode is never open, and a device without a configuration API either: it’s stated in the documentation.

JUNG HOME v0.1.1: GitHub - LM1LC3N7/gladys-jung-home · GitHub
The JUNG HOME gateway locally: lights, dimmers, shutters, outlets, thermostats. You authorize “Gladys” in the JUNG HOME application; the gateway certificate is retained, and a change blocks everything until your approval. Setpoints (5 to 30 °C), outlets, and JUNG HOME scenes are disabled by default.

Deako v0.1.1: GitHub - LM1LC3N7/gladys-deako · GitHub
Deako switches and dimmers via the local API of the Deako Connect: on, off, intensity. “All off” on many lights turns them all off. If the Deako application already occupies the Connect, the integration waits without saturating it. The most recent Deako switches do not have a local API.

Your feedback is welcome in the GitHub issues.

A small wave of updates, this time focused on the United States: three official open data integrations (NOAA, NIFC), no account or key required, and an update, recap here upon release:

  • US Wildfires: Current fires near you according to NIFC (name, distance, burned area, percentage of containment), with a trigger for a new fire within the selected radius, the American equivalent of Canada Wildfires by @lmilcent
  • Hurricanes (NHC): Active tropical storms and hurricanes from the National Hurricane Center (Atlantic, East and Central Pacific): category, wind, distance from home, and formation risk at 2 and 7 days, with triggers; more precise than GDACS for the United States
  • Severe Storms (SPC): The risk level of severe storms from the Storm Prediction Center at your location, today, tomorrow, and the day after tomorrow (from “storms” to “high risk”), and the probabilities of tornadoes, hail, and wind, in addition to the alerts from the National Weather Service by @Will_71
  • Avalanche Bulletins 1.1: In addition to BERA from Météo-France, the avalanche danger from American centers (avalanche.org: Colorado, Utah, Sierra, Northwest…)

If anyone was already on it, let me know :slight_smile:

Three of the four integrations from the American wave are out, in open data from NOAA and avalanche.org, without account or key:

All tested on real data from the day (storm Pena in the Pacific for the NHC, a small risk area in Texas for the SPC), not yet on a real Gladys installation, nor during a real day of storms. These are forecasts, not an official alert service. The US Wildfires are ready, they will arrive a little later. Your feedback is welcome :slight_smile:

Second US wave, open data without account or key, summary here upon release:

  • US Drought : the drought level of your county according to the US Drought Monitor (from D0 “abnormally dry” to D4 “exceptional”), its evolution week by week, with a trigger when it worsens, the American equivalent of VigiEau
  • US Power Grids : the grids of New York (NYISO) and New England (ISO-NE), and other operators that publish without a key: real-time wholesale prices by zone, consumption, production mix and low-carbon share, in addition to CAISO by @lmilcent
  • US Lotteries : the draws of Powerball and Mega Millions (open data from the State of New York), with your lucky numbers and a trigger when they come out
  • Amtrak : your Amtrak trains in real time (delay, next station, estimated arrival time), with delay and arrival triggers, according to the open Amtraker API (unofficial)

If someone was already on it, let me know :slight_smile:

Two of the four integrations from the second American wave have been released, without account or key:

Tested on real data from the day (the draws of the week, the California Zephyr over several days of travel), not yet on a real Gladys installation. Gladys 5.3 is required.

The other two are ready and will arrive a bit later, along with the US Wildfires from the previous wave: US Drought (US Drought Monitor, by county), and the electric grids, which will ultimately only cover New York (NYISO): ISO-NE, MISO, SPP, and PJM do not publish anything open and stable without an account. Your feedback is welcome :slight_smile:

The next 1000 integrations to develop :smiley:

The last three announced American integrations at numbers 459 and 461 are out, in open data without account or key:

Tested on real data from the day, not yet on a real Gladys installation. Gladys 5.3 is required. This concludes the American series: eight integrations in total. Your feedback is welcome :slight_smile:

I’m taking five P1s from the list, all testable without hardware or paid account, summary here at the end:

  • Piper / Wyoming (tts) : Gladys speaks with Piper, locally and in French, via the Wyoming protocol, so also with any other Wyoming server (lines 1 and 2 of the list)
  • Google Translate TTS (tts) : the free voice of Google Translate, without key or account
  • Local AI (ai) : the Gladys assistant on your own models, with Ollama, LM Studio or any OpenAI-compatible server (lines 9 and 41). The Ollama integration I made remains of type device, for scenes: this one is a real AI provider
  • Local Lists (provider) : task and shopping lists for the household, stored in Gladys without any external service, with a widget and scene actions
  • ESPresense : room-by-room presence of your phones, watches and tags, according to ESP32 ESPresense via MQTT

If anyone was already on it, let me know :slight_smile:

I’m taking five P1s from the new list (t/11535), all testable without hardware or paid account, summary here at the end:

  • Piper / Wyoming (tts) : Gladys speaks with Piper, locally and in French, via the Wyoming protocol, so also with any other Wyoming server (lines 1 and 2 of the list)
  • Google Translate TTS (tts) : the free voice of Google Translate, without key or account
  • Local AI (ai) : the Gladys assistant on your own models, with Ollama, LM Studio or any OpenAI-compatible server (lines 9 and 41). The Ollama integration I made remains of type device, for scenes: this one is a real AI provider
  • Local Lists (provider) : task and shopping lists for the household, stored in Gladys without any external service, with a widget and scene actions
  • ESPresense : room-by-room presence of your phones, watches and tags, according to ESP32 ESPresense via MQTT

If anyone was already on it, let me know :slight_smile:

The five P1 items from the new list reserved earlier have been released, all in v1.0.0:

You need Gladys 5.3 for the first three. None have yet run on a real Gladys installation, your feedback is welcome :slight_smile: