Gladys Assistant 4.81: Shutters, AI quota and Zigbee2MQTT 🚀

News
1

Hello everyone!

Version 4.81.0 is available! :rocket:

This update focuses mainly on shutters (AI, Alexa), with several improvements around AI, Zigbee2MQTT, and some very useful daily fixes.

:window: Shutters

Following community feedback (Gladys AI and Alexa with my shutters), shutters and curtains are now better supported:

  • :robot: AI: Added a new tool device.set-shutter, allowing the agent to control your shutters (open, close, stop, position between 0 and 100 %)
  • Alexa: Support for shutters and curtains via Alexa, with control of opening/closing and positioning.

You can now tell Gladys „close the living room shutters“ via AI, or control them by voice with Alexa!

:robot: AI

  • :bar_chart: AI quota display in the interface (Integrations → Artificial Intelligence), to track your remaining text and image requests, the reset date, and real-time status.

Screenshot 2026-06-26 at 16.42.38
Screenshot 2026-06-26 at 16.42.381820×616 41.7 KB

:satellite_antenna: Zigbee2MQTT

Two improvements to facilitate configuration:

  • :key: Display of MQTT credentials directly in the Zigbee2MQTT configuration interface (host, port, user, password), with the ability to hide/show the password and copy the fields in one click. Handy for connecting other tools to your MQTT broker!

Screenshot 2026-06-29 at 09.55.36
Screenshot 2026-06-29 at 09.55.361994×1210 245 KB

  • :electric_plug: Added missing dongles to the list of supported coordinators (Home Assistant, SONOFF, SMLIGHT, Texas Instruments, ZigStar, etc.).

:clapper_board: Scenes

  • :wrench: The Ask AI, Send a message, and Send a camera image actions now automatically preselect the first available user (and the first camera if applicable), instead of leaving the field empty.

:light_bulb: Philips Hue

  • :bulb: Fixed a bug where a newly paired Hue bulb was not controllable until Gladys had been restarted. Gladys now automatically resynchronizes the Hue bridge when a new bulb is created.

:bug: Bug Fixes

:desktop_computer: System

  • :thermometer: CPU temperature display in system settings, with a colored indicator based on temperature thresholds. System information refreshes automatically every 30 seconds (CPU temperature display).

:heart: Thanks to Contributors

A big thank you to @Will_71 and @bertrandda for their contributions to this version, and thanks to the entire Gladys community for your feedback, testing, and ideas that help move the project forward! :rocket:

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

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

View the full release notes on GitHub

3

I’m using this post to talk about the use of SSH in Gladys.

As you know, more and more users are coming through the starter kit and have never used SSH on their installation. My goal is for everything to be achievable directly from the interface: if a feature is missing, don’t hesitate to let me know, I can add it, as was recently done for the Zigbee2MQTT integration :slightly_smiling_face:

SSH is not necessary to use Gladys, and ideally it never should be in the context of standard use!

In this sense, it’s best to avoid highlighting it on the forum, except for topics outside of Gladys or very technical needs among experienced users :slightly_smiling_face:

4

A reasonable compromise would be to have an « expert Â» mode with an integrated terminal communicating with the host PC.

5

I was wondering about updating the host that’s on Ubuntu
How could we manage that?
Given all the vulnerabilities we’ve seen lately, it’s important to remember to update the OS :slight_smile:

6

On Ubuntu, security and package updates are managed automatically.

As for the kernel, updates may require a reboot of the mini-PC to be effectively applied. In practice, it is therefore sufficient to restart the device from time to time (via the On/Off button in front of the mini-PC).

That said, on a mini-PC used only locally, on a private network and not exposed to the Internet, the level of risk remains generally quite low.

This isn’t really the direction of the project.

For advanced uses, SSH access to the host machine already does the job very well, with much more complete and mastered tools. The idea is rather to keep the application interface simple, and to leave the “expert” cases out of the scope of the UI :slight_smile:

7

Do you know how they are managed on Ubuntu?
I thought you had to use a specific tool to automatically handle security updates

8

Yes, Ubuntu uses unattended-upgrades to automatically install security updates. It’s enabled by default, so there’s nothing to configure. You just need to restart the mini-PC from time to time so that any kernel updates are applied.

That said, you really don’t need to worry about this in our case: for a mini-PC accessible only on a local network, the risk level is very low. :slightly_smiling_face:

That’s also why I originally created Gladys Plus: it allows you to access your instance from anywhere in the world without opening your local network. It’s the best in terms of security :locked_with_key: