Maybe most people don't use focus modes or Do Not Disturb on iOS, because the current notification implementation completely ignores them, and I'm surprised I don't see it mentioned more often.

I use focus modes pretty extensively - to block certain notifications during work hours, block others during personal hours, block most (with a few exceptions) during sleep... but notifications as-built ignore the quiet notification flag on iOS. This means you either get buzzes for every enabled notification (even with phone DND enabled), or you get zero notifications at all (with watch Quiet Time enabled).

To compound this, you can only automatically enable Quiet Time on a basic schedule (which might work for SLEEP at least if your sleep schedule is consistent...) or for calendar events. You can't even enable Quiet Time when the watch detects sleep.

There is a PR to respect the silent flag and Eric responded:

pretty cool find! If this gets added, it should be off by default. Many people rely on keeping their phone in DND permanently and still receiving Pebble notifications. I like the idea of re-using the same toggle as android!

One person's bug is another person's feature 😉

I think he's referencing the toggle on Android which is something like "Respect phone do-not-disturb". Is he right that many of you keep the phone in DND and want notifications to still buzz your wrist? This is especially distracting if you wear the watch to sleep and use it as an alarm - so you basically have to manually enable and disable Quiet Time every night.

tl;dr Quiet Time as-built is largely all-or-nothing and manual, but Pebble already receives a flag from the iPhone about whether the notification should be silent (including during DND) and I'm surprised that a toggle to respect that silent flag on iOS isn't a higher priority for the community.

guys, always wear your protection! It’s a small chip, but..

(have no idea how it happen)

I'd like to know if it's possible to make different buzzing patterns for different notifications, so for instance WhatsApp buzz twice, Signal long &short buzz

Originally, I bought a soft screen protector off etsy. It took about two weeks to come and is overcut. Meaning that it wasn’t the exact shape of the screen, so there’s always overhang and because of that both protectors came in a single week..

I have since ordered a bumper and it’s nice and snug, but I want to add a screen protector. Any good recommendations that would fit with a bumper?

Thanks in advance! *note I’m in the states

I have a PT2 and the first Notifications are shown at the watch faces, then nothing. Even in the notification menu, it´s just empty. Connection via bluettoth is given all the time. My first thought was i have turnt something off... So i did a factory reset. The same problem was here again. First one came, then nothing. Whatsapp and Signal have permissions.

Thanks for your Help.

I run this on my vps (along with a bunch of other things in an docker-compose / nginx setup), but you can run it anywhere that you can get networking to. You have to enable 2FA authentication for your Amazon account, which maybe you should do anyway. Given that it registers as a device that can send text to your Alexa.

I have this configured as just another mcp for the regular index01 agent. I can say "Tell Alexa to set a timer for 45 minutes" from the laundry room and then Alexa alarm will go off in the house. You can actually drop the "Tell" and say "Alexa, set a timer for 5 minutes" and seems to work. Since it is really sending text commands just like the alexa-app, I assume you can send it anything, though I only use Alexa for alarms, Spotify, and occasional trivia questions :)

AI Disclosure: 100% generated code with a steady and experienced hand.

I used to be Android, now I’m iPhone, and I’m considering a Pebble.
The thing I loved about the Pebble was long battery life and filtered, silent notifications on my wrist and media playback.

Does it live up to my simple expectations?

Happy owner of a Pebble Time 2 here!

I enable and disable Airplane Mode quite often to avoid keeping Bluetooth on when I'm not wearing the watch. However, whenever the Airplane Mode screen appears, I can clearly see the watch face still visible in the background, like ghosting/image retention.

I contacted support through the app, and they asked me to upload a video showing the issue. The problem is that I can't get my phone's camera to capture it. It's clearly visible to the naked eye, but it doesn't show up in the recording.

I've also tried filming in slow motion, with no luck. I'm using a Pixel 6a.

Any idea how I could capture this properly on video?

In addition to the "Most Loved" and "All" sections of both the Watchfaces and Apps pages, it would be nice to see new entries as well. Or am I crazy and just missing the way to view new stuff?

I need an BPM tapper app. But there is no app that support touch screen, So I made it

It support touch screen and speaker

