hass-circadian_lighting

Handle 0.110 entity class name change

Removes warning caused by https://developers.home-assistant.io/blog/2020/05/14/entity-class-names/

Use the same timezone for "now" time and configured lat/long

If a user configures lat/long then they want CL to behave as if they're at that location, therefore the "now" time needs to be the "now" time at that location.

Allow user to set "initial transition" as a configuration parameter

This is the transition used when the Circadian Lighting switches is turned on, a light is turned on, sleep state changes, or disable state changes. Value defaults to 1 (sec) if not configured.

Allow user to set "initial transition" as a configuration parameter

This is the transition used when the Circadian Lighting switches is turned on, a light is turned on, sleep state changes, or disable state changes. Value defaults to 1 (sec) if not configured.

Hotfix for malformed services.yaml causing crashes with Home Assistant Android app (and who knows what else).

NOTE: I know there are a few open pull-requests and features that users are waiting for. I plan on going through those as soon as possible but wanted to push this fix through because it's causing relatively major issues for users and other developers.

Hotfix for malformed services.yaml causing crashes with Home Assistant Android app (and who knows what else).

NOTE: I know there are a few open pull-requests and features that users are waiting for. I plan on going through those as soon as possible but wanted to push this fix through because it's causing relatively major issues for users and other developers.

Only react to light state change to 'on'

And only when light isn't already on. This should allow for users to disable CL when they adjust a light from the frontend, without CL immediately readjusting.

Define "initial transition" and use it when CL switch is turned on

A 1 sec transition was used when a light is turned on or when sleep state changes. The short transition should also be used when the CL switch is turned on. Also, because this is used in multiple spots, better to define it in one spot (this will also make it easier to make it configurable, if desired)

Adjust lights immediately when disable entity state changes

I'm thinking about removing the disable entity option, but while it remains this is the proper behavior

Exemption handling

Handles some unexpected state behavior

Define "initial transition" and use it when CL switch is turned on

A 1 sec transition was used when a light is turned on or when sleep state changes. The short transition should also be used when the CL switch is turned on. Also, because this is used in multiple spots, better to define it in one spot (this will also make it easier to make it configurable, if desired)

Adjust lights immediately when disable entity state changes

I'm thinking about removing the disable entity option, but while it remains this is the proper behavior

Exemption handling

Handles some unexpected state behavior

Only react to light state change to 'on'

And only when light isn't already on. This should allow for users to disable CL when they adjust a light from the frontend, without CL immediately readjusting. This also should remove the need for checking state of each light before adjusting, because infinite loops should no longer trigger.

Check light values before setting them

Hopefully this eliminates possible "infinite loop" of adjustment, where the SERVICE_TURN_ON call triggers CL to adjust and so on.

Remove configuration options from entity attributes

The biggest concern is that apparently any device_class with longitude, latitude, and elevation will show up on the HA map (not just device_tracker). In general, however, configuration options in attributes is extraneous and the community voted to remove them (https://community.home-assistant.io/t/circadian-lighting-custom-component/61246/355)

• Re-wite values calculation to ensure we don't get unexpected results and simplify calculation.
• Tweak default interval/transition.

Add manifest.json (#17) and services.yaml

Fix issue with homeassistant configuration set to elevation: 0.

Remove time_zone configuration variable

astral seems to only be compatible with with deprecated time zone strings, and because times returned are timezone aware the calculations still work properly.

Improve getting astral times

• Include time_zone and elevation to get more accurate times.
• Always pass date into get_sunrise_sunset (otherwise it was returning inconsistent results).
• Add some debug logging.

Initial (versioned) release

Moved to new repository from https://github.com/claytonjn/home-assistant/tree/claytonjn-circadian_lighting with new Home Assistant folder structure (The Great Migration) and Custom Updater support.