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 refrig…
It takes 5 cloud services to hear my doorbell
61–70 of 282 posts
Re: It takes 5 cloud services to hear my doorbell
#62I 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 tr…
Over engineering is subjective / evolving. You could have bought a bell...
No because similar commercial products were either out of stock or not compatible with my AC voltage.
Re: It takes 5 cloud services to hear my doorbell
#63I 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 tr…
Re: It takes 5 cloud services to hear my doorbell
#64I 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 tr…
Over engineering is subjective / evolving. You could have bought a bell...
Over engineering is about the solution, not the requirement:
> I wanted something that lets me play a custom bell
Re: It takes 5 cloud services to hear my doorbell
#65Re: It takes 5 cloud services to hear my doorbell
#66I 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…
I couldn't find a front door camera I liked so I ended up building my own from parts.
Having worked for "the cloud" for years, I tell everyone I know, there is no cloud, there is only other people's hard drives.
Re: It takes 5 cloud services to hear my doorbell
#67I 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!
This is absurdity.
Re: It takes 5 cloud services to hear my doorbell
#68Re: It takes 5 cloud services to hear my doorbell
#69I 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 tr…
Over engineering is subjective / evolving. You could have bought a bell...
Granted maybe your requirements are ridiculous. But I also had cases where I DIYed a solution because the commercially available solutions all either didn't fulfil the requirements and/or had anti-features that ruled out their use. I haven't had any regret so far with these solutions, with some of these being active for over a decade.
There may be over engineering, but replacing a bought solution that needs to connect to the internet and someone else's computer to ring a bell with a simple 433MHz sender and a MP4-player module isn't that. Do you know what is required for a device to even connect to a WiFi? That alone is more complex than the whole system the user built here.
Re: It takes 5 cloud services to hear my doorbell
#70I guess $30 for what is effectively a glorified chime for your door is a bit much, but considering the time it probably took to put together this (kind of over-engineered) and the (presumably) monthly cost of the VPS, it makes more sense.
Also, I feel like something like MQTT or another message broker could simplify this significantly, making the whole VPS /state endpoint unnecessary, without exposing your home mini pc to the internet, since the mini pc would connect to the MQTT (I think HA actually has a built in mqtt integration? although you'll still need to make something to process the message once the MQTT gets it) and the SmartThings API would also (assuming the processing after the SmartThings API is hit is customizable in some form)