• 10 dec 2017: forum version update. In case of issues use this topic.
  • 30 nov 2017: pilight moved servers. In case of issues use this topic.
Hello There, Guest! Login Register


Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
pilight and Lirc
#1
Hello, I am using pilight on my Raspberry Pi 3 with a 433 MHz receiver connected to GPIO18 in order to read the values from a Temperature Sensor. Everything works great and I am very happy with it.
On the same PI i had connected an Infrared Transmitter on the GPIO24 in order to turn on/off an old light bulb controlled via InfraRed. It did work good until I installed pilight and commented the /boot/config.txt line
Code:
dtoverlay=lirc-rpi,gpio_out_pin=24

When this line is active, the pilight Daemon does not start and I get the error:

Code:
pilight-receive: NOTICE: no pilight ssdp connections found


and in the /var/log/pilight.log there is:

Code:
[Apr 23 14:09:03:568672] pilight-daemon: INFO: daemon listening to port: 5000
[Apr 23 14:09:03:573014] pilight-daemon: ERROR: wiringX failed to write to /sys/class/gpio/gpio18/edge for gpio edge (Device or resource busy)
[Apr 23 14:09:03:578409] pilight-daemon: ERROR: unable to register interrupt for pin 1
[Apr 23 14:09:03:578461] pilight-daemon: ERROR: could not initialize 433gpio hardware module
[Apr 23 14:09:03:573512] pilight-daemon: INFO: new client, ip: 127.0.0.1, port: 48080


It's weird because I read that pilight should be even able to control Lirc

Do you have any idea of what I'm doing wrong?
Thank you very much in advance!
 
Reply
#2
Lirc uses BCM pin numbering, pilight follows the Raspberry Pi pin numbering.
[Image: ?u=https%3A%2F%2Fi1.wp.com%2Fcdn.makezin...ns.png&f=1]
As you can see here, BCM pin 24 is the same as wiringX 1 which translates to P1 pin GPIO 18.
 
Reply
#3
Thank you for your answer, but I tried to write on /boot/config.txt


Code:
dtoverlay=lirc-rpi,gpio_in_pin=23,gpio_out_pin=22


which should be the wiringX 3 if I understand your table correctly.
Then i reboot and i get again the error:

Code:
[Apr 24 06:55:09:626766] pilight-daemon: ERROR: wiringX failed to write to /sys/class/gpio/gpio18/edge for gpio edge (Device or resource busy)
[Apr 24 06:55:09:631229] pilight-daemon: INFO: new client, ip: 127.0.0.1, port: 42718
[Apr 24 06:55:09:633448] pilight-daemon: ERROR: unable to register interrupt for pin 1
[Apr 24 06:55:09:633567] pilight-daemon: ERROR: could not initialize 433gpio hardware module

EDIT:

In my config.json i had to set the sender for the 433MHz hardware to -1 (because I only need the receiver):

Code:
{
        "devices": {},
        "rules": {},
        "gui": {},
        "settings": {
                "log-level": 6,
                "pid-file": "/var/run/pilight.pid",
                "log-file": "/var/log/pilight.log",
                "standalone": 0,
                "port": 5000,
                "webserver-enable": 0,
                "webserver-root": "/usr/local/share/pilight/webgui",
                "webserver-http-port": 5001,
                "webserver-https-port": 5002,
                "webserver-cache": 1,
                "whitelist": "",
                "gpio-platform": "raspberrypi3"
        },
        "hardware": {
                "433gpio": {
                        "sender": -1,
                        "receiver": 1
                }
        },
        "registry": {
                "webserver": {
                        "ssl": {
                                "certificate": {
                                        "location": "/etc/pilight/pilight.pem"
                                }
                        }
                },
                "pilight": {
                        "version": {
                                "current": "8.1.4"
                        }
                }
        }
}

Then it worked! Thank you for the hint!
 
Reply
#4
I'm using this kind of setup myself.
Code:
dtoverlay=lirc-rpi,debug,gpio_in_pin=27

Code:
        "hardware": {
                "433gpio": {
                        "sender": 0,
                        "receiver": 1
                }
        },
 
Reply
  


Possibly Related Threads...
Thread Author Replies Views Last Post
  pilight 8.1.4 crashes after some hours Ulrich.Arnold 3 62 Yesterday, 08:46 PM
Last Post: curlymo
  pilight-send does not stop (terminate) va13 3 67 05-15-2019, 06:06 PM
Last Post: curlymo
  oom_reaper: reaped process pilight-daemon va13 4 86 05-15-2019, 08:03 AM
Last Post: va13
  cant configure or even start pilight on raspi 3b Xvnx23 2 97 05-06-2019, 09:47 PM
Last Post: fourty2
Sad Raspberry Pi: "NOTICE: no pilight ssdp connections found" abusch 8 135 04-30-2019, 09:10 PM
Last Post: curlymo
  Using pilight-daemon socket API def_meggi 4 87 04-29-2019, 05:58 PM
Last Post: curlymo
  pilight-flash not working danny 9 174 04-27-2019, 09:02 PM
Last Post: curlymo
Question Pi 3+ & pilight & 433Mhz RXB6: no receiption hacklschorsch 3 440 02-05-2019, 10:37 PM
Last Post: hacklschorsch
  Consecutive pilight commands habitoti 4 385 01-28-2019, 03:32 PM
Last Post: habitoti
  pilight not working with fresh Openhab 2 image habitoti 2 266 01-24-2019, 08:44 PM
Last Post: habitoti

Forum Jump:


Browsing: 1 Guest(s)