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.