• 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
Raspbian jessie - pilight 7 - no pilight ssdp connections found
#1
Hello,

I'm new to this forum, so would like to say Hello Smile

I have a problem since I installed my Raspberry Pi new. I installed Raspbian Jessie on a clean SD Card and installed first wiringPi and then pilight v7.
On my old Raspbian Wheezy I worked with pilight 6 and everything works find.
Now as I installed pilight 7 I am not getting this to work for me.
The installation went fine. But everytime I try to send an command with pilight-send I got the error:
Code:
pilight-send: ERROR: no pilight ssdp connections found
I tried to install the old version 6, but the same error. I googled a lot, but there was no sutable answer.
Can someone tell me what could be the problem?
And if you need, which files I should upload?

Thanks a lot.
shirocko
 
Reply
#2
To me it sounds like a network issue, I recommend to check the pilight WIKI, in particular the network section and the loopback adapter setting requirements. I am using the jessie distribution since its release for the pi and found no issues so far with pilight V7, this includes the development environment including gcc, however i have to stress that i am not using any precompiled packages, but compile the git repositories myself.
 
Reply
#3
Hi,

thank you for your answer.
I have a network configuration based on the dhcpcd.conf and the default Interfaces config. Might that be a problem?
(As side info: only with the interfaces file I got Nö working network config under jessie)

Thanks
shirocko
 
Reply
#4
You do need the loopback adapter to be defined.

Did you start reading the wiki ? and did you compare the corresponding parts of your file /etc/network/interfaces with the wiki ?

As a short cut, please start reading here the english version of the FAQ:
https://manual.pilight.org/en/faq

