ZHA Phantom effects - lights switch on and off independently without automation

COLT9001 commented 1 month ago

The problem

Phantom effects - lights switch on and off independently without automation

What version of Home Assistant Core has the issue?

2024-8-1

What was the last working version of Home Assistant Core?

2024-7-x

What type of installation are you running?

Home Assistant OS

Integration causing the issue

zha

Link to integration documentation on our website

No response

Diagnostics information

In the log and directly in front of the lamps, it is always possible to recognize sporadically without a recognizable pattern that the lamps simply switch on without any action. Sometimes even off, but often only on. We have over 100 smart lamps from Ledvanced and it's an absolute disaster when the lighting does things like this......

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

Automation is not the cause, their last execution was often hours ago

It is always individual luminaires, not group scenes etc

The lights can also be controlled and can be switched off, but they always switch on again sporadically after an undefined, varying amount of time

home-assistant[bot] commented 1 month ago

Hey there @dmulcahey, @adminiuga, @puddly, @thejulianjes, mind taking a look at this issue as it has been labeled with an integration (zha) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `zha` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign zha` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

zha documentation zha source _{^{(message by IssueLinks)}}

dmulcahey commented 3 weeks ago

The devices may be leaving and rejoining the network. In the zha config panel can you disable identify on join and see if it stops? Also, enable zha debug logging and catch the issue happening a couple times then disable debug logging and attach the log that is downloaded here please.

COLT9001 commented 3 weeks ago

Hello, I tried it once

the joining identification was deactivated. I noticed that the lamps switch on normally and assume the last state. The joining identification has a color-changing flashing effect, but that doesn't happen like that. I also suspected that it might have something to do with the "StartUpBehavior" setting. I switched half of the lamps from PreviousValue to Off. But that didn't help either.

When the lamps switch on, there isn't always a wireless connection to the system. Sometimes the lamps are on but not accessible. Sometimes, however, the switching on is also registered cleanly in the log. But then there is no trigger in the log, such as an automation or something else. Only the switching on is logged. No idea where it gets the command from. The Zigbee 3.0 stick is new from Sonoff

I have to say, however, that there are always problems with the network, that devices are no longer accessible, even though they are less than 2 meters away from the controller or repeater without any obstacles. It can sometimes take a while until they are accessible again. However, no device has been offline permanently.

I also set all the WiFi frequencies to a low channel. The Zigbee on channel 25, as high as possible. I also scanned, there are no WiFi connections from the neighbors that could interfere with the channel.

Only the Bosch Smart Home still transmits Zigbee. But it is also relatively far away on channel 11.

The whole problem with the network started when I exceeded the number of 100 devices.

In the logging i have an example at 16:42:54 ErrorLog.txt

dmulcahey commented 3 weeks ago

What kind of lights are these?

COLT9001 commented 3 weeks ago

Hi,

Most is Leadvance GU10 https://shop.ledvance.com/products/ledvance-smart-reflektorlampe-mit-zigbee-technologie-4-9w-par16-lichtfarbe-rgbw-einstellbar-sockel-gu10-1er-pack

And some Hue Lightstrips, Bulbs and Spots.

Am 22. August 2024 12:45:57 UTC schrieb "David F. Mulcahey" @.***>:

What kind of lights are these?

-- Reply to this email directly or view it on GitHub: https://github.com/home-assistant/core/issues/123764#issuecomment-2304582392 You are receiving this because you authored the thread.

Message ID: @.***> -- Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.

TheJulianJES commented 3 weeks ago

Which light models are affected by the issue? Only the LEDVANCE lights or also the Philips Hue lights?

COLT9001 commented 2 weeks ago

Everyone is affected. However, as LEDVANCE are the most commonly installed, it happens much more frequently there too

Am 23. August 2024 05:33:52 UTC schrieb TheJulianJES @.***>:

Which light models are affected by the issue? Only the LEDVANCE lights or also the Philips Hue lights?

-- Reply to this email directly or view it on GitHub: https://github.com/home-assistant/core/issues/123764#issuecomment-2306324610 You are receiving this because you authored the thread.

Message ID: @.***> -- Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.

TheJulianJES commented 2 weeks ago

Please download the diagnostics information for ZHA on the integrations page and upload it here.

COLT9001 commented 2 weeks ago

Ok, no Problem.

config_entry-zha-64b8538ecae24a5c9be8600ff7a76594 (2).json

TobiasFriberg commented 2 weeks ago

I have the same issue on my IKEA Tradfri bulbs, they spontaneously "turn on" without any trace on why. Random times every day and on every light (happens to all of them).

edit: "start-up behavior" is "off".

COLT9001 commented 1 week ago

I have also continued to monitor the problem and found the following:

Lights are not only switched on but also off without being activated
When switching on you see a corresponding entry in the log, when switching off you see nothing. There is no log entry
However, you can switch the lamp on again immediately after switching it off without triggering. It can therefore be reached in the network despite this action and reacts to commands.
It happens again and again that lamps are not accessible in the network. However, this only lasts for a limited time and at some point they are automatically reconnected to the network. It is often related to switching on the phantom, but not always

Is there any way of debugging the ZHA at protocol level? Somehow I am missing the possibilities to track down the problem

COLT9001 commented 1 day ago

Yesterday I changed the SonOff 3.0 stick to the ConBee 2 stick again. But there are the same problems. Newly added lamps also have the same problem. At the moment it even seems to be the case that entire HaScenes are activated uncontrolled. (In the living room, all the lights come on at once and then go out again a minute later, but there are no log or status entries).

Is it possible that individual lamps that had no connection but still have a protoxcol saved after the reconnect send this further into the network and this causes the problem?

home-assistant / core