IR Remote Transforms to RF

Most consumer remote controls operate using infrared light. This works well assuming the piece of equipment has a line of sight to the remote. But if you have, say a receiver in a cabinet or closet, the IR remote signal can't reach the sensor. Some equipment has remote receivers that you can leave poking out, but it is still not very handy. That's why some equipment now uses RF remotes. [Xtropie] used a pair of inexpensive 433 MHz RF modules to convert an IR system to RF. You can see a short video about the project below.

We might have been tempted to simply put an IR LED on the receiver so it could feed IR into the device sensor, but [Xtropie] took a different approach. He found the IR sensor and tied the RF receiver directly into its output. It seems to work, but we probably would have removed the IR sensor to make sure there were no conflicts.

In fact, if you removed the sensor, you could reuse it and connect it to the IR transmitter. It wasn't clear how you could easily package the RF transmitter and the remote. But it struck us that you could wire the transmitter directly to the LED output and avoid the IR sensor at all. If there isn't space in the remote case, maybe a 3D printed extension would do the trick.

Of course, nothing stops you from using RF remotes with your own projects. Of course, another way to go RF remote is to leverage WiFi.

#mischacks #ir #remote #rf #rfremote #rfremotecontrol

Reusing Proprietary Wireless Sockets Without Wireless Hacking

Bending various proprietary devices to our will is a hacker's rite of passage. When it comes to proprietary wall sockets, we'd often reverse-engineer and emulate their protocol - but you can absolutely take a shortcut and, like [oaox], spoof the button presses on the original remote! Buttons on such remotes tend to be multiplexed and read as a key matrix (provided there's more than four of them), so you can't just pull one of the pads to ground and expect to not confuse the microcontroller inside the remote. While reading a key matrix, the controller will typically drive rows one-by-one and read column states, and a row or column driven externally will result in the code perceiving an entire group of keys as "pressed" - however, a digitally-driven "switch" doesn't have this issue!

One way to achieve this would be to use a transistor, but [oaox] played it safe and went for a 4066 analog multiplexer, which has a higher chance of working with any remote no matter the button configuration, for instance, even when the buttons are wired as part of a resistor network. As a bonus, the remote will still work, and you will still be able to use its buttons for the original purpose - as long as you keep your wiring job neat! When compared to reverse-engineering the protocol and using a wireless transmitter, this also has the benefit of being able to consistently work with even non-realtime devices like Raspberry Pi, and other devices that run an OS and aren't able to guarantee consistent operation when driving a cheap GPIO-operated RF transmitter.

In the past, we've seen people trying to tackle this exact issue, resorting to RF protocol hacking in the end. We've talked about analog multiplexers and switches in the past, if you'd like figure out more ways to apply them to solve your hacking problems! Taking projects like these as your starting point, it's not too far until you're able to replace the drift-y joysticks on your Nintendo Switch with touchpads!

#homehacks #wirelesshacks #analogswitch #hackadayio #homeautomation #reverseengineering #rfremotecontrol #smarthome #wirelessoutlet