Gladys Assistant 4.84.2: Synology, weather, doorbells, Lucide icons and safer update

Hi everyone!

After the launch of external integrations in 4.84, this version refines the subject (especially on Synology), and adds several concrete improvements on the interface, climate, Gladys Plus, and system update sides.


External Integrations: Synology Fixes and /data Permissions

On some Synology NAS (e.g., DS920+), the Docker kernel does not expose the CPU CFS scheduler. Gladys then tried to create external integration containers with a CPU limit (NanoCPUs), which caused the installation to fail with an error of the type « NanoCPUs cannot be set Â».

Gladys now detects if the kernel supports it and only applies the CPU limit if possible. Other limits (memory, etc.) remain in place.

Another point: the /data folder of integrations was not always created with the correct permissions (root vs. non-privileged user of the image). The supervisor now prepares this folder before each container creation, which fixes new installs and repairs existing ones on the next container restart.

If you are on Synology and the installation of an external integration was blocked: this version should unblock the situation.


Air Conditioning: Fan Speed and Swing

Thanks to @Terdious: the AC gains new types of features:

  • Fan speed
  • Horizontal/vertical swing
  • Extended modes (ventilation, heating, dehumidification
)

The UI only displays the options actually supported by the device and automatically switches to a dropdown menu when space is limited.

These types are generic: usable by any integration (including external integrations), not just Tuya.

The JS SDK has been updated to 0.10.0 with these new types.


Doorbells: Doorbell Category + Ring Type

Thanks again to @Terdious, a doorbell no longer needs to be a generic « button Â».

New doorbell category with the ring type: the « someone rang Â» event becomes a first-class citizen in Gladys (widgets, scenes, future dedicated notifications, etc.).


Scenes: New Lucide Icons + Search

The theme switches to Lucide (replacing Feather, no longer maintained since 2023). The fe fe-* classes remain the same.

The scene icon selector is also redesigned:

  • Search field
  • Translated name under each icon
  • More readable grid

No more scrolling through 262 anonymous silhouettes :smiley:


Gladys Plus: Step-by-Step Configuration

The Gladys Plus linking screen no longer just shows a generic error message when the instance is not found.

Instead: a step-by-step guide, a button to retry, links to the documentation/support, and clearer explanations about local authorization (and why it’s important for security).

Documentation: Connect your Gladys instance to Gladys Plus | Gladys Assistant

Don’t hesitate to tell me if it’s clearer for new users.


System Update: Safer, and Visible Errors

Following a forum report: clicking « Update Â» could leave the UI stuck on « updating Â» without doing anything.

Several improvements:

  • Manual update only affects the Gladys container (not all other containers on the machine)
  • If your image is frozen on an immutable tag (v4.x.x instead of latest / v4), Gladys refuses the update and explains why, with the recommended tag
  • Errors finally appear in the interface (instead of disappearing into server logs)
  • Watchtower image pinned to a stable version

Other Improvements

  • Device Discovery: Limit increased from 200 to 2000 devices (large Zigbee/Matter installations are no longer silently truncated)
  • Security: Handlebars update (CVE-2026-33937), thanks to anupamme for their first contribution!

Thanks to Contributors

A big thank you to @Terdious and anupamme for their contributions to this version, and to the entire community for the feedback (Synology, updates, etc.) that helped prioritize these fixes.

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

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

View full release notes on GitHub

@pierre-gilles is it possible to add snowflakes to the icons for @Will_71’s thermostat?
I just checked and Claude didn’t add them.
Otherwise, it’s perfect for searching in the icons :clap:

EDIT: I just noticed that the brand icons (LinkedIn, Twitter, etc.) are present, but Lucide removed them :thinking: I have the impression that the version is not the most recent.

Yes, it’s possible, I’ll add that!

Oops :grinning_face_with_smiling_eyes: Actually, instead of including the entire Lucide library (nearly 2,000 icons, which is quite heavy), Claude suggested keeping only a subset of icons that he deemed relevant for home automation.

