I didn’t see anyone reporting this: when Circadian Lighting action is set for a device in a routine or scene, while editing the scene the summary of actions listed under the device appears fine. Upon saving then recalling the routine or scene, under the device it shows instead “Unknown action” (instead of Circadian Lighting: Active/Inactive). I noticed this for several weeks with older versions of the driver.
I don’t understand why this happens, the presentation of the capability is fine, just like the others on the device.
The strange thing is that the command does not send the Active or Inactive values, it is sending the Circadian value and that is why it says that the action is unknown.
The worst thing is that it makes the Circadian function malfunction
I have updated the presentation and the translation and for the moment everything is the same.
I have reboot the hub and it doesn’t change either.
We will have to wait and see if it updates the presentation when the maximum hub caching times are met.
If it is not fixed I will have to create another new capability to replace it
This morning I experienced the same issue with the 11-Aug driver. The complication might be the Circadian Lighting. I had it switched on, and the On Handler again did not turn on the light, and the CLI showed no Zigbee commands were sent. When I switched Circadian Lighting off it started working, then switched it back on and it continued working.
This particular bulb that was experiencing the on/off issue I’m pretty sure that Circadian Lighting was only ever set manually. The device has no routines/scenes that change the Circadian setting (only on/off since I always want that bulb active in Circadian). I’ll see if it happens again… for now it’s still working fine.
Since yesterday afternoon - all of my Ikea GU10 bulbs have stopped working. I didn’t actually see any information around things being moved from the old Groovy / DTH devices, to these new Edge Devices. Looks like thats been going on for a long time - not sure why I never saw anything for that.
I’ve added the driver channel as part of this thread ( thanks Mariano )
I believe the specific bulbs I use, dont have a profile associated with these drivers.
I also can’t see how I can drill down and get the relevant info for the bulbs, since this smarthings update to ‘mysmartthings’
All I know is they currently show as : TRÅDFRI bulb GU10 WS 400lm
If I try and drill down into any of these bulbs - they only give me
information within the 3 dots menu - dont see anything for driver.
The bulbs all show in the mystartthings area - as ‘DTH’ they are pretty old, got added to the account back in 2017 - and were added with a custom device handler that was available at that time for the Ikea bulbs.
I’m guessing I might need to remove, and readd them to smartthings then, if this driver already has a profile included ?
I’ll need to have a think at what I want to do. My SmartThings hub is in a rack - and I remember with these bulbs when I first got them, I had a nightmare to get the hub to detect them, they had to be literally right next to the hub - and had to reset them multiple times before they were actually seen by ST. I have 16 of these that would need to be re-added, I might just bin them off, and replace with some Philips ones, as they are seemless to add.
Welcome to the wonderful world of Samsung SmartThings in (never ending) transition. But thanks to the great work of folks like @Mariano_Colmenarejo with some (re-)work, you can choose to keep them. So far, thanks to the community Edge driver contributors who did most of the heavy lifting for this platform, I have not yet had to bin anything worth crying over – although I am in tears daily over lost functionality from the old IDE/Classic app, and there’s nothing the community can do about this except gripe - which itself can be a valuable contribution.
That may be the issue. My under cabinet lights were turning off at 4am instead of sunrise & im scratching my head what the heck & posted my issue & @jkp posted check alexa hunches & sure enough that was the peoblem.