OSRAM LIGHTIFY Light turning on by itself

No. I’m not.

One of the SmartThings zigbee engineers is working on the mysterious Osram turning on issue. He’s been posting in the following thread:

1 Like

Thanks @JDRoberts, was literally in the process of linking to that post over here but you beat me to it!

1 Like

This started for me within the last few days. The times it happened, I thought it was a glitch but then it started happening more frequently.

I have OTA disabled
"Zigbee OTA is disabled"

Can the firmware be checked via SmartThings or do I need to connect it to my hub.

SmartThings shows the following for my 2 devices.

Data	
model: Gardenspot RGB
application: 01
manufacturer: OSRAM
endpointId: 03
Raw Description	03 0104 0102 00 09 0000 0003 0004 0005 0006 0008 0300 0B04 FC0F 01 0019

and

Data	
model: LIGHTIFY Flex RGBW
application: 03
manufacturer: OSRAM
endpointId: 03
Raw Description	03 0104 0102 00 09 0000 0003 0004 0005 0006 0008 0300 0B04 FC0F 01 0019

Look in the IDE under the specific device. Compare the time the firmware was checked with the time that it came on. Mine was the same…

@surge919 SmartThings found in their labs on older firmware, if an OSRAM device was forced to relay a lot of ZigBee messages, the bulb would ‘panic’ turning the bulb on. They only found this with very old firmware versions though.

Yes, that’s true too. But it was also going on when checked for a firmware update even before there were updates to apply.

From what I understand that the bulb comes on due to the OSRAM device resetting not the firmware check. SmartThings as part of the relogin process (after the bulb resets) checks the firmware version. That is why the firmware check is at the same time.

I don’t know if they’ve definitively determined all of the reset cases though.

1 Like

Mine weren’t all coming on during the firmware check. Only some of them (same firmware) and only when checked. Doesn’t matter - problem seems solved.

1 Like

In any case, glad to hear the issues for you have been resolved. I know the OSRAM issues were a very annoying problem. With them turning on as well as with ZigBee devices dropping off the network.

Weren’t your’s resolved too?

I had a few SmartThings battery devices drop off the network. I luckily didn’t have the bulbs turn on. Some battery replacements and removing the OSRAM bulbs as repeaters (when rejoining the SmartThings devices) worked. I really only had one sensor that kept giving me issues. I now have the new firmware so I’ve reset the battery devices. I haven’t had any issues for well over a week.
SmartThings did increase the delay for their devices, so that may be the real resolution.

I wasn’t losing any devices. Maybe because I’m between 250-300 devices. Stronger mesh - I don’t know. I just had a few bulbs turn on, annoying, but didn’t bother me much. I wrote an app and the issue would fix itself (at least on the surface, wife didn’t notice anymore).

The Firmware - Last Checked time is more recent than the last time it turned on on it’s own but I wasn’t home at the time so I don’t know if the light actually turned on or not.

I also changed (as suggested in another thread) the device type to "ZLL RGBW Bulb"
I’ll see if that makes a difference. I should know within a few days since the devices were turning on at least once a day on their own.

My garden spots turned on last night. I have no active automation on it after the holidays.

And it was on again when I went home for lunch. I’m unplugging it for now, still not sure what’s triggering it.

+1 happening to me too… every morning around 6:30am or so pst.

I’ve had this issue over the last few weeks, two bulbs (both A60s) in particular turning themselves on at odd times with no apparent trigger. Has anyone else noticed this on their systems?

