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…

Btw, we are going to release an improvement to the Nuki integration in next Gladys release to prevent the Nuki integration from starting if not configured, so this could definitely help you for this! ( not 100% sure) Nuki 1.0.1 : Check that service is configured,…

Well.. that goes way over my head. If I can provide something that would help you, just reach out

I’m going to release very soon the new Gladys version with this fix, and if you could just try the release to see if it fixes your issue. If not we’ll investigate more together :blush:

[image] pierre-gilles: Je me demande si cela pourrait venir de l’intégration Nuki, car l’intégration Nuki utilise MQTT pour écouter des messages MQTT provenant des serrures Nuki. Je valide ce point, j’ai egalement des logs Nuki qui n’etaient pas present avant, liés à mqtt. Pour le moment de …

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…

Titre : Utilisation élevée du CPU (~60%) avec v

Configuration

pierre-gilles Mars 20, 2026, 2:29 17

@bamboleate Je viens de publier une mise à jour de Gladys (v4.71.0) avec le correctif, dites-moi si cela résout votre problème !

Sujet		Réponses	Vues
Intégration HomeKit et Siri Développement	87	3090	Décembre 3, 2025
Problème zwave et google home Configuration	28	1290	Mars 28, 2022
Zigbee2MQTT avec dongle CC2652BLE SimpleLink - Ca fonctionne! Configuration zigbee2mqtt	49	2724	Mars 21, 2022
Problème de refresh avec matterbridge Configuration	15	212	Juin 23, 2025
Gladys Assistant 4.2 est disponible avec la compatibilité Zigbee2mqtt ! 🚀 Actualités	146	5755	Mai 17, 2021

Titre : Utilisation élevée du CPU (~60%) avec v

Sujets connexes