sockets turning off randomly

[fsedarkalex]

Hi,

I have a few sockets from OSRAM, IKEA and some brand using Tuya firmwares.

I observed that sometimes my socket are randomly switching off and on (or on and off, depends on their original state) again within a second.
This happens always for the IKEA ones. For the TUYA-Type the sockets even remain off sometimes.

I never have observed this with OSRAM yet (which does not mean it could not also happen).

The TUYA type socket sometimes even drop out of the network and I have to rejoin them manually.

Is this any known issue or anything I can do about it? I remeber when I first observed this, I had seen a few reports and it seems that this has started with a specific HA release but I think that was ZHA (home-assistant/core#101291).

I am using Z2M so this should not be related to HA version but ZHA's "bug" was related to an incompatibility with some coordinators.
Maybe Z2M has the same issue or better said is causing the same issue to happen?

I am using a SONOFF Zigbee 3.0 USB Dongle Plus as coordinator.

UPDATE:
I forgot to mention: The sockets which are dropping out of the network are staying in Z2M and when trying to send a command it says "No network route"

[fsedarkalex]

I noticed that these "ghost toggles" are often followed by a "no network route" ping result, too but the sockets seem to stay online long term.

This could mean, the "ping" is probably causing this behavior? @Koenkk Maybe this is an issue? Shall I open a bug report?

[Koenkk]

Then the next step would be sniffing: https://www.zigbee2mqtt.io/advanced/zigbee/04_sniff_zigbee_traffic.html

[fsedarkalex]

I did not sniff yet, but I got a debug log created with Z2M while the issue happened. Will this help?
IDK if there is anything confidential in these so will not publish them here right now.

Just for my own later reference: issue happened today, ~22:18

[Koenkk]

I did not sniff yet, but I got a debug log created with Z2M while the issue happened. Will this help?

I can check, please provide the debug log of -5min till +5min of when the issue occurred

[fsedarkalex]

please provide the debug log of -5min till +5min of when the issue occurred

I sent the log via discord. Hope that's okay (idk if there is confidential innformation readable from the log)

[Koenkk]

Thanks for the log, what is the ieeeAddress/friendly name of the problematic plug?

[fsedarkalex]

I am still on 20230507 and I will move to the latest version (Koenkk/Z-Stack-firmware#505) now before doing any further testing. MAybe the new version even solves the issues I am experiencing.

I will keep you updated!

[fsedarkalex]

The update did not change anything regarding this issue

[fsedarkalex]

<!-- div#d_1723660937765 p {font-family:Calibri, Arial, Helvetica, sans-serif; font-size:12.0pt; color:#1F497D} --> issue was somewhere around 22:19. The device is `BueroGross/SteckdoseRaketencam` (`0x7cb03eaa0a0c0b67`) thanks for having a look! Sent from NineVon: Koen Kanters ***@***.***>Gesendet: Mittwoch, 14. August 2024 20:37An: Koenkk/zigbee2mqttCc: fsedarkalex; AuthorBetreff: Re: [Koenkk/zigbee2mqtt] sockets turning off randomly (Discussion #23435) Thanks for the log, what is the ieeeAddress/friendly name of the problematic plug? —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***> [ { ***@***.***": "http://schema.org", ***@***.***": "EmailMessage", "potentialAction": { ***@***.***": "ViewAction", "target": "#23435 (reply in thread)", "url": "#23435 (reply in thread)", "name": "View Discussion" }, "description": "View this Discussion on GitHub", "publisher": { ***@***.***": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

[Koenkk]

On 22:19 z2m tries to ping the device, maybe this causes the issue. Can you try to disable the availability feature for this device?

[fsedarkalex]

I already tried that before but issue persisted

[Koenkk]

Then I expect that either the device crashes or another device is turning it ON/OFF (unlikely, but can be confirmed by sniffing https://www.zigbee2mqtt.io/advanced/zigbee/04_sniff_zigbee_traffic.html)