• 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
  pilight for Raspbian Buster (raspberry pi 4) ? starob 32 7,571 08-10-2020, 09:12 AM
Last Post: simanuel
  pilight switch node in node-red framp 0 261 06-24-2020, 10:01 PM
Last Post: framp
  pilight-control TML 13 963 05-27-2020, 07:51 AM
Last Post: curlymo
  API Requests by HTTP from other devices fore use in pilight scootermacro 2 449 05-10-2020, 08:19 AM
Last Post: scootermacro
  pilight-send seems successful but doesn't actually send RF signal ayeyebrazov 37 3,238 03-31-2020, 01:02 PM
Last Post: curlymo
  pilight 8.1.5 not working on Raspberry pi after reboot beejayf 4 896 03-08-2020, 12:14 AM
Last Post: beejayf
  pilight cpu usage possibly associated with noticeable sluggishness? hepcat72 4 947 01-28-2020, 08:02 PM
Last Post: hepcat72
  apt.pilight.org stable Release' is not signed. thomasol 2 980 01-23-2020, 11:34 PM
Last Post: thomasol
  pilight and SIGNALduino cc1101 Caleus 0 731 01-19-2020, 09:13 AM
Last Post: Caleus
  filter stopped working after update to pilight 8.1.5 zlin50 19 2,138 01-03-2020, 02:15 PM
Last Post: curlymo

Forum Jump:


Browsing: 1 Guest(s)