Also, a doorbell ringing on the outside of the door is not only silly but in case of an apartment complex highly annoying for your neighbors.
And make sure your neighbors like being monitored through your five services.
Personally I have a button outside my front door. It is connected with a copper wire to the other side of the door to a small device that sends out an audible notification. No cloud required.
With a video doorbell you can get notifications when a person enters your property. You can notify police or neighbors if it’s a stranger
Then you don’t need 5 cloud services and people can go back to knocking.
Same thing as DVR for analog surveillance cameras, just with eth (usually PoE) ports.
Cameras deter crime. Not ALL crime. Criminals aren’t stupid and will simply go burgle someone that isn’t recording.
People have been stealing things from stores which have had cctv for decades. Your premises are manifestly false.
CCTV doesn't work well when people feel like nobody is going to bother to check its footage (e.g. pocketing a $2 drink from a big-box department store). But when it comes to homes, there are much higher chances of captured footage being used and examined, so it may cause opportunistic burglars to look at other houses instead.
Just because something doesn’t work 100% of the time doesn’t mean it can’t be effective.
My next plan is to do a doorbell. I want it fully local only and I know there are providers who offer this brand new for $$$ but I love the idea of picking up cheap IoT devices and hacking them instead. My current candidate is EZVIZ DB1C but I haven’t bought it yet and definitely open to suggestions!
That said, the author might also consider installing an actual doorbell, which is a device their home should have had decades ago. You'll also want something to provide power to the Nest, so this is almost free.
Add to this the security and downtime risks, and the equation really doesn't look good. Equipment that is tied to someone else's cloud is an astonishingly bad idea, but everyone has their own immediate (or even long-term) reasons for ignoring advice. "You get what you deserve."
As a recent owner of a Samsung fridge, I'm really curious to know what the plan is here. The probability of me paying a monthly for my refrigerator is exactly zero.
Suggestions welcome!
(The actual doorbell button is still there too, so it's a crapshoot which one somebody decides to use in the first place. And yes, many video doorbells have a "chime adapter" to take care of this, but our house's doorbell wiring made them run in fear.)
[1] More precisely, we did until we moved to a manufactured home that did not even have a doorbell installed, after which I had to do some jiggering (now we have a Ring chime that the doorbell can talk to over the house's LAN). But the setup I describe above worked fine for a number of years in the house we were in before.
(Yours wasn't a latency issue though, what kind of latency do you get with your 5-cloud services chain?)
Also, interesting about the SmartThings API access moving to a subscription model: https://hackaday.com/2026/07/28/samsungs-smartthings-api-ter... (this link is in the article - the cost is only for third party usage, not if you're directly using the SmartThings app).
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.
People really need to touch grass.
Is it so difficult to expose a MQTT thing or some other random HTTP server, default off but configurable in some developer settings, that could be used to control the device/read state? It would certainly make the minority that is us power users happy.
However, those companies don’t make the kind of perpetual revenue that bring in capital, and the companies that make the devices that don’t make you pay for their service end up not lasting as long as those that do.
Sadly, it seems that the prudent business decision is to lock your customers into your ecosystem.
Generally ONVIF is the protocol one should be looking for in a camera, it indicates that the edge device can play ball with a central server (Frigate, Blue Iris, etc). Profile M specifies the metadata into external mqtt:
It’s not, that’s called a duct tape solution, which is the opposite of engineering, that’s poor design and bad practice, there are so many failure points and moving parts that it’s eminent it will fail. The engineering design should be reliable, simple, and efficient. Instead of that cluster chaos you made, you could have had a relay wired inside the bell that simultaneously trigger a normal and simple electric-based bell, so it works for you and the other person.
"look at what i can do with the assistance of an LLM"
shows an rube goldberg construction sure it works. but geez support and security is a nightmare.
next round of outdoor cams and doorbells are going to be wholly selfhosted.
if they live for another 9 months I'll have the budget for it.
Sounds like a feature more than a bug.