Since Apple simply won’t allow 3rd party apps the full api access they need to do everything, I’m stuck with my Apple Watch if I want all the Apple stuff, and I’m too lazy/annoyed to try to switch ecosystems.
*via Apple Home via Homebridge
You may already be aware, but Apple Home/Siri can talk to Home Assistant directly using https://www.home-assistant.io/integrations/homekit/ which is how I have it set up. You can also have HomeKit devices paired directly with an instance of the HomeKit Bridge, or expose devices in your Apple Home to Home Assistant.
Out of interest, what API access are you missing?
You can also do timers, reminders, web searches and similar basic assistant things with Bobby - another recent addition to what the Pebbles can do: https://rebble.io/2025/03/24/introducing-bobby-our-new-pebbl...
When Pebble died I decided that I'd rather less smart and more battery than more smart and less battery, so I got a Withings watch and have been reasonably happy since.
But this looks really good now and I'm happy to support it even if it doesn't win over my wrist space.
Hopefully they sort out Health Connect support on the Pebble Android app by January so that I can at least sync steps between watches if I'm switching between them.
I think my credit card offers a 3 month return period (2 months longer than an average store's 30 day return period).
Eric isn't in this because he want you to have a better watch, he is in this so he can sell you out at the first opportunity. It may not be FitBit or Automattic this time, but that's just what he does.
They were totally fine products, I enjoyed using them. I am no longer using them, but such is the nature of consumer gadgetry.
I don't recall getting rogered at any point in that process?
When FitBit bought Pebble in 2016, some may argue that this was a good thing, the development of the watch and the OS just stopped - it was dead. FitBit had no intention of keeping the Pebble and just wanted to implement the software into it's own ecosystem.
Google bought FitBit in 2019 and released the source code for PebbleOS this year - but that is kind of late now, isn't it?
I don't think anyone was arguing this - Pebble simply went bankrupt. FitBit just bought some of their IP/assets I think. There was no expectation of them buying it and continuing support or development.
If this is true or not, I have no idea.
I'm generally pretty hostile to companies being acquired and breaking their past customers' products. Shutting down various required cloud services, making software undownloadable, etc.
But I don't think that happened? The roadmap simply ended, but every watch that was out there kept working as-advertised for a good long while?
In fact, I still wear a Pebble daily. Both my Time and Time Steel still work great and I still strongly prefer the whole concept and the UI/UX to any other watch. As soon as they release the iOS app, my Pebble Time will become my "work watch", paired to my job-issued iPhone.
That's not eink technology, it's most likely Sharp Memory-in-Pixel (MIP) LCD display, where the difference between BW and color isn't as bad as in eink technology which uses actual pigment particles inside the pixel cells that "cloud" the contrast.
joewhale•6h ago
net01•6h ago
duomo•4h ago
4ggr0•4h ago
yjftsjthsd-h•4h ago
latexr•3h ago
That seems like an easy fix: Make the software switch to something else (like a “charge me” message) right before turning off for lack of power.
zevon•1h ago
aidenn0•3h ago
teekert•5h ago
jkestner•5h ago