We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Environment
pisugar-programmer --version pisugar-programmer 1.7.4
To Reproduce
$ echo "get rtc_time" | nc -q 0 127.0.0.1 8423 rtc_time: 2022-12-12T20:40:37.000-05:00 $ echo "rtc_alarm_set 2022-12-12T21:00:00-05:00 127" | nc -q 0 127.0.0.1 8423 rtc_alarm_set: done $ echo "get rtc_alarm_time" | nc -q 0 127.0.0.1 8423 rtc_alarm_time: 1999-12-31T21:00:00.000-05:00 $ echo "get rtc_alarm_enabled" | nc -q 0 127.0.0.1 8423 rtc_alarm_enabled: true $ sudo pisugar-poweroff --model "PiSugar 2 Pro" 3 2 1 0...
Expected behavior
Approx. 20 minutes later at 21:00 I thought the Raspberry Pi would reboot; but it did not.
The text was updated successfully, but these errors were encountered:
Something that is kind of weird is that the response to get rtc_alarm_time says the year is 1999
get rtc_alarm_time
Sorry, something went wrong.
by the way, the web interface doesn't work either.
@fengyc @JdaieLin @wlmh110 ....any comments?
I understand now. The pisugar must NOT be plugged in. If it is plugged in it will not wake up.
That seems like a weird behavior. It should wake up whether its plugged in or not.
fengyc
No branches or pull requests
Environment
To Reproduce
Expected behavior
Approx. 20 minutes later at 21:00 I thought the Raspberry Pi would reboot; but it did not.
The text was updated successfully, but these errors were encountered: