Version 4.86.0 is out, and this one is simple to describe: it's the biggest release in the history of the project. 🚀

The numbers speak for themselves. In 7 days, we merged 68 pull requests, touching more than 1,000 files and adding around 28,000 lines of code. For comparison, our biggest releases used to top out at 35 pull requests, over two weeks. We just did twice that, in half the time.

And this isn't a one-off spike. Every single week, we blow up the productivity of this project a bit more, and the reason is no secret: AI. Out of the 68 pull requests in this release, 62 were co-authored with Claude. Specs, implementation, tests, code review, even the CI that fixes its own failures: AI is now everywhere in the Gladys development loop, and the result is a pace this project has simply never seen before.

👉 You can follow that pace live, day by day, on the development activity page. Commits, contributors, streaks: everything is there, updated automatically.

Now, let's look at what actually landed in your home.

📱 A new Devices page​

Until now, seeing every device in your Gladys meant walking through each integration one by one. That's over.

Gladys now has a Devices page, in the main menu, listing all the devices of your instance in one place:

• Search by name
• Filter by room and by integration
• Sort them A-Z, Z-A, or by room
• See at a glance the features of each device
• Jump straight to the device in its integration with Open in integration

It sounds simple, and that's exactly the point: when you have 60 devices spread across 8 integrations, this page becomes the one you keep open.

🍏 HomeKit becomes a first-class citizen​

This is probably the biggest chunk of work in this release. The HomeKit bridge went from "lights and sensors" to almost everything Gladys knows how to control.

Newly exposed to the Home app on your iPhone:

• Thermostats (with modes and operating state)
• Locks
• Fans
• Buttons
• Smoke sensors
• Presence sensors, exposed as HomeKit Occupancy Sensors
• Device batteries, so iOS warns you before a sensor dies
• Your house alarm, exposed as a HomeKit Security System: you can arm and disarm Gladys straight from the Home app, or with Siri

And because exposing everything isn't always what you want, you can now choose exactly which devices are visible in HomeKit:

The bridge restarts automatically when you save, and your pairing is kept: no need to remove and re-add Gladys in the Home app.

Two long-standing bugs were also fixed along the way: thermostat modes are now mapped correctly, and HomeKit services are looked up by feature instead of by device type (which used to break devices that mix several categories).

🌤️ A brand new weather widget, and a sun widget​

The weather widget has been fully redesigned, and it now shows a lot more than the current temperature:

• Hourly forecast and daily forecast
• Rain (amount and probability), wind and its direction
• UV index, pressure, humidity, moon phase
• Weather alerts
• And a display mode selector: you pick the blocks you want, the widget shows only those

Next to it, a brand new Sun widget shows the position of the sun over your day: sunrise, sunset, dawn, solar noon, dusk, plus the current azimuth and elevation, drawn as a horizon curve.

Small but satisfying detail on dashboards: chart tooltips now follow your cursor instead of covering the curve you're trying to read.

🧩 An integrations catalog you can finally browse​

With native integrations plus 45 community external integrations already published, the catalog needed a real structure. It now has one:

• Browse by category: heating & cooling, lighting, energy, cameras & security, multimedia, protocols & hubs, network & presence, messaging, voice assistants & AI…
• Facet filters: Native, Community, Local, Cloud, Gladys Plus
• Sort by newest first, to see what the community shipped this week
• New and Soon deprecated badges
• Accent-insensitive search (typing "camera" finds "caméra")
• Your filters and sort order are kept when you navigate back from an integration page

And when a search returns nothing, Gladys now points you to the external integrations: the recommended way to add a new device compatibility, that you can build yourself in an afternoon.

🎬 Scenes: loops, variables and calendars​

Scenes got their biggest upgrade in a long time.

• Loops. A new "As long as… repeat…" block repeats a group of actions while its conditions hold. Conditions are re-evaluated before every iteration, so a "Get last state" action placed before a condition refreshes its value on every loop. A maximum number of iterations acts as a safety limit.
• Set a variable. A new action defines a variable (fixed text or a computation), reusable in every following action of the scene.
• Get calendar events. A new action fetches the events of the day, of tomorrow, or of the next X hours from your shared calendars, and hands the next actions a ready-to-use sentence, the number of events and the event list. Perfect for a morning announcement on your speaker.
• Multi-select in the device state trigger. One trigger can now watch several features of the same type: the scene starts as soon as one of them matches.
• Choose the channel of the "Send a message" action, instead of always broadcasting to every configured messaging service.
• Send text to a device directly from the "Control a device" action.
• Value lists in the editor now show readable labels instead of raw numbers.

📡 MQTT: Home Assistant Discovery​

Big one for MQTT users: Gladys now understands the Home Assistant Discovery protocol.

Any device publishing its configuration on the homeassistant/ topic of your broker is discovered automatically and shown in a new Discovery tab. You name it, pick a room, and add it to Gladys in one click.

In practice, that's a huge number of ESPHome, Tasmota, Zigbee2MQTT and DIY devices that now show up in Gladys with zero manual configuration.

🎥 Cameras: PTZ control​

Motorized cameras can now be moved from Gladys. A camera device can expose:

• A movement feature (pan left/right, tilt up/down, zoom in/out, stop)
• Presets you define yourself (name + value sent to the camera), to recall a framing like "Entrance" or "Garden"
• Pan, tilt and zoom position features

A directional pad and a preset selector appear on the live view of the camera widget, and in the room widget. You choose which movements your camera actually supports, so only the working buttons are displayed.

Also fixed: cameras now keep their true colors in fullscreen in dark mode.

⚡ Energy: solar production and grid flows​

Gladys now models a full home energy flow, with new device feature categories:

• Production sensor: production power (your solar panels)
• Grid sensor: import power, export power, signed grid power (import +, export −), and import/export indexes
• Home output sensor: home output power and index, including off-grid output

On top of that, Gladys can now compute a production index from meter readings, the same way it already did for consumption, so you get proper production history even from devices that only report a raw index.

🧠 New device feature types​

Several new building blocks landed for integrations and for MQTT virtual devices:

