Bruh style RF Switches - Can't recieve their codes?

Configuration
1

Hi Everyone!
I’m back to try this again (I have the worst luck with HA it would seem…).

I’m trying to add my first proper bit of useful automation (besides Kodi + Weather to test it’s working), by using the tutorial from BruhAutomation here:

I followed it to the letter (at last I think I have, double and tripple checked).
But I just seem to be getting random codes through. Even if I don’t press any buttons on the remote.

I wanted to show exactly what’s happening so made a video:

(Only available via this link, it’s not public)

I welcome any ideas… At this point I’m begining to think i’ll have to buy a new transmitter/reciever kit… :frowning:

2

I followed the same tutorial amd I’m having the same issue.
I figured that the fact that it’s receiving data is a good thing, probably it’s picking up data from my weather stations (also 433 mhz).

I was trying to set it up for the Home Easy protocol, perhaps this protocol isn’t working with the tranciever I bought:
http://www.dx.com/nl/p/geeetech-superheterodyne-3400-wirelesss-receiver-433mhz-rf-transmitter-kit-green-370793#.WIe5EfnhBaQ

I expect to receive a couple of 433 mhz door sensors any day now, will try if that works.

3

Put the transmitter within a few inches when you are trying to get the codes. Since you are getting codes Im guessing you have it wired correctly. I found that multiple presses (think 10 not 2 or 3) will give you a bunch of readings and you can figure out the consistent code that pops up.

The range of the receiver seems to be weak although it will pick up other local signals and that noise can be confusing unless you have a bunch of repeated presses.

4

I tried holding it around 2 inches away and still got a load of rubbish through with some sensible looking codes (but as they didn’t repeat when I was pressing the same buttons I guessed it was just more noise).
When you say 10times rather than 2, do you neet to hammer it 10 times quickly? or 10 1 second long presses with a break inbetween?

I just had a thought that I could try disconnecting the transmitter while I’m trying to get the codes? Maybe that would help?
I can’t think of any other 433mhz sources in the house though, unless my neighbour has something that fires random codes at random times?

I’m so sad I can’t get this going though. I happened across Bruh-Automation’s video a while back (months now) and I’m still unable to get it working…although this is definately the closest I’ve gotten!

5

10 or so times rather quickly. You won’t get the same code over and over, however, for me when i looked for a pattern the one that showed up the most was what worked.

6

Ahhhhh! I was expecting to see the same code sent over time and time again! Thanks for that little insight!

I wont be able to try it again now until tomorrow because I’m driving my wife crazy running upstairs all of the time and turning the lights on and off constantly…

Do you think it’s worth disconnecting the transmitter until the codes are learnt?

7

Its actually pretty normal that (cheap) 433 receivers which are not shielded or used without a low pass filter (LPF) catch quiet a lot of noise.

Otherwise you have to try to identify patterns and find your device code and keep on testing.

8

You might not see the exact same code, but you should see the same code piping up frequently.

I did all my config while the transmitter was connected. I don’t see why it needs to be removed, it is inactive unless its sent a code to transmit.

9

btw: My 433 infrastructure (sender and receiver) is build upon the pilight component and I created a LPF for the receiver. That works quiet good.

10

That sounds interesting, however being a complete novice to Python, Linux and DIY Electronics I think it may be best for me to get a better quality transmitter/reciever set if it comes to needing to buy something.

11

I also tried that but was unable to get any proper code. Then i used this method - https://www.samkear.com/hardware/control-power-outlets-wirelessly-raspberry-pi and all is working great. Got the codes but then switching for HA took 3-4 click just to turn it on and off, Then i changed the method and use command line -

- platform: command_line                                                                    
  switches:                                                                                   
    camera:                                                                                
      command_on: "/var/www/rfoutlet/codesend 42xxxx"                                               
      command_off: "/var/www/rfoutlet/codesend 42xxxx"

All working great now

12

Thats Great!
So, being a newbie… I only need to do Step 6 is it?
Or would I also need to do Step 2?
And do I punch in the terminal codes as is? or will I need to adjust them for my install?
(It’s a fresh install done using the Rasp Pi image install)

13

Check the link provided above it has complete write up to connect the rf t raspberry and test them from console by sending command. If all that work you can just use command line,

14

Hi, I have had a look through. However, like I said being a newbie to Linux, HA, Python, Terminal, Everything… I’m struggling.

For example:

[quote]The source files for the software can be pulled using git.

git clone git://git.drogon.net/wiringPi[/quote]
I get a “-bash: git: command not found” error.
Is this because I to make a second SD card just to do the signal sniffing with, then once I have these from that SD card, add them to my HA image on my current card?

He also says:

Having never used GitHub before I’ve no idea how to “pull” it down, what format I should pull it down as, and what I need to do with it to get it into a workable state for the Pi.

Thank you for pointing me in this direction though so far.

15

UPDATE!
I read up on Git for the Pi.
Got that all working, followed the entire tutorial, got down to where you run the script to sniff the codes and got no output at all.
I re-ran the Python code from the Bruh tutorial and got my normal output of nonsense noise (it also seems to stop recieving codes after a minute or two). So I think its the cheap reciever.
I’ve ordered a second cheap reciever/transmitter set as well as a new seperate shielded RXB6 Superheterodyne reciever. (All three only cost £7 including postage so figured it was worth a try!)

16

I am having the same problem, I have put a scope on the data output pin of the RX and I am getting just constant square waves out around 7.2kHz. If I put the buttons on the remote I can see the wave shape moving.

I was expecting only to get pulses out when a button was pressed. I have ordered another receiver.

Does anybody know if there should be a constant output from the RX

Will report back

17

Got the new reciever today.
Managed to sniff the codes well! :grinning:
(The bruh tutorial gave me one set of codes (with messy codes inbetween) and the one linked to above gave a completely seperate set of codes…Not sure what’s up with that…)

Tried using these codes. Nothing.

Re-checked the wiring. Nothing.

Moved the switches into the same room for testing in case of a weak signal. Nothing.

Tried using the guidance above to send via a command. Nothing.

Tried limiting my tests to just 1 plug to get me started, edited the config to do this, hit the home assistant restart option… Nothing.

18

maybe post your config here so we can check it?

19

I’ve got it showing up in the frontend just fine. but I hit the switch and nothing happens.
I’ve also tried using the code from the tutorial in the link further down in this thread to turn off the test switch:

/var/www/rfoutlet/codesend 9435659

With no joy…

Config is below:

# RF Switches
switch:
  platform: rpi_rf
  gpio: 17
  switches:
    Charger:
      protocol: 3
      pulselength: 78
      code_on: 9435651
      code_off: 9435659
      signal_repetitions: 15

Pulselength seemed to change between 77 to 86, but most were between 77 and 79 hence going for 78.

20

And now after restarting home assistant from the front end It’s not starting again and I cant SSH in…
Yey… :unamused:

Any tips on how to get this thing running again?
(I have turned it off and back on again btw)

The pi clearly isnt booting as its currently sat there with the red light on with no yellow…