Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Lights get stuck at last state #72

Open
JannKleen opened this issue Dec 1, 2019 · 0 comments
Open

Lights get stuck at last state #72

JannKleen opened this issue Dec 1, 2019 · 0 comments

Comments

@JannKleen
Copy link

JannKleen commented Dec 1, 2019 •
edited
Loading

When restarting kelvin, all worked fine again.

The error message displayed is:

Could not determine interval for current schedule: No current interval as the requested timestamp (2019-12-01 10:22:15.818838737 +0000 UTC m=+392460.500503615) lays after the end of the current schedule (2019-11-30 23:59:59

(it might be cropped on the right side, as I got it out of a screen which is running kelvin)

Running date on my RPi returns the correct (UTC) time.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@JannKleen