Hello everyone,
Here’s what happened over the past two days on my 24 external Gladys integrations. There have been many changes. Don’t forget to update from the store.
Tuesday, October 7: Common Bases
On all 24 repositories:
- Automatic manifest verification on each pull request, with the same checks as the Gladys store. A manifest error is thus detected before publication.
- Dependabot enabled: GitHub actions and the Docker image are automatically updated.
- A GitHub Release for each version, with its changelog, to easily track what changes.
Frequent fixes:
- Widgets that no longer displayed anything: Gladys now waits a maximum of 15 seconds. Beyond that, the widget remained broken until the page was reloaded. Now, the widget always responds in time (Air Quality, UV Index, Pollen, Forecast.Solar, Proxmox, PBS, TCL, VigiEau, TV Guide).
- Clearer connection status: it indicates what’s wrong, instead of « disconnected » (NUT, Proxmox, PBS, Electricity Maps, LG ThinQ).
New features:
- Mammotion: widget, scene triggers and actions (Gladys 5.1).
Wednesday, October 8: A Complete Audit
Each repository was audited. Common points:
- Node 22 minimum, tests on Node 22 and 24, and Docker image built on each pull request.
- Stricter image (npm ci, pinned base image for some integrations).
- Node 26 was tested, then we reverted to Node 24 pending Node 26 becoming LTS.
- Documentation (EN/FR) and changelogs updated.
Main points, integration by integration:
- Apple Device Tracker: clean recovery after an iCloud failure, without multiplying connections on the account
- Broadlink: IR/RF codes sent only once, codes published as buttons (no longer as switches), codes.json file protected against corruption
- Daikin Cloud: API quota better protected, failed reads reported, sessions preserved
- Devmel AirSend: timed shutter stopped on time even in case of error, orders not replayed by mistake, service restarted only after several failures
- Electricity Maps: faster retry, respect of Retry-After, fewer duplicates in history
- Forecast.Solar: quota respected, coordinates hidden, less history
- Home Connect: quota saved, recovery after a failed startup, refreshed token preserved
- Host Supervision: measurements continue even if Gladys or the host has an issue
- LG ThinQ: pause when Gladys is away, quota protected on forced reads
- Mammotion: refusal of a second mowing launch in preparation, session errors better recognized
- NUT (UPS): more robust reads, status grouped on all servers
- Olvid: each call to the daemon is time-limited, session preserved during Gladys reconnections
- Pollen: one request per cycle, new attempt in case of network outage, sends limited to not exceed Gladys’ quota
- Fuel Prices: dates in Paris time, search kept for 5 minutes, distance removed from device parameters
- TV Guide: more reliable guide download, widget and status fixed
- Proxmox VE: maximum delay for each request, one VM list read per cycle
- Proxmox Backup Server: time-limited requests, certificate pinning possible, removed datastores removed
- Air Quality: retries, Open-Meteo reads grouped, safer location editor
- Synology: NAS with self-signed certificates work again, certificate pinning possible
- TCL Lyon: schedules in Lyon time, new device read immediately
- UV Index: retries, last value kept as a backup, hourly cache, grouped reads
- VigiEau: refresh, location list and logs strengthened
- Yoto: refused token refreshed, new attempt on startup, less frequent queries
- Z2M Devices Monitor: TLS with a private certification authority, broker outages tolerated, backup maintained even if Gladys is down
Next: New Plugins, and I Need You
Pierre-Gilles kindly offered me a Team Premium seat. A big thank you to him ![]()
Thanks to this, I will develop other plugins for Gladys.
To choose the next ones, I will pick from this topic: Most Popular Home Assistant Integrations: Candidates for Gladys External Integrations
Don’t hesitate to share your opinion or vote for those that interest you. This will help me choose the order.
But I won’t necessarily have all the equipment at home. I will therefore need testers:
- If you have one of the devices or services from this list, let me know here.
- If you want to test a version before its release, reply to this topic indicating your hardware.
- Feedback on existing integrations (bugs, ideas) is also welcome, on the forum or on GitHub.
Thank you all for your feedback. It’s what drives these integrations forward ![]()