Device turns on without configured command

[thotha]

Description of the issue

Since this year I face the problem, that one channel (L2) of a specific “Actuator Switch” does suddenly turn on without interaction of my side or from any known automations. After no luck with my own trouble shooting I did change the device in question with an other device from the same brand and model. So the device identifier, the IEEE ID and also the device name are all new now. But instead that the problem did move with the device in question, the problem did stay at the room of the problem but changed from port "L2" to "L1" even with the exchanged actuator.

Device with the problem is a 2 gang switch (FMS2C017) by KnockautX (Official support by Z2M) and three other units I use do NOT have any such problems.

My problem is know to figure out

• Which part of the setup is responsible. Hassio Core, Hassiso System, Z2M, MQTT Broker, some hidden leftovers, ...
• How to get the needed log files to find the problem

In the Home Assistant Community I didn't get any feedback since January 30. https://community.home-assistant.io/t/zigbee-device-turns-on-without-configured-command/682013/1

Thank you for anyones help and suggestions.

Addon version

1.35.3-1

Platform

Core 2024.2.1 Supervisor 2024.01.1 Operating System 11.5 Mosquitto broker 6.4.0

Logs of the issue (if applicable)

No response

[MrFr33man123]

+1

For me the problem with all zigbee lights turning on after a restart of the Home Assistant MQTT Client Integration. Zigbee2Mqtt Topics for the bulbs get updated. The log from z2m reads state off then 4 times state ON and after that again 2 times state OFF but the state OFF is not reflected from the bulb. So every time I restart HA all lights turn on. I can't seem to find the root of evil. I removed the retain flag from the mqtt topics no succsess. A restart of z2m also triggers a all lights on phenomena. states.json has STATE:"OFF" so i am totally lost!

[thotha]

Additional note: If I let the false triggered channel "ON", there won't be any additional "power-on" events triggered. If I "power-off" every time it gets triggered, well, the next "power-on" will happen within the next few minutes up to a few hours.

[MrFr33man123]

Yesterday I found my issue to be the Groups State. It was ON and never OFF so when the group State got loaded it turned on every light in the Group even if just a few members of the group where on. So this is not expected behavior but from a logical standpoint understandable. Group state should have an option to not get retained and restored.

[github-actions[bot]]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days