Download source PDF Page last generated on 11:01, 29 January 2016 Github 
Frequently Asked Questions
Frequently Asked Questions..........................................................................................................................1
General..................................................................................................................................................... 1
Retrieving running pilight version..........................................................................................................1
Fixing SSDP connection issues............................................................................................................2
Disabling SSDP completely..................................................................................................................2
Using PHP inside the pilight webserver................................................................................................2
Using other devices besides 433.92 MHz.............................................................................................2
Fixing broken Lirc and 1-wire protocols................................................................................................2
Fixing the high CPU usage after a Kernel upgrade...............................................................................2
Sending & Receiving................................................................................................................................. 3
The GPIO connected receiver does not work.......................................................................................3
I only see sent codes, not received ones..............................................................................................3
Let devices learn new codes sent from pilight......................................................................................3
The send-repeat setting does not work anymore..................................................................................3
Configuration............................................................................................................................................. 4
How to use raw codes in the configuration...........................................................................................4
How to fix an empty webGUI................................................................................................................4
Compilation............................................................................................................................................... 4
How to fix errors about missing dependencies.....................................................................................4
Myths........................................................................................................................................................ 4
pilight support for Domoticz and pimatic...............................................................................................4
The Raspberry Pi is not fast enough to handle domotica software.......................................................4
General
Retrieving running pilight version
You can use the following command to retrieve the pilight version:
If you run a stable version, only the version will be shown:
If you run a developmental version, a commit message will also be shown. It will point to the last commit
included in your pilight compilation.
In this case, the 24th commit after version 7.0 with the SHA id gb64a135 is running. To see which commit
this is, check the git development commit list.
pi@pilight:~# pilight-daemon -V
pilight-daemon version v7.0
pilight-daemon version v7.0-24-gb64a135
Fixing SSDP connection issues
Make sure your iptables are set correctly:
Also make sure your network interfaces are configured correctly in /etc/network/interfaces:
1 auto lo
2 iface lo inet loopback
3 allow-hotplug eth0
4 auto eth0
5 iface eth0 inet static
6 address x.x.x.x
7 netmask 255.255.255.0
8 gateway x.x.x.x
Especially the iface lo inet loopback part is essential for SSDP to work. A reboot could be necessary after
making these changes.
To make sure these settings do not get overriden, you might need to disable the service dhcpcd:
Disabling SSDP completely
Add the standalone setting in the config.json and set it to 1. However, because all pilight clients use SSDP
to find the main pilight daemon, you need to pass the server and port arguments when you want to control
this standalone running daemon.
Using PHP inside the pilight webserver
You probably encounter this message when running pilight in debug mode:
This means that you miss some packages to run PHP. The required packages pilight needs for PHP
support are:
• php-cgi
• base64
• cat
Using other devices besides 433.92 MHz
pilight was built with 433.92 MHz devices as a reference, but the code is not limited to this frequency. We
actually always wrote the code with other frequencies in mind. The only reason no other frequencies like
868 MHz are supported is lack of time and the lack of other developers to do it for us. The hardware part of
pilight is completely modular so adding support for other frequencies should be as easy as writing new
protocols.
Fixing broken Lirc and 1-wire protocols
You probably installed the latest Raspberry Pi kernel. The new kernel works with device trees so the kernel
knows what devices you want to use. Check the Raspberry Pi documentation how to use this new device
tree.
Fixing the high CPU usage after a Kernel upgrade
The wiringPi GPIO library used in pilight version 5.0 and lower contained a bug. This is fixed in pilight
pi@pilight:~# sudo iptables -A INPUT -s 127.0.0.1 -j ACCEPT
pilight-daemon: ERROR: php support disabled due to missing php-cgi executable
pi@pilight:~# sudo update-rc.d -f dhcpcd remove
version 6 and up.
Sending & Receiving
The GPIO connected receiver does not work
The most encountered reason for this problem is the quality of the receiver. A lot of users buy unsupported
(cheap) receivers from either eBay, DealExtreme or similar sites often referred to as FS1000A and XY-MK-
5V. However, these receivers have a terrible range. To make sure it is the receiver and not a fault in
connecting the device to your Raspberry Pi, make sure to keep your remote next to the receiver. If it still
fails, check then check your connections.
If you do want to use pilight for controlling devices across your house, consider buying a good quality
receiver. Refer to the pilight shop for supported peripherals.
I only see sent codes, not received ones
The pilight receive output always contains an origin value. This means you can see from were the outputted
code came from. Only if this field says receiver you know that the code was picked up by the receiver.
When it says sender the codes has been created and processed internally. pilight processes these codes
as if it was a received code so it can update the GUIs and config. Only if you see receiver you know it was
not generated by pilight.
Let devices learn new codes sent from pilight
Some protocols support learning devices. This learn feature temporarily sends an increased amount of
codes to the device. Check the protocol send arguments to see if your protocol supports it. For example,
the KlikAanKlikUit protocol does this as follows:
The send-repeat setting does not work anymore
pilight version 6 was the last version supporting the global send-repeat setting. This setting told pilight how
often a pulsetrain was repeated. This setting got removed because it interfered with a lot of protocols.
Most remote control devices repeat a pulsetrain two to six times on a single button press. On some devices
all pulsetrains are identical, so repeating them does not introduce any issues. However, on some devices
the 1st pulsetrain differs from the subsequent pulsetrains. In addition, some devices sent a wakeup pulse
sequence before the very 1st pulsetrain to trigger internal wakeup logic. Most devices use footer pulses,
while devices transmit header pulses, and some devices transmit both.
If you keep the button pressed on some remote controls, a series of pulsetrains is sent until the button is
released, while others stop sending repetitive pulsetrains after a certain time period, and some set a toggle
bit for repetitive pulsetrains each time a button is pressed.
pilight was not differentiating between those various operating scenarios, because the send-repeat
parameter specified only how often a single pulsetrain was re-transmitted for all devices. So increasing the
global send-repeats actually broke a lot of these protocols. We therefore removed the old global send-
repeat parameter and replaced it with a protocol specific repeat parameter, currently not configurable from
userspace.
We also discovered that in almost all cases, the solution was not increasing the send-repeats parameter,
pi@pilight: ~#pilight-send -p kaku_switch -i 1 -u 1 -t -l
but instead using a good antenna.
Configuration
How to use raw codes in the configuration
This is not possible, because pilight cannot know what these codes mean and how to interpret them.
How to fix an empty webGUI
You need to add devices to the "GUI" section of config.json as well, not just the "devices" section.
Compilation
How to fix errors about missing dependencies
If you get this or a similar error, it means you are missing some of the required dependencies pilight needs.
Currently, these dependencies are:
• libunwind
• libpcap
It depends on your platform how to install these dependencies.
Myths
pilight support for Domoticz and pimatic
The possibility is there, but it is up to the developer of Domoticz and pimatic to (re-)add support.
The Raspberry Pi is not fast enough to handle domotica software
Although almost all available Domotica solutions for the Raspberry Pi use external hardware such as the
RFXCom and Tellstick. pilight proves that with even the most simple hardware, the Raspberry Pi can be
turned into a full domotica solution. Even without filtering the receiver noise, the Raspberry Pi can easily
process all pulses. Without low-pass filter, pilight currently uses around 40% CPU power. That leaves a lot
of resources for other applications. However, the RF receivers can drain the GPIO buffers, so if you use
pilight without some sort of hardware filtering, no other GPIO intensive applications can be used
simultaneously, such as IR receiving with Lirc.
-- Looking for libunwind
CMake Error at CMakeLists.txt:42 (message):
Looking for libunwind - not found
-- Configuring incomplete, errors occurred!
Top