You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sync alarms from the scheduler library on the bangle so they show up in the device alarms for the bangle device in Gadgetbridge. And vice versa?
How should creating and deleting alarms via Gadgetbridge and on the bangle impact each other? When connected and when disconnected?
BUG: Currently adding an alarm via gadgetbridge and selecting all 7 days of the week sets an alarm on the bangle, but only to be run once - not all days. fixed with #3178
Also reference #2782 introducing setting alarms and timers via the Bangle.js App Loader. Given that pull request I don't think this issue is time sensitive, punintended.
I think this would be a a nice quality of life improvement though. After I have gotten some feedback on this I'll probably try to tweak this.
The text was updated successfully, but these errors were encountered:
That sounds reasonably doable - it seems like we do something a bit similar for the calendar at the moment, so could use that way of doing things - I think we make the Bangle responsible for sending current timers on connect
Sync alarms from the scheduler library on the bangle so they show up in the device alarms for the bangle device in Gadgetbridge. And vice versa?
How should creating and deleting alarms via Gadgetbridge and on the bangle impact each other? When connected and when disconnected?
BUG: Currently adding an alarm via gadgetbridge and selecting all 7 days of the week sets an alarm on the bangle, but only to be run once - not all days.fixed with #3178This issue is duplicated on BangleApps repo on github and on Gadgetbridge repo on codeberg.
Also reference #2782 introducing setting alarms and timers via the Bangle.js App Loader. Given that pull request I don't think this issue is time sensitive, punintended.
I think this would be a a nice quality of life improvement though. After I have gotten some feedback on this I'll probably try to tweak this.
The text was updated successfully, but these errors were encountered: