I am super sensitive to over engineering. For my doorbell I wanted something that lets me play a custom bell sound. You would be surprised that 99% of the solutions out there are complete over engineered stacks that depend on wifi devices, Internet access, connecting to various cloud services... So I built my own: a basic wireless button sends a radio 433 MHz signal, and my receiver is plugged inside the house and triggers an off-the-shelf playback PCB module that reads an MP3 off an SD card and plays it on a speaker wired to the module. No Wifi, no Internet, no cloud, no apps. And the rare times I want to change the sound, I update the MP3 on the SD card.
artisinal
I fail to see the relation between a video doorbell and stopping a burglar. Burglars wear masks.
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.
show comments
VladVladikoff
I’ve recently been looking into what older gen IoT devices I can buy used for cheap and are also hackable (some existing progress has been done before me is my bar).
My first adventure was with an Amazon Echo Dot 2, I picked up two off Facebook marketplace for $5 each and managed to vibe code my way into a working implementation of LibreEcho (which does not currently support the echo dot). I’ve got that wired into my home local AI brain so it can do tasks like add grocery items to shared notes, or download movies or TV shows (jellyseer+flexget+jellyfin+etc).
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!
disillusioned
So... you already owned Google Home minis... why not buy Google's Nest doorbell, which rings every Google Home device out of the box with none of the absurdity? If you have a Google 4k TV Streamer, it even pops up on your TV when someone rings the doorbell...
show comments
johnhtodd
I am constantly amazed that people rely on anyone else's compute infrastructure for things like doorbells, cameras, locks, switches, or sensors (network infrastructure is, at the moment, a seemingly acceptable integration for isolated communication.) There is inevitable over-pricing and capture by these companies; it's in their nature.
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."
stickfigure
The interesting thing here is that Samsung thinks they are going to get people to pay for API access to their smart devices, when "app access" is free. We are now past the point where LLMs can automate the apps. You don't even need to write the code, the LLM will do it for you.
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.
show comments
tehlike
Reolink poe+frigate
vghaisas
I thought it was finally time to write up the story of my absurd home doorbell implementation, especially because the upcoming Samsung SmartThings API pricing means things will have to change soon.
Suggestions welcome!
show comments
Banditoz
It's crazy these things don't have much interopability with third parties.
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.
show comments
tamimio
>an over engineered
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.
show comments
addag
Peak Home Alone behavior right here.
wonnage
Not sure if Blink is more locked down but Ring works alright with just Homebridge + HomePods
senectus1
this is one reason I haven't replaced my aging eufy stuff.
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.
jimt1234
> ...then it would also helpfully play a sound on the doorbell...which we could not hear.
Sounds like a feature more than a bug.
t098i3
I take it the house wasn't wired for a traditional doorbell and you didn't want to drill the necessary holes in the doorframe and wall?
I am super sensitive to over engineering. For my doorbell I wanted something that lets me play a custom bell sound. You would be surprised that 99% of the solutions out there are complete over engineered stacks that depend on wifi devices, Internet access, connecting to various cloud services... So I built my own: a basic wireless button sends a radio 433 MHz signal, and my receiver is plugged inside the house and triggers an off-the-shelf playback PCB module that reads an MP3 off an SD card and plays it on a speaker wired to the module. No Wifi, no Internet, no cloud, no apps. And the rare times I want to change the sound, I update the MP3 on the SD card.
I fail to see the relation between a video doorbell and stopping a burglar. Burglars wear masks.
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.
I’ve recently been looking into what older gen IoT devices I can buy used for cheap and are also hackable (some existing progress has been done before me is my bar). My first adventure was with an Amazon Echo Dot 2, I picked up two off Facebook marketplace for $5 each and managed to vibe code my way into a working implementation of LibreEcho (which does not currently support the echo dot). I’ve got that wired into my home local AI brain so it can do tasks like add grocery items to shared notes, or download movies or TV shows (jellyseer+flexget+jellyfin+etc).
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!
So... you already owned Google Home minis... why not buy Google's Nest doorbell, which rings every Google Home device out of the box with none of the absurdity? If you have a Google 4k TV Streamer, it even pops up on your TV when someone rings the doorbell...
I am constantly amazed that people rely on anyone else's compute infrastructure for things like doorbells, cameras, locks, switches, or sensors (network infrastructure is, at the moment, a seemingly acceptable integration for isolated communication.) There is inevitable over-pricing and capture by these companies; it's in their nature.
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."
The interesting thing here is that Samsung thinks they are going to get people to pay for API access to their smart devices, when "app access" is free. We are now past the point where LLMs can automate the apps. You don't even need to write the code, the LLM will do it for you.
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.
Reolink poe+frigate
I thought it was finally time to write up the story of my absurd home doorbell implementation, especially because the upcoming Samsung SmartThings API pricing means things will have to change soon.
Suggestions welcome!
It's crazy these things don't have much interopability with third parties.
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.
>an over engineered
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.
Peak Home Alone behavior right here.
Not sure if Blink is more locked down but Ring works alright with just Homebridge + HomePods
this is one reason I haven't replaced my aging eufy stuff.
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.
> ...then it would also helpfully play a sound on the doorbell...which we could not hear.
Sounds like a feature more than a bug.
I take it the house wasn't wired for a traditional doorbell and you didn't want to drill the necessary holes in the doorframe and wall?