The FAQ is also available in dutch, italian and german (use the flag symbol at the upper left menu.
 
Reply
#5
Had the same problem with Jessie.

The daemon dhcpcd overrides the settings in /etc/network/interfaces!

Just disable the daemon using

Code:
sudo update-rc.d -f dhcpcd remove

and it works! Wink
 
Reply
#6
Hi,

I have kind of the same problem, did you have a look here?

I can confirm that it works fine for me when I restart the pilight daemon by hand. Nevertheless I'm a little reluctant to automatically restart with a (random) sleep that now by chance works for most of us.

Isn't there a cleaner solution for timing the start-up of pilight after the network is fully up and running?

Cheers,
ramyres
 
Reply
#7
Added this in the pilight FAQ.
 
Reply
#8
(01-25-2016, 02:45 PM)ramyres Wrote: ... Isn't there a cleaner solution for timing the start-up of pilight after the network is fully up and running?
Yes,
For jessie and systemd, add the following line in the Unit section:
After=network.target
It will delay execution of the command until the network is up.
 
Reply
#9
(01-29-2016, 11:22 AM)wo_rasp Wrote: For jessie and systemd, add the following line in the Unit section:
After=network.target

Thanks, I'll give it a try on the weekend.

Cheers,
ramyres
 
Reply
#10
pilight-receive
pilight-receive: NOTICE: no pilight ssdp connections found


OS Raspberry pi 2.

trying to use a 433mHz receiver but i cant even get pilight-receive to work. Tried everything i could find in the forums.

/etc/network/interfaces


Code:
# Include files from /etc/network/interfaces.d:
source-directory /etc/network/interfaces.d


auto lo
iface lo inet loopback
allow-hotplug eth0
auto eth0
iface eth0 inet static
adress 192.168.1.255
netmask 255.255.255.0
gateway 192.168.1.1


allow-hotplug wlan0
iface wlan0 inet manual
wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf
iface default inet dhcp


now running nightly build after reading forumposts, no luck there either.

When i do -D it will receive signals via the receive (its magnet sensor from Nexa)
So stuff happens. It has worked once, but cant get pilight-receive to work again.



Code:
sudo service pilight status
● pilight.service - LSB: Starts pilight-daemon
   Loaded: loaded (/etc/init.d/pilight)
   Active: inactive (dead) since sön 2016-02-07 16:52:02 CET; 3s ago
  Process: 1306 ExecStop=/etc/init.d/pilight stop (code=exited, status=0/SUCCESS)

feb 07 16:38:19 CavePi pilight[374]: Starting : pilight.
feb 07 16:38:21 CavePi systemd[1]: Started LSB: Starts pilight-daemon.
feb 07 16:52:02 CavePi systemd[1]: Stopping LSB: Starts pilight-daemon...
feb 07 16:52:02 CavePi pilight[1306]: Stopping : pilight.
feb 07 16:52:02 CavePi systemd[1]: Stopped LSB: Starts pilight-daemon.

No luck here.

When i do -D

Code:
sudo pilight-daemon -D
[Feb 07 15:52:51:602696] pilight-daemon: INFO: version v7.0
[Feb 07 15:52:51:603076] pilight-daemon: DEBUG: ssdp sent search
[Feb 07 15:52:51:700800] pilight-daemon: INFO: no pilight daemon found, daemoniz                                                                     ing
[Feb 07 15:52:51:701452] pilight-daemon: INFO: daemon listening to port: 60727
[Feb 07 15:52:51:702561] pilight-daemon: DEBUG: new thread socket, 1 thread runn                                                                     ing
[Feb 07 15:52:51:703077] pilight-daemon: INFO: new client, ip: 127.0.0.1, port:                                                                      42612
[Feb 07 15:52:51:703074] pilight-daemon: DEBUG: new thread ssdp, 2 threads runni                                                                     ng
[Feb 07 15:52:51:703498] pilight-daemon: DEBUG: client fd: 6
[Feb 07 15:52:51:703756] pilight-daemon: DEBUG: client id: 1
[Feb 07 15:52:51:704086] pilight-daemon: DEBUG: new thread sender, 3 threads run                                                                     ning
[Feb 07 15:52:51:704191] pilight-daemon: DEBUG: running on a raspberrypi
[Feb 07 15:52:51:704647] pilight-daemon: DEBUG: new thread broadcaster, 4 thread                                                                     s running
[Feb 07 15:52:51:712720] pilight-daemon: NOTICE: php support disabled due to mis                                                                     sing php-cgi executable
[Feb 07 15:52:51:712752] pilight-daemon: DEBUG: new thread 433gpio, 5 threads ru                                                                     nning
[Feb 07 15:52:51:713499] pilight-daemon: DEBUG: new thread receive parser, 6 thr                                                                     eads running
[Feb 07 15:52:51:713878] pilight-daemon: DEBUG: new thread events client, 7 thre                                                                     ads running
[Feb 07 15:52:51:714273] pilight-daemon: DEBUG: new thread events loop, 8 thread                                                                     s running
[Feb 07 15:52:51:714401] pilight-daemon: DEBUG: ssdp sent notify
[Feb 07 15:52:51:714656] pilight-daemon: DEBUG: ssdp sent notify
[Feb 07 15:52:51:714564] pilight-daemon: DEBUG: webserver listening to port 5001
[Feb 07 15:52:51:714172] pilight-daemon: DEBUG: ssdp sent search
[Feb 07 15:52:51:715332] pilight-daemon: DEBUG: new thread webserver worker #0,                                                                      9 threads running
[Feb 07 15:52:51:715739] pilight-daemon: DEBUG: new thread webserver client, 10                                                                      threads running
[Feb 07 15:52:51:716173] pilight-daemon: DEBUG: new thread webserver broadcast,                                                                      11 threads running
[Feb 07 15:52:51:716343] pilight-daemon: DEBUG: ssdp sent notify
[Feb 07 15:52:51:716589] pilight-daemon: DEBUG: cpu: 0.000000%, ram: 0.298700%
[Feb 07 15:52:51:716802] pilight-daemon: DEBUG: ssdp sent notify
[Feb 07 15:52:51:717153] pilight-daemon: DEBUG: ssdp sent search
[Feb 07 15:52:51:811227] pilight-daemon: INFO: new client, ip: 192.168.1.225, po                                                                     rt: 39384
[Feb 07 15:52:51:811335] pilight-daemon: DEBUG: client fd: 12
[Feb 07 15:52:51:811403] pilight-daemon: DEBUG: client id: 2
[Feb 07 15:52:51:811778] pilight-daemon: DEBUG: socket write succeeded: {"action                                                                     ":"identify","options":{"config":1},"media":"all"}

[Feb 07 15:52:51:812063] pilight-daemon: INFO: new client, ip: 192.168.1.225, po                                                                     rt: 39385
[Feb 07 15:52:51:812196] pilight-daemon: DEBUG: client fd: 14
[Feb 07 15:52:51:812294] pilight-daemon: DEBUG: client id: 3
[Feb 07 15:52:51:812135] pilight-daemon: DEBUG: socket write succeeded: {"action                                                                     ":"identify","options":{"config":1,"core":1},"media":"web"}

[Feb 07 15:52:51:812535] pilight-daemon: DEBUG: socket recv: {"action":"identify                                                                     ","options":{"config":1},"media":"all"}
[Feb 07 15:52:51:812869] pilight-daemon: DEBUG: socket write succeeded: {"status                                                                     ":"success"}

[Feb 07 15:52:51:813129] pilight-daemon: DEBUG: socket recv: {"action":"identify                                                                     ","options":{"config":1,"core":1},"media":"web"}
[Feb 07 15:52:51:813306] pilight-daemon: DEBUG: socket write succeeded: {"status                                                                     ":"success"}

^C[Feb 07 15:52:53:774299] pilight-daemon: DEBUG: received interrupt signal, sto                                                                     pping pilight...
[Feb 07 15:52:53:775495] pilight-daemon: DEBUG: garbage collected event operator                                                                      library
[Feb 07 15:52:53:775596] pilight-daemon: DEBUG: freed options struct
[Feb 07 15:52:53:775653] pilight-daemon: DEBUG: freed options struct
[Feb 07 15:52:53:775706] pilight-daemon: DEBUG: freed options struct
[Feb 07 15:52:53:775755] pilight-daemon: DEBUG: freed options struct
[Feb 07 15:52:53:775821] pilight-daemon: DEBUG: freed options struct
[Feb 07 15:52:53:775875] pilight-daemon: DEBUG: freed options struct
[Feb 07 15:52:53:775927] pilight-daemon: DEBUG: freed options struct
[Feb 07 15:52:53:775973] pilight-daemon: DEBUG: garbage collected event action l                                                                     ibrary
[Feb 07 15:52:53:776024] pilight-daemon: DEBUG: garbage collected event function                                                                      library
[Feb 07 15:52:53:776072] pilight-daemon: DEBUG: garbage collected events library
[Feb 07 15:52:53:777345] pilight-daemon: INFO: removed stale pid_file /var/run/p                                                                     ilight.pid
[Feb 07 15:52:53:777934] pilight-daemon: DEBUG: garbage collected fcache library
[Feb 07 15:52:53:778022] pilight-daemon: DEBUG: garbage collected sha256cache li                                                                     brary
[Feb 07 15:52:53:778074] pilight-daemon: DEBUG: garbage collected webserver libr                                                                     ary
[Feb 07 15:52:53:778432] pilight-daemon: DEBUG: garbage collected ssdp library
[Feb 07 15:52:53:778521] pilight-daemon: DEBUG: garbage collected options librar                                                                     y
[Feb 07 15:52:53:778854] pilight-daemon: DEBUG: client disconnected, ip 127.0.0.                                                                     1, port 60727
[Feb 07 15:52:53:778868] pilight-daemon: DEBUG: client disconnected, ip 192.168.                                                                     1.225, port 60727
[Feb 07 15:52:53:779157] pilight-daemon: DEBUG: garbage collected socket library
[Feb 07 15:52:53:779210] pilight-daemon: DEBUG: garbage collected config devices                                                                      library
[Feb 07 15:52:53:779241] pilight-daemon: DEBUG: garbage collected config rules l                                                                     ibrary
[Feb 07 15:52:53:779367] pilight-daemon: DEBUG: garbage collected config gui lib                                                                     rary
[Feb 07 15:52:53:779425] pilight-daemon: DEBUG: garbage collected config setting                                                                     s library
[Feb 07 15:52:53:779481] pilight-daemon: DEBUG: stopping thread 433gpio
[Feb 07 15:52:53:779548] pilight-daemon: DEBUG: stopped thread 433gpio, 10 threa                                                                     ds running



sudo service pilight start. Starts the Daemon.

Webgui tells me that 100% CPU is used tho.

http://prntscr.com/a06jcr screenshot.

Please help.
 
Reply
  


Possibly Related Threads...
Thread Author Replies Views Last Post
  pilight-control modify values coolinx 16 267 11-13-2019, 08:02 PM
Last Post: curlymo
  Bug: double free or corruption in pilight-send blackzombie 12 304 10-07-2019, 08:15 PM
Last Post: blackzombie
  [Fixed] High CPU usage when pilight usb nano disconnects DieterK 1 190 08-13-2019, 05:43 PM
Last Post: curlymo
  pilight Nano USB interface curlymo 228 100,251 07-10-2019, 06:14 PM
Last Post: curlymo
  problems compiling pilight on Odroid C2 WitchDoctor 101 10,866 03-14-2019, 09:01 PM
Last Post: curlymo
  pilight 8 what chages for custom protocols? polo 11 3,151 02-15-2019, 06:22 PM
Last Post: polo
  pilight-debug shows nothing minhdomanh 3 608 10-18-2018, 07:01 AM
Last Post: felfert
  pilight-send and pilight-daemon DieterK 0 610 06-20-2018, 12:44 AM
Last Post: DieterK
  Lights not switched on or off by rules in pilight 8.1.0 rorie 22 2,754 06-12-2018, 03:56 PM
Last Post: curlymo
  check API in pilight 8 stratege-0815 4 1,497 02-11-2018, 09:34 AM
Last Post: stratege-0815

Forum Jump:


Browsing: 1 Guest(s)