Talking Reminder Clock With ESP32-S3, BLE Setup & Round Display

by Chanchaldada in Circuits > Microcontrollers

62 Views, 0 Favorites, 0 Comments

Talking Reminder Clock With ESP32-S3, BLE Setup & Round Display

Phone reminders have a simple problem: they all sound the same. A beep for medicine, a beep for a meeting, a beep for drinking water. After a few days, people swipe them away without reading them.


We wanted a reminder that actually gets noticed: a small desk clock that speaks the reminder in a familiar recorded voice, shows clearly what it is for, and stops with one tap. It also had to keep working when the WiFi goes down, because a medication reminder cannot depend on the router. We built it end to end on a single ESP32-S3 board: board bring-up, firmware, Bluetooth setup, the web interface and the audio pipeline.

Supplies

Hardware: What We Used


We built the whole device around the Waveshare ESP32-S3-Touch-LCD-1.85, an off-the-shelf board with a round touch display and an audio amplifier already on it. The ESP32-S3 gives us WiFi and Bluetooth LE on one chip, two CPU cores, and enough memory for a full-screen display buffer and voice clips. There is no soldering and no custom PCB, which keeps the build simple to repeat.


The bill of materials:


- Waveshare ESP32-S3-Touch-LCD-1.85, speaker version (ESP32-S3, 16 MB flash, 8 MB PSRAM)

- 1.85" round 360×360 display (ST77916) over QSPI

- CST816 capacitive touch controller for the STOP button

- On-board I2S audio amplifier

- Small speaker on the board's speaker connector

- USB-C cable and 5 V USB power supply

- 3D-printed stand (optional)


Software: PlatformIO with the Arduino framework (C++17), Arduino_GFX, NimBLE-Arduino, ArduinoJson, LittleFS, and the nRF Connect app for Bluetooth setup.

The Brief

The device had to do five things:


- Play the user's own recorded voice clips at scheduled times, not a generic beep

- Show the reminder's icon and title on a screen you can read from across a desk, and stop with one tap

- Set up WiFi from a phone, with no password stored in the firmware

- Let anyone manage reminders and clips from a web browser, with no app to install and no cloud account

- Keep firing reminders when WiFi drops


No cloud dependency. Everything runs on the device itself: the scheduler, the web server and the audio playback.

Firmware: Step by Step

We wrote the firmware in C++ on the Arduino framework with PlatformIO.


Step 1 — Board bring-up. Two details cost us bench time. The touch controller didn't show up in an I2C scan: it sits on its own bus (SDA 1 / SCL 3, address 0x15) and only answers while a finger is on the glass, so we found it by probing pin pairs while touching the screen. The display stayed black until we set up the TCA9554 IO expander, because the LCD reset line goes through it.


Step 2 — Display. The full 360×360 screen is drawn in PSRAM about 30 times a second. The clock screen shows analog and digital time, the date, the next reminder and a WiFi status dot. While a reminder plays, it shows an audio-reactive ring, the reminder's icon and title, and a red STOP button.


Step 3 — Scheduler. Every minute the firmware checks each reminder. It fires when the hour and minute match and today is one of its weekdays, or its one-time date. One-time reminders switch themselves off after playing. Up to 32 reminders are saved as JSON in flash.


Step 4 — Audio. A separate task streams 16-bit WAV from flash to the I2S amplifier, with pause, resume and seek. Plain WAV keeps playback simple, and about 10 MB of flash is reserved for clips.


Step 5 — WiFi resilience. Once the time is synced, the clock and reminders run on the device's own time. If WiFi drops, the clock keeps retrying, opens Bluetooth setup in the background after 2 minutes, and retries the saved network every 30 seconds.

Bluetooth Setup and the Web Interface

This is where BLE mobile app development company thinking shaped the design, even without a custom app. The phone side of a BLE product is where most user frustration happens, so we kept the setup flow as simple and safe as possible.


There is no WiFi password in the firmware. On first start, the clock advertises over Bluetooth LE as DMV-Audio-XXXX. From the free nRF Connect app, the user writes the WiFi name and password to a custom GATT characteristic, and the clock replies with notifications: connecting, connected with its IP address, or failed.


Two things we handled carefully:


- Safe credentials — WiFi details are saved only after a successful connection, so a typo never replaces a working network.

- Radio sharing — on the ESP32-S3, WiFi and Bluetooth share one radio. WiFi's power-saving mode has to stay on while Bluetooth is active, or the radio stack stops. With that set, both run side by side.


Everything else happens in a browser at http://dmvaudio.local. The pages are built into the firmware:


- Dashboard — time, WiFi signal, next reminder, free space and quick play

- Reminders — add, test, switch on or off, or delete reminders

- Audio — upload clips with a progress bar

- Settings — time server, time zone and volume

- Wi-Fi — scan, connect, forget the network or reopen Bluetooth setup


Audio conversion happens in the browser. Users upload mp3, m4a, ogg or wav, and the page decodes it, mixes it to mono, resamples it and uploads a plain WAV, so the chip never has to decode MP3.

Prototype

The prototype is the Waveshare board with a speaker connected, powered over USB-C. We kept it on an off-the-shelf board on purpose: no custom PCB, no soldering, and the whole device can be rebuilt in minutes.


During development we refined three things:

- The boot sequence, so the IO expander and LCD reset run before the display starts

- The WiFi connection, using the remembered channel and router for a fast reconnect at boot

- The network change flow on the web page, so a failed new network falls back to the old one


A 3D-printed stand is the natural next step for putting it on a desk.

Results

What the finished prototype does:


- A typical restart reaches a synced clock in about 5 seconds

- The round display runs at about 30 frames per second

- Up to 32 reminders, each with a voice clip, 1–10 repeats and one of 8 auto-picked icons

- Reminders keep firing when WiFi drops; Bluetooth setup opens automatically after 2 minutes offline

- No cloud service, no account and no app to install

What This Kind of Build Takes

If you're planning something similar, the pieces that matter most don't show up on a spec sheet: hardware details that aren't where you expect them, WiFi behaviour that never silences the core function, and a setup flow that a non-technical user can finish without help.


The patterns here carry over to many connected devices: Bluetooth setup instead of hard-coded passwords, local scheduling that doesn't depend on the network, and heavy work like audio conversion moved off the microcontroller and into the browser.

Limitations & What’s Next

We want to be clear about what the current version doesn't do yet:


- After a full power cut, the clock needs WiFi once to get the time before reminders can fire. The board's PCF85063 RTC chip isn't used yet.

- The web page has no password, so it should stay on a trusted network.

- Only one WiFi network is saved at a time.

- STOP is the only touch action so far.


Next on our list: use the on-board RTC so reminders survive power cuts without WiFi, add a password to the web page, and add snooze using the board's motion sensor.


Questions about any part of the build? Ask in the comments.