Osram/Sylvania Lightify (it works)

Osram Sylvania just announced a switch today too:

@Sticks18

Noticed this since I updated the firmware:

65f75f32-bbbe-437b-9633-b45952970286  12:32:59 PM: debug [raw:0000 8021 00 00 0000 00 44A4 00 00 0000 00 13 00, profileId:0000, clusterId:8021, clusterInt:32801, sourceEndpoint:00, destinationEndpoint:00, options:0000, messageType:00, dni:44A4, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:13, data:[00]]
65f75f32-bbbe-437b-9633-b45952970286  12:32:59 PM: warn DID NOT PARSE MESSAGE for description : catchall: 0000 8021 00 00 0000 00 44A4 00 00 0000 00 13 00
65f75f32-bbbe-437b-9633-b45952970286  12:32:59 PM: debug description is catchall: 0000 8021 00 00 0000 00 44A4 00 00 0000 00 13 00
65f75f32-bbbe-437b-9633-b45952970286  12:32:58 PM: debug [raw:0000 8021 00 00 0000 00 44A4 00 00 0000 00 12 00, profileId:0000, clusterId:8021, clusterInt:32801, sourceEndpoint:00, destinationEndpoint:00, options:0000, messageType:00, dni:44A4, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:12, data:[00]]
65f75f32-bbbe-437b-9633-b45952970286  12:32:58 PM: warn DID NOT PARSE MESSAGE for description : catchall: 0000 8021 00 00 0000 00 44A4 00 00 0000 00 12 00

This is causing the Level to not update sometimes. Also seeing some of these, but not sure if it affects anything:

7202c76d-72fc-47b7-99fc-68e9b75e4f34  12:34:09 PM: debug description is catchall: 0104 0006 03 01 0000 00 58D7 00 00 0000 0B 01 0100
7202c76d-72fc-47b7-99fc-68e9b75e4f34  12:33:28 PM: info [name:switch, value:on, type:switch]
7202c76d-72fc-47b7-99fc-68e9b75e4f34  12:33:28 PM: debug description is catchall: 0104 0006 03 01 0000 00 58D7 00 00 0000 0B 01 0100
7202c76d-72fc-47b7-99fc-68e9b75e4f34  12:32:58 PM: info [name:switch, value:on, type:switch]
7202c76d-72fc-47b7-99fc-68e9b75e4f34  12:32:58 PM: debug description is catchall: 0104 0006 03 01 0000 00 58D7 00 00 0000 0B 01 0100

I might have some time next week to dig into it.

Another fun one:

d654a1dc-2e00-44c8-85e0-695d054c101e  12:41:29 PM: error groovy.lang.MissingMethodException: No signature of method: java.util.LinkedHashMap.debug() is applicable for argument types: (java.lang.String) values: [color cluster updated successfully]
Possible solutions: getAt(java.lang.String), dump(), get(java.lang.Object), get(java.lang.Object), get(java.lang.Object), plus(java.util.Map) @ line 77

Are these Osram TW bulbs? And what devicetype are you using?

The top one is kind of crazy. It looks like a bind response message. I don’t think the ST system ever let those come through to the parse section before. Then again, we started seeing the OTA update pings recently too. Probably related to something ST is doing behind the scenes as they work on the Zigbee functionality/development.


Bottom one is the typical default response when a message is sent to the bulb. This is the default response saying an ‘on’ command was sent. It shouldn’t affect anything. Just the bulb confirming command received. Not sure why you would see so many close together.

Yeah TW 60W. I’m using the official device too instead of the one you and I wrote. I was mashing refresh() to get that to show up, so that’s why that was happening.

However, I have noticed the ColorTemperature and Level is not updating on the app consistently. The bulb seems to be taking the command though.

They still have some work to do with the new zigbee stuff. The new recommendation is to only sendEvents from parse, so they’re waiting for the bulb to respond to the commands before reporting the new state. Before it was fire and assume. The bulb might not be reporting those attribute changes properly or the messages might be getting lost in the network traffic.

They’re also resending all the config stuff for each cluster every time that refresh() is pressed, which is smart in case they were missed during join; but adds a lot of traffic and could cause issues getting all those messages back and parsed.

I updated my Osram TW over the holidays. Maybe this weekend I can load the stock devicetype and do some debugging on it.

1 Like

