Greetings, and many thanks for Alarms++! I've been using it and am very happy with it.

I just took a business trip to a different timezone, and noticed that the alarm I have set in Alarms++ is still reflecting the timezone of where I set it -- not the timezone that I am in.

Specifically, I have a wakeup alarm set for 6am. I created this alarm when I was home -- in the US Eastern time zone. However, I am currently in the US Pacific time zone -- -3 hours from US Eastern time. The alarm went off this morning at 6am US Eastern time (i.e., 3am US Pacific time). Meaning: the alarm seems to be "pinned" to US Eastern time, not "6am in the current timezone".

A few more data points:

• My phone switched timezone when I arrived here, and therefore so did my Pebble. Meaning: both my iPhone and Pebble are reflecting the correct local time (in the US Pacific timezone).
• When I go into Pebble->Settings->Alarms++, it shows that the alarm is set for 6am -- it does not indicate a timezone.

Is this intentional behavior?

If so, would it be possible to add a toggle (either globally or on each alarm) to differentiate between:

• Trigger this alarm at time X in the timezone in which the alarm was created
• Trigger this alarm at time X in the local timezone

FWIW/as a random comparison point: alarms set in the default iOS Clock app are treated as "time X in the current timezone." I.e., if I set an alarm for 6am while in the US Eastern timezone, but then travel to a different timezone, the alarm will go off at 6am local time (not 6am US Eastern time).

Thank you!

Is it possible?

Almost daily the pin for the next day on my recurring alarms doesn't show up. I have to open the app, go to the alarm and go back out. After approx 30 seconds the pin appears most of the time. Anything I can do about that?

Just an idea (don't know, is it usefull or not). I noticed that I had better wake up to the new alarm sound. After some time, I'm getting used to it, and wake up much worse. Maybe it works and vibration?

I use this for a daily reminder in the afternoon but it's not reliable; sometimes it goes off right on time, other times it's several minutes late. I suspect that it's trying to sense my movement like a smart alarm even though I have the smart alarm time set to 0 minutes, which I was hoping meant that it wouldn't be a smart alarm at all.

Hi,
nice new feature would be to have possibility to go to pebble timeline, select future alarm++ pin and dismiss just this one occurance.

why: There are situations when I just woke up and feel no necesity to trigger alarm

thanks
Lubo

Might there be a way to access and edit the Alarms++ entries via the phone app? It's nice to be able to create them using the Pebble, but it would be faster, if it could be synced with the Pebble/Rebble app or some other third-party app. How might one attempt this, if possible?

Thanks,
Jay

Hi
I am not sure if this project is alive but I would really appreciate function to snooze till I get out from bed. I presume it can be easily implemented:

• when alarm is triggered remember number of steps and snooze
• when next time alarm is triggered check the number of steps and dismiss alarm or show alarm again

Thanks

I have the strangest bug still - I have 3 alarms, a Mon/Wed, Tues/Thurs, and Friday alarm, all at different times. Sometimes on a Monday, I'll get both my Mon/Wed and Tues/Thurs alarm, and I sometimes on the weekend, I'll get my weekday alarms.

I've only been able to replicate this bug on Pebble Time.

I tried to fix this myself as an exercise in learning pebble programming but was unable to do so.

I found that when you return to the main window after either adding or removing a description, the black background for the selected item is not the right size. It is in fact the size for the previous state of the menu item (small if adding, large if removing).

I am not yet familiar enough with pebble dev to point the finger at where the issue is occurring but I thought I'd report it as I've hit a wall in determining the cause.

I am beginning to wonder if the fault lies in the pebble menuLayer API.

It'd be cool to be able to set a nudge alarm. Something that would basically go off for a quick pulse and wouldn't require a dismissal. It would auto dismiss.

The description character length is too short. Could you make it longer?

I just received my Pebble Time (yay!) and am using Alarms++.

I've noticed that my daily "wake up!" alarm is coming in a minute or two late. I don't have hard data on this, though (because I'm usually kinda groggy/just waking up).

With some experimentation right now, however, I notice that setting alarms for <=10 minutes from now do not seem to activate. For example:

1. Go to the 3rd alarm on my watch (currently unused/off).
2. Middle button, set it to ~3 minutes from now.
3. Get back to the main alarm listing screen, verify that the time is set correctly for ~3 minutes from now and it is "ON"
4. ~4-5 minutes later, realize that the alarm hasn't gone off.
5. Repeat the procedure and set an alarm ~11 minutes from now.
6. ~13-14 minutes later, realize that the alarm hasn't gone off.

Did the basalt/Pebble Time OS update cause something odd to happen with how alarms are scheduled?