I like a good smart watch and I appreciate open source, but an ESP32 isn't a great pick when low power consumption is important and the device is going to be communicating regularly. I'm surprised LILYGO went that direction in a watch form factor.
Yeah one of the Nordic nRF chips would be nice. But I guess the advantage of ESP is the hobby developer community. It's not going to be as good on battery power but the barrier to entry for people wanting to tinker is really low.
an esp32 on an 1100mah battery will last years on deep sleep, and about a day with wifi on and in high power modes.
a pixel watch 4 says they last 30 hours , ambiguously. they use a battery less than half the size. in reality with constant use they'll drop dead in 6 hours.
the thing is clunky and heavy , anyway -- so if it lasts as long as an off the shelf watch who cares?
also, the primary reason : lilygo shoves ESPs into everything.
I'm not sure if my Pixel Watch 3 is much more efficient than your 4 or if by "constant use" you literally mean scrolling through it actively for hours at a time, but I only charge mine maybe twice a week. It's on at all times, connected to my phone via Bluetooth and to my Wi-Fi network when I'm home, and I actively manage any push notifications I get from it, but otherwise it seems to idle fairly efficiently.
Several Garmin watches last for weeks (24 days full charge, actual 1-2 weeks with heavy gps and fitness tracking), and I struggle to understand why consumers accept anything less. It seems like consumers don't realize what's available.
Galaxy watch 7 (I think) weather here. Also about 30 hours. It's a charge every day thing, but allowing for some forgetfulness. It's not ideal, but it's manageable and certainly functional.
I’ll need to check my notes on power consumption. I’ve spent quite a bit of time trying out different modes and configurations… it’s not great. I would not expect years at all. You gotta be very careful about what has to stay on and off.
Furthermore, bugs. To this time there’s random crashes that happen with sleep which limits their use
I have some relevant experience. I built this a few years ago:
https://imgur.com/a/diy-automatic-e-ink-newspaper-using-rust...
After careful optimization, the v1 got about 6 months out of a 1100 mAh battery. Later improvements and bumping to a 3300 mAh battery got me to 14 months, before my kid yanked it off the wall, total'd the panel and I rebuilt it. The test continues.
That said--op isn't wrong. If power usage is the metric you optimize for, there's much better BOM than an esp32.
What would you suggest instead?
Nordic Semi, or maybe ST Micro. I've got an STM32WB on my bench at the moment with sensitive coulomb counting and it looks very promising but without all those radios. Of course with all those radios (ie, if you need LoRa on a watch... which is a design decision I'm also skeptical of) then Nordic has a good track record.
Different use case (environmental data recorder) but our current product uses an STM that turns on an ESP32 (not trusting that sleep mode) when it needs radio, to run on 2 AAs forever.
Do you have any info you can share on this recorder? Sounds really interesting!
http://supermechanical.com/pickup Been in production hell thanks to tariffs (wrote a lot about it) but should ship by summer.
For an application using bluetooth low energy, a Nordic NRF52840 turned out to be the winner.
An advantage of ESP32-S3 could be that it seems possible to run Linux on it.
Not natively. It's not a supported architecture and lacks an MMU. Those who have run Linux on it have done so through a RISC-V emulator or similar.
Most of their lora devices are ESP32.