• Text and Selection feature types. "Selection" lets you define your own list of choices (scenes, modes, sources…) with a readable label and the value published to your device.
• A Maintenance category, to track the remaining life of consumables (vacuum brush, filter…).
• NO2, O3 and SO2 sensors, alongside the existing air quality categories.
• A per-feature setpoint step, driven by the device: your thermostat can now step by 0.5 °C when it supports it, instead of a hard-coded 1.

🤖 The AI keeps learning​

Gladys' AI assistant can now answer weather questions in the chat: "What will the weather be like tomorrow?" is answered from your configured weather provider, like temperature or humidity questions already were.

Also fixed: when you ask a question about the whole house instead of a specific room, the AI no longer gets confused about what you're targeting.

🏠 House: find your address by typing it​

Setting the location of your house no longer requires hunting on a map: type your address, and Gladys finds it. The search is powered by OpenStreetMap (Nominatim), and Gladys tells you clearly that the address you type is sent to that third-party service.

🔌 Integrations and external integrations​

• External integrations can now be installed and updated from a locally built Docker image. No registry needed, which makes developing one much faster.
• A new Wake-on-LAN permission: an integration can ask to send magic packets through Gladys on your local network, and you approve it explicitly.
• Docker images left behind by external integrations are now cleaned up.
• A new account link configuration field, for providers that don't use OAuth2.
• Zigbee2MQTT: support for HS1SA-E features, the container restart policy is reconciled on startup, and the scene action now makes it clear that the topic must include the zigbee2mqtt/ prefix.
• Z-Wave JS UI: the built-in integration is now flagged as deprecated in the catalog, and every one of its devices gets a Migrate button to move it, with its history, to another integration.
• Published MQTT and Zigbee2MQTT payloads are now logged, with a warning on invalid JSON. Debugging an automation just got a lot easier.

🛠️ Under the hood​

This is where the AI-driven pace really shows. In one week:

• Gladys now runs on Node.js 24.
• Server tests run in parallel, one worker per core, with a snapshot-based database reset and per-file sandboxes. The test suite went from a bottleneck to a non-issue.
• The Cypress CI job was slimmed down and cached.
• Security: all high and critical dependency advisories were patched.
• Sequelize was upgraded to 6.29.
• Scene condition formulas now fail closed, with a pinned operator surface.
• And the CI now runs a daily automated fix pass: review-bot feedback fires Claude Code cloud sessions that open the fix themselves.

Plus a long tail of interface fixes: the water heater boost control no longer overflows narrow dashboard cards, drag & drop works with a mouse on touchscreen PCs, motion sensors stop showing their last state report as their last motion, binary buttons are labeled with the action they apply, and the integrations badge is aligned in the mobile menu.

🚀 Why this pace matters​

I want to be clear about what's happening here, because it's the most important part of this release.

A release of this size used to be a multi-month effort. This one took one week, and not by cutting corners: the specs are written, the tests are there, the code is reviewed, and the test suite actually got faster along the way. AI removed the part of the work that was pure friction: boilerplate, tests, refactors, review passes, CI plumbing.

What that means for you is simple: the features you ask for on the forum now ship in days, not quarters. Several items in this release came straight from a forum thread this week.

👉 Follow the project's pace on the development activity page. It's updated automatically, and honestly, it's become my favorite page of the website.

❤️ Thank you​

Huge thanks to everyone who contributed to this release: @Dreamthy, @William-De71, @callemand, @cicoub13, @bertrandda, @prohand, @Terdious, Stéphane Escandell and Anupam Mediratta.

And thanks to everyone publishing external integrations: the catalog went from 20 to 45 community integrations in two weeks. If your device isn't supported yet, you can now build it yourself.

As always, Gladys updates automatically within 24 hours if you use Watchtower, otherwise you can do it in one click from the settings.

Remember to set up Telegram to get an alert on your phone when Gladys updates!

See the full release notes on GitHub

Version 4.84.0 is out, and it's probably the most important release in the history of the project. 🚀

For 6 years, we patiently built 36 integrations inside the Gladys core. Each one required a pull request, a review, tests, and a lot of my time. That was the bottleneck of the project.

Today, that bottleneck is gone. With external integrations, anyone can build and publish a Gladys integration, without asking my permission. The result came fast: 20 integrations are already available, built in a few days by 6 different contributors.

In other words: in a few days, the community produced more than half of what we had achieved in 6 years. This is a step change for the project.

🧩 How external integrations work​

An external integration is a Docker container supervised by Gladys. It talks to Gladys through a dedicated API, and Gladys automatically generates its whole interface: device list, discovery, configuration form.

Concretely, for you as a user:

• You open the integrations catalog in Gladys
• External integrations show up next to the native ones, with a community badge
• You click Install: Gladys pulls the image, starts the container, and displays the interface
• You can start, stop, update it, view its logs or uninstall it, right from Gladys

Each integration runs in an isolated sandbox (256 MB of RAM, 0.5 CPU, read-only filesystem, isolated network). If an integration crashes, it crashes alone: it cannot take your Gladys instance down with it. That guarantee is what makes it safe to publish without review.

📦 20 integrations, in a few days​

Here is what the community has already published:

Devices: Airzone Cloud, De Dietrich, Enki, Freebox, MELCloud, MELCloud Home, MyNeomitis (Axenco), Netatmo, Philips Hue, Roborock, SmartThings, Spotify, TP-Link Kasa, Tuya, UPnP / IGD, Zendure

Messaging: CallMeBot, Free Mobile SMS, ntfy, Telegram

Thanks to @callemand, @cicoub13, @Dreamthy, @Terdious and @William-De71 for these first integrations!

👉 Browse the full catalog on the website, updated live.

👨‍💻 A call to developers: we need you​

This is where I need you.

If you own a device Gladys doesn't support, you can now make it work yourself, and share it with the whole community. Here is what that means in practice:

