IdeaWell

Project ideas from Hacker News discussions.

It takes 5 cloud services to hear my doorbell

Original Article

Hacker News Discussion

📝 Discussion Summary (Click to expand)

Theme 1 – Cloud dependency and vendor lock‑in concerns
Many commenters worry that relying on proprietary cloud services (e.g., Samsung SmartThings, Ring) leads to recurring fees, loss of control, and fragility when companies change pricing or shut down APIs.

  • “the upcoming Samsung SmartThings API pricing means things will have to change soon.” – vghaisas
  • “Imagine paying a Korean company five bucks a months so you can get a notification on your phone that your fridge needs a new water filter.” – artisinal
  • “Sadly, it seems that the prudent business decision is to lock your customers into your ecosystem.” – cortesoft
  • “Equipment that is tied to someone else's cloud is an astonishingly bad idea.” – johnhtodd

Theme 2 – Effectiveness vs. privacy of video doorbells/CCTV
Opinions split on whether cameras actually deter crime or merely invade privacy and annoy neighbors, with some citing deterrence value and others questioning real‑world impact.

  • “I fail to see the relation between a video doorbell and stopping a burglar. Burglars wear masks.” – artisinal
  • “It's video surveillance, it makes it more likely they'll go elsewhere. That's literally the whole point of Ring.” – ezfe
  • “Cameras deter crime. Not ALL crime. Criminals aren’t stupid and will simply go burgle someone that isn’t recording.” – schumpeter
  • “People steal things from stores which have had cctv for decades… I have no idea why people think these goofy webcams have any effect other than invading the privacy of your neighbors.” – mathisfun123

Theme 3 – DIY, local‑only, and hacked solutions
A strong thread advocates building or repurposing simple, offline devices (wireless buttons, copper‑wire bells, hacked IoT gear) to avoid clouds and subscriptions.

  • “So I built my own: a basic wireless button sends a radio 433 MHz signal… No Wifi, no Internet, no cloud, no apps.” – mrb
  • “Personally I have a button outside my front door… No cloud required.” – artisinal
  • “My first adventure was with an Amazon Echo Dot 2… I’ve got that wired into my home local AI brain.” – VladVladikoff
  • “Amazon had these little Dash buttons… I hacked one so I could… record the moment i started and finished feeding my infant.” – KPGv2

🚀 Project Ideas

Generating project ideas…

LocalDoorbell: Self‑hosted ESP32 Doorbell with Custom Sound

Summary

  • A wireless button (433 MHz or ESP‑Now) triggers an ESP32 inside the house to play a custom MP3 or tone on a speaker, eliminating the need for any cloud service.
  • Core value: instant, private, fully local doorbell with user‑defined sounds and zero subscription fees.

Details

Key Value
Target Audience DIY home‑automation enthusiasts, privacy‑conscious renters/homeowners
Core Feature Wireless button → ESP32 → local audio playback (MP3/tone) with optional MQTT status
Tech Stack ESP32, Arduino/ESP‑IDF, LittleFS for audio storage, optional MQTT broker, simple web UI for config
Difficulty Medium
Monetization Hobby

Notes

  • HN users praised mrb’s 433 MHz + MP3 player solution as “the only commercial doorbells designed like this” and wanted a replicable, open‑source version (mrb: “I built my own… no Wifi, no Internet, no cloud”).
  • Provides a practical, low‑latency alternative to SmartThings/Ring latency complaints (vghaisas: “It takes a few seconds, but a lot of that is just the HA polling interval”).

ChimeBridge: Retrofit Adapter for Existing Mechanical Chimes

Summary

  • A small ESP32‑based module connects to your existing wired doorbell chime via a relay and accepts wireless inputs (433 MHz, Zigbee, or a simple push‑button) to ring the chime locally.
  • Core value: adds wireless/smart capability to any legacy doorbell without replacing the chime or relying on external servers.

Details

Key Value
Target Audience Homeowners with working mechanical chimes who want wireless buttons or smart integrations
Core Feature Relay‑driven chime activation from wireless/button input; local web UI for pairing and debounce
Tech Stack ESP32, 5 V relay module, RF receiver (433 MHz) or Zigbee module, optional MOSFET for button, local HTTP config page
Difficulty Medium
Monetization Hobby

Notes

  • Commenters noted the difficulty of getting Ring/Nest to work with existing chimes (jonhohle: “every time I have it trigger the mechanical doorbell power drops enough to brown out the Ring”).
  • ChimeBridge solves that by isolating the chime from the smart device, a solution HN users repeatedly asked for (pdonis: “All we had to do… install an extra widget that came with the Ring doorbell”).
  • Enables local‑only setups, satisfying the desire to avoid subscription‑based APIs (vghaisas: “upcoming Samsung SmartThings API pricing”).

DoorbellHub: Local Event Aggregator for Multi‑Source Doorbell Notifications

Summary

  • Collects doorbell press events from any source (RF button, video doorbell MQTT, Home Assistant, HTTP webhook) and instantly triggers multiple local alerts: speaker chime, LED strip flash, push notification to local phone app, or optional snapshots from a local camera.
  • Core value: unified, low‑latency notification system that works entirely on your LAN, reducing reliance on cloud‑based doorbell services.

Details

Key Value
Target Audience Users with multiple smart doorbell devices or DIY buttons who want centralized, private alerts
Core Feature Event ingestion (MQTT, HTTP, ESP‑Now) → configurable actions (audio, light, local push) via rule engine
Tech Stack Node.js/Python runtime, Mosquitto MQTT broker, Express/FastAPI for UI, WebSocket dashboard, optional Home Assistant custom component
Difficulty Medium‑High
Monetization Revenue‑ready: One‑time hardware kit ($39) + optional premium rule‑engine subscription ($2.99/mo)

Notes

  • HN discussion highlighted latency and “5‑cloud services chain” frustrations (vghaisas: “It takes a few seconds… HA polling interval”).
  • Users expressed interest in MQTT as a lightweight alternative (VoidWhisperer: “MQTT… could simplify this significantly”).
  • DoorbellHub directly addresses the ask for a local, interoperable solution that avoids multiple cloud hops and provides immediate, customizable feedback.

Read Later