Five cloud services and a VPS just to make a doorbell chime indoors

After a burglary prompted a home-security upgrade, blogger Vivek Ghaisas bought a cheap Blink video doorbell — only to discover it made answering the door harder, not easier. Visitors now rang the bell (which chimed uselessly outside) instead of knocking, and notifications only reached his phone, leaving his less phone-attached wife unaware of waiting guests. His goal was simple: play an alert on the Google Home minis already in the house.

Getting there was anything but simple, thanks to two self-imposed rules: no paid subscriptions and no exposing his home mini-PC to the internet. The resulting contraption chains five cloud services together. A Blink ring fires an Alexa routine, which flips a virtual light bulb in Samsung SmartThings — essentially one bit of state stored in the cloud. SmartThings emits a webhook to a tiny server on a VPS, which exposes that on/off state; a Home Assistant routine on his home PC polls that endpoint and plays an audio file on a Google Home mini when it trips.

The Rube Goldberg design has run reliably for roughly 18 months, but it illustrates how consumer smart-home ecosystems force absurd workarounds because they don’t interoperate. The setup is now threatened by Samsung’s plan to charge $4.99/month for personal SmartThings API access — a fee for storing a single boolean — which will push Ghaisas to re-engineer the pipeline yet again.