RPi RF Receiver addon

segepe · October 17, 2018, 2:19pm

Many updates , but no one interested in this problem ?
Or do someone have a solution to this ?

Updated to latest HassOS, but thinking of downgrading

joeflan · October 17, 2018, 3:13pm

@segwpe The problem is it looks like the creator of this addon has abandoned it, or at least hasn’t checked for awhile. Someone needs to fix the code and rebuild the package or else this will most likely be dead forever

fryguy04 · October 28, 2018, 4:01am

After some effort (addons are new to me) found the Bug, Fixed it and submitted a Pull Request to @Pantomax

Bottom line: Hassio added Apparmor that now needs to be set to False to access GPIO pins for RF receiver.

Happy to report I now have a binary_sensor that can be toggled via RF Codeds received.

Here’s a link to the Code (pull request)
And documenation of setting Apparmor:False for Add-Ons

fryguy04 · October 28, 2018, 4:08am

Fixed the issue. (see below). In mean time you can add this custom URL to install the fixes. Let me know how it works for you! https://github.com/fryguy04/hassio-addons

h2r2 · November 2, 2018, 9:04pm

Just tested and it works. Thanks a lot.

Home Assistant 0.81.2, HassOS 1.12, Raspberry Pi 3 Model B + (ARMv8) (8024081)

segepe · November 11, 2018, 1:53pm

Hi…sorry for my delayed answer…

Tested it and it worked…now I just need to get my weatherstation to connect

riker09 · November 29, 2018, 6:01pm

Great work in catching that AppArmor error. Now I’m wondering how I can use that addon to send codes? I have several cheap outlets that are controlled via 433MHz and I have sender and receiver both hooked up to my HassOS powered RPi 3B. I recall this was working with Hassio (not HassOS) without much trouble. I think I had to map the device inside the Docker container, but that was about all I had to configure. I recently changed to HassOS and only now I was realizing why my automations weren’t working anymore.

ha_novice · December 28, 2018, 2:37pm

Hi

I have a fresh install of HASS.IO on my RPi 3B and have installed the Mosquito Core add-on and followed the instructions for the install. However, when starting the RPi RF receiver I see the error below in the logs. Any suggestions as to what might be wrong as I am running on a Raspberry Pi?

Using base prefix '/usr'
New python executable in /data/venv/bin/python3
Also creating executable in /data/venv/bin/python
Installing setuptools, pip, wheel...
done.
Running virtualenv with interpreter /usr/bin/python3
Collecting rpi-rf
  Downloading https://files.pythonhosted.org/packages/e8/b4/092c00607f8e12670c0ac8cb9d4ec495952726105cc36c879825151630bf/rpi_rf-0.9.7-py3-none-any.whl
Collecting RPi.GPIO (from rpi-rf)
  Downloading https://files.pythonhosted.org/packages/af/2f/407b6e4cc8a0bdf434825a160bba1807991886b63cce16a5f1a6e1f24cdf/RPi.GPIO-0.6.5.tar.gz
Building wheels for collected packages: RPi.GPIO
  Running setup.py bdist_wheel for RPi.GPIO: started
  Running setup.py bdist_wheel for RPi.GPIO: finished with status 'done'
  Stored in directory: /root/.cache/pip/wheels/6d/fc/be/f0bd634b0033499def11c5c8b63731c3de443eed482dbe4c71
Successfully built RPi.GPIO
Installing collected packages: RPi.GPIO, rpi-rf
Successfully installed RPi.GPIO-0.6.5 rpi-rf-0.9.7
Traceback (most recent call last):
  File "/share/rpi-rf_receive.py", line 15, in <module>
    from rpi_rf import RFDevice
  File "/data/venv/lib/python3.6/site-packages/rpi_rf/__init__.py", line 2, in <module>
    from .rpi_rf import RFDevice
  File "/data/venv/lib/python3.6/site-packages/rpi_rf/rpi_rf.py", line 9, in <module>
    from RPi import GPIO
  File "/data/venv/lib/python3.6/site-packages/RPi/GPIO/__init__.py", line 23, in <module>
    from RPi._GPIO import *
RuntimeError: This module can only be run on a Raspberry Pi!

ha_novice · December 28, 2018, 4:47pm

Update…

Looks as though from other threads that GPIO may not be compatible with the 64-bit version of HassOS:

Trent_Go · March 8, 2019, 5:13am

Anyone got an idea why I am getting this…?

2019-03-08 05:09:40 - [INFO] rpi-rf_receive: 2 [pulselength 396, protocol 1]
Error: Connection refused
2019-03-08 05:09:43 - [INFO] rpi-rf_receive: 1048576 [pulselength 1783, protocol 4]
Error: Connection refused
2019-03-08 05:09:44 - [INFO] rpi-rf_receive: 131080 [pulselength 958, protocol 2]
Error: Connection refused
2019-03-08 05:09:44 - [INFO] rpi-rf_receive: 128 [pulselength 656, protocol 2]
Error: Connection refused
2019-03-08 05:09:44 - [INFO] rpi-rf_receive: 524288 [pulselength 1838, protocol 4]
Error: Connection refused

