- Joined
- Nov 4, 2018
- Messages
- 102
- Reaction score
- 148
On another note I'm not a raspberry pi expert or even a novice but is there a way to just delay it testing the network or even booting upon start up? But still have it boot no matter what after like 30sec upon power up?I think i know whats happening. When you reboot, reef-pi starts before network is online, as a result when reef-pi starts and connects to hs300 it fails (since network is not up yet). If you reload reef-pi without pi rebooting, it should fix it. If you want to make it full proof , i.e. when reboot happens reef-pi does not start before network comes online, update /lib/systemd/system/reef-pi.service like this (notice the after and wants directive). This will ensure reef-pi is started only after network is up. Reboot your pi to verify this works. Note, this also mean if by any chance your network is down, and pi reboots, reef-pi will not start. This is the reason we dont ship with this settings. I am working on to make things like this (configurations beyond reef-pi, but related to the underlying pi itself) user configurable in near future,.
Code:[Unit] Description=raspberry pi based reef tank controller After=network-online.target Wants=network-online.target [Service] ExecStart=/usr/bin/reef-pi daemon -config /etc/reef-pi/config.yml WorkingDirectory=/var/lib/reef-pi Restart=always RestartSec=90 StartLimitInterval=400 StartLimitBurst=10 [Install] WantedBy=multi-user.target
Thank you

