"Activity" - Garage door triggering non-stop

[Husky14]

Hello,

I still have an activity every second. I think it can fill my partition where Gladys is in the logs. Is this normal?

[cicoub13]

Hello

Can you tell us more about this sensor (which model) and how it is integrated into Gladys?
Some sensors are very verbose

[Husky14]

Hi, thanks for your help.

The integration is Tuya « cloud » and I have a MOES smart garage door module Zigbee (works with Tuya)

[Husky14]

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

[cicoub13]

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:

1. In Zigbee2mqtt (Z2M interface > device > Settings), add a debounce of one or two seconds. Z2M then groups close messages. You can also put linkquality in filtered_attributes if the signal does not interest you.
2. 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).

[Husky14]

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

[cicoub13]

[Husky14]

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.

[Husky14]

Yes, I remember that with a URL, I had access to my devices when I installed Z2M.

But I don’t have the URL.

[Husky14]

It’s good, I managed to retrieve it with the AI

[Husky14]

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?

[cicoub13]

@Husky14

The state is no longer correct

Is it wrong or do you have a delay? The debounce adds delay (that’s the point).

@Husky14

Is it a problem if the activity runs in a loop every second?

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.

[Husky14]

1. Even after waiting several seconds, the status is incorrect.
2. 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

[Husky14]

[Husky14]

[Husky14]

I’m still having the same problem with my garage door that keeps communicating after reinstalling everything following a Gladys lockup.

I think the problem I had was that the history or logs of this issue filled up the space on my partition, so I couldn’t update the integrations or Gladys.

Even though I increased the space allocated to Gladys, with Gladys running 24/7 every day, I can’t even imagine how much space it will take up.

Do you have a solution to this problem?

Thanks

[Husky14]

[Husky14]

Is there a link with the Tuya integration because I installed it at the beginning so that it works but in this integration I have no device.

My model is the MOES SMART GARAGE DOOR MODULE with « works with TUYA »

[Husky14]

Forget it, I’ve spent too many hours on it. I’m done.

Thanks anyway.

[guim31]

I understand you’re fed up. Here’s just the essentials:

1. It’s not your config, it’s the module. The MOES ZM-102-M is known to send 1 to 3 messages per second, even when the door doesn’t move (issue Zigbee2mqtt #29059, closed without a fix, and the same observation on the Home Assistant side). No setting can silence it. The debounce just groups the messages, and it’s the one that messed up your state: don’t re-enable it.

2. It’s very likely not the one that filled your disk. Your screenshot shows it: 428,402 states weigh 9.1 MB, that’s about twenty bytes per state. At one message per second, that’s less than 2 MB per day and per feature. As for the Zigbee2mqtt and MQTT container logs, Gladys caps them at 10 MB.

3. To make it take up no space at all, on the device page, also uncheck « Keep history » on Open (Yes/No), then click Save. It’s this recording that deletes, in the background, the already stored states. On your screenshot, Switch is unchecked but still displays 428,402 states: if you hadn’t saved, you need to do it too. The door remains controllable, and its state remains up to date on the dashboard as in the scenes. If you want to keep the history of openings, leave it enabled and rather reduce the retention period to 1 month in Settings > System.

4. Tuya is not to blame. « Works with Tuya » just means the module works with a Tuya gateway. At your place, it goes through your Zigbee key and Zigbee2mqtt, so you can disable the Tuya integration.

If one day you want to know what really filled the partition, paste here the result of these three commands and we’ll tell you what to safely delete:

df -h

sudo docker system df

sudo du -sh /var/lib/gladysassistant/* | sort -h