• 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:
  • 1 Vote(s) - 5 Average
  • 1
  • 2
  • 3
  • 4
  • 5
[solved] another pilight ssdp missed connection on RPI
#1
Sometimes, when raspberry pi (jessy) reboot, pilight restart without ssdp conenction. As I use piSchedule, after a reboot sometimes I miss my schedule because of this ssdp. I had to manually restart pilight in order to get ssdp right

I was investigating and seems that is because of dhcp (pilight start before IP is assigned), and the solutions here is disable dhcp and configure static IP. For other reasons this is not able for my configuration.

I have read some about init, systemd, rc stuff and seems that I have found a solution that seems to work.

This is what I have made:


Code:
sudo mkdir /etc/systemd/system/pilight.service.d
sudo nano /etc/systemd/system/pilight.service.d/pilight.conf

and put into this config file this text:


Code:
[Unit]
Require = network-online.target
After = network-online.target

I want to share this if it can help other people.
 
Reply
#2
This would be good to have in pilight by default, can you make a pull request on the pilight repository on GitHub?
 
Reply
#3
I have similar issues (using pilight V 7.0 also running on Raspbian Jessie) but if I make the provided fix I get

Code:
systemd[1]: Started LSB: Starts pilight-daemon.
systemd[1]: [/etc/systemd/system/pilight.service.d/pilight.conf:2] Unknown lvalue 'Require' in section 'Unit'

I then changed "Require" to "Requires" and then this error message is gone (maybe a typo in your code?) but then I get for sudo service pilight status
Code:
Warning: Unit file changed on disk, 'systemctl daemon-reload' recommended.
I get get rid of this warning if I run the recommended command but after an reboot of the Pi the warning is back again.
Do you also have this warning? Is there something I should do about it?
piSchedule still did not work from automatic start (I'm not sure if this is because of the warning or other issues).

I fixed the issue in my case by not using
/etc/systemd/system/pilight.service.d/pilight.conf
but instead activating "Wait for network at boot" in raspi-config and adding $named $network in /etc/init.d/pilight (and /etc/init.d/piSchedule )

Code:
# Required-Start:    $named $network $remote_fs $syslog
# Required-Stop:     $named $network $remote_fs $syslog
I'm not sure if this is a real fix or just causes the pilight service to state later which then works (I read that others used a "sleep 10")
 
Reply
  


Possibly Related Threads...
Thread Author Replies Views Last Post
  [Fixed] RaspberryPi4 pilight 8.1.5 - Send isn't working DominikB1993 4 39 Yesterday, 10:25 PM
Last Post: DominikB1993
  Real 433Mhz Remote is disturbed by pilight service henne111 2 156 10-06-2019, 06:18 PM
Last Post: wo_rasp
Tongue (solved) pilight 8.1.5-1-gc0a175e0 Chrashes fleisch 5 578 10-03-2019, 01:15 PM
Last Post: fleisch
  Starting pilight on boot: "cannot bind to the SSDP multicast network" pilino1234 4 343 09-29-2019, 02:08 PM
Last Post: tomk
  [Already fixed in 8.1.2] Loss of webserver-connection Ulrich.Arnold 34 2,655 08-02-2019, 02:25 PM
Last Post: curlymo
  Solved - On / Off Command is the same command tigrablue 11 476 07-23-2019, 11:24 AM
Last Post: curlymo
  pilight for Raspbian Buster (raspberry pi 4) ? starob 29 2,438 07-15-2019, 08:45 PM
Last Post: curlymo
  pilight-receive Filteroption not working Alex 2 568 07-14-2019, 08:35 AM
Last Post: Alex
  pilight usb nano format conversion ettman8 2 452 07-14-2019, 08:32 AM
Last Post: curlymo
  pilight 8.1.4 crashes after some hours Ulrich.Arnold 47 2,685 06-29-2019, 08:58 PM
Last Post: curlymo

Forum Jump:


Browsing: 1 Guest(s)