Zigbee Spots turn on "themselves"

Hi folks,

i finally brought my Paulmann spots into permanent connection with the network (no more switching on/off by wall switches to power on needed).

But now… after 2 days different spots turn on by magic hands.
But not with full brightness, just quite dimmed.

First i thought the the change of the Zigbee stick location could cause this issue, but after moving the stick again to its first location the problem still persisted.

I allready took a look at the Z2M log and found logs like e.g.:
[2025-03-30 18:55:31] info: z2m:mqtt: MQTT publish: topic ‘zigbee2mqtt/bridge/event’, payload ‘{“data”:{“friendly_name”:“Küche Spot 6”,“ieee_address”:“0x00158d0007599b1b”},“type”:“device_announce”}’
The timestamps fits the possible time window in which some spots turnd on.

But what to do next?

kind regards
schlotzi

Today i found following logs:

[2025-03-31 09:24:08] info: z2m:mqtt: MQTT publish: topic ‘zigbee2mqtt/Küche Licht Z2M Group’, payload ‘{brightness:1,color:{h:124,hue:124,s:2,saturation:2,x:0.3217,y:0.3314},color_mode:color_temp,color_temp:166,state:ON}’
[2025-03-31 09:24:08] info: z2m:mqtt: MQTT publish: topic ‘zigbee2mqtt/Küche Spot 5’, payload ‘{brightness:1,color:{h:124,hue:124,s:2,saturation:2,x:0.3217,y:0.3314},color_mode:color_temp,color_temp:166,effect:null,linkquality:80,power_on_behavior:null,state:ON}’

The “Spot 5” is member in the “Küche Licht Z2M Group”
but also 5 other spots which did not turn on.

9 min later again this spot and the group.

[2025-03-31 09:33:16] info: z2m:mqtt: MQTT publish: topic ‘zigbee2mqtt/bridge/event’, payload ‘{data:{friendly_name:Küche Spot 5,ieee_address:0x00158d0006c5e0bf},type:device_announce}’
[2025-03-31 09:33:18] info: z2m:mqtt: MQTT publish: topic ‘zigbee2mqtt/Küche Licht Z2M Group’, payload ‘{brightness:1,color:{h:124,hue:124,s:2,saturation:2,x:0.3217,y:0.3314},color_mode:color_temp,color_temp:166,state:ON}’
[2025-03-31 09:33:18] info: z2m:mqtt: MQTT publish: topic ‘zigbee2mqtt/Küche Spot 5’, payload ‘{brightness:1,color:{h:124,hue:124,s:2,saturation:2,x:0.3217,y:0.3314},color_mode:color_temp,color_temp:166,effect:null,linkquality:69,power_on_behavior:null,state:ON}’

But it is not allways this particular spot.

kind regards

Hi folks,

another attempt for help.

I dont have a idea what to do.

Things i have done/ happened since my last post.
-delted the affected devices from Z2M and added them again with new names. It did not help…

But instead other spots in different rooms started the same behavior…
i realy dont have an idea where to start.

kind regards
schlotzi

I can’t promise this will fix the problem, since I use ZHA, but:

I had some lights too that would turn on without any real reason. After a lot of testing I figured out it happened when turn_off was called with a transition, when the light was already off. This would happen when, i.e., turning off all lights in an area.

If that is also what causes your lights to turn on (the behaviour seems very similar, although in my case ZHA did not report them as actually being on), you could try the blueprint I made that somewhat prevents the behaviour: Monkeypatch blueprint for Tradfri LED1949C5 spookily turning on. I don’t know if it also works for Z2M, however.

Thank you for reply.
I´ll look at it on the weekend although i dont have much hope that it can help me to solve my issue.

The thing is, that the lights turn on without anyone doing anything! (really!:wink: )
Every morning i get up, 2-5 out of 14 spots are switched on… and i am the one went to bed last.
Also i have grouped the spots into groups out of 6/6/2 spots and i only switch the whole group in my automations as well.
Another thing is that the spots which switch on themselve are out of different groups and not the whole group switches on…

Sooo yeah. idk :smiley:

kind regards
schlotzi

Run some basic troubleshooting on them.

Given you have 3 groups of 6/6/2:

  • Go through each bulb in one group of 6 and set their default power_on_behavior to off.
  • Go to another group (use the one with 2 bulbs - less hassle) and remove them from the zigbee network.
  • Leave the other group of 6 untouched.
  • Monitor for a couple of days

If the first group stops turning on by itself, it’s either a power issue or a connectivity issue.
If the second group doesn’t stop turning on by itself, it’s definitely a power issue.

Out of curiosity, how are you controlling your lights? Purely via automation, or are you using a smart switch?

1 Like

Is there a way to trace whether there is a command to turn on the spots and where it came from?

@ShadowFist

  • All spots are permanently wired (no power switch).
  • I switch them by inputs on different (detached) relay/input controller.
    (Shelly Pro 1PM and Shelly I4)

Its mostly the same spots that switch on themself.

I drew a shematical of the flat which should show the distances between devices an the coordinator.

red A = Zigbee Coordinator
yellow (group out of 2 spots)
dark red (group out of 6 spots)
blue (group out of 6 spots)
green other Zigbee devices (climate sensors, window sensors, smart plugs and motion detectors).
black lines are walls.

the spots which are affected are mostly (95%) dark red (No. 3 to 6, lqi between 85-98)
and sometimes blue (No. 6, lqi 65).

i changed the power on behavior from the dark red now to previous.
Some spots had no setting here, some on, some off. Funny because i never changed anything here.
Thank you for that setting hint!(i somehow allways overlooked it).
Have a great hope this will help!

P.S.:
While i am overthinking the thing with the power on behaviour i remember, that the affacted spots sometimes flickered once in an hour. before i had a zigbee network.
I thought it maybe is caused by not connection to any zigbee network. But maybe they have a power issue since they were build in few years ago or they just faulty, bcs the red ones all have the same power supply cable.

1 Like

That is why I suggested the troubleshooting steps above. If there’s a power issue, you’ll still need to look into it carefully. However, setting the power_on_behaviour is a good enough workaround for now.