Supported input mode - touch - button - Z axis (experimental)

Supported metronome - Screen flash - Sound - Vibration - Flash + Sound - Flash + Vibe

Can adjust BPM with up/down button to match your music

Does anyone know if it's possible to turn off just the step counter in health monitoring, or maybe manually set it to zero?

I'm unable to walk and bedbound, so as amusing as it is for it to say I'm walking hundreds of steps a day, it's entirely inaccurate.

I want to keep the heart rate and sleep tracking, but I can only find a way of turning them all off.

Finally got a PT2, as someone who had an OG Pebble back in high school and later a Pebble Time, this feels just like I remember, and I love it. The only thing kind of bugging me is the backlight has a significantly more blue tint compared to my PT. I know it's an rgb backlight, but has anyone figured out the best hex value for a neutral light without much tint? I played with it for a while and couldn't nail it down.

Thanks y'all!

I've had my pebble time 2 for a few weeks now, and prior to that, the pebble time steel on and off since 2015.

between them I've also tried fitbit, fossil, and amazfit.

Coming back to pebble is like coming home, this is everything a smartwatch should be. Minimal, fun, long battery life, always on display. Functional, I can read and respond to notifications easily. Great build quality.

of course it's missing a few things, such as you can't answer calls on it.

My question is, with it hitting all these points so well, why has it not hit the mainstream? Marketing? Is it not flashy enough?

Would love to hear your thoughts and theories.

Reposting since Reddit seems to hate the links I've linked...

Since I got my Time 2 I've been working on something to help me build watch faces without having to deal with a lot of C or JS code. The end result is a set of files you can plug into CloudPebble to build and publish your watch face for use.

The emulated display in the app is reasonably 95% accurate, I can't use and distribute the device fonts because they're (in my opinion) unreasonably expensive to license sometimes things have to be shifted around slightly once in CloudPebble or on-device but overall I think it works great.

Link to the app can be found in the Github repo: https://github.com/tapresle/pebble-watchface-builder

Released a small update, 1.2.0, to my watchface for photographers — the one that lets you track the light through the day.

What's new:

• The 24-hour ring around the dial can now be turned around in the settings: noon at the top, midnight at the bottom, so the sun climbs the left side and comes down the right, the way it moves in the sky.

• The small text on the Astro screen is bold now, and on PT2 and Round 2 it also went up a size step, which should make the information easier to read.
• A small correction to the weather colours on the Clock screen. Green turned out to be the dimmest of the three on a real display, so "good conditions" looked fainter than "bad ones". It uses a brighter green now.
• A small fix to how the light ring is drawn on the black-and-white watches.

Thanks to u/BitLicker and u/Alfiewoodland for the suggestions.

• Repebble Appstore: https://apps.repebble.com/be7ddcf0613941d1842c8310
• Rebble Appstore: https://apps.rebble.io/en_US/application/6a7c98ebe5bc86000907ff68
• Source code + .pbw: https://github.com/Greenteyn/alpenglow-watchface

