[UPDATED] Osram Lightify RGBW A19/BR30 US version (HA) DTH

Just bumping this, can anyone help me figure out if the above is the latest strip firmware? Many thanks :slight_smile:️

My strip (US) is showing:

Target version: 0x01020492
Current Version: 0x01020492

Which means the latest firmware ST is pushing is 0x01020492, doesn’t mean 493 wont work… :slight_smile:

1 Like

Great thanks @nathancu that sounds promising, hopefully 493 for the outdoor strip will be ok and I won’t need a gateway, fingers crossed! :slight_smile:

I am also having issue with my Lightify Flex Strip. Smartthings quiclkly recognized the device and added, but when I use the app to turn on/off the status changes in the app and the ice but the light never turns on??? Here is the one I purchased:

Firmware is as follows:
0x01020492

Getting the following in the IDE:
92b01959-3352-4d45-a975-417559cf89ac 6:45:21 PM: info DID NOT PARSE MESSAGE for description : catchall: 0000 8021 00 00 0040 00 0DE9 00 00 0000 00 00 2A00
92b01959-3352-4d45-a975-417559cf89ac 6:45:21 PM: debug description is catchall: 0000 8021 00 00 0040 00 0DE9 00 00 0000 00 00 2A00
92b01959-3352-4d45-a975-417559cf89ac 6:45:19 PM: debug ON/OFF REPORTING CONFIG RESPONSE: SmartShield(clusterId: 0x0006, command: 0x07, data: [0x00], destinationEndpoint: 0x01, direction: 0x01, isClusterSpecific: false, isManufacturerSpecific: false, manufacturerId: 0x0000, messageType: 0x00, number: null, options: 0x0040, profileId: 0x0104, senderShortId: 0x0de9, sourceEndpoint: 0x03, text: null)
92b01959-3352-4d45-a975-417559cf89ac 6:45:19 PM: debug description is catchall: 0104 0006 03 01 0040 00 0DE9 00 00 0000 07 01 00
92b01959-3352-4d45-a975-417559cf89ac 6:45:17 PM: debug [raw:0000 8021 00 00 0040 00 0DE9 00 00 0000 00 00 2900, profileId:0000, clusterId:8021, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:0DE9, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[29, 00], clusterInt:32801, commandInt:0]
92b01959-3352-4d45-a975-417559cf89ac 6:45:17 PM: info DID NOT PARSE MESSAGE for description : catchall: 0000 8021 00 00 0040 00 0DE9 00 00 0000 00 00 2900
92b01959-3352-4d45-a975-417559cf89ac 6:45:17 PM: debug description is catchall: 0000 8021 00 00 0040 00 0DE9 00 00 0000 00 00 2900

I’ve been using the device handler since OSRAM change the API. One nice things the lightify gateway and the old API had was setting transition times in the curl command. With their new API (that is not ready for primetime), this ability is gone.

I’ve worked through the code on your device handler and see where you set they transition values, I was wondering if anyone could help me take that a step further and make that a parameter I can pass at run time from Webcore. I’ve added the additional input to the function but it doesn’t show up in webcore.

how can you change the default max blink(on) time from 3600 seconds to infinite or something larger? 1hour is not enough.

This thread hasn’t been active in quite awhile. I stumbled across it doing a google search, and was surprised as I scrolled down that I had actually posted in here earlier this year asking the same question I had googled.

Anyway, I am still interested in updating this device handler to pass the color transition time as a parameter at runtime instead of a preference. While I’m somewhat competent with coding, groovy doesn’t quite click with me and I was looking for a little insight.

Does this device handler still work for US based bulbs running the latest firmware?

The three I have still work just fine…

Great work on the handler! I do have question, does this Device Handler not work with the SmartThings Connect app? It seems to work fine in SmartThings classic.

Has anybody gotten this DH working in the new app? @nathancu @RLDreams

This is literally one of two things keeping me from moving everything to the new app.

My osrams have worked in NewApp for a while.

No changes necessary…

That said Im moving to Sengled bulbs instead of Osram / Sylvania every time one dies because the osrams keep falling off the network and need to do an off/on cycle to come back and the color accuracy on the Sengleds are just better.

That said what’s not working?

It’s working for me too, but I just don’t have all the options that this DH provides in the new app like it does in the classic app. (Like pulse, blink and color loop. )

1 Like

Ah gotcha, those never were reliable for me and I don’t use them. TBH I rarely even use the color functions. I’m a switch guy. These are just for accent lighting here and there in my setup.

You have the original osrams?
Or do you have any of the new sulvanlia smart + ones.
Like you my old ones are dropping and giving me issues. The few new ones I have give me no issues.

Both. I find the Osrams and Sylvania’s both have problems being repeaters (which is causing problems with other zigbee devices) and don’t reproduce certain colors (particularly deep purples) very well My Sylvanias work better than the older Osrams, but still less than the wife cares for. The rooms where I have replaced my Sylvanias or Osrams with Sengleds don’t have problems (likely because the Sengleds don’t repeat and let my Zigbee repeaters take over…)

1 Like

Mine are led strips above my kitchen cabinets that slowly loop through the color spectrum between sunset and 11pm.

I have zero problem with the strips. They’re rock solid. The ones that give me a headache are a19 bulbs…

Isn’t that funny bc that’s the same experience I have with my strips vs bulbs.
I wonder if they use a different chip.

I have never even installed the new app. I try to stay with the standard DTH for local execution.
I used this DTH for holidays a couple of years ago and had issues keeping everything in sync, hub was getting overloaded with the constant commands for colorloop, flash, etc.