• A template to clone. The official template already contains a working integration (sensors, a switch, a dimmable light, a plug, a camera), the JavaScript SDK, a Dockerfile and a GitHub Actions workflow that builds and publishes your image in one click. You start from something that runs, and replace the logic with yours.
• With AI, it's even faster. The simplest path today: clone the template, and ask Claude to rewrite the integration for your device starting from that base. That's exactly how I ported the CallMeBot integration to an external integration, and in my experience the result was good on the first try.
• You're not alone with your protocol. Many devices already have an open-source library or integration somewhere else. You can take inspiration from it, or reuse the existing dependency directly: that's often the bulk of the work already done.
• No pull request, no review, no approval from me. You publish a public GitHub repository with a manifest file, you add the gladys-assistant-integration topic, and that's it.
• Published within an hour. An automatic indexer runs every hour, validates your manifest, and publishes your integration in the catalog of every Gladys instance.

There has never been an easier way to contribute to Gladys. If everyone brings the integration they need, we can cover in a few months what we would never have covered in years.

👉 Read the step-by-step developer guide

And if you publish something, come show it on the forum: I can't wait to see what you build.

🤖 Gladys' AI keeps improving​

The AI assistant keeps getting better, with several requests coming straight from the forum:

• Full light control: you can now ask Gladys to set the brightness, the color and the color temperature of a bulb, not just turn it on or off.
• Energy questions: Gladys now answers consumption (kWh) and cost questions over a date range ("how much did electricity cost me in July?").
• More reliable scene creation: a two-stage tool routing significantly improves the quality of AI-generated scenes.
• Better formatted answers: the Markdown in AI answers is finally rendered properly in the chat. No more raw **27 °C**.

🏠 Matter​

• Air conditioners: operating mode management (Thermostat SystemMode), requested on the forum.
• CO2 sensors: now supported.
• Fixed a "Cannot mix BigInt and other types" crash on electrical attributes.
• Updated matter.js to 0.17.6.

🔌 Other integrations​

• Enedis: energy costs are recalculated after each sync.
• CalDAV: better sync, with support for deleted events.
• Zigbee2MQTT: the IEEE address and the Z2M link are no longer lost after saving a device.
• MQTT: an empty custom topic no longer matches every message, and the "manually stopped" status is properly cleared when saving the configuration.
• Telegram: the integration can now be disabled (stops the bot, deletes the key, unlinks users).
• RTSP cameras: more readable logs when an image poll fails.

🖥️ Interface​

• Charts: displayed units now follow the live device feature units, and undefined values no longer break formatting.
• Dashboard: it is now clear that tablet mode only applies to the current browser.
• Integrations catalog: your filters and sort order are preserved when you navigate back from an integration page, and a button lets you refresh the catalog on demand.

🛠️ Technical​

• Service dependency installs are now parallelized (4 at a time), which noticeably speeds up the Gladys build. This is on the development side only: it changes nothing on your instance.
• Messaging service failures are now isolated: one failing service no longer prevents the others from delivering the message.
• On the CI side: branch Docker images are automatically pushed to the GitHub registry, and a /build-arm64 command builds an ARM64 image on demand on a PR.

❤️ Thank you​

Thanks to everyone who contributed to this version, and especially to the first external integration developers who jumped in before the official announcement. In a few days, you proved the model works.

As always, Gladys updates automatically within 24 hours if you use Watchtower, otherwise you can do it in one click from the settings.

Remember to set up Telegram to get an alert on your phone when Gladys updates!

See the full release notes on GitHub

Version 4.83.0 is available! After the major 4.82 release (Activity journal + MQTT), this version focuses on reliability, performance, and a few very concrete daily improvements — especially for installations with a lot of history, and for Gladys Plus.

⚡ Activity page: instant display, even on large databases​

On an installation with hundreds of millions of states, filtering activity on an infrequent category (openings, buttons…) could freeze the interface for several tens of seconds.

The Activity page now loads the history in progressive time windows: the first events are displayed immediately, and the search continues in the background with a banner like « Searching for activity — {month}… ».

On a database of 448 million states, an « Openings » filter that took 20–33 s to respond now displays the first results in ~100 ms.

Thanks to @Terdious for this work!

🧹 Automatic cleanup of orphaned states (DuckDB)​

Since the migration of histories to DuckDB, a bug caused the « no longer keep history » purge of a feature, as well as the deletion of devices in some cases, not to clean up states correctly in DuckDB.

Result: « zombie » states (features without history, or already deleted features) could accumulate for years without anyone noticing — until the Activity journal arrived.

This release fixes the purge, and runs once at startup a background job that cleans up orphaned states, gently (in batches, with pauses), to avoid saturating the CPU or blocking the rest of Gladys.

On a test installation, 45 million orphaned states were purged. You can follow the progress in Settings → Tasks.

Thanks again to @Terdious!

🔐 Gladys Plus: 2FA flow redesigned​

The entire Gladys Plus two-factor authentication flow has been reworked to better handle many small unpleasant cases that had been reported (missing configuration, code errors, going back, etc.).

Don’t hesitate to share your feedback on 2FA. I really want it to be simpler for beginner users, and I’m aware that the authentication steps remain a bit complex for a non-technical user.

A next step would be to add recovery codes, so you can reset 2FA yourself if you lose your phone or authentication app.

🛟 Gladys Plus restoration: no more temporary account​

When restoring a backup from the registration screen, Gladys previously created a temporary local account with hardcoded credentials. If the flow was interrupted or failed, this account could remain, block registration… and leave an instance in a painful state.

This temporary account has been removed. Restoration works without creating a local user, and instances already « blocked » by an old temporary account are automatically healed at startup.

🎬 Scenes: duration in seconds on state trigger​

On the Device State Change trigger, the option « run after the condition has been valid for… » only offered minutes.

You can now choose seconds or minutes — practical for reacting quickly (e.g. « if movement remains detected for 10 seconds »).

Existing scenes remain in minutes by default.

🖥️ Interface​

• Dashboard: widget types are sorted alphabetically according to the interface language (thanks @Will_71)
• Scenes: same for trigger and action lists (thanks @Will_71)
• MQTT: excessive vertical spacing corrected in the device list
• Activity: horizontal scroll of filters improved on Windows
• Scenes: fixed a black gap on multi-line variable chips
• HomeKit: color temperature values out of bounds (e.g. LED strips) are now bounded to the max HomeKit value (500 mireds), which avoids HAP warnings like « characteristic was supplied illegal value »

🛠️ Technical​

