Alarm AlarmRepeat fail

[Galaxy-Man]

Hi
I know someoelse raised this as an issue but I did not see it get resolved. If you still remember how you supported this library can you help?

The Alarms do not work:

Alarm.alarmRepeat(13, 28, 0, MorningAlarm);
Alarm.alarmRepeat(17, 28, 0, EveningAlarm);
Alarm.alarmRepeat(dowSaturday, 9, 15, 0, WeeklyAlarm);
Alarm.alarmRepeat(dowSunday, 9, 15, 0, WeeklyAlarm);

These timers work:

Alarm.timerRepeat(15, Repeats); // timer for every 15 seconds
id = Alarm.timerRepeat(2, Repeats2); // timer for every 2 seconds
Alarm.timerOnce(10, OnceOnly); // called once after 10 seconds

I am running this with the ESP32 time library and your library. There is nothing else that I can see would interfere with the operation.

ESP32 Boards tried ESP32 DoIT, Wemos and TTGO.

The time is being picked up correctly and set.

The Enviro is as below.
configTime(0, 3600, "pool.ntp.org");
setenv("TZ", "GMT0BST,M3.5.0/1,M10.5.0", 1);
tzset();

Any suggestions where to look as to why the Alarm Repeat is not firing?

Thank you for any help.

[jhagberg]

Hej
No I did not get anything to test with so I could not reproduce it. I have not touch any of the alarm functions just replaces the time handling with the newlibC . But of course it might mess up something.

I do not have any ESP32 board to test with but if you can make a small sketch that shows the bug I can try it on the boards I have.

Also it maybe its time to see if there is any update on the alarm functions. I have not used this lib for a long time.

[Galaxy-Man]

This issue can be closed, I am using the DailyTimer library for ESP32.

Thanks.

[jor3l]

I'm not able to get this to run on a ESP8266, timerRepeat prints nothing

[jor3l]

I needed to add Alarm.delay(1000) to the loop so it works

[jhagberg]

Hej yes, you need to invoke that like in my example. Could this be the case for you also @Galaxy-Man ?

see:

ESP8266TimeAlarms/examples/TimeAlarmExample/TimeAlarmExample.ino

Line 61 in fff9617

Alarm.delay(1000); // wait one second between clock display

[jeanlemotan]

This could have been due to the bug fixed in #8