So I followed the tutorial video from @brusc (Thanks Ben!!) on youtube , but I can’t get the RF transmitter to switch the outlet on/off.
At first I could not get the service to show up, and in my log I found “RuntimeError: No access to /dev/mem. Try running as root!” after some research here I found running the line “sudo adduser hass gpio” in putty did the trick, now I have no errors in my log, and I see the switch on my dash, but when I click it nothing happens (I have the outlet right net to the ant)…
Something I did notice is when I ran the rfrx.py script, then turned the switch on and off via HA, it did pick up a the same on/off codes from the remote, but the pulse length was ~353 where as the pulse length on the remote was 181.
Here is the putty logs of what I was getting from the rfrx.py script
I am not sure where to go from here, since I see the switch and I am not getting any other errors, I am guessing it something on the hardware set up side (confirmed the codes and wires to gpio are correct)…Any other troubleshooting tips? Thanks!!
So I got the better Superheterodyne transmitter in the mail today thinking it may have been acting funky bc I got the cheaper one, but still have no luck.
I still think its weird that when I am running the script and listening to the signals from the remote, the pulselength is different, than when I listening to HA and clicking the “On/Off” switch on my dashboard. Is this normal for it to look so different and to be all over the place? (Really if anyone could check theirs that would be greeaatttt)
Also is it normal for the pulselength to somethings change? While listening to the remote, I get 181 mostly, but sometimes I get a 180,183 or 185.
Any help with this would be greatly appreciated, with out this working I don’t have much to automate
Just adding some additional information for you (the thread is old so you may have solved this already). I think it’s pretty normal to get different pulse lengths. In fact, your output listening to the remote is WAAAAY more consistent than mine. I get all sorts of values and pulselengths and even protocols. It may have to do with where it is situated. Mine is on my Pi with the ZWave stick next to it and under 4 monitors.
In any event, I just try to lock into the pulses that are around 189 and go with that. So far, I’ve had ok results. I’m currently fighting with a new batch of switches now that I got on ebay. not sure if it’s the switches or my configuration yet.
