Environment: Gladys v4.70.0 (auto-updated via Watchtower) Docker on Linux (Ubuntu), network_mode: host MQTT integration with multiple devices (Raspberry Pis) Problem: After Watchtower automatically updated Gladys from v4.66.8 to v4.70.0, the container started consuming ~60% CPU consta…

Ah, too bad :grinning_face_with_smiling_eyes: At least we managed to fix a bug in the Nuki integration along the way! The v4.67.0 release only includes three changes: Nuki integration Gladys Plus backup improvement HAP dependency upgrade To rule out any issue related to the HomeKit dependency u…

Hello, Je confirme que les logs mqtt en trop cela vient de l’intégration Nuki v1, c’est normalement corrigé sur la v1.0.1 ( @mutmut avait détecté ce soucis dès la release G4.67)). Le susbribe mqtt au démarrage se faisait sur tous les devices existants, l’attribut de recherche était mal configuré et …

@bamboleate I just released a Gladys upgrade (v4.71.0) with the fix, let me know if it fixes your issue! [image] Gladys Assistant 4.71 : Nuki & Matter Actualités Cette nouvelle version apporte des améliorations importantes sur Matter, Nuki, et plusieurs correc…

Hi @Pierre-Gilles , I upgraded from v4.66.8 to v4.71.0 and still see ~60–70% CPU usage. After some deep debugging, I found two separate issues: Issue 1: Race condition with MQTT retained messages (startup crash loop) On startup, Mosquitto immediately replays all retained messages on gladys/master…

Thanks for the feedback, I’ll investigate both issues :+1: That said, I don’t think they were introduced in Gladys v4.67.0, so they’re probably not the root cause of the high CPU usage you’re seeing. Since you mentioned the CPU usage is constant (not just at startup), it also doesn’t look like a r…

Hi @Pierre-Gilles , I measured the MQTT message rate using mosquitto_sub -t '#' piped through pv: ~0.8 messages/second (291 messages over ~6 minutes, all topics combined) That seems on the low end, so I don’t think throughput is the issue. The high CPU (~60–70%) is constant and doesn’t correlate w…

I found the issue! :tada: The Nuki integration was subscribing to the wildcard MQTT topic homeassistant/# on startup, even when the Nuki integration wasn’t being used :sweat_smile: On top of that, the handling on the Nuki side was quite heavy for each Home Assistant discovery message, so it was co…

Hi @Pierre-Gilles , I tested the fix image gladysassistant/gladys:fix-nuki-home-assistant-wildcard-listen but unfortunately the CPU usage is still at ~60-70%. No NotFoundError in the logs anymore (the retained messages race condition seems resolved), but the high CPU persists. I also noticed that …

That’s it! When I disable Apple HomeKit in dashboard/settings/service, and restart the gladys container (the fix_nuki one AND latest, as of now, v4.71.0), CPU time goes way down, container cpu 0.3% I do have apple devices, but i don’t run Apple home Kit devices anyway so FOR ME the problem is solve…

Hi, I’m glad you were able to resolve your issue. If it’s related to the HomeKit integration, I’ll look into it. I’m pretty sure it’s an issue related to mdns, I’ve already mentioned it here: Installer Gladys sur NAS Qnap - #13 par bertrandda . The latest version of the dependency we’re using makes q…

Great! Glad we were able to identify the main issue :grinning_face_with_smiling_eyes: I’ll release the Nuki fix once I get confirmation from @ProtZ that everything is still working as expected. @bertrandda , feel free to reach out if you need any help :+1:

Titel: High CPU usage (~60%) with v4.70.0 – fixed by downgrading to v4.66.8

Configuration

pierre-gilles April 3, 2026, 6:36pm 35

Good news, all the fixes are live in Gladys Assistant 4.72:

Topic		Replies	Views
Problème zwave et google home Configuration	28	1288	March 28, 2022
Zigbee2MQTT avec dongle CC2652BLE SimpleLink - Ca fonctionne! Configuration zigbee2mqtt	49	2694	March 21, 2022
Problème de refresh avec matterbridge Configuration	15	206	June 23, 2025
Gladys Assistant 4.2 est disponible avec la compatibilité Zigbee2mqtt ! 🚀 Actualités	146	5673	May 17, 2021
[Z2M] Tests en zigbee2mqtt 1.42.0 > 2.1.3 >..> 2.4.0 >..> 2.6.1>...>2.7.2 Développement zigbee2mqtt	33	985	December 8, 2025

Titel: High CPU usage (~60%) with v4.70.0 – fixed by downgrading to v4.66.8

Related topics