Since this is a component with multiple platforms the structure is a bit different than single conponents/platforms.
The “old” file custom_components/circadian_lighting.py should now be custom_components/circadian_lighting/__init__.py
So there should not be any circadian_lighting.py files in the root of the custom_components dir.
in the custom_components/circadian_lighting/ dir you should now have:
__init__.py
sensor.py
switch.py
Thanks a lot ! It seems to be working fine now :).
Hey all, I know I need to update the instructions for the new file structure. I’ve been holding out because I want to either get CL working with custom updater or I want to get it integrated as a native HA component. My big hangup for getting it integrated natively is that I want to add functionality to enable/disable colortemp and brightness on the fly for each CL switch. Ideally the front-end would have a button to toggle colortemp and a button to toggle brightness for each CL switch entity, either on the entity row or in the more-info panel. Problem is, there’s no existing front-end component with this functionality. I reached out in Discord, but I got the impression that there wasn’t much interest for me to add a special entity row or card for CL so I’m not sure if a PR would be accepted.
So at this point I’m trying to decide if I should keep pushing to get answers for native integration, or if that’s a waste of time and I should just move forward with getting CL working with custom updater and build a custom entity-row that people could manually add to Lovelace if they’re so inclined.
Thanks! Working here too 
@claytonjn if you go the custom_updater route hit me up on discord and we can probably find a solution that is easy for you and the users 
I was thinking something more like this:
The problem is convincing the front-end devs that something like that should be accepted as an official entity row.
I have two lights controlled by circadian_lighting. However I only want one light to have disable_brightness_adjust: true. Is this possible? I tried adding a second circadian_lighting platform switch but seems HA only uses the first one.
EDIT: in order to get this working, you must define a unique name for each switch.
You have to set up a second switch, not a second platform.
My brightness stays at: 100. during the day. Did i miss somthing. Here is my config
circadian_lighting:
interval: 60
transition: 3
switch:
- platform: circadian_lighting
min_brightness: 18
max_brightness: 100
lights_ct:
- light.milight_diningroom_1
name: diningroomIt’s only supposed to dim at night. Is your switch turned on? IE: switch.circadian_lighting_diningroom
Hi, thanks for a truly great plugin!
I have a really strange issue though. I have a lot of automations using node-red and I have found that when I have an automation that sets a specific brightness to a light when turned on, the circadian lighting plugin cannot budge it. However the brightness indicator in the interface says that the brightness is as expected (255 for example).
To take an example. I have a motion sensor in my bathroom that turns on the light to brightness 100 if the state of the bathroom light was off. Simple.
However, in this case I would expect that circadian lighting would take over and dim the light to the appropriate lighting level (255 for the middle of the day). BUT this does not happen. The interface is updated to say that the light is at 255 brightness, but the light itself is not changed. And if I use the dimmer in home assistant, to change the brightness to like 99%, the lights very briefly brighten before being returned to the start.
The reason why I believe this to be a bug in your component and not in Home assistant is that no other thing behaves this way. This exact automation has been running in combination with dimmers etc without issue, and there has been no issue with the interface not showing the actual dimmed value.
If I change my automation to NOT specifically append brightness when turning on the light, everything behaves as expected. and also, strangely if I dim using my wall dimmer it also starts working (i.e. dimming while the light is on). This only seems to be an issue when the light is started with a set brightness.
As new users only can upload a single image, I have concatinated the three images I originally attached:
To the left is a working example:
To the right is the non working example, where I set brightness explicitly on trigger:
At the bottom is the entire node red flow, if that’s interesting, it’s the top svc: light:turn_on node that is showing:
This is an issue with all my automations that set the brightness this way, not just this specific one, but it was the easiest to explain. I really would like this to work with a set brightness, since I would like to default to a low brightness to avoid blinding someone in the middle of the night if the previous brightness was high on a lamp that is not used often.
My home assistant version is 0.84.5, and I know it’s not the latest, but I really need to prepare before updating to the lovelace ui, as I’ve heard that many people are having issues with their old config.
Again, thank you so much for this component, it is really striking, but this issue is driving me mad, and I truly hope you have some insight into what could be the issue!
Below I’ll attach the JSON for my node red nodes if that is useful:
[{"id":"2023a3a9.ab1d8c","type":"api-call-service","z":"f0f89a8e.bd0bc8","name":"","server":"8ad07cbe.ddf6","service_domain":"light","service":"turn_on","data":"{\"entity_id\":\"light.lower_bathroom_ceiling\",\"brightness\":100}","render_data":false,"mergecontext":"","x":1015,"y":2500,"wires":[[]]},{"id":"24a8387d.4e0bc8","type":"api-current-state","z":"f0f89a8e.bd0bc8","name":"Only turn on if off","server":"8ad07cbe.ddf6","halt_if":"on","halt_if_type":"str","halt_if_compare":"is","override_topic":false,"override_payload":false,"override_data":false,"entity_id":"light.lower_bathroom_ceiling","state_type":"str","x":615,"y":2500,"wires":[["2023a3a9.ab1d8c"]]},{"id":"1c896d7b.1be5f3","type":"switch","z":"f0f89a8e.bd0bc8","name":"on/off","property":"payload","propertyType":"msg","rules":[{"t":"eq","v":"on","vt":"str"},{"t":"eq","v":"off","vt":"str"}],"checkall":"true","repair":false,"outputs":2,"x":335,"y":2560,"wires":[["618024e.24ccddc","24a8387d.4e0bc8"],["6357a7ef.15c698"]]},{"id":"3c040d05.814b42","type":"server-state-changed","z":"f0f89a8e.bd0bc8","name":"Lower bathroom entrance","server":"8ad07cbe.ddf6","entityidfilter":"binary_sensor.lower_bathroom_entrance_motion","entityidfiltertype":"exact","outputinitially":false,"state_type":"str","haltifstate":"","halt_if_type":"str","halt_if_compare":"is","x":115,"y":2491,"wires":[["1c896d7b.1be5f3"]]},{"id":"618024e.24ccddc","type":"change","z":"f0f89a8e.bd0bc8","name":"Inject stop","rules":[{"t":"set","p":"payload","pt":"msg","to":"stop","tot":"str"}],"action":"","property":"","from":"","to":"","reg":false,"x":595,"y":2560,"wires":[["21885c07.4f6664"]]},{"id":"6357a7ef.15c698","type":"api-current-state","z":"f0f89a8e.bd0bc8","name":"Sensor state toilet","server":"8ad07cbe.ddf6","halt_if":"on","halt_if_type":"str","halt_if_compare":"is","override_topic":false,"override_payload":false,"override_data":false,"entity_id":"binary_sensor.lower_bathroom_toilet_motion","state_type":"str","x":510,"y":2620,"wires":[["f0f66891.572a58"]]},{"id":"4c297892.c61368","type":"inject","z":"f0f89a8e.bd0bc8","name":"","topic":"","payload":"on","payloadType":"str","repeat":"","crontab":"","once":false,"onceDelay":0.1,"x":115,"y":2620,"wires":[["1c896d7b.1be5f3"]]},{"id":"b86f01ab.e3b8f","type":"inject","z":"f0f89a8e.bd0bc8","name":"","topic":"","payload":"off","payloadType":"str","repeat":"","crontab":"","once":false,"onceDelay":0.1,"x":115,"y":2660,"wires":[["1c896d7b.1be5f3"]]},{"id":"e677c52a.d89af8","type":"server-state-changed","z":"f0f89a8e.bd0bc8","name":"Lower bathroom toilet","server":"8ad07cbe.ddf6","entityidfilter":"binary_sensor.lower_bathroom_toilet_motion","entityidfiltertype":"exact","outputinitially":false,"state_type":"str","haltifstate":"","halt_if_type":"str","halt_if_compare":"is","x":105,"y":2540,"wires":[["1c896d7b.1be5f3"]]},{"id":"21885c07.4f6664","type":"stoptimer","z":"f0f89a8e.bd0bc8","duration":"1","units":"Minute","payloadtype":"num","payloadval":"0","name":"","x":940,"y":2580,"wires":[["a1566272.93c25"],[]]},{"id":"f0f66891.572a58","type":"api-current-state","z":"f0f89a8e.bd0bc8","name":"Sensor state entrance","server":"8ad07cbe.ddf6","halt_if":"on","halt_if_type":"str","halt_if_compare":"is","override_topic":false,"override_payload":false,"override_data":false,"entity_id":"binary_sensor.lower_bathroom_entrance_motion","state_type":"str","x":740,"y":2620,"wires":[["21885c07.4f6664"]]},{"id":"a1566272.93c25","type":"api-call-service","z":"f0f89a8e.bd0bc8","name":"","server":"8ad07cbe.ddf6","service_domain":"light","service":"turn_off","data":"{\"entity_id\":\"light.lower_bathroom_ceiling\"}","render_data":false,"mergecontext":"","x":1195,"y":2614,"wires":[[]]},{"id":"8ad07cbe.ddf6","type":"server","z":"","name":"Home Assistant","legacy":false,"hassio":false,"rejectUnauthorizedCerts":true,"ha_boolean":"y|yes|true|on|home|open"}]
Have you tried turning on debug logging for Circadian Lighting, and if so, is the behavior different between when you do and do not set brightness in Node-RED?
Also, to confirm, you want Node-RED to turn the lights on at 100, then CL to adjust them immediately?
Thank you for your swift response. Unfortunately after enabling debug mode I can no longer replicate the issue. I’ll have to try again tomorrow, perhaps this is just an issue during the day (when the light levels are > 250) or something. I’ll try to check before work tomorrow, but worst case I work from home on friday.
Yes that is correct! 100 is just an arbitrary number, so it’s probably lower (like 1) at least for some lights.
Upon further research I realised that my error description was entirely wrong.
I can reproduce the issue just using home assistant and the brightness sliders. To reproduce:
Debug log says:
2019-02-26 20:43:22 DEBUG (SyncWorker_1) [custom_components.switch.circadian_lighting] light.lower_bathroom_ceiling CT Adjusted - color_temp: 400, brightness: 61.777598968505856, transition: 1 2019-02-26 20:43:22 DEBUG (SyncWorker_18) [custom_components.switch.circadian_lighting] light.lower_bathroom_ceiling CT Adjusted - color_temp: 400, brightness: 61.777598968505856, transition: 1
I am using the Deconz-integration in home assistant to control my trådfri-lights.
So according to CL it should have adjusted. CL uses the same service call to adjust the lights as the front-end (and everything else) so try this:
dev-service page call the light.turn_on service with this service data:{
"entity_id":"light.lower_bathroom_ceiling",
"color_temp":400,
"brightness":61.777598968505856,
"transition":1
}
The only thing I can think of is maybe Deconz doesn’t like non-integer brightness - the front end thinks the light changed due to the service call, but the light never actually adjusts. Try the above and let me know the result.
Ah, I think I found the issue! It seems that either Home assistant, or Deconz, or Trådfri cannot change both brightness and color in the same command
{ "entity_id":"light.lower_bathroom_ceiling", "brightness":100.777598968505856, "color_temp":200, "transition":1 }
Does not work
However
{ "entity_id":"light.lower_bathroom_ceiling", "color_temp":200, "transition":1 }
Followed by
{ "entity_id":"light.lower_bathroom_ceiling", "brightness":100.777598968505856, "transition":1 }
Works brilliantly! Is a “dual step” something that could be a mode or something? I really don’t know how to track this issue further to the source!
Hmm, this seem to explain the issue at hand:
Sorry for the spam, but I found some kind of workaround:
{ "entity_id":"light.lower_bathroom_ceiling", "brightness":25.777598968505856, "color_temp":100, "transition":0 }
Works fine, but is a bit… choppy (as expected)
Edit:
So by modding the code to set the “on demand transition” to 0 instead of 1 on line 332, it works, albeit very choppily when “transitioning”. I suspect there would be som reworking needed to make it transition “pretty”. As far as I understand it Trådfri can only do one thing at a time, and that includes transition times, so it would have to do it a bit more involved…
Thanks for your help in troubleshooting this! If you have any idéas in how to implement a “trådfri compatible” fade, that would be much appreciated and would make my setup work a lot better, but as for now it at least kind of works 
.
I’m glad you got to the root of the problem! Certainly there are many possible options to fix this, but from the CL side of things it would basically require looping say 100 times with no transition and changing brightness 1/100th each time. While possible, there are some big drawbacks to this approach. CL can only control things through the standard hass.services.call. Every time that happens there are multiple things occurring, including: writing events to the event buss, updating states to the db, and potentially triggering other automations, etc. So if CL implemented such a workaround all that would happen times 100 for each light that’s adjusted.
The real solution, ultimately, needs to be implemented in the component that actually registers the entity (in this case Deconz).
By the way, you could pull the brightness attribute directly into Node-RED so that when it first turns on lights CL doesn’t have to re-adjust. CL would still control adjusting them throughout the day but in the initial turn_on they wouldn’t be at one level and then change 