Hey @Philipp_Schreyer, I just restarted the addon and well… it still works. The only difference is the “version” in the first line, it say “3.2.2” on my Hassio.
starting version 3.2.2
Running virtualenv with interpreter /usr/bin/python3
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.
Collecting rpi-rf
Downloading rpi-rf-0.9.6.tar.gz
Collecting RPi.GPIO (from rpi-rf)
Downloading RPi.GPIO-0.6.3.tar.gz
Building wheels for collected packages: rpi-rf, RPi.GPIO
Running setup.py bdist_wheel for rpi-rf: started
Running setup.py bdist_wheel for rpi-rf: finished with status 'done'
Stored in directory: /root/.cache/pip/wheels/16/e2/54/205bfe1826862c70b36a59d02c340d06726cdbd82f5b88dfdb
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/ae/4d/3b/e924997dbf06810adf3b2e37f1d9627b2327eb9cbb285949c9
Successfully built rpi-rf RPi.GPIO
Installing collected packages: RPi.GPIO, rpi-rf
Successfully installed RPi.GPIO-0.6.3 rpi-rf-0.9.6
2018-01-11 12:40:17 - [INFO] rpi-rf_receive: Listening for codes on GPIO 27
2018-01-11 12:40:26 - [INFO] rpi-rf_receive: 4096 [pulselength 1222, protocol 4]
...
Actually I’m not sure where the problem could be, are you using the right GPIO? Probably yes, you should at least read the line
[INFO] rpi-rf_receive: Listening for codes on GPIO 27
and then not receiving anything.
I am using the 0.60 version of Hassio, what about you? Did you already updated to the 0.60.1?
this is the last lines of my supervisor log:
18-01-11 11:25:56 INFO (MainThread) [hassio.addons.git] Pull addon https://github.com/home-assistant/hassio-addons repository
18-01-11 11:25:56 INFO (MainThread) [hassio.addons.git] Pull addon https://github.com/pantomax/hassio-addons repository
18-01-11 11:25:57 INFO (MainThread) [hassio.addons] Load addons: 23 all - 0 new - 0 remove
18-01-11 12:00:16 INFO (SyncWorker_17) [hassio.docker.interface] Clean de3cd379/armhf-addon-rfreceiver docker application
18-01-11 12:00:18 INFO (SyncWorker_17) [hassio.docker.addon] Start docker addon de3cd379/armhf-addon-rfreceiver with version 1.5
So that looks good, though.
Yes, I already use 0.60.1 and I saw another thing:
The addon stopps automatically. After I started it and got the output from the last post, when I reload the page it says: STOPPED. When I restart (addon and machine) this doesn’t bring a solution
I think I’m not going to upgrade my Hassio then . I’ll have a look if something is changed on declaring the addons, maybe there’s something I should change. Thanks for letting me know
just wanted to give some feedback here.
I made a fresh install of Hass.io yesterday coming from Hassbian.
Installed this addon from your repository and it works like a charm. Maybe @Philipp_Schreyer forgot to copy the python file to share? How would your addon behave if it is not there?
Only thing I also experience is that I can’t read codes properly. The addon just logs codes everytime and if I hold the button of my remote it logs lots of different codes and protocols.
I think this is caused by my cheap RF receiver. Just ordered a better one, will let you know.
exactly the same HW here , just orderer the bottom one now.
So you’re running the better receiver with 3.3V ?
The cheap one behaves the same on 3.3V and 5V.
Well, me too, I keep receiving a couple of codes every second, but that’s just because our houses are full of interferences unless you live in the middle of nowhere
So I got the new receiver today, soldered an antenna, connected it to 5V and there it is. Just working great! I simply use the mqtt sensor you implemented as triggers in automations to control devices. Couldn’t be much easier.
Thanks a lot for this add-on!
P.S. still get phantom reads while pushing the buttons on the remote but almost none otherwise
1398036 is switch off
1398033 is switch on
Glad to hear it’s working fine.
I guess outdoor temperature sensors use a different code for every tenth of temperature degree, but I don’t really know how they work. Maybe it’s a standard protocol, who knows.
Bye the way I just received this antenna:
I’m not sure it will extend the reception range but it is cheap and it looks good. I’ll keep you updated.
I thought I’d worked out some kinks, but then notice this is the Log File. Any idea why I get the message this can only be run on a Raspberry Pi? I am using a Pi 3 Model B. I tried both of the versions in the repository with the same results: RPi RF Receiver and RPi RF Receiver 3.
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!**