I should add - I don’t really understand what your ultimate goal is… are you just trying to figure out what the solar angle is when your lights come on today, then you’re going to use that to, make an automation to just turn them on when the solar angle gets to that level?
Wouldn’t it be easier to just make an automation based on sunset with a time offset?
lol. no, right now my lights are powered when an external light sensor switches on power to the lights. This is a non-smart device, but it switches the lights on on a light level I like.
The only way for me to make this smart is check the sun angle when that happens. Ive been monitoring that now for some time, but would like to ‘save’ the angel in the input_number.
If I am satisfied the sun angle is round and about the same when the lights turn on, I can use that, in a new automation as a trigger and take out the external light sensor.
I don’t think the sunset offset is as constant as the sun angle for this purpose and, but I could of course also check that. Any idea how I could add the offset to my current notification?
This is also useful when the “sunset” event is not dark enough outside and you would like the automation to run later at a precise solar angle instead of the time offset such as turning on exterior lighting.
with my current automations id like to capture the correct solar angle.
I can use that later on in the ‘new’ automation. Not sure if I need elevation and a minus setting, or azimuth? Both are solar angle?
well, now that you mention that, I have never given that any thought, but have never had any reason too. It has been working for the last 20 years without a hiccup… So I gather it’s reliable enough to test for solar_angle.
Yes the CC. I disable it most of the time, since HA dev’s warn us not to use CC when issues arise, but have it ready for these kind of needs.