-
-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
2.4.2 Startup Log files - question over constraints. #22
Comments
You are right. The adjustment means it's ensures that the time period is in the future and end comes after start time. Will check this tomorrow. Meanwhile, please report back if the light goes into constrained mode at 21.00. Do you have long lat, timezone and elevation configured under 'homeassitant'? I need to add this to the docs as its critical for timezone and sun component. What is your timezone? I am +8:00. |
Just posed a fix. v2.4.3 |
Hi Danny, I am in Washington DC area (EST = GMT-5). My lat/lng/elev/TZ are all set correctly (date time in the logs above looks correct). I upgraded to 2.4.3 (note: version in the .py file is still 2.4.2 listed) Below is the same log snipper and seems FIRST_END is as expected.
|
initial start/stop callbacks workin 2.4.4 |
Hi Danny,
Please see below. I started HA at 9:30am local time; and it did detect it was inside the constraint period like it should.
It then adjusted that the FIRST_START callback is tomorrow at 7am. This makes sense as we've passed it already for today.
What I think might be a bug is the FIRST_END callback is also set for tomorrow; at 21:00. I would have suspected this should have been today? Or am I not following the logic of the callbacks correctly?
John
The text was updated successfully, but these errors were encountered: