Home Automation: Simple Vs Easy

We’ve been talking a bunch of home automation on the Podcast lately, and this week, in the Mailbag segment, a reader asked us about our setups. Neither Kristina nor I are poster children for the home automation movement: she has absolutely no smart anything because she didn’t want her data up in “the cloud”, and I have an entirely local system that’s really nothing more than a bunch of ad-hoc scripts that talk to an MQTT broker, everything fully DIY but held together with metaphorical duct tape. Neither of us are doing it right, but we’re doing it wrong in interestingly different ways.

Kristina thought, probably because of the range of commercial devices out there that tie you into using their remote data storage services, that giving up control of her data was necessary to use it. And it might be, if you insist that setting up the system be as easy as possible. But the tradeoff for this ease is a drastic reduction in simplicity. You shouldn’t need a remote server in some foreign country to turn your lights on and off. Adding “the cloud” into the mix brings a lot of complexity, mostly in the form of servers that have to be paid for somehow by whatever company is providing the service. It needs to be secure. You might even have to create accounts, remember passwords, and manage that whole deal. Sure, that’s easy enough, but it’s a lot of moving parts, and you can’t blame her for rejecting that complexity.

My system is hosted on a now-ancient OrangePi in the corner, and the network in question is an old WiFi router that it sits on. Nothing needs to leave my four walls, but actually some of it does – I bridge some of the MQTT topics out to an external server for my own amusement. There is no protocol, and no real “system” frankly. Each device in the network has its own topic, and I’m responsible for knowing what it means. The thermometer in the basement has an ESP8266 that transmits on the home/basement/temperature topic, and it puts out its temperature in degrees Celsius. It was the simplest system I could think of, but I have to write whatever software I want to log, display, or act on the data. Of course, that’s simple if you can write some four-liner scripts on the OrangePi broker, but it’s not easy enough that my wife wants to hack on it.

So if the full-buy-in commercial systems are easy but overly complex, and my DIY network is transparently simple but requires a level of hands-on that isn’t easy for “normies”, is there a middle ground? I know half of you are already screaming Home Assistant or Domoticz, and you’re also thinking of which client device libraries you like the most for all your DIY applications: ESPHome vs Tasmota, for instance. And you’re all right!

We are living the in the golden age of the home automation projects. Open-source software and firmware, combined with an abundance of online tutorials and worked examples, have made huge strides toward bridging the gap between simplicity and ease of use. You can set up a hub for everything on a single-board computer, upload the software of your choice, and you don’t need the complexity or loss-of-support liability of a cloud provider. At the same time, setup is easy enough if you’re willing to roll up your sleeves a little bit, and when it’s not, chances are good that someone else has already figured it out for you. These days, interoperability with popular commercial products is shockingly easy to boot.

I need to spend some time and rationalize my system: given the state of the art, it’s simply too simple, and taking a step into an open-source solution would make it easier to use for the rest of the family, without overly complexifying things, adding sketchy dependencies, or losing our data sovereignty. I haven’t finished exploring my options yet, but from what I can see, the community has converged on some goldilocks setups: not too simple or too easy, but rather just right. Thanks, y’all!

Building A Ceiling-Based Crane Robot To Keep A Room Clean

One of the joys you get to experience whether as a proud parent or pet owner is that a lot of things get left around haphazardly. You could of course pick every piece of discarded clothing, half-destroyed toy and detritus yourself, but as a parent of three children himself [Nathaniel Nifong] opted to use his engineering background to potentially over engineer a wires-suspended robotic claw to do this picking up for him.

What he calls Stringman robots requires an anchoring point at four corners of a room, after which the robotic crane can then scour across the ceiling, identify targets to pick up and move these to predesignated drop-off points. It’s an open source project with the LeRobot-based firmware available on GitHub in addition to build instructions for the physical hardware. There’s also a pilot run of ready to use hardware and kits for those who want to trial it, but aren’t interested in building it themselves via [Nathaniel]’s company website.