• DuckDB migration: switch from the duckdb package (deprecated) to @duckdb/node-api. Same engine, same .duckdb files: no data migration on the user side. Precompiled binaries replace native compilation.
• Automatic publication of the Gladys Plus front-end after a production release

❤️ Thanks to the contributors​

A big thanks to @Terdious and @Will_71 for their contributions to this version, and thanks to the entire community for your feedback and tests — especially those of you who run Gladys on very large history databases: it’s thanks to you that we can validate these performances in real conditions.

As always, Gladys updates automatically within 24 hours if you use Watchtower, otherwise you can do it in one click in the settings.

Don’t forget to configure Telegram to receive an alert on your phone when Gladys updates!

See the full release notes on GitHub.

Today I'm releasing what is, so far, one of the biggest releases of the year, and there's a real reason for that.

We're clearly at a turning point in the way software gets built: AI models keep getting more powerful, and the tools to use them day to day are finally becoming mature. Over the past two weeks, two of them changed the way I work on Gladys.

Claude Fable 5, Anthropic's flagship model, the one that was temporarily restricted in the United States because its capabilities worried the authorities. It let me tackle very technical topics that would have taken me entire days, and build major features like the Activity journal I detail below.

Cursor's cloud AI agents, controllable from mobile. About ten days ago, Cursor launched its iOS app: you can now hand a development task to an agent straight from your phone, and let it work autonomously, without a computer. The complete redesign of the MQTT integration was done entirely by a Cursor agent while I was travelling.

🏠 New Activity page: your home's history, live​

The flagship feature of this release: a new Activity tab that displays a visual timeline of everything happening in your home, door openings, motion detections, lights turning on and off, sensor values, and more.

What makes this page useful every day:

• Timeline grouped by day ("Today", "Yesterday", then full dates) with colored icons per event family.
• Burst grouping: consecutive states from the same sensor are merged into a single line with a ×N badge, expandable to see each timestamped occurrence. Essential for setups with 100 to 200 devices.
• Filters by family (Openings, Motion & presence, Buttons, Lights, Climate, Security, Energy, and more), a room selector, and device search.
• Real time, with a floating "N new events" pill when you've scrolled down.
• Infinite scroll with pagination.

📡 MQTT: a complete redesign of the virtual device experience​

The MQTT integration gets a major UX overhaul, inspired by community feedback (forum):

• Compact list of devices grouped by room.
• Feature catalog with a realistic dashboard preview and search.
• Auto-generated external IDs (mqtt:{slug}-{4chars}), always editable.
• Copy button for MQTT identifiers and URLs.

🤖 AI: model selection and improved context​

I keep pushing the AI agent inside Gladys, because I'm convinced it's the future of home automation: controlling your home by voice or text, running any action, querying your sensors.

This release adds an AI model selector in the chat. You can test the different Scaleway models (Mistral, Llama, Qwen, Gemma, and more) and compare their answers in real situations at home. A cost indicator (€, €€, €€€) helps you get your bearings.

Once the best model is identified, I'll do the math to integrate it durably into Gladys Plus, in a way that's sustainable for the project. In the meantime, test it and share your feedback on the forum!

Other AI improvements:

• Richer context: irrelevant tool calls and messages are excluded from the context for better answers.
• Fixed the "turn a device on/off" action schema.
• Enriched debug file (last 50 messages).

⚡ Tuya: smart meter support​

• Support for Tuya smart meters, both cloud and local.
• Reading through the Thing Model shadow API for devices without legacy specifications.
• Measurements: total power, active/reactive energy, voltage, current.
• Clean display names (Tuya code typos no longer leak into the UI).
• A fixture-based test infrastructure to industrialize adding new Tuya devices.

📱 Interface & dashboard​

The Gauge widget now supports a customizable name to tell apart several gauges from the same device (for example two MQTT water tanks), and we fixed the scroll getting stuck on mobile when you rested your finger on a gauge.

On the mobile side, action buttons and headers are now responsive across many pages (integrations, settings, and more), with buttons stacking on mobile and better wrapping of button groups.

🔧 Integrations & fixes​

🛠️ Under the hood (for contributors)​

• Frontend migration from preact-cli (webpack) to Vite: faster dev startup, improved HMR, a modernized build. Nothing changes for the end user, but it's a healthier technical foundation for what's next.
• New supported_options field on DeviceFeature: integrations can now declare the modes and values supported by a feature (for example vacuum modes).
• Expanded developer documentation (AGENTS.md).

❤️ Thanks to the contributors​

Thanks to @Terdious, @Will_71, @Sescandell, and @bertrandda for their contributions, and to the whole community for the feedback on MQTT, the Activity journal, and mobile UX.

A word too for Gladys Plus subscribers: it's thanks to you that I can pay for the AI tools that make all of this possible. If you want to see Gladys move even faster, Gladys Plus is the best lever. On top of supporting the project, you unlock the advanced features: backups, AI agent, remote access, voice assistants, MCP integration, Enedis, and many more.

As always, Gladys updates automatically within 24 hours if you use Watchtower, or you can do it in one click from the settings. See the full release notes.

Version 4.81 is here 😀 This release brings rolling shutter control to the AI agent and Alexa, a new AI quota display, several Zigbee2MQTT improvements, and a bunch of fixes.

🪟 Rolling shutters​

Shutters get a lot of love in this version:

• 🤖 A new device.set-shutter tool lets the AI agent control your shutters directly: open, close, stop, or set them to any position between 0 and 100%. You can now just ask Gladys to "close the living room shutters halfway".
• 🗣️ Shutters and curtains are now controllable through Alexa, with both open/close and position control.

🤖 AI​

A new quota display gives you full visibility on your AI usage: you can now see your remaining text and image requests, their reset dates, and your real-time status under Integrations → Artificial Intelligence. No more guessing how much you have left.

📡 Zigbee2MQTT​

Two nice improvements for Zigbee users:

• 🔑 The interface now displays your MQTT credentials (host, port, username, and password), with a toggle to show or hide the password and one-click copy, making it much easier to connect external tools.
• 🔌 Added support for several missing coordinator types (dongles), including Home Assistant, SONOFF, SMLIGHT, Texas Instruments, and ZigStar models.