As for the near future, I want to try showing the sun and moon azimuth with a compass arrow (assuming it doesn't drain the whole battery faster than anyone gets to use it), and to make an analogue version of the watchface as a separate app.

If you have any suggestions or remarks about the app, leave a comment - I'll see what I can do for the next version.

What it says. Ever since I got my Time 2 and connected it, my phone will randomly reboot while I'm using it. It even once rebooted in the middle of watching a YouTube video. I tried unpairing and forgetting the watch, clearing the app cache, reinstalling the app, and factory resetting the watch, but nothing seemed to help.

Well i finally retired my Amazfit watch after 10 years.
Its lasted me well and did everything i need. Time, steps, receive texts, awesome battery life. Didnt need anything more.

When i found out the pebble was being relaunced I was all over it.

So far loving it! Still learning what it can do

About a week ago I shared Big Time here, my watchface built around keeping the time as big and readable as possible. A bunch of you tried it, purchased Pro, and sent me some really helpful feedback. Thank you!

Big Time Pro is $1.99. There is a 48 hour free trial.

I've been continuing to work on it, and the latest addition is probably my favorite so far: analog mode.

Instead of squeezing a normal circular watch into a rectangle, I built the clock around the available space. The hands dynamically change length and the analog clock can expand to fill almost the entire display depending on which data is visible. Raise your wrist, tap, or activate the backlight and the information bars come back while the clock shrinks to make room for them.

So now Big Time can be a giant digital clock, a rectangular analog watch, a minimal full-screen analog watch, or a pretty information-heavy watchface depending on how you configure it.

I've also continued adding smaller options and improvements based on feedback from people here.

Thanks again to everyone who tried it, bought Pro, gave it a heart, or sent me suggestions. Seeing people actually using something I made has made working on this ridiculously fun.

Pebble: https://apps.repebble.com/big-time_a8993caeef5d4fa688e2db68

Rebble: https://apps.rebble.io/en_US/application/6a8c81aafde9d90008cc78c4

it would be nice if the charge screen would show how much charge is left. they could use the cord length to show how much charge is left, how urgent it is.

Has anyone found a similar band to the nomad bands? I've been trying to find one in the orange or the glow yellow for my pebble but have yet to find out.

Saw this on the latest email and couldn't find via image search. Thanks!

There may be some genuinely good news on the horizon for Pebble users in the UK.

As some people here will know, Apple has been required by the EU's Digital Markets Act to open up considerably more of iOS to third-party connected devices. Some of the resulting APIs are very interesting for Pebble.

For example, Apple's new Accessory Notifications framework allows a third-party accessory to receive iPhone notifications, including their content and interactive actions.

More importantly, communication isn't only one-way: an accessory can send notification actions and text responses back to iOS. Apple even specifically supports different handling for incoming calls, alarms and timers:

“For specialized notification types, check kind to apply appropriate handling such as full-screen displays for incoming calls or distinct alert styles for alarms and timers.”

Apple — Accessory Notifications:
https://developer.apple.com/documentation/accessorynotifications

There's also a new Accessory Transport Extension framework providing secure communication between iOS and third-party accessories. Notification contents are encrypted by the system before being passed to the transport extension:

“Your transport extension sends the encrypted data to your accessory, but is unable to decipher the notification’s content.”

https://developer.apple.com/documentation/AccessoryTransportExtension

Apple has also introduced proximity-triggered pairing for third-party hardware, giving accessories something much closer to the seamless AirPods-style pairing experience:

https://developer.apple.com/proximity-pairing/

The catch: these features are EU-only

At the moment, ordinary users outside the EU can't use several of these new interoperability features.

Apple says explicitly for Accessory Notifications:

“You can develop and test an app that uses this framework on devices in any region. Customer installations of your app can only use the framework on devices located in the EU that are signed in with an Apple Account with an EU country or region.”

So those of us in the UK don't get it.

However, that might change — because the UK CMA is now pursuing Apple over essentially the same issue.

The UK regulator is specifically looking at third-party wearables

Under the UK's new digital markets competition regime, the Competition and Markets Authority has designated Apple's mobile platform as having Strategic Market Status, giving it powers to impose requirements on Apple.

The CMA has identified connected devices as one of the interoperability issues it intends to address. Its Apple roadmap says Apple's restrictions can:

“reduce the ability for third parties, including UK app developers, to compete effectively (particularly where these third parties compete with Apple’s own first-party services).”

It proposes potentially:

“Requiring that Apple enables interoperable access for third parties to key functionality in iOS and iPadOS in relation to key use cases”

CMA Apple roadmap (PDF):
https://assets.publishing.service.gov.uk/media/687f893cf2ecaeb756d0e1e6/Roadmap__Apple_.pdf

But it gets much more explicit in the CMA's 2026–27 Annual Plan.

Under interoperability, the CMA says it wants:

“Allowing wearables or other connected devices to connect to Apple’s mobile platforms on even terms with Apple’s own products”

https://www.gov.uk/government/publications/cma-annual-plan-2026-to-2027/annual-plan-2026-to-2027

That's potentially very significant for Pebble.

This isn't just a vague future ambition

Apple has already made commitments to the CMA which took effect on 1 April 2026.

Among other things, Apple has agreed to provide a process through which UK developers can request interoperable access to iOS/iPadOS functionality.

The CMA describes it as:

“Enabling developers to more easily request interoperable access to features and functionality within Apple’s mobile operating systems…”

and says:

“Apple has committed to considering requests fairly and objectively.”

https://www.gov.uk/government/news/cma-secures-commitments-from-apple-and-google-to-improve-fairness-in-app-store-processes-and-enhance-ios-interoperability

Apple also has to report statistics including:

“interoperability requests received, outcomes and timeliness”

and the CMA says that if the voluntary measures aren't effective:

“we will not hesitate to move to formal requirements where necessary.”

Most importantly, the CMA's current programme of work, updated 14 August 2026, says:

“We expect to progress work in relation to Apple concerning browsers (removal of the WebKit restriction) as well as interoperable access to functionality for connected devices.”

https://www.gov.uk/guidance/the-cmas-programme-of-work-across-mobile-platforms

What could this mean for Pebble?

Nothing has been announced yet, so UK support for Apple's new accessory APIs is definitely not guaranteed.

But the pieces line up rather neatly.

The EU required Apple to improve interoperability with third-party connected devices. Apple consequently built APIs which allow third-party accessories to receive and interact with iPhone notifications, distinguish calls/alarms/timers, communicate securely with iOS, and get a much more Apple-like pairing experience.

Those capabilities are currently restricted to EU users.

Meanwhile, the UK CMA is independently targeting Apple's restrictions on connected devices and explicitly says its objective includes allowing wearables to connect to Apple's mobile platforms “on even terms with Apple's own products.”

Apple has already been required to establish a UK interoperability-request process, and the CMA says further work specifically concerning connected devices is coming.

And importantly, Apple has now already built much of the technical infrastructure needed to provide this interoperability in the EU. If the CMA ultimately requires similar access in Britain, Apple wouldn't necessarily need to invent a UK-specific solution — it could potentially make its existing accessory frameworks available here.

For Pebble, that could eventually mean substantially better iPhone integration.

It would be particularly interesting to know whether the rePebble team has already submitted — or plans to submit — an interoperability request to Apple under the new UK process.

And what about the US? 🇺🇸

The situation is less concrete than in the UK, but there's regulatory pressure there too.

The US Department of Justice's antitrust case against Apple specifically identifies Apple's treatment of third-party smartwatches as an example of allegedly anticompetitive behaviour. The DOJ argues that Apple restricts competing watches' access to iPhone functionality — including actionable notifications, which are exactly the sort of capability Apple's new EU APIs open up.

DOJ — United States v. Apple:
https://www.justice.gov/atr/case/us-and-plaintiff-states-v-apple-inc

So there isn't currently an EU/UK-style process that guarantees these APIs are coming to US Pebble users, and the outcome of the DOJ case is uncertain. But Apple is facing pressure on the same third-party smartwatch restrictions in the US as well.

Apple has also established a process through which developers outside the EU can request access to OS capabilities used by Apple's own services or accessories:

https://developer.apple.com/support/interop-request/

So the EU may ultimately prove to be where this more open accessory model starts, rather than where it ends.

Sources

Apple — Accessory Notifications
https://developer.apple.com/documentation/accessorynotifications

Apple — Accessory Transport Extension
https://developer.apple.com/documentation/AccessoryTransportExtension

Apple — Proximity-triggered pairing
https://developer.apple.com/proximity-pairing/

CMA — Apple roadmap
https://assets.publishing.service.gov.uk/media/687f893cf2ecaeb756d0e1e6/Roadmap__Apple_.pdf

CMA — Annual Plan 2026–27
https://www.gov.uk/government/publications/cma-annual-plan-2026-to-2027/annual-plan-2026-to-2027

CMA — Apple interoperability commitments
https://www.gov.uk/government/news/cma-secures-commitments-from-apple-and-google-to-improve-fairness-in-app-store-processes-and-enhance-ios-interoperability

CMA — Current mobile-platform programme of work
https://www.gov.uk/guidance/the-cmas-programme-of-work-across-mobile-platforms

US DOJ — United States v. Apple
https://www.justice.gov/atr/case/us-and-plaintiff-states-v-apple-inc

Apple — Interoperability requests
https://developer.apple.com/support/interop-request/