The basic idea is that this crane can run for an hour or so and deal with the mess in its room without having to do anything yourself. The process isn’t perfect yet, of course, with the underlying diffusion transformer to implement machine vision requiring more refinement. The gripper itself struggles with objects like books, which can be a concern for parents and bookworms, and of course while the crane is operating the wires will dip down as a potential risk to anyone in the room.

Compared to an overhead crane like a traditional bridge crane this wire-suspension crane is probably more stable, but either is an interesting engineering challenge when applied to a household. Next it would probably also be cool if items could be put away where they belong instead of dropped into a bin, as so far that task will still be left to deal with by the adult humans.

Continue reading “Building A Ceiling-Based Crane Robot To Keep A Room Clean”

3D Printed Hose Sprayer Sets Phasers To Suds

The weather is warming up, and for many of us that means more time spent working out in the yard. You probably won’t find any new life or new civilizations out there, but if you’ve spent the last few months indoors on your computer, the garden may as well be a strange new world. In that case, you’d do well to equip the members of your landing party with this Star Trek: The Original Series hose sprayer designed by [Curt Turner].

If you’re wondering how [Curt] managed to 3D print a functional hose sprayer, the short answer is that he didn’t. Once assembled, the printed parts cleverly attach to the top of a standard sprayer, specifically the model 56516 “Pro Flo” from Orbit. Without the design constraints that would have come from trying to make the thing actually contain pressurized water, [Curt] was free to focus on the aesthetics, and it shows.

Even with a garden variety — no pun intended — sprayer strapped to the bottom, it’s remarkable how much the “Sprayser” looks like the real thing. Well, not real, but you know what we mean.

[Curt] has also done an excellent job documenting this project for others that want to imagine they’re fighting off Romulans in their backyard. He’s got assembly diagrams that break down which color each of the principle components is to be printed in, as well as a build video that we’ve embedded below.

We’ve seen a fair number of Star Trek props built over the years, some of which have packed in considerably more functionality than anything they would have had back on the set. These days you can even by an officially licensed tricorder that can actually do some of the things the fictional versions were capable of.

Continue reading “3D Printed Hose Sprayer Sets Phasers To Suds”

Medication Reminder Uses Only One Button

As anyone who takes medicines regularly will attest to, the days have a tendency to blur together, making it hard to remember if you did something like take that day’s dose or not. There are plenty of products available to help keep track of medication reminders but many are overly complicated, so [Jeroen] built this one which keeps simplicity and usability as its core design principle.

[Jeroen] calls it the MedMinder, and it’s a small, compact, rectangular device with a four-character display meant to sit on a countertop. When it’s time to take a medicine, the display will show that medicine’s four-letter code until the user pushes the single button under the display, signalling that they’ve taken their dose. If many different medications have to be taken at the same time, it displays the first priority until the button is pushed, and then displays whichever one is next after that.

Programming is a little less straightforward, as the medications need to be added to the source code and uploaded to the Arduino that sits at the center of this build, but with the source code available this isn’t too difficult for someone with minimal experience with microcontrollers.

In an idealized world, technology should make our lives simpler or easier, and this small device goes a long way towards helping with that goal. Especially for an important but mundane task that can be surprisingly easy to lose track of. Although we glossed over the accuracy of this device’s clock in this article, we do have a comprehensive guide for selecting the right real-time clock for microcontrollers like this.

Why The Smart Home Bubble Popped

Circa 2015 or so, it seemed like you couldn’t move a finger without being bombarded with ads and articles about ‘smart homes’ and the ‘internet of things’ — all of which would make our lives so much easier and more automated. Fast-forward a decade and this dream has mostly evaporated along with many of the players in the space. Why this happened is the topic of a recent video by [Caya].

An interesting bit of context that the video starts off with is that home automation really kicked off back in 1975, when the X10 protocol and related devices using power lines for signaling began being sold. These fully integrated solutions generally worked reasonably well, but what all changed when the IoT and ‘smart home’ craze kicked off and brought with it an explosion of new standards.

Over the past decade we have seen the concept of a ‘smart home’ collapse into a nightmare of abandoned IoT devices, subscription services, forced ads, privacy violations, and an increasingly more congested 2.4 GHz spectrum that everything from WiFi and Zigbee to Bluetooth and others ended up competing for, with a corresponding collapse in reliability of data transmissions.

As raised in the video, a big issue is that of the financial viability of running the remote services for a smart home solution, even if this is the part that should make it as plug-and-play as a 1990s-era smart home solution. To the average user setting up their own locally hosted smart home solution isn’t really a straightforward option.

Although at the end [Caya] demonstrates using Home Assistant (HA) as a locally hosted alternative, this is still not something that a non-techie will be able to set up or maintain. Even if you shell out a cool two-hundred clams for the Home Assistant Green plug-and-play hardware solution, the average person will be lost the second any of the prescribed steps in provided documentation do not work. Woe to whoever is the person who is ‘good with computers’ in those cases.

Ultimately another problem with ‘smart homes’ is that they’re really not that smart, as you can definitely set up all kinds of rules in HA and similar solutions, but this is more painstaking manual automation with all the excitement of programming PID controllers. Having an actual intelligence behind the system that could react to what’s happening would make it a far easier sell, yet which is where all the ‘smart assistants’ like Alexa keep falling flat.

Currently [Caya] has set up his HA-based lighting configuration to be used by OpenClaw ‘agentic AI’, as a way to add some actual ‘smarts’, but it’s telling that he hasn’t integrated the smart lock of his apartment into the system yet. Nobody wants to have the OpenClaw agent tell you that it ‘cannot open the front door’ for you, after all.

Continue reading “Why The Smart Home Bubble Popped”

DecayDock Keeps Track Of Spoilage

Many of us have suffered the common experience of buying a great deal of (now very expensive) food, only to have it go off before it can be consumed. [ptallthings93] has whipped up a simple device to try and tackle this problem.

The result is DecayDock, which lives on a fridge and tries to keep track of what’s going on inside. It achieves this with the use of an ESP32-CAM module, which combines the capable microcontroller with a camera for image detection work. With the aid of an Edge AI model, it’s able to detect common food items that are held in front of the camera, which are in turn added to an internal inventory. The items are tracked over time based on expected shelf lives, and the freshness of various items in the fridge is displayed on an attached LCD screen with a green/yellow/red color coding system.

The system is only making estimates—it’s not able to actually identify when the cheese has gone moldy or the milk has gone sour. Still, if you struggle to remember what you should be prioritizing to use in your fridge, it might be a handy aid.

Ultimately, we never really saw smart fridges dominate the market, even though the idea has long been a popular one in futurist circles. Perhaps none of them thought that nobody really wants to stand staring down at a screen on the fridge all day. In reality, some areas of the home are best left unsmartified.

Automating Window Shades With Home Assistant

Most people love window shades, but many dislike the tedium of having to open and close them over the course of each day. While there are automation options here, if you’re in a rental place like [Rooster Robotics], then you’d prefer something less intrusive, as well as less cloud-bound. This is basically why he opted to build his own solution from scratch to open and close roller shades via Home Assistant.

The comments to the video helpfully point out that technically his point about there not being commercial options with a forced remote account ‘feature’ is false, as the Aqara Roller Shade Driver E1 for example is just a regular Zigbee device which can be used with a wide range of home automation ecosystems. That said, it’s always nice to have your own device that you fully control.

Of course, these devices are deceptively simple, as you still have to somehow know how far open the curtain is, which is also useful if you just want to open the curtain a certain amount. The other issue is the need to have the motor parallel with the wall unless you enjoy having a big wart sticking out from the wall.

Solving the first issue was attempted with a Hall effect sensor, and the second with angled gearing. With some refinements this led to a functioning design, allowing the development of a custom PCB with an ESP32-S3 module for WiFi control. In the final design the Hall effect sensor and magnets were replaced with an AS5600 magnetic rotatory position sensor that requires just one magnet and offers a much higher resolution.

Currently the design files are not available, but [Rooster Robotics] has indicated that they are looking at open sourcing the files in the future.

Continue reading “Automating Window Shades With Home Assistant”