🎬 Scenes​

The Ask AI, Send Message, and Send Camera Image actions now automatically select the first available user and camera, instead of leaving the fields empty. One less thing to configure when building a scene.

💡 Philips Hue​

Fixed a bug where newly paired Hue bulbs required a Gladys restart before they could be controlled. The bridge now resynchronizes automatically, so new bulbs are immediately available.

🐛 Fixes​

• ✏️ Corrected the handling of accents and special characters in scene messages, AI prompts, voice notifications, and SMS.
• 🌡️ System settings now display your CPU temperature, with color-coded thresholds and an automatic refresh every 30 seconds.

❤️ Thanks to the contributors​

A big thank you to @Will_71 and @bertrandda for their contributions to this release. And thanks to the whole Gladys community for your feedback, tests, and ideas that keep the project moving forward! 🚀

As always, Gladys updates automatically within 24 hours if you use Watchtower, or you can do it in one click from the settings. See the full release notes.

Lots of new things lately 😀 This version 4.80 brings many stability improvements, fixes for Matter, Netatmo, and Tuya, plus several AI additions.

🤖 AI​

The AI agent keeps improving, with two new features:

• ➕ Added a new sensor.set-state tool, letting the agent directly change the state of certain sensors when asked. For example, you can use the AI to read a camera image looking at a meter and store the value it reads into a virtual device. You could also automatically read a license plate and store the number into a virtual device!
• 🐞 Added a button to download the AI's debug context as JSON, to make it easier to diagnose issues and share them with the community.

The AI-generated weekly reports now appear in the background tasks (Settings → Tasks), which lets you track their execution and easily spot any errors. A random delay was also added before they're generated, to avoid overloading the servers all at once.

🏠 Matter​

This version further improves Matter compatibility:

• 🌡️ Added local temperature reporting on compatible devices.
• 🔄 More robust connection process.
• 📝 Richer logs to make debugging easier.
• 🌀 Several fixes for Matter fans.
• 🎛️ Fixed a bug where a device's unique identifier changed when it was updated.
• ⚡ Reads the initial state of device features at startup.
• ❗ Errors when registering a device are now shown directly in the interface.

Matter.js was also updated to version 0.17.3, a major step forward bringing notably:

• Support for the Matter 1.5 / 1.5.1 specification, improving compatibility with the newest devices.
• A 20-50% reduction in memory usage, letting Gladys run even more smoothly.

📡 Integrations​

Tuya​

The Tuya integration keeps maturing: a new common mapping layer to improve device handling in both local and cloud modes, and an assistant to automatically create a GitHub ticket when a device is partially or not supported.

Netatmo​

Two important improvements: restored automatic OAuth token refresh, and a more resilient automatic reconnection in case of authentication errors, including during business API calls.

Zigbee2MQTT​

Zigbee devices now display their IEEE address as well as a direct link to open the device in Zigbee2MQTT, making diagnostics and configuration easier. Remember to add your Zigbee2mqtt interface URL in the settings to use this feature 😉

🐛 Fixes​

• Fixed a bug on scenes using the next sunrise trigger.
• Fixed an issue preventing a device from being saved when energy_parent_id was invalid.

❤️ Thanks to the contributors​

A big thank you to everyone who took part in this release: @cicoub13, @Terdious, and @Will_71. And thanks to the whole Gladys community for your feedback, tests, and contributions that keep the project moving forward quickly! 🚀

As always, Gladys updates automatically within 24 hours if you use Watchtower, or you can do it in one click from the settings. See the full release notes.

Gladys v4.79 is out 🙂, with a smarter AI agent, a better voice assistant, and support for more Matter devices.

🤖 Artificial intelligence​

This version brings several improvements to the AI agent:

• Scene creation: fixed the schema and increased the timeout to fix a scene-creation bug reported by @GBoulvin and @Jluc.
• Better error handling: clearer feedback when the AI doesn't respond.
• Tool calls via Telegram: you can now see tool calls on Telegram, just like on the web.

• New tools:
  • Web Request: the agent can query APIs or web pages. It's a personal need I implemented, and it's incredibly handy!
  • Compare Times: compares times of day.

These new tools unlock very powerful things, for example, fetching a store's opening hours and telling you whether it's currently open! Super useful in scenes via the "Ask the AI" action. The possibilities are endless.

🎙️ Voice assistant​

• Stop button to interrupt an answer in progress.
• Microphone detection: if no sound was recorded, Gladys now shows an error message.

🏠 Matter​

Extended support for new device types: vacuum cleaners, NO₂ sensors (nitrogen dioxide index), and fans.

📡 Zigbee2mqtt​

• Updated to Zigbee2mqtt 2.12.0
• Support for the SONOFF SNZB-01M remote (4 buttons)

🔧 Node-RED​

A version selector lets you move to a major version of Node-RED directly from the Gladys interface.

Handy for moving to v5, which just came out! ⚠️ Make sure the modules you use are compatible with v5.

🎬 Scenes​

• Wider value field for sensor thresholds
• A Back button to navigate more easily in the scene editor

☁️ Gladys Plus​

When a remote user is deleted on Gladys Plus, the corresponding local user is automatically deleted on your instance.

📋 Full changelog

As always, the update is automatic within 24 hours if you use Watchtower, or you can do it manually via Settings → System. Happy updating! 🎉

I just released Gladys Assistant 4.78! Here's what's new, starting with the headline feature: an AI-powered weekly report of your home.

🤖 AI weekly report​

The flagship feature of this version: the weekly home report. Every week, Gladys can send you a personalized summary of your connected home: comfort, energy consumption, disconnected sensors, trends, and practical advice.

By default, the report is sent every Sunday at 6pm, which is configurable in the "Artificial Intelligence" integration:

Here's a real example of a report from my own production home:

Hello, here is your weekly home summary for the period from June 2 to June 8, 2026.

Your total electricity consumption for this week was 55.99 kWh, for a cost of €8.26. We see a downward trend compared to the previous week, which showed a consumption of 59.12 kWh and a cost of €9.36. The washing machine plug in the utility room consumed 2.11 kWh over the period.

