It takes 5 cloud services to hear my doorbell · Bit Nebula
It takes 5 cloud services to hear my doorbell
It all started in the winter of 2024. There was a burglary in our apartment building and we decided we needed to invest in our home’s security. The …Bit Nebula
Zarxrax
in reply to diesisteinusername • • • Public Messageglimse
in reply to Zarxrax • • • Public MessageThere are downsides to consider...
There's options for decent-looking doorbell cameras without all the fuss. I use Amcrest, I know a lot of others use Reolink
MonkderVierte
in reply to glimse • • • Public MessageThey are the same picture meme.
glimse
in reply to MonkderVierte • • • Public Messagedoorbell camera next to a security camera photograph.
The psychological effect of a security camera (do I really need to clarify bullet and dome cameras?) is different than a doorbell camera.
pHr34kY
in reply to diesisteinusername • • • Public MessageI was tempted to run PoE to the other side of the wall where my server is. A doorbell that could do it all locally on my server.
Then I thought "fuck it" and bolted an antique brass bell there instead. At least you know it's working.
Crylos
in reply to diesisteinusername • • • Public MessageReolink for the win in my opinion.
Of course a nice brass bell as indicated would work too.
Carlos Solís
in reply to diesisteinusername • • Public Message
in reply to Carlos Solís • • • Public MessageCarlos Solís
• • Public Message
in reply to Carlos Solís • • • Public MessageCarlos Solís
• • Public Message
in reply to Carlos Solís • • • Public MessageCarlos Solís
• • Public Message
in reply to Carlos Solís • • • Public MessageIf your freezer is on your local wifi and your computer is also on the local wifi you should be able to see all the packets it is transmitting over the wifi with Wireshark on your computer. If either your computer or freezer has a hard connection then you'll need a little more trickery as switches/home routers minimise network congestion by directing traffic to specific MAC addresses as required.
Assuming you are all wifi, basically you load Wireshark (is free software, easily downloaded) and tell it to capture all packets from your wifi adaptor (there should be a handy option on the initial screen when you load the application). Once you start capturing you'll be capturing everything on your wifi so it pays to be quick with what you want to achieve to minimise the data.
So, once you start capturing you open your fridge door a few times, leave it open till it beeps, maybe do that twice, then stop capturing. Following that you will just need to filter the capture by all packets from your fridges network IP or MAC (you should be able to find these from your home router).
... Mostrar másIf your freezer is on your local wifi and your computer is also on the local wifi you should be able to see all the packets it is transmitting over the wifi with Wireshark on your computer. If either your computer or freezer has a hard connection then you'll need a little more trickery as switches/home routers minimise network congestion by directing traffic to specific MAC addresses as required.
Assuming you are all wifi, basically you load Wireshark (is free software, easily downloaded) and tell it to capture all packets from your wifi adaptor (there should be a handy option on the initial screen when you load the application). Once you start capturing you'll be capturing everything on your wifi so it pays to be quick with what you want to achieve to minimise the data.
So, once you start capturing you open your fridge door a few times, leave it open till it beeps, maybe do that twice, then stop capturing. Following that you will just need to filter the capture by all packets from your fridges network IP or MAC (you should be able to find these from your home router). Once you have all the packets you should be able to click on them and expand all the details to see what data they are sending and where it's being sent to. You should also see all the packets coming back from the vendor.
Carlos Solís
• • Public Message
in reply to Carlos Solís • • • Public MessageGhoelian
• • • Public Messagedream_weasel
in reply to Carlos Solís • • • Public Messagecenzorrll
in reply to dream_weasel • • • Public MessageLogi
in reply to cenzorrll • • • Public Messagecmnybo
in reply to Carlos Solís • • • Public MessageCarlos Solís
in reply to cmnybo • • Public Messagecmnybo
in reply to Carlos Solís • • • Public MessageNewNewAugustEast
in reply to Carlos Solís • • • Public MessageCarlos Solís
in reply to NewNewAugustEast • • Public MessageNewNewAugustEast
in reply to Carlos Solís • • • Public MessageCarlos Solís
in reply to NewNewAugustEast • • Public MessageWhyJiffie
in reply to Carlos Solís • • • Public MessageCarlos Solís
in reply to WhyJiffie • • Public Messageczardestructo
in reply to diesisteinusername • • • Public MessageStentor | Nicholas Lekatsas
www.lekatsas.usMonkderVierte
in reply to czardestructo • • • Public Messageczardestructo
in reply to MonkderVierte • • • Public MessageGitHub - OliveTin/OliveTin: OliveTin gives safe and simple access to predefined shell commands from a web interface.
GitHubMonkderVierte
in reply to czardestructo • • • Public Messageczardestructo
in reply to MonkderVierte • • • Public MessageOh that's a silly question. Why not?
The honest answer is in the US all doorbells are powered by simple 24VAC transformers that burn 6–7 watts just being powered up, forever, for decades. This annoyed me plus I wanted a fun bell so I wired up a pi to use a modern, efficient 24VDC power supy to ring the bell and it gets turned on by the pi only when its needed so now my idle wattage is more like 0.25W.
RamRabbit
in reply to diesisteinusername • • • Public MessageNurgus
in reply to RamRabbit • • • Public MessageOP's purpose was video security, not doorbells. People pushing the button instead of knocking was an unintentional consequence.
Your 70s doorbell is not helpful.
JohnEdwa
in reply to Nurgus • • • Public MessageMy doorbell is a sign that says "Knock", because my 70's doorbell is broken. It requires 0 cloud services to fix the problem of people pressing an unhelpful button.
[EDIT] To people downvoting this, did you read the article? Specifically, this part:
He then goes on a tech bodgeathon to fix the button, instead of just placing a sing that says "Knock" to go back to the thing that worked before.
Nurgus
in reply to JohnEdwa • • • Public Messagezerofk
in reply to RamRabbit • • • Public MessageMonkderVierte
in reply to zerofk • • • Public MessageStrider
in reply to diesisteinusername • • • Public MessageApologies if someone is offended by the following. It's not meant as an offense, but a professional opinion about design and Implementation.
This is a really good example of absolutely not keeping it simple and utilizing so many dependencies you'd need to monitor to be sure your solution works that the overall design is just plain bad.
If you ever implement something and get caught in so many things, take a step back and think about how your goal could be achieved in a much simpler way or even if your requirements are that important in the first place.
Anyhow. 5c from a tech guy.
GottaHaveFaith
in reply to Strider • • • Public MessageMonkderVierte
in reply to Strider • • • Public Messageian
in reply to Strider • • • Public MessageThe whole digital landscape for users is a disaster. With separate silos, incompatible formats, information loss and slow, manual effort with no overview.
This is caused by big business land grabs and the total lack of information standards. A shameful state of IT to have in 2026.
WhyJiffie
in reply to ian • • • Public Messagewonderingwanderer
in reply to Strider • • • Public MessageHere's a simpler solution:
Wire an electric dinger to a power source via a momentary off-on switch, and have the button activate it when pushed.
It was already solved, it needed not be over-engineered to hell and back.
Ludicrous0251
in reply to diesisteinusername • • • Public MessagePetteriPano
in reply to Ludicrous0251 • • • Public MessageMunkisquisher
in reply to PetteriPano • • • Public MessagePetteriPano
in reply to diesisteinusername • • • Public MessageI have a wireless doorbell with a speaker that plugs in to an outlet.
I'd much like to replace it with a zigbee-button, but I've had issues finding a foolproof (wife-approved) zigbee thing to make the ding-dong-noise.
Munkisquisher
in reply to PetteriPano • • • Public MessageDouble them up, add an esp into the dingdong box, detecting the sound sent to the speaker or probe somewhere else in the circuit, or even use a small mic if you don't want to pull it apart.
Or it's probably a 433 mhz signal from the button, sniff that and basically you can have your own receiver
Munkisquisher
in reply to Munkisquisher • • • Public Messagethere's someone who's done the 433 mhz approach here community.home-assistant.io/t/433mhz-wireless-doorbell-monitor-on-an-esp/818738
or here reuben.science/posts/making-wifi-doorbell
Hacking my Wireless Doorbell
Reuben (reuben.science)billwashere
in reply to diesisteinusername • • • Public MessageHaraldvonBlauzahn
in reply to diesisteinusername • • • Public MessageThankfully, it takes still zero cloud services to make my breakfast, ride my bike, and open my door.
And you can bet on that I'll keep it that way.
anewfox
in reply to diesisteinusername • • • Public Messagenibbler
in reply to anewfox • • • Public Message