Got some logging from the IDE, my brain is shot right now so if anyone can interpret what is happening I’d be very grateful. Entry prior to this last power on is at 18:45, two minutes later it powers back on…

 18:47:55: debug [name:level, value:100]
 18:47:55: debug description is read attr - raw: B37A03000808000020FE, dni: B37A, endpoint: 03, cluster: 0008, size: 08, attrId: 0000, encoding: 20, value: fe
 18:47:55: info DID NOT PARSE MESSAGE for description : catchall: 0104 0008 03 01 0040 00 B37A 00 00 0000 07 01 00
 18:47:55: trace zigbeeMap : [raw:0104 0008 03 01 0040 00 B37A 00 00 0000 07 01 00, profileId:0104, clusterId:0008, sourceEndpoint:03, destinationEndpoint:01, options:0040, messageType:00, dni:B37A, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:07, direction:01, data:[00], clusterInt:8, commandInt:7]
 18:47:55: debug description is catchall: 0104 0008 03 01 0040 00 B37A 00 00 0000 07 01 00
 18:47:52: info DID NOT PARSE MESSAGE for description : catchall: 0000 8021 00 00 0040 00 B37A 00 00 0000 00 00 1100
 18:47:52: trace zigbeeMap : [raw:0000 8021 00 00 0040 00 B37A 00 00 0000 00 00 1100, profileId:0000, clusterId:8021, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:B37A, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[11, 00], clusterInt:32801, commandInt:0]
 18:47:52: debug description is catchall: 0000 8021 00 00 0040 00 B37A 00 00 0000 00 00 1100
 18:47:52: info DID NOT PARSE MESSAGE for description : catchall: 0000 8021 00 00 0040 00 B37A 00 00 0000 00 00 1000
 18:47:52: trace zigbeeMap : [raw:0000 8021 00 00 0040 00 B37A 00 00 0000 00 00 1000, profileId:0000, clusterId:8021, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:B37A, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[10, 00], clusterInt:32801, commandInt:0]
 18:47:52: debug description is catchall: 0000 8021 00 00 0040 00 B37A 00 00 0000 00 00 1000
 18:47:51: debug [name:switch, value:off]
 18:47:51: debug description is on/off: 0
 18:47:50: info DID NOT PARSE MESSAGE for description : catchall: 0104 0006 03 01 0040 00 B37A 00 00 0000 07 01 00
 18:47:50: trace zigbeeMap : [raw:0104 0006 03 01 0040 00 B37A 00 00 0000 07 01 00, profileId:0104, clusterId:0006, sourceEndpoint:03, destinationEndpoint:01, options:0040, messageType:00, dni:B37A, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:07, direction:01, data:[00], clusterInt:6, commandInt:7]
 18:47:50: debug description is catchall: 0104 0006 03 01 0040 00 B37A 00 00 0000 07 01 00
 18:47:48: info DID NOT PARSE MESSAGE for description : catchall: 0000 8021 00 00 0040 00 B37A 00 00 0000 00 00 0E00
 18:47:48: trace zigbeeMap : [raw:0000 8021 00 00 0040 00 B37A 00 00 0000 00 00 0E00, profileId:0000, clusterId:8021, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:B37A, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[0E, 00], clusterInt:32801, commandInt:0]
 18:47:48: debug description is catchall: 0000 8021 00 00 0040 00 B37A 00 00 0000 00 00 0E00
 18:47:48: info DID NOT PARSE MESSAGE for description : catchall: 0000 8021 00 00 0040 00 B37A 00 00 0000 00 00 0D00
 18:47:48: trace zigbeeMap : [raw:0000 8021 00 00 0040 00 B37A 00 00 0000 00 00 0D00, profileId:0000, clusterId:8021, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:B37A, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[0D, 00], clusterInt:32801, commandInt:0]
 18:47:48: debug description is catchall: 0000 8021 00 00 0040 00 B37A 00 00 0000 00 00 0D00
 18:47:46: trace zigbeeMap : [raw:B37A0303000A0100002000, dni:B37A, endpoint:03, cluster:0300, size:0A, attrId:0001, result:success, encoding:20, value:00, isValidForDataType:true, clusterInt:768, attrInt:1]
 18:47:46: debug description is read attr - raw: B37A0303000A0100002000, dni: B37A, endpoint: 03, cluster: 0300, size: 0A, attrId: 0001, result: success, encoding: 20, value: 00
 18:47:44: trace zigbeeMap : [raw:B37A0303000A0000002000, dni:B37A, endpoint:03, cluster:0300, size:0A, attrId:0000, result:success, encoding:20, value:00, isValidForDataType:true, clusterInt:768, attrInt:0]
 18:47:44: debug description is read attr - raw: B37A0303000A0000002000, dni: B37A, endpoint: 03, cluster: 0300, size: 0A, attrId: 0000, result: success, encoding: 20, value: 00
 18:47:42: debug [name:colorTemperature, value:2703]
 18:47:42: debug description is read attr - raw: B37A0303000C070000217201, dni: B37A, endpoint: 03, cluster: 0300, size: 0C, attrId: 0007, result: success, encoding: 21, value: 0172
 18:47:40: debug [name:level, value:100]
 18:47:40: debug description is read attr - raw: B37A0300080A00000020FE, dni: B37A, endpoint: 03, cluster: 0008, size: 0A, attrId: 0000, result: success, encoding: 20, value: fe
 18:47:38: debug [name:switch, value:off]
 18:47:38: debug description is catchall: 0104 0006 03 01 0040 00 B37A 00 00 0000 01 01 0000001000
 18:44:45: debug [name:s

They turn on by themselves because they are a joke. A cheap joke. I got fed up with these Osrams, A60 and gu10, that I’m swapping them out for Fibaro Dimmer’s, more expensive but more reliable.