Osram Plug 01 switches triggering on and off briefly

deCONZ General Support
1

Hi, I have 3 Osram plugs in my Zigbee network with a Conbee II. For some time now they have been triggering a short toggle of the switching status. If one plug causes this error, all the others usually react after a short time.
I have already tried a few things, Conbee stick with no extension, different location, with and without hub. Latest updates of Conbee Stick and plugs.

Here some Infos:
Docker with Conbee II
Gateway Version 2.28.1
Firmware: 26780700

Osram Plug 01
Vendor 0x110c
Image 0x0027
Version 0x01020509

In the Deconz debug I see such information, but I can’t analyse it:

sc state/on: not synced
sc tick --> statecallfunction

Does anyone have any idea where I can do further error analysis?
Has anyone ever had a similar problem and been able to solve it?

I would be grateful for any ideas or help.
Thanks!

2

I think these are the plugs with the firmware issue that causes malformed packets in zigbee. @manup can you confirm?

3

I think these are the plugs with the firmware issue that causes malformed packets in zigbee. @manup can you confirm?

No not as far as I remember also couldn’t find issues for this.

sc state/on: not synced
sc tick --> statecallfunction

This indicates that there are on/off control commands queued.
The question is from where do these come. Are the plugs part of any scene or automation?

4

yes, there was a plug in an automation, but it didn’t work.
I have just seen that v2.30.2 has been available as stable since 2025-05-08. I will download it straight away.

5

Hi, I’ve just had another ‘Osram plug’ flashing again, so unfortunately the software update doesn’t seem to have helped.
Usually, but not always, there are other SC tick --> StateCallFunction nearby. I think they come from normal working actions.
Here are some messages from the DebugLog again. These are from the ‘osram plug’ that was flashing. I hope someone has an idea?

DeviceAnnce of LightNode: 0x7CB03EAA00B0DF5C Permit Join: 0
0x7CB03EAA00B0DF5C foundGroup 0xFFF0
0x7CB03EAA00B0DF5C foundGroup 0x000F
0x7CB03EAA00B0DF5C foundGroup 0x0003
0x7CB03EAA00B0DF5C foundGroup 0x0010
0x7CB03EAA00B0DF5C foundGroup 0x0007
6

The device announce looks like the device rebooted. Meaning that either your power dropped or something else is going on inside the device.

7

Thanks, that sounds plausible. But I already have the latest software and the plugs are connected to the normal power outlet in the flat, and no other device reboots. Only the plugs.

Any ideas what I could do?

8

Bad firmware of the plug

9

And about the “foundGroup” logs, I don’t find it in the plugin core but it mean you have your plug in 5 groups ?
It can explain why you have all plugs that react same (if you have an automation on a group)

10

thank you very much, I will reinstall the firmware for all of them next week.
And yes, I also have groups with the plugs, but no more automations. I deleted these some time ago, could there still be some remains of them in Phoscon? Can I check this?

11

You can find all groups direclty in tha API using Phoscon/help/API Information/groups.
Some groups are “natives”, but 5 …

But I can make mistake, I haven’t found this message in code, not sure what it mean exaclty.