-
Notifications
You must be signed in to change notification settings - Fork 75
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
Acceptable for variables? #72
Comments
As a follow up, it seems the big hurdle is screenBlankHours. If I delete the variable, it operates on the 1-6 default. What disables this all together? I'll try adding it back and setting it to 0-0. |
Change-type: patch Signed-off-by: Chris Crocker-White <chriscw@balena.io>
Change-type: patch Signed-off-by: Chris Crocker-White <chriscw@balena.io>
Change-type: patch Signed-off-by: Chris Crocker-White <chriscw@balena.io>
@ScottTheHippy I've just written a fix for it to allow you to run with blank variables, when #73 merges give it a try and let me know! |
Default to all-day operation fixes #72
P.S. thanks for building the project and thanks for reporting this! I am glad you had fun :) Feel free to reopen this issue if this does not fix it. |
Change-type: patch Signed-off-by: Chris Crocker-White <chriscw@balena.io>
Default to all-day operation fixes chrisys#72
Howdy- I'm trying to get the screen to show the time 24/7. What I'm finding is that the variable(s) operatingHours, screenBlankHours, and/or outOfHoursName seem to be in effect even if deleted. I tried setting screenBlankHours to "0" and that didn't seem to make a difference. Is there some combination of these variable settings that will lead to the clock showing 24/7? Thanks, and fun thing to build. I had the same screen as you, and I might have used a lot of bad language moving that resistor. :)
The text was updated successfully, but these errors were encountered: