If you’re working on a home automation project, you’re probably knee-deep into MQTT by now. If not, you should be. The lightweight messaging protocol is an ideal choice for getting your “Things” on the Internet, and controlling them all can be done easily through a simple web interface or an application on your mobile device. Or if you’re [serverframework], you make yourself a handsome little all-in-one MQTT remote.
The hardware here is pretty simple; inside there’s just a NodeMCU ESP8266 development board, some buttons, an RGB LED to give feedback, and a 3.7v 1200mAh LiPo battery with associated charging module. Everything is held inside a nice little wooden box that looks like it would fit right in with the living room decor. We’d like to see some kind of a cover over the exposed perfboard the circuit is assembled on, but that’s arguably a personal preference kind of thing.
Most of the magic in this project is actually happening on the software side. Not only does the provided source code handle all the MQTT communications with Home Assistant, but it provides a clever user interface that allows [serverframework] to perform 25 functions with just five buttons. No, you aren’t seeing things. There are actually six buttons on the device, but one of them is a dedicated “power” button that wakes the remote out of deep sleep.
If you’d like to learn more about getting this protocol working for you, our resident MQTT guru [Elliot Williams] has plenty of thoughts on the subject. From his talk at the 2017 Hackaday Supercon to his home automation tutorial series, there’s plenty of information to get you started.
Continue reading “Handheld MQTT Remote For Home Automation”
Ever make something just to see if you could? Yeah, we thought so. [serverframework] wanted to see if he could clone the remote that opens his neighborhood gate, inspired by the long distance ding-dong-ditch efforts of [Samy Kamkar].
This clone uses an ATtiny85 and an RF module to emulate and send the frequency that the gate is waiting for. To accomplish that, [serverframework] had to figure out both the operating frequency and the timing used by the remote. The crystal inside seemed to indicate 295 MHz, and a quick check of the device’s FCC registration confirmed it. Then he used an SDR dongle to watch the data coming across when he pressed the button, and ran it through Audacity to figure out the timing.
Unfortunately, the 295 MHz crystal is a rare beast, so [serverframework] had to transplant the original to the donor RF module. Then it was just a matter of programming the ATtiny85 to send the frequency with the right timing. It actually does a better job since the original has no timing crystal, and the ‘tiny is clocked with a standard 16 kHz oscillator. The code is available within [serverframework]’s excellent write-up, and you can see a tiny demo after the break.
There’s more than one way to clone a gate remote. This one leverages MQTT to turn friends’ phones into remotes.
Continue reading “Cloned Gate Remote Does It (Slightly) Better”
Sometimes you build a computer and use it every day. Sometimes you build a different type of computer and it sits alone on a mountaintop for years. The design considerations for these two setups are remarkably different, right down to the type of file system used. For small computers like [Jo] is using, and for the amount of time they sit alone in remote locations, he decided to build his own file system for them.
Known as JesFs ([Jo]’s embedded serial File system), the file system is for SPI Flash and intended for use in scientific data logging. It can be used on the chip-scale processors found in many development boards, and is robust enough to use in applications where remoteness is a concern. It has a small RAM footprint, is completely open source, includes wear leveling, and has a number of security features built-in as well.
Some of the benefits of using a file system on such a tiny chip aren’t immediately obvious unless you’re doing a lot of data logging, but it does allow you to change virtually any aspect of the firmware much more easily if everything is accessible as a file, and not something you would have to change by reflashing the whole chip, for example. There are also a number of traps that you can easily fall into when working with file systems for tiny devices.
Thanks to the wonders of the internet, collaborating with others across great distances has become pretty simple. It’s easy now to share computer desktops over a network connection, and even take control of another person’s computer if the need arises. But these graphical tools are often overkill, especially if all we really need is to share a terminal session with someone else over a network.
A new project from [Elis] allows just that: to share an active terminal session over a web browser for anyone else to view. The browser accesses a “secret” URL which grants access to the terminal via a tunnel which is able to live stream the entire session. The server end takes care of all of the work of generating this URL, and it is encrypted with TLS and HTTPS. It also allows for remote control as well as viewing, so it is exceptionally well-featured for being simple and easy to run.
To run this software only a binary is needed, but [Elis] has also made the source code available. Currently he finds it a much more convenient way of administering his Raspberry Pi, but we can see a lot of use for this beyond the occasional headless server. Certainly this makes remote administration easy, but could be used collaboratively among a large group of people as well.
Kids spend too much time in front of a screen these days. They also won’t get off my lawn, and music today is just a bunch of static. They don’t respect their elders, either. While kids today are terrible, we can fix that first problem — sitting in front of a screen all day. For his Hackaday Prize entry, [Donovan] has created a device that optimizes screen time to reduce sensory overload. It’s the Optimote, the combination of a remote control and biofeedback.
The idea behind the Optimote is to actually to reduce stimulation when watching something on a screen. For many people, including people on the autism spectrum, watching TV or YouTube videos can often result in debilitating sensory overload. You can’t relax in this state, you can’t learn, and you certainly can’t get any entertainment value out of the glowing rectangle in front of your face.
The Optimote uses a pulse sensor, an Arduino, an incredible break-away cable that seems to be missing from any other wearable device like this, and a software stack that interacts with VLC. During periods of high pulse rate, the video skips to low-intensity footage. There’s a ‘calm’ mode that puts media volume and tempo in sync with heart rate. The ‘thrill’ mode plays an eerie scene looping with the Jaws theme.
So far, the prototype is a success, and [Donovan] is looking forward to large-scale user experience testing to determine how effective and enjoyable this technology can become.
In the very late 1990s, something amazing was invented. White LEDs. These magical pieces of semiconductors first became commercially available in 1996, and by the early 2000s, you could buy a single 5mm white LED for less than a dollar in quantity one. A year or two later, an astonishing product showed up on infomercials airing on basic cable at 2 a.m. It was a flashlight that never needed batteries. With a small white LED, a few coils wrapped around a tube, and a magnet, you could just shake this flashlight to charge it. It’s just what you needed for when the Y2K virus killed all electronics.
Of course, no one uses these flashlights now because they suck. The early white LEDs never put out enough light, and charging a flashlight by shaking it every twenty seconds is annoying. There is another technology that desperately needs a battery-less solution, though: remote controls. They hardly use any power at all. That’s exactly what [oneohm] did for his Hackaday Prize entry. He created the Undead Remote.
The dream of a battery-less remote control has been dead since your parents got rid of that old Zenith Space Command, but here it is. This is really just a shake flashlight, a diode rectifier, a large capacitor, and some glue. Shake the remote, and you can change the channel. Is it useful? Certainly. Does it look weird and is it slightly inconvenient? Also yes. But there you go. If you want an easy way to deal with batteries in your remote control, this is a solution.
There’s no limit to the amount of work some people will put into avoiding work. For instance, why bother to get up from your YouTube-induced vegetative state to adjust the volume when you can design and build a remote to do it for you?
Loath to interrupt his PC streaming binge sessions, [miroslavus] decided to take matters into his own hands. When a commercially available wireless keyboard proved simultaneously overkill for the job and comically non-ergonomic, he decided to build a custom streaming remote. His recent microswitch encoder is prominently featured and provides scrolling control for volume and menu functions, and dedicated buttons are provided for play controls. The device reconfigures at the click of a switch to support Netflix, which like YouTube is controlled by sending keystrokes to the PC through a matching receiver. It’s a really thoughtful design, and we’re sure the effort [miroslavus] put into this will be well worth the dozens of calories it’ll save in the coming years.
A 3D-printed DIY remote is neat, but don’t forget that printing can also save a dog-chewed remote and win the Repairs You Can Print contest.
Continue reading “High-Effort Streaming Remote For Low-Effort Bingeing”