OK so I bought an OSRAM Lightify 60W bulb thinking that it would be pretty easy to add since I saw the news about it being supported. However, when I add it, it shows up as an icon with a question mark with “Unknown” and I can do nothing with it. What’s the trick to adding these, is there still custom code needed?
When I look at it in the device list, it has a ZigBee ID and a Device ID. This is my first ZigBee device, all my others are Zwaves.

I sometimes had the lights attached as unknown. Just had to re add them to have them show up properly.

I can confirm that the OSRAM E27 Edison Screw A60 ES Cap 10 W LED Lightify RGB Light Bulb works with the UK SmartThings hub. No custom device type was needed, the hub connected to bulb almost instantly as Zigbee Hue Bulb. Getting the bulb into pairing mode was awkward, I hope Osram will add a pair button I can press. The sliders in smart app are bit wobbly, easy to get the colour I want. Could really use numeric RGB input

The RGB version of this bulb is currently at its lowest ever price of 15.50 GBP on Amazon UK if anyone is looking to buy.

2 Likes

Which is the correct device type for the Osram BR30 RGBW bulb here in the US? I can’t get any of the ones in this thread to control the color, only the white.

I think ST has a general zigbee RGBW devicetype available now that should work. Or you can use the one in the first post here.

Thanks, after some tinkering I found that the Osram flexible RGBW strip device worked for these bulbs. I have one of the strips also so I figured it was worth a try after the others only partially worked.

I’ll check out the one you linked to also. Thanks!

So the RGBW bulbs are now available in the US (via amazon) for $40. Does ST have native support for RGBW yet or is it only available with a hub/bridge?

See the two posts above yours. I don’t think they’ve officially added this bulb to the supported list, but it will connect directly and get full functionality using one of the stock RGBW devicetypes like the Flex or new Zigbee RGBW Dimmer or using a custom devicetype I refined for the UK version.

1 Like

“Available” is a relative term. I ordered some on December 19 and they still haven’t shipped. Currently they are showing 2-5 weeks to ship.

I’m not exactly sure what’s going on with the Osram bulbs on Amazon. I got some BR30s yesterday and paired them up (with some tinkering) successfully last night but now that page on Amazon links to a completely different product. I ended up using the device type that ST has for the LED strip and given the success of that it’s a safe bet that it will work with these as well. Hopefully mine will ship eventually and I’ll get to find out…

Mine worked no problem. However as they are directly to Smart things I get a flicker every so often and sometimes have to turn them on and off to reset them when they don’t respond.

@Polaris, Have you updated the firmware in the bulbs? It’s known to be an issue with older firmware that these bulbs seem to have shipped with of late.

Did this for the 8 LIghtify RGBW’s I own this weekend (2 of which were installed, the other 6 I’d been waiting for time to refresh before I did). The process requires the Lightify hub, which cost me about £20 from Amazon, and is quite slow, as the firmware update happens over-the-air via Zigbee.

For bulbs that you’ve already installed, the process that worked for me:

  1. switch off bulb at wall
  2. remove
  3. plug into handy spare desk lamp (worth keeping around if you do a lot of this)
  4. turn on, count to 5, turn off, count to 5, repeat five times:
  5. the fifth time it turns on you should get a brief flash after 5-10 seconds
  6. Fire up the Lightify app, tell it to scan for new bulbs
  7. Power the bulb off then on again
  8. It should find the bulb with a name something like AS60RGBW 01
  9. Back out of the setup screen
  10. Bottom right of the app you should see a red (1) on the rightmost tab - it’s found the bulb and that it needs a firmware update (should be to version 01020407)
  11. Select this tab, go to the updates menu entry and hit update for that bulb.
  12. Wait. (You can quit the app at this point, or you can tap on the bulb name and watch the progress bar. Either way the bulb will flash once when its updated).
  13. delete the bulb from the Lightify app
  14. turn it off.

I’ve found that at this point, if the bulb was previously installed in a SmartThings setup, you can plug it back in, turn it on, off then on again and it will flash and re-pair into the ST network. You may need to re-save any SmartApps that are expecting to find it, but otherwise this seems to Just Work[tm]

Hope this helps someone.

1 Like

I have succumb and bought a Lightify hub (and a couple more bulbs!) fingers crossed! Thanks for the help!

Do these work with ST?

LIGHTIFY LED RT 5/6 RGBW
LIGHTIFY LED RT 5/6 Tunable White