Regarding the maintenance of your equipment, several sensors are silent and need your attention. The CO2 sensor in the office hasn't transmitted data for several months. In addition, the bathroom motion sensor has been inactive for 5 weeks, and the presence detector in the toilet has been offline for a very long time.

Of course, we can make this report evolve if you have ideas!

📊 Dashboard: Link widget​

You can now add a Link widget to your dashboard to access an external interface in one click: Zigbee2mqtt, Tasmota, your router's interface, a NAS, a camera, etc.

Each link is customizable, title, URL, and icon (website, server, NAS, Wi-Fi, web interface…):

Handy for centralizing all your access points inside Gladys.

🔌 Integration list: redesigned on mobile​

The integrations page has been reworked for clearer, more pleasant navigation on mobile.

🧠 Removal of the old local "brain"​

The old local AI system (pre-recorded questions/answers) has been removed. It dated back to a time when AI didn't exist, and it gave a poor first impression to someone installing Gladys for the first time. Removing this old code makes Gladys lighter, drops an NLP library that's no longer useful, and helps Gladys start faster 🙂

⚡ Energy monitoring​

Fixed a grouping bug in the monthly/yearly consumption widget. Data should now display correctly over those periods.

🎬 Scenes​

When selecting a device property in a "device state change" scene trigger, devices without a room are now visible under a "No room" category. No more "ghost" devices that were impossible to select 🙂

📡 Zigbee2mqtt​

Two additions for Zigbee2mqtt users:

• DEVELCO keypad: support for keypad actions (disarm, arm day/night/all zones, exit delay, emergency).
• Alarm sirens: new trigger_alarm and stop_alarm actions (e.g. Bosch outdoor siren), usable in your scenes and automations.

As usual, the update is automatic within 24 hours if you use Watchtower, or you can trigger it in one click from the settings.

Thanks to the whole community for the feedback, tests, and suggestions. I'm very curious to hear what the AI weekly report looks like in your homes!

Full changelog: v4.77.0 → v4.78.0

I've published a new Gladys image for the Raspberry Pi, compatible with the Pi 3, 4, and 5.

This image is based on Raspberry Pi OS Trixie (Debian 13), 64-bit. It's available directly in Raspberry Pi Imager, under the Home automation category.

For the occasion, I also rewrote the installation tutorial on the site, with every step illustrated:

👉 Install Gladys on a Raspberry Pi

My take on the Raspberry Pi​

I'll be honest: I still don't think the Raspberry Pi is the best long-term option, a mini-PC remains more powerful and more reliable for a daily setup. I also strongly advise against using a microSD card: in practice, data corruption often happens after a few months. If you go with a Pi, plan for an NVMe SSD instead.

But for people who already have a Pi on hand, it's an excellent way to discover Gladys without dealing with Docker or the command line 🙂

What's next​

I'm keeping a strong focus on distribution and on finding ways to make Gladys easier to install, whatever hardware you have. The goal is for as many people as possible to be able to try Gladys and form their own opinion.

I'm working on an "Ubuntu + Gladys" image that would let you install Gladys on a mini-PC with fewer steps than a classic Ubuntu install. If you have ideas to make Gladys more accessible and easier to install, I'm all ears!

The repo: raspberry-pi-os-gladys

A new version of Gladys is available, with several nice improvements, including a brand-new Voice Assistant widget you can drop right onto your dashboard 🎙️

🎙️ New Voice Assistant widget​

You can now add a Voice Assistant widget directly to your dashboard.

Handy on a wall-mounted tablet or a smartphone. I'd love your feedback, it's first and foremost a proof of concept that could grow into more voice features in Gladys if you find it useful!

📊 Gauge widget: customizable color thresholds​

Thanks to a contribution from @Terdious, the Gauge widget becomes even more flexible. You can now define custom color thresholds to instantly see whether a value is in a low, normal, or critical zone.

Perfect for tracking temperature, humidity, electricity consumption, or any other important indicator.

📥 System logs download​

Diagnosing a problem just got easier. A new button lets you easily download the system logs from the Gladys settings, which makes sharing information much simpler when you ask for help.

🔌 Tuya integration improvements​

The Tuya integration keeps progressing thanks to @Terdious:

• Local support for the Tuya 3.4 protocol
• Local support for the Tuya 3.5 protocol
• Various stability and compatibility improvements

Great news for Tuya users who want to keep local control of their devices.

📋 Full changelog

Happy updating, everyone! 🎉

Since I first integrated AI into Gladys, the promise was there but the reality stayed limited: you asked a question, the AI answered. One input, one output. No intermediate reasoning, no real autonomy. What I'm announcing today changes that, deeply.

Gladys can now "think" before answering​

You may know Claude Code, Anthropic's development agent that, faced with a complex problem, breaks it down, iterates, uses tools, and adapts until it finds the solution. That's exactly the model I applied to Gladys.

From now on, when you ask Gladys a question, it no longer just tries to phrase an answer. It acts. It can chain several tool calls in a row to reach its goal:

• What's the current CO2 level in the living room?
• Turn on the living room lights and switch off the fan
• Show me my energy consumption over the last month
• Create a scene that every morning at 7am sends me a message with the CO2 level in the living room, the kitchen, and the state of my doors
• Create a scene that, when there's motion in my garage, sends the AI a photo from my camera and checks whether the car is my red Tesla Model 3. If it is, the AI stays silent; otherwise, it warns me that an unknown car is there.

These are requests that would have required several manual steps before, or simply didn't work at all! This work builds in part on the MCP server developed by @bertrandda, which I integrated into this new architecture. Thanks to him!

A redesigned, genuinely usable interface​

I also took the opportunity to completely rebuild the chat interface. Clearer, smoother, and actually usable on mobile.

Each tool call is shown clearly in the conversation, so you understand what Gladys is doing and can easily diagnose anything that doesn't go as planned.

Telegram and Nextcloud Talk too​

Do you use Gladys on the go via Telegram or Nextcloud Talk? The improved agent is available on those channels as well, so you get all this power straight from your phone, without opening the web interface.

Try it now, for free​

