Project ideas from Hacker News discussions.

Converting a $3.88 analog clock from Walmart into a ESP8266-based Wi-Fi clock

📝 Discussion Summary (Click to expand)

1. Radio‑time signals are great but fragile
- “WWVB clocks running off the 60 kHz pretty much solve the clock problem in the US.” – Animats
- “I have a few WWVB clocks. The ones that are on the north/south walls will never sync on their own.” – unsnap_biceps
- “I’ve never had a WWVB clock work for me in North Carolina.” – js2

2. Wi‑Fi, NTP, GPS and BLE are the go‑to alternatives
- “WiFi NTP clock I purchased just works, like I always hoped the WWVB clocks would have.” – js2
- “GPS isn’t too hard… the receivers are inexpensive ($5‑$10) and it only takes a few connections.” – ssl‑3
- “Home assistant has pretty good BLE capabilities. But honestly, as has already been pointed out wifi is already really cheap.” – russdill

3. DIY hacking thrives on cheap, low‑end components
- “The SRAM with EEPROM backup chip… costs less than $1 in single quantities.” – teraflop
- “The 47L04 only holds 4 kilobits.” – mftrhu
- “I have a few I2C chips en route, and I can’t wait to get my hands on them.” – mftrhu

4. Design, aesthetics and user‑experience matter
- “It’s like they hired a design firm in the early 00’s and decided that design language is the peak of human horology.” – geerlingguy
- “Battery life is 1‑2 years, which is pretty good for a device with a radio.” – Animats
- “These clocks are irritating because they show up in the results when searching for ‘radio atomic clock’ and similar.” – orev

These four threads—signal reliability, alternative sync methods, component‑level hacking, and product design—capture the bulk of the discussion.


🚀 Project Ideas

AutoSync GPS Wall Clock

Summary

  • Low‑cost wall clock that uses GPS for time, auto‑detects timezone/DST, and drives a stepper‑motor analog movement.
  • Persists hand positions in FRAM to avoid drift and reduce battery usage.
  • Solves unreliable WWVB reception and manual DST adjustments.

Details

Key Value
Target Audience Homeowners, offices, DIY enthusiasts needing accurate analog time without Wi‑Fi.
Core Feature GPS‑driven time, automatic DST, stepper‑motor movement, FRAM persistence.
Tech Stack ESP32‑C3, u‑Blox NEO‑6M GPS, DRV8834 stepper driver, 4 kbit FRAM, 3.7 V Li‑Po battery, 3‑axis magnetometer for orientation.
Difficulty Medium
Monetization Hobby

Notes

  • “GPS isn’t too hard, either” (ssl‑3) – the hardware is inexpensive and the firmware is straightforward.
  • “GPS receiver… only $5‑$10” (ssl‑3) – keeps the bill under $30.
  • Users frustrated with “radio clocks that never pick up the signal” (js2) will appreciate a GPS‑based solution that works indoors.
  • The FRAM chip (47L04) keeps hand positions without wearing out EEPROM (sowbug, mftrhu).

BLE Time Beacon

Summary

  • Tiny BLE beacon that broadcasts a NTP‑style timestamp every minute, no app required.
  • Designed for low‑power devices that lack Wi‑Fi but can scan BLE (e.g., smart bulbs, thermostats).
  • Provides a stateless, battery‑friendly time source.

Details

Key Value
Target Audience IoT devices, smart home gadgets, low‑power sensors.
Core Feature BLE advertising of UTC timestamp, optional local time zone offset.
Tech Stack nRF52832, Zephyr RTOS, simple C firmware, 3 V coin cell.
Difficulty Low
Monetization Hobby

Notes

  • “BLE being a good low‑power and relatively stateless solution” (sowbug) – this beacon eliminates the need for a phone app.
  • “No app on a phone just to maintain a wall clock” (sowbug) – the beacon can be discovered by any BLE‑capable device.
  • The beacon can be paired with a simple web UI for configuring time zone offsets, satisfying “no configuration” frustration.

TimeSync API

Summary

  • Cloud service that aggregates multiple time sources (WWVB, DCF77, GPS, NTP) and exposes a single, highly accurate UTC endpoint.
  • Includes fallback logic, health checks, and a lightweight client library for IoT devices.
  • Ideal for devices that cannot receive radio signals or have intermittent internet.

Details

Key Value
Target Audience IoT manufacturers, home automation hubs, embedded developers.
Core Feature Multi‑source time aggregation, health monitoring, REST/WS API.
Tech Stack Node.js, Docker, Redis, NTP client, GPS receiver (u‑Blox), MQTT broker.
Difficulty Medium
Monetization Revenue‑ready: $5/month per device tier.

Notes

  • “Need a service that aggregates time signals” (discussion) – this fills the gap left by unreliable radio clocks.
  • “GPS unit” (delfugal) – the API can expose GPS time when available, otherwise fall back to NTP.
  • “Time sync over local network” (briHass) – the API can be hosted on a local gateway, providing time to devices without internet.

ClockCal Kit

Summary

  • DIY hardware kit + firmware for building analog stepper‑motor clocks with magnetic sensors and FRAM persistence.
  • Includes a web UI for calibration, hand‑position detection, and firmware updates.
  • Addresses the difficulty of calibrating stepper clocks and detecting hand positions.

Details

Key Value
Target Audience Hobbyists, makers, small‑scale clock manufacturers.
Core Feature Stepper motor drive, magnetic sensor detection, FRAM persistence, calibration UI.
Tech Stack Arduino Nano 33 BLE, DRV8825 stepper driver, Hall sensors, 4 kbit FRAM, ESP‑8266 for Wi‑Fi, web UI (React).
Difficulty Medium
Monetization Hobby

Notes

  • “Magnetic sensors at the bottom of the clock hands” (sowbug) – the kit implements this for reliable hand‑position detection.
  • “FRAM chip” (sowbug, mftrhu) – the kit uses the 47L04 to store hand positions without EEPROM wear.
  • “Calibration firmware” (staplung) – the web UI guides users through aligning the hands, solving the “75% need modifications” problem.

Read Later