my configuration.yml

mqtt:
broker: core-mosquitto
port: 1883
username: homeassistant
password: qwer1234!@#$

rpi-rf_receive.py:

mosquitto_address = “127.0.0.1”
mosquitto_port = “1883”
mosquitto_user = “homeassistant”
mosquitto_password = “qwer1234!@#$”

And Mostquitto broker um… component…?

{
“logins”: [
{
“username”: “homeassistant”,
“password”: “qwer1234!@#$”
}
],
“anonymous”: false,
“customize”: {
“active”: false,
“folder”: “mosquitto”
},
“certfile”: “fullchain.pem”,
“keyfile”: “privkey.pem”
}

Trent_Go · March 8, 2019, 5:38am

nvm I got it… it’s combination of the the ip address and the USERNAME not being an actual user on my system…

Trent_Go · March 8, 2019, 2:45pm

Ok I to am getting what seems like random data now… even when I use the transmitter that came with the receiver… app armor is set to false for sure… just checked the repo i pulled from… any clue? any one?

Does this have anything to do with the problem I am having??

1552081029: New client connected from 172.30.33.3 as mosqpub|187-de3cd379-rf (c1, k60, u’Trent’).
1552081029: Client mosqpub|187-de3cd379-rf disconnected.
1552081029: New connection from 172.30.33.3 on port 1883.
[INFO] found Trent on local database
1552081030: New client connected from 172.30.33.3 as mosqpub|188-de3cd379-rf (c1, k60, u’Trent’).
1552081030: Client mosqpub|188-de3cd379-rf disconnected.
1552081030: New connection from 172.30.33.3 on port 1883.
[INFO] found Trent on local database
1552081030: New client connected from 172.30.33.3 as mosqpub|189-de3cd379-rf (c1, k60, u’Trent’).
1552081030: Client mosqpub|189-de3cd379-rf disconnected.

perjury · March 17, 2019, 6:34pm

Any idea why this massively increases the size of the Hassio snapshot? Without this addon my snapshots are about 6MB. With this addon they are in excess of 210MB!

Paul_Flavel · March 20, 2019, 12:06am

For anyone who is not aware of an alternative, or can’t get this to work on your setup.

https://www.itead.cc/wiki/Sonoff_RF_Bridge_433

Cheap, can be flashed with tasmota, decent range (although have not tested max range).
Currently using mine for the cheap Chinese 433 door bell, and some other 433 stuff.

adas4190 · March 20, 2019, 6:45am

I use OpenMqttGateway on nodemcu as a Rf to mqtt device. Fast and reliable

planetawylie · March 20, 2019, 7:32pm

Never thought of using the bridge. Would you be able to recommend a good remote RF ?

I want to have a remote (or 2) I can use for turning vol up/down, advance next song, for my Sonos devices. Since Sonos app removed that ability from the lock screen on iOS and their app sometimes takes forever to open and connect to the speakers, I thought this would be a great alternative. Especially for when I have guests staying.

Thanks!

snoozy · May 11, 2019, 9:40am

Hello, first of all thanks a lot for this script, I think we can do some awesome things with it

I’m running hassio on a pi 3+ and have the cheap receivers. I’m able to receive the code of my switch, unfortunately in super short range (ca. 30-50 cm). I added an antenna, tried 5V, 3.3V and voltage divider… I will buy the more expensive receiver, we will see.

I’m new to hassio and I can’t get the automation running.

I defined this in my configuration.yaml

vacuum:
  - platform: xiaomi_miio
    host: 192.168.178.73
    token:  6b77793350577659736537655a5a314b

sensor:
platform: mqtt
state_topic: “sensors/rf/receiver”
name: “RF Receiver”

this in my automation.yaml

- alias: 'Robo hello'
    initial_state: 'on'
    trigger:
      platform: mqtt
      topic: "sensors/rf/receiver"   
      payload: '3880184'   
    action:
      - service: vacuum.locate

This is how the log of the script looks:

2019-05-11 11:36:27 - [INFO] rpi-rf_receive: 3880184 [pulselength 297, protocol 1]

This is what I got from MQTT, I finally added my main user to the rfi script since I could not get it running with the MQTT user I added.

[INFO] found steff on Home Assistant
1557567432: New client connected from 172.30.32.1 as mosqpub|194-de3cd379-rf (c1, k60, u'steff').
1557567432: Client mosqpub|194-de3cd379-rf disconnected.

Now I don’t know what is wrong or where to have a look.
Any help welcome

MartiAbernathey · July 13, 2019, 9:46pm

The biggest problem with this solution is the number of switches it controls. I’m already on my second and looking at maybe buying another one.

1technophile · July 14, 2019, 7:47am

Hello,

Are you using the stock firmware or a custom one?

MartiAbernathey · July 16, 2019, 10:45pm

Espurna