After that, we can always add icons on a case-by-case basis, or even include the entire library. We just need to keep in mind that it significantly increases the frontend size (about 275 KB of icons loaded at startup, which is not negligible) and that, from a UX perspective, we end up with quite a long list. :grinning_face_with_smiling_eyes:

So, it’s a balance to find!

My comment wasn’t about the number of icons but the fact that Lucide removed brand icons from their library to avoid lawsuits with those brands.
And since some remain, that means Claude didn’t take the latest version of Lucide and/or he kept some Feather icons.

Claude’s response:

Brand icons: this is not a versioning issue. The theme is on the latest (2.1.0). Lucide did remove them in 2022, and that’s exactly why I kept in theme 2.0.0 a small companion font (feather-brands, ~2.5 KB) containing these 10 glyphs. Without it, fe-github, used 5 times in the front end, on external integration pages, would display as an empty square. This is intentional backward compatibility, not a leftover.

I did see that :smiling_face:

So I don’t know where this version comes from because Lucide is at v1.28.0 :thinking:

So we have a mix of Lucide and Feather, that’s fine with me :sweat_smile:

He was talking about the Gladys theme version, it’s a dependency we maintain and that contains Lucide inside.

Claude added 217 icons that he deemed relevant for the smart home.

Including:

Search Result
snowflake Snowflake
thermostat Radiator
heating Flame, Radiator, Hot and Cold
air conditioning Vent, Snowflake, Hot and Cold
shutter Roller shutter

Merged and available in the next version of Gladys

Hello I still have the issue with my Synology:

Okay, weird, I’ll investigate!

Small remark, it’s more practical if you put the logs in code form rather than a screenshot, easier to give to Claude :wink:

Could you run a docker info on your NAS?

Sorry, I hadn’t seen your request:

docker info
Client:
 Version:    24.0.2
 Context:    default
 Debug Mode: false

Server:
 Containers: 88
  Running: 62
  Paused: 0
  Stopped: 26
 Images: 364
 Server Version: 24.0.2
 Storage Driver: aufs
  Root Dir: /volume1/@docker/aufs
  Backing Filesystem: extfs
  Dirs: 1910
  Dirperm1 Supported: true
 Logging Driver: db
 Cgroup Driver: cgroupfs
 Cgroup Version: 1
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs db fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: runc io.containerd.runc.v2
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 067f5021280b8de2059026fb5c43c4adb0f3f244
 runc version: 0320c58
 init version: ed96d00
 Security Options:
  apparmor
 Kernel Version: 4.4.302+
 Operating System: Synology NAS

 OSType: linux
 Architecture: x86_64
 CPUs: 4
 Total Memory: 19.39GiB
 Name: DiskStation
 ID: fea133db-b005-4bb6-9400-a55492fa0fa8
 Docker Root Dir: /volume1/@docker
 Debug Mode: false
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false

WARNING: No kernel memory TCP limit support
WARNING: No cpu cfs quota support
WARNING: No cpu cfs period support
WARNING: No blkio throttle.read_bps_device support
WARNING: No blkio throttle.write_bps_device support
WARNING: No blkio throttle.read_iops_device support
WARNING: No blkio throttle.write_iops_device support

WARNING: The aufs storage-driver is deprecated, and will be removed in a future release.
         Refer to the documentation for more information: https://docs.docker.com/go/storage-driver/

I’m going to make a PR to solidify the topic and react to failure events dynamically, but normally the fix I published yesterday should work. You can clearly see in the docker info that NanoCPU management isn’t there on your end.

Are you 100% sure you’re on 4.84.2?

How can I check this? :thinking: If I can’t trust the Gladys interface :thinking:

Well actually you are indeed on 4.84.2, you can trust the UI :slight_smile:

I found the real cause of the bug, I’ll push it in the next version (tonight)

Oh great!
Looking forward to seeing the explanation :wink:
Don’t hesitate if you need more info