Pilight component broken since last update

Configuration
21

My doorbell receiver and RF wallsockets.

You wrote
"For everybody who urgently wants to use the newest release with the pilight hotfix do the following within the homeassistant checkout folder:

git checkout tags/0.32.2
wget https://raw.githubusercontent.com/janLo/home-assistant/ca083e68082a00eecce00ac60065261946611997/homeassistant/components/switch/pilight.py -O homeassistant/components/switch/pilight.py"

but I don’t really know how to do that.
that first command already gives an error when I want to run it.

22

This fix is already in home-assistant. So no need any more to patch your code manually.

23

Oh really? Didn’t know that.
So will you help me troubleshoot? Can also be on gitter.

I didn’t change anything but since the last (I did skip a few versions) version nothing RF works.
The pilight log file (in var/log) doesn’t show anything useful.
Is there a log elsewhere?

When I start pilight in the normal pi environment and try to run a command I do get an error:

pi@raspberrypi:~ $ sudo service pilight start
pi@raspberrypi:~ $ pilight-send -p kaku_switch -i 1052693 -a -t
[ Jan 08 11:09:27:74633] pilight-send: NOTICE: no pilight ssdp connections found
pi@raspberrypi:~ $

But I’m not sure if I’m testing properly.
Can there be 2 pilight installations on a AIO Hass installation? Like in the normal environment and in the virtual environment?

24

Hmm I had a similar error. Try this:

sudo service pilight restart

and then

sudo su

pilight-daemon -D

Do you get output like this?

[Jan 08 11:13:44:303444] pilight-daemon: INFO: version v7.0
[Jan 08 11:13:44:303537] pilight-daemon: NOTICE: already active (pid 1217)
25

Ok that seemed to work. I don’t have the error anymore but RF command not working yet.

26

I don’t know about send command, but is your pilight-receive receiving?

27

What you see has nothing to do with any home-assistant pilight related code, but with the pilight c-library installation on your RPI. I would recommend to search the pilight forum. For example this discussion might help.

28

I have the feeling there are 2 pilight installations. 1 in the normal pi environment and 1 in the virtual home assistant environment.
Do you know how I can access the virtual environment and test pilight from there?
I tried:

Change to homeassistant user: sudo su -s /bin/bash homeassistant
Change to virtual environment: source /srv/homeassistant/homeassistant_venv/bin/activate

But then when I try to restart pilight it asks for a password for hass user. Which doesn’t have a password.

(hass_venv) hass@raspberrypi:/home/pi$ sudo service pilight restart             
We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:

    #1) Respect the privacy of others.
    #2) Think before you type.
    #3) With great power comes great responsibility.

[sudo] password for hass:

When I stop pilight in the normal environment with :

pi@raspberrypi:~ $ sudo service pilight stop

then the webgui is still accessible. So I think it normally uses the pilight in the virtual environment…

So how do I access on a command line the virtual environment so that I can restart pilight and run commands?

[EDIT]
Now that I think of it, I don’t think I even use pilight to Send codes.
In my config I have :slight_smile:

  - platform: rpi_rf
    gpio: 17
    switches:
      kaku1:
        code_on: 1048597
        code_off: 1048596

So that means the issue is with rpi_rf, right?
That’s different than pilight, right?

29

You mix something up. The virtual environments affects python packages. Pilight is a c-library running as a deamon/service and cannot be effected by virtual environments. Do whereis pilight and you will see where you c-library is.