Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
I like the new
I'm not sure how a
I'm not sure how to use a
Ah good point haven't thought about that, I'll change it to UTC.
Currently it doesn't work ;) it's still work in progress and only contains the CLIP resource without the rules conditions and functionality behind it implemented. The main idea is it to define intervals consisting of two CLIPDaylightOffset sensors, with the interval defined via resourcelink(s) containing the sensor uniqueids.
We are working on a UI in the Phoscon App where the user can define individual daylight related intervals like "morning" and then say, this automation (like motion sensor control or switch configuration) should be active in this interval.
One side effect of the interval points being CLIPDaylightOffset sensors rather then condition values in rules is that they can be reused for multiple automations. So the user can just modify just a handful of intervals and all the related automations will automatically follow without rewriting the rules.
The rule condition operators need to be extended to support the CLIPDaylightOffset sensor as reference point, for example CLIPDaylightOffset sensors
However the TSR/TSS additions are a great idea, these can be very useful and are simpler to implement for many applications which don't require the overhead of a CLIPDaylightOffset sensor.
I would suggest going for both :)