You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 23, 2021. It is now read-only.
Most of the Hue entities are available through the CC, the one sensor missing is the Daylight sensor, which is unique for each Hub.
This will allow for further logic in HA to use in home/away schedules, and the options the App offers (Hue is expanding that at the moment, given the extra rules being created)
I am aware of what we can do in the HA ecosystem, like offsets in triggers etc, but exactly that subject is cause for great confusion in the community.
Having a clear daylight sensor being on/off following Hue rules is very very adequate and easy to use. No more confusions which (light, day, dark, above_horizon,offset)sensor to use to mimic Hue behavior. Simply use hue_daylight.
full PR ready for that, which has now been delayed/closed to be discussed further in this FR.
some pictures:
There are other "day(light)" sensors, most obvious one the core sun integration. Still, sun-up/down isn't identical to Hue daylight. And exactly that is needed to mimic the Hue behavior in HA.
I've already created the sensor logic, and test logic, so adding would be very easy (using it myself in my local setup as you can see)
Extra burden for the system would be negligible, especially considering the amount of the many lights and accessories people have.
Also, this would be a 1 time set and forget setup. Simply read all attributes on the Hue hub and show them in the sensor.
Please consider adding to the binary_sensor.py.
Thanks!
The text was updated successfully, but these errors were encountered:
Most of the Hue entities are available through the CC, the one sensor missing is the Daylight sensor, which is unique for each Hub.
This will allow for further logic in HA to use in home/away schedules, and the options the App offers (Hue is expanding that at the moment, given the extra rules being created)
I am aware of what we can do in the HA ecosystem, like offsets in triggers etc, but exactly that subject is cause for great confusion in the community.
Having a clear daylight sensor being on/off following Hue rules is very very adequate and easy to use. No more confusions which (light, day, dark, above_horizon,offset)sensor to use to mimic Hue behavior. Simply use hue_daylight.
full PR ready for that, which has now been delayed/closed to be discussed further in this FR.
some pictures:
There are other "day(light)" sensors, most obvious one the core sun integration. Still, sun-up/down isn't identical to Hue daylight. And exactly that is needed to mimic the Hue behavior in HA.
I've already created the sensor logic, and test logic, so adding would be very easy (using it myself in my local setup as you can see)
Extra burden for the system would be negligible, especially considering the amount of the many lights and accessories people have.
Also, this would be a 1 time set and forget setup. Simply read all attributes on the Hue hub and show them in the sensor.
Please consider adding to the binary_sensor.py.
Thanks!
The text was updated successfully, but these errors were encountered: