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.
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!
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.
I'll have to check the latency of my 'smart' doorbell now. I have occasionally heard the doorbell, taken the obligatory time to find the key to unlock the door to find that it was just a package delivery, but enough time had passed that the courier was nowhere to be seen.
(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).
We have a Ring doorbell that hooks into the actual chime that the old doorbell used, so it still preserves the old doorbell's functionality[1]. I can understand not wanting to buy into the Ring ecosystem (we started using them before they were bought by Amazon), but maybe there are cheaper doorbells that also do that? All we had to do to make the old chime work with the Ring doorbell was install an extra widget that came with the Ring doorbell inside the chime; the Ring doorbell's instructions explained how to do it. It just needed a screwdriver and a few minutes' work.
[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.
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.
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!
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!
I'll have to check the latency of my 'smart' doorbell now. I have occasionally heard the doorbell, taken the obligatory time to find the key to unlock the door to find that it was just a package delivery, but enough time had passed that the courier was nowhere to be seen.
(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).
We have a Ring doorbell that hooks into the actual chime that the old doorbell used, so it still preserves the old doorbell's functionality[1]. I can understand not wanting to buy into the Ring ecosystem (we started using them before they were bought by Amazon), but maybe there are cheaper doorbells that also do that? All we had to do to make the old chime work with the Ring doorbell was install an extra widget that came with the Ring doorbell inside the chime; the Ring doorbell's instructions explained how to do it. It just needed a screwdriver and a few minutes' work.
[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.