First, update Gladys to v4.76.0. Then you'll need Gladys Plus, and I'm offering you a full one-month trial, no credit card required. Each account gets 3,000 requests per month + 500 image-analysis requests. That's more than enough to explore what the agent can do, and I'm curious to read your feedback on what works, what surprises you, and what you'd like to see next!

For the AI model, I've reached the limits of Mistral Small 3.2 with this tool, so for now I've switched to Gemma 4, still on Scaleway, hosted in France, with your data fully private 🔒

Of course there may be bugs, and I'm keen to hear your feedback 🙂

Do you have devices that aren't compatible with Gladys and don't use an open protocol like Zigbee or Matter? Don't worry. I've built an AI-powered Matterbridge plugin factory that automatically develops plugins for your devices. No development skills required.

Prerequisite: Matterbridge must be installed and configured. If it isn't yet, first follow this tutorial in the documentation.

How does it work?​

You open a GitHub ticket describing your device, the AI develops the plugin overnight, and all you have to do is test it. If something is wrong, you leave a comment and the AI iterates.

Step 1: Create a GitHub ticket​

Head over to the factory repository: 👉 matterbridge-ai-plugin-factory/issues

Click "New Issue":

Then select the "Plugin Request" template:

Fill in the form:

• Title: the name of the plugin you want
• Links: if you know of similar plugins on other projects (Home Assistant, Homebridge…), add the links. The more context you provide, the more relevant the result will be on the first try.
• Features: describe what you want to control. Examples: temperature, on/off, humidity, brightness…
• Additional context: optional, but useful if your device has any quirks.

Tip: if you don't know what to put in the links, say so in the description and ask the AI to search on its own. But the more precise you are, the better the result.

Step 2: Install and test the plugin​

The factory runs every morning and processes one plugin per run. Once yours is developed, the AI replies directly on the ticket with a download link:

Download the file, then in Matterbridge click "Upload +":

Then enter the plugin name in the "Plugin Name" field and click "Add +":

The plugin is installed, you can test it!

Step 3: Give feedback​

If the plugin doesn't work as expected, leave a comment on the GitHub ticket. The AI will read your feedback and fix the plugin on the next run:

Don't hesitate to open tickets, that's exactly what it's for! And if you have questions about how the factory works, ask away.

I'm really proud to see Gladys featured on Antoine Guilbert's blog, a French home automation blogger who produces excellent, high-quality content 🙂

The article is great: well-researched, beautifully written, and it perfectly captures the vision behind Gladys and what we're trying to build with the project.

I really recommend giving it a read, it's a genuinely pleasant one:

👉 Read the article on AntoineGuilbert.fr

And to encourage this kind of initiative and content around Gladys, feel free to leave a little comment under the article or share it on your social networks 🙏

I just added a new page to the documentation: the recommended hardware to build a reliable home automation setup with Gladys.

👉 See the recommended hardware page

The idea behind this page is to give a clear reference for someone starting from scratch and wondering what to buy. Instead of spending hours comparing dozens of products across forums, you get a curated list of well-rated devices that are compatible with Gladys.

Everything is based on Zigbee, it's what I use at home, and what I show in the video training course.

Feel free to send me your feedback: if you have devices you particularly like and that deserve a spot on the list, I'm all ears!

A new version of Gladys Assistant is available, with several fixes and improvements around Matter, Zigbee2MQTT, and sun-based scenes ☀️

✨ New features​

🌅 Offset before/after sunrise and sunset​

You can now configure a delay before or after sunrise and sunset in your scenes. A few example use cases:

• Turn the lights on 30 minutes before sunset
• Close the shutters 15 minutes after sunset
• Trigger a scene before sunrise

Thanks @cicoub13 for this contribution 🙌

💡 Zigbee2MQTT: Philips Hue Dimmer Switch v2 added​

Support for the Philips Hue Dimmer Switch v2 remote has been added in Zigbee2MQTT. You can now easily use it in your Gladys scenes and automations.

🛠 Fixes​

• Matter: fixed a 409 error on some devices. Fixed an issue that could cause a 409 error when updating Matter devices sharing the same unique identifier.
• Gladys Plus: fixed an association bug on first login. Fixed an issue that could prevent a user from being correctly associated with Gladys Plus on first login.

Gladys updates automatically, or you can do it in one click from the settings.

👉 See the full changelog on GitHub. Thanks to all the contributors!

A new version of Gladys Assistant is available: v4.73.0! This release brings several important improvements around energy, Matter, Local Tuya support, and the Airplay integration.

🧩 Matter.js updated to 0.16.11​

Gladys now ships the latest version of Matter.js (0.16.11). This is a big update, we're moving up from 0.13.0, and it improves the compatibility and stability of Matter devices.

Please check that your Matter devices still work after this update, as there's a Matter.js file migration that was a little tricky for some users.

➡️ Pull request #2501

🔌 Local Tuya: the first foundation​

This first PR lays the groundwork for Local Tuya support in Gladys, which will eventually let you control some Tuya devices locally, without relying on the cloud. Thanks @Terdious!

➡️ Pull request #2434

⚡ Energy management & MCP optimization​

This version adds new energy features and improves the performance of the MCP (Model Context Protocol) used by AI clients. Thanks @bertrandda!

➡️ Pull request #2522

🔊 AirTunes library replaced​

The airtunes library has been replaced by airplay-sender to improve the stability and maintainability of the Airplay feature. Thanks again @bertrandda!

➡️ Pull request #2439

As usual, you can update Gladys directly from the interface, or simply wait for it to update on its own. Thanks to all the contributors 🙌

🔗 Full changelog

After several years of strong growth, Gladys Plus hit a plateau in 2025: growth slowed, then almost stopped. So I took a step back to understand what was holding it back, and invested a lot of time getting Gladys Plus back on track.

As you know, Gladys Plus is what funds a large part of the development of Gladys Assistant: the infrastructure, the encrypted services, the time spent on the project, and more broadly the independence of Gladys.

The goal is simple: make the offer clearer, easier to try, and better at explaining what it actually brings. Here are the main changes 👇

A new Gladys Plus page​

The Gladys Plus page has been completely reworked:

• prices are now much more visible;
• the differences between plans are clearer;
• the included features are better explained;
• the page answers frequent questions better;
• and there's a more honest comparison with Nabu Casa / Home Assistant Cloud.

