Hello,
I still have an activity every second. I think it can fill my partition where Gladys is in the logs. Is this normal?
Hello
Can you tell us more about this sensor (which model) and how it is integrated into Gladys?
Some sensors are very verbose
Hi, thanks for your help.
The integration is Tuya « cloud » and I have a MOES smart garage door module Zigbee (works with Tuya)
Here are the logs (green and red lines) that are looping
2026-09-26T06:30:07.617581971Z 2026-09-26T08:30:07+0200 connect.js:87 (MqttClient.) Error detected, letting automatic reconnection handle it
2026-09-26T06:30:12.617774239Z 2026-09-26T08:30:12+0200 connect.js:76 (MqttClient.) Attempting to reconnect to MQTT broker…
2026-09-26T06:30:12.619258273Z 2026-09-26T08:30:12+0200 connect.js:80 (MqttClient.) Error while connecting to MQTT
2026-09-26T06:30:12.619882850Z 2026-09-26T08:30:12+0200 connect.js:81 (MqttClient.) ErrorWithReasonCode: Connection refused: Not authorized
The three repeating lines (switch « Off », « Good signal », « Closed ») correspond to the features that Zigbee2mqtt creates for this MOES module (trigger, garage_door_contact, linkquality). The Tuya Cloud integration does not create any signal or opening sensor. Can you check in Integrations > Zigbee2mqtt that your « Garage Door » is there?
If so, here’s what happens: this Tuya module sends its values very often, even when nothing changes. Each time, Gladys records the 3 values, hence this flow in the Activity screen.
To calm this down:
- In Zigbee2mqtt (Z2M interface > device > Settings), add a
debounceof one or two seconds. Z2M then groups close messages. You can also putlinkqualityinfiltered_attributesif the signal does not interest you. - In Gladys, on the device page, deactivate « Keep history » on the features you don’t need (the signal, for example). They will no longer be stored or displayed in Activity.
For the MQTT logs « Not authorized », it’s another topic: it’s the MQTT integration (and not Zigbee2mqtt) that tries to connect every 5 seconds with a bad identifier. If you don’t have MQTT devices outside of Zigbee2mqtt, disable it in Integrations > MQTT. Otherwise, correct the user and password in its configuration.
For disk space, you can also limit Docker logs (--log-opt max-size=10m --log-opt max-file=3).
Thanks
I can’t find the Z2M interface → device > settings.
Is settings the configuration in the top tab?
I can’t find a YAML location
I’ve been trying with IA for over 2 hours, we managed to stop the activity, but we were losing the states and/or the garage door button. I went to modify the file in nano in the terminal where I was able to add a debounce. It solved one issue but not the other.
It’s good, I managed to retrieve it with the AI
Okay, so what you’re telling me, I did it with the AI in the terminal. It solved the activity problem, but the state is no longer correct. So, after 2 hours, it ended up being one or the other.
Is it a problem if the activity runs in a loop every second?
Is it wrong or do you have a delay? The debounce adds delay (that’s the point).
It’s not a problem unless your system is slow (Raspberry Pi, for example) or you have a slow disk (non-SSD or SD card).
I have plenty of devices that write every second and no issues.
If the history doesn’t interest you, you can go to Gladys, on the device page, disable « Keep history » on the features you don’t need (the signal, for example). They will no longer be stored or displayed in Activity. But you can still display them in a Dashboard or act on them in scenes.
- Even after waiting several seconds, the status is incorrect.
- I think I’ll just leave it running like this. I just hope it won’t fill up the logs and consequently my partition. I don’t know about that. And yes, I’ve already unchecked keep history.
Thanks for your help 