Circadian Lighting [Custom Component]

claytonjn · November 2, 2018, 6:32pm

Are you turning off the group using HA, or externally? When you turn off the group, does the group in HA not immediately change states to off?

sergi.suarezj · November 3, 2018, 10:13am

I change from ha. And in ha if the switch turns off,bulbs starts to dimming off but before dimming off completely they come back on.

claytonjn · November 3, 2018, 4:13pm

Okay so that’s what doesn’t make sense to me, something’s definitely not right. If you have light.room configured in CL, and you turn off light.room, that should immediately stop CL from doing any adjustments. CL doesn’t know anything about the lights in light.room, all it knows is that the light.room that’s configured is off so don’t do anything.

I think there’s definitely something else going on here. Off the top of my head, the only thing I can think of is that maybe deconz has strange behavior with transitions. What do you have interval and transition set to? By default, they are both 15 minutes which means that every 15 minutes it updates with a 15 minute transition, which results in a continuous and smooth change. Maybe what’s happening is that with deconz when lights are still transitioning and the group is turned off the lights don’t turn off. You could try testing by setting transition to 0 and see if that fixes the issue.

sergi.suarezj · November 3, 2018, 4:18pm

Unfortunately the behaviour is the same.

claytonjn · November 3, 2018, 4:52pm

Hmm, can you add set the CL components to debug logging level in configuration.yaml?

logger:
  logs:
    custom_components.circadian_lighting: debug
    custom_components.sensor.circadian_lighting: debug
    custom_components.switch.circadian_lighting: debug

Then hopefully we can figure out what’s really going on.

Nesty · November 5, 2018, 1:30pm

Hello, do you plan to implement custom updater? https://github.com/custom-components/custom_updater
Thank you for answer.

claytonjn · November 5, 2018, 4:26pm

I’ve been considering it, but it seems there’s some push to getting this added as a official component so I’ll likely pursue that first.

TMCBackline · November 6, 2018, 7:34pm

Hi,
I have just returned home after a few days, and updated to HA v0.81.6. Unfortunately i am now receiving an ‘Invalid Config’ error on my overview page. I have attached a screenshot of the error.
The Circadian Lighting component is my favorite of all the HA features, so i am a bit gutted i can’t use it at the moment.
Has anyone else had this error and fixed it in 0.81.6?

Thanks

claytonjn · November 6, 2018, 7:48pm

Without logs there’s no way of knowing, but I assume you need the fix from last week, see post 104: Circadian Lighting [Custom Component]

Thank you so much, I really love hearing such positive feedback!

TMCBackline · November 6, 2018, 9:08pm

Perfect! I assumed after the update and the issues i have had with MQTT and media components that the update was the issue and that would be enough!

Thank you for putting the hard work and time into this project!

mouth4war · November 8, 2018, 12:39pm

This may be a long shot but would you consider introducing a way to transition the lights from circadian to sleep mode values?

Reason: It’s hard as hell to manage with automations and turning the switch off and on. Would be great if it were built in to the light update function.

claytonjn · November 8, 2018, 5:11pm

@sergi.suarezj, not sure if you saw my post here - I still think the logging could help us troubleshoot but I was able to reproduce the issue in a specific scenario. Do you by any chance send turn_off with a transition, or in general do the deconz lights take a while to fade off? With my Hue lights if I send turn_off to a Hue group with even a relatively short timeout (10 seconds for example) the group initially has an off state in HA but shortly after it updates back to on while the lights fade off. The problem is that with CL when the group switches state in HA back to on CL immediately updates the group, keeping it on.

If this is in fact what’s going on I’m not sure what the best solution would be, to be honest. Every solution I can think of would cause other negative behavior.

claytonjn · November 8, 2018, 5:12pm

Couldn’t you just set interval to something like 1 second?

sergi.suarezj · November 8, 2018, 5:32pm

@claytonjn Yes I know, But I’m travelling right now without access to my HA.
When I’m back at home and do some home work I plan to change my setup and capture the logs you need.
I’m sorry to not letting you know that I was unable to get the logs in a shorter time.

claytonjn · November 8, 2018, 5:43pm

No problem, I realized I didn’t quote you or tag you so I thought you may have missed it!

mouth4war · November 8, 2018, 9:24pm

Ah I think I didn’t explain clearly what I’m trying to do.

It’s got to do with sleep mode and the fade/transition from normail circadian to sleep mode. I’m doing it using a script so I have to turn off the circadian switch then fade the lights then turn it on again.

I would instead ask for a sleep_delay parameter. This delay can be used to update the lights on a 2-3 second interval (sleep_interval?) from normal values (color_temp/brightness) to and from sleep mode values.

claytonjn · November 9, 2018, 4:22pm

I see, so even with a short period it would cause the lights to abruptly change when entering sleep mode. I’ll have to think about this, I do think it’s a good idea but it would add a bit of complexity and I’m worried adding too many configuration options would cause confusion for users.

mouth4war · November 10, 2018, 10:36am

Hey it’s a feature and you can make it optional, defaulting to 0 second delay (instant update to and from sleep mode values). People who want a gradual change can set a value to have a gradual change.

I see you considered this before as well, in post 22 Circadian Lighting [Custom Component]

oakbrad · November 10, 2018, 5:31pm

I finally did get this great component up & running, however I don’t appear to be getting the color values I would expect and am wondering if I need to tweak something in my config?

I am using Milight RGB bulbs via the MQTT Light platform (this hub https://github.com/sidoh/esp8266_milight_hub/).

When I turned the circadian switch on last night, the lights were deep orange and moved more toward red as it got later. Seemed to be working. However this morning it’s still returning a orange-warm value.

I guess I would expect at 9am for it to be a blue-cool white light, correct? To me eye they appear almost as warm as they were last night at 11pm.

Not a lot of room to get warmer here, this does match the RGB value above from the sensor.

I also noticed if I attempt to set a min_colortemp or max_colortemp it says that is an invalid config option. 5500K seems too warm to me, but I wasn’t able to set it any higher

claytonjn · November 11, 2018, 11:03pm

Yes, I do think that’s a good idea, but I was still going to use the turn_on service call transition, not implement my own. Using sleep like in the example you provided is blocking and holds up the process while it wait, so that would have a negative impact on performance. I’m almost positive the component wouldn’t even be considered for official integration if that were there. I’m still thinking about it and will try to come up with a good solution but ultimately I think that should really be fixed at the device level.