The idea isn't to "oversell" Gladys Plus, but to clearly explain who it's for, what it brings, and why it's paid.

A much simpler free trial​

Before, you had to enter a credit card to try Gladys Plus. That was probably too much friction, especially for people who just want to test remote access, backups, or the Plus integrations.

It's now possible to start a one-month free trial without a credit card. The goal is to let more people try Gladys Plus with peace of mind, no strings attached.

A clearer offer​

I've also reworked how the plans are presented to better distinguish use cases:

• a lighter plan for those who mainly want remote access;
• a full plan for those who want all the Gladys Plus features.

Why I'm doing all this​

Gladys is an open-source, independent project, with no ads, no data resale, and no investors. That's a strength, but it also means the project needs a healthy business model to keep moving forward. Gladys Plus is the heart of that model.

My goal is to reach a level of revenue that lets me dedicate much more time to Gladys, keep improving the product, and grow the project sustainably.

How you can help​

If you use Gladys Plus: thank you so much ❤️

If you've never tried it, now is probably the right time:

👉 Try Gladys Plus free for a month

And if you know someone looking for a simple, local, open-source, privacy-friendly home automation solution, tell them about Gladys. Thank you all for your support over the years 🙏

I spent a lot of last week tinkering with Matterbridge, and I had a real "aha" moment I wanted to share: we're going to be able to make any device Matter-compatible, and therefore Gladys-compatible, without writing a single line of code.

A bit of context​

I've told you about Matterbridge before: a project that lets you install plugins to bring non-Matter devices into Matter. Today, Matterbridge already lets you use, inside Gladys:

• Somfy shutters
• Shelly devices (generations 1, 2 and 3)
• and soon, Roborock robot vacuums

But Matterbridge is still young, and it doesn't have a plugin for everything.

The problem it solves​

In Gladys, I've always taken the approach of building large, tailor-made integrations, spending a lot of time on the user experience and the interface. The trouble is, some of you have very specific needs: niche devices, sometimes no longer even sold. For those products, it's hard to justify the development time of a native integration that would serve only a handful of users.

What if those integrations could simply be Matterbridge plugins, developed by an AI?

The Matterbridge plugin system is well-defined, well-documented, and full of examples. And these integrations often already exist elsewhere in open source (Node-RED, Home Assistant): we can simply ask the AI to translate, say, a Node-RED plugin into a Matterbridge plugin. There's nothing to invent, it's just "translating code"!

What I tested​

I built a Matterbridge plugin for my Mitsubishi air conditioner, without writing a single line of code. I show the whole thing here:

And now?​

The logical next step: what if we fully automated the creation of Matterbridge plugins? Imagine a "plugin factory", driven by Claude Code, running on a server, that would pick up GitHub tickets and develop plugins with no human intervention.

With a system like that, we could industrialize the development of integrations and close the gap between Gladys and projects like Home Assistant. I genuinely think this is a revolution, and it confirms my decision to invest heavily in Matter this year, because it really is the future of the connected home.

What do you think?

Gladys Assistant 4.72.0 is available 🎉, with a faster AI, a more stable HomeKit, and a long list of fixes.

✨ New features​

• Zigbee: dual on/off support for the IKEA BILRESA button. The IKEA BILRESA button is now fully supported via Zigbee2mqtt.
• AI: lower latency and cost. Camera images sent to the AI are now resized before sending, which reduces both the latency and the cost of API calls.
• Integration list: tags added. Integrations are now tagged (local, cloud, Gladys Plus) to make their operating mode clearer.
• ZwaveJS UI: out of alpha. The ZwaveJS UI integration is stable enough, the alpha warning banner has been removed.
• MQTT: renamed to "MQTT Virtual Devices" to make the integration easier to understand for users coming from Home Assistant.
• Node-RED: warning before container deletion. A message now warns that deleting the Node-RED container also deletes all associated data.

🐛 Bug fixes​

• HomeKit: fixed high CPU usage related to mDNS. A bug caused abnormally high CPU usage. It's fixed by offering several mDNS options.
• Nuki: fixed handling of Home Assistant discovery messages. The integration was listening too broadly, which caused performance issues when many Home Assistant-compatible devices shared the same broker.
• CalDAV: configuration errors are now displayed directly in the interface.
• Backup restoration: more robust. Security was hardened in the Gladys Plus backup restore function, notably by using execFile for OpenSSL commands.
• User account creation: the text above the "email" field is now clearer.
• Zigbee2mqtt: fixed an energy tracking bug where devices with energy features were always shown in the "Discovery" tab.
• Energy monitoring: fixed a bug when deleting a meter in the Zigbee2mqtt integration.
• Matter: fixed color handling by using a numeric bitmap for optionsMask in Matter color control.

Thanks to all the contributors for this release: @bertrandda, @cicoub13, and @David-Digitis.

To update, you can wait 24 hours or go to Settings → System → Update. Happy Easter weekend, everyone! 🏠

Last week, Mistral released a new Text-to-Speech model (Voxtral) capable of running 100% locally, without sending any data to the cloud. I wanted to test it head-to-head against ElevenLabs, and honestly, the results are really good!

It complements their Speech-to-Text model released back in February. I put both to the test, and you can see (and hear) the comparison in my latest video:

A change in Gladys Plus: moving to Mistral Small 3.2 on Scaleway​

While exploring Mistral's models, I'm also announcing a change to the AI powering Gladys Plus.

I'm replacing OpenAI GPT-5 mini with Mistral Small 3.2, hosted in France on Scaleway 🇫🇷

The model is faster, cheaper, and your data stays with a sovereign French host. It's win-win-win! In concrete terms, this affects:

• camera image analysis
• proactive scenes
• conversations with the AI

And since the model is cheaper to run, I'm taking the opportunity to increase the monthly quotas included in the subscription:

• 3,000 text requests / month
• 500 camera image analyses / month

My goal is to unlock new use cases for you. If AI prices drop by another factor of 10 in the coming months, I'll raise the limits again 😀

If you haven't tried Gladys Plus yet, there's a free trial:

👉 Try Gladys Plus