The Cheapest Tech – $6 DIY Internet of Things Smart Outlets



Hey guys!
What up! In this video, I’ll be showing you how to create your own $6 RF Smart Outlets that you can use to automate anything you can plug in. It’s sweet and honestly one of the best ways to get started automating stuff around your place. Let me know if you have any questions or comments. Happy to help how I can!
Cheers,
Ben

— Python Recieve Script —

— Random Notes —
If you setup your Pi in a virtual environment, you may need to run the command sudo adduser hass gpio to allow the Hass user account to access the GPIO pins!

Theoretically cutting the antenna header wire to 173mm allows for optimal transmission and receiving. Thanks Mack Goodman!

— The Tech I Use —

— Product Links —
Outlets:
Etekcity RF Outlets –

RF RX TX:
Header Wires –
Superheterodyne 433 RF RX TX –
Superheterodyne 433 RF RX TX (alternative) –

Favorite Pi Parts:
Raspberry Pi 3 –
Case –
SD Card –
Power Supply –
LIFX –
Aeotec Z-Stick Gen 5 –
NodeMCU ESP8266 Chip –

— Resources —
My Website –
Home Assistant –
Forum –
Chatroom –
GitHub –

20 Replies to “The Cheapest Tech – $6 DIY Internet of Things Smart Outlets”

  1. Steve Dinn

    I realize this video is like 2 years old, but I was wondering if this could work when HA is not actually running on the RPi.

    I run HA on an Ubuntu server that I use for a bunch of other stuff, but I would love to integrate RF control into my automations. I was thinking of buying a Pi Zero and the RF modules to run seperately, probably in a more central location tab my office closet. Is this workable in HA?

  2. sa müh

    @BRUH Automation, first of all thank you for your video. I recieved data for the very first time after trying pilight, fhem and many other readers. is there a possibility with you python script to recieve binary data? My Intertechno remote (ITLS-16) just send: [INFO] rsfx: 8 [pulselength 1658, protocol 4]
    [INFO] rsfx: 4 [pulselength 1658, protocol 4]
    [INFO] rsfx: 4 [pulselength 1696, protocol 4]

    the codes are quite short. isn't it? how can I interprete the protocol?

  3. Kellen Chase

    Been looking at z-wave components. Gonna play with this. Just trying to think around the security piece. No encryption. I guess that’s future proofing. Thanks for the video. I’ll check it out and probably go down a rabbit hole on your other videos if you’ve got similar content. 🙂

  4. Michael Henderson

    Thanks for the video. I have been using the Eteckcity outlets for several years, and now I can control them with my Pi3B+. I haven't tried to set up Home Assistant yet. Being a newbie to the programming world., it is a great success when anything works!

  5. james clift

    hello has anyone managed to get a sonoff bridge to work in home assistant for home security ie a small touch panel for a code and for 433 sensors to work with in home assistant to know the presence of someone in a room or windows open and to control the switches and blinds

  6. Enrico Icardi

    Followed your guide (and just bought different remote controls)…….and I have a problem:

    If i run
    `$ python3 rpi-rf_send -g 17 -t 3 -p 101 15194300`
    `2018-04-01 14:31:47 – [INFO] rpi-rf_send: 15194300 [protocol: 3, pulselength: 101]​` is the code I'm sending, BUT, this is what I receive:

    ​`2018-04-01 14:31:47 – [INFO] rpi-rf_receive: 15063220 [pulselength 521, protocol 5]`

    ​Playing around with pulselength I realised that any `pulselength < 140` with basically make me receive close-to-random stuff.
    If I use `pulselength > 140` things are fine, but I need to send `pulselength == 101`…

    Do you have any hints on what could be wrong here?

Leave a Reply

Your email address will not be published. Required fields are marked *