From 9baff8d403e9e5a2fbbb5b12919aa74fa33d1636 Mon Sep 17 00:00:00 2001 From: BWS Systems Date: Tue, 8 Nov 2016 15:55:50 -0600 Subject: [PATCH] Another update --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 173b731..16a0792 100644 --- a/README.md +++ b/README.md @@ -34,8 +34,6 @@ pi@raspberrypi:~/habridge $ wget https://github.com/bwssytems/ha-bridge/releases ``` For next gen Linux systems (this includes the Raspberry Pi), here is a systemctl unit file that you can install. Here is a link on how to do this: https://www.digitalocean.com/community/tutorials/how-to-use-systemctl-to-manage-systemd-services-and-units -*NOTE ON RC.LOCAL*: Due to the way network subsystem is brought up on the pi, it uses the new systemctl to start services. The old style runlevel setup, which rc.local is part of does not get the benefit of knowing if the network has been fully realized. Starting ha-bridge from rc.local on next gen systems will cause unexpected results and issues with discovering registered devices. - ``` [Unit] Description=HA Bridge @@ -51,6 +49,8 @@ WantedBy=multi-user.target ``` Basic script setup to run the bridge on a pi. +*NOTE ON RC.LOCAL*: Due to the way network subsystem is brought up on the pi, it uses the new systemctl to start services. The old style runlevel setup, which rc.local is part of does not get the benefit of knowing if the network has been fully realized. Starting ha-bridge from rc.local on next gen systems will cause unexpected results and issues with discovering registered devices. + Edit the shell script for starting: ``` pi@raspberrypi:~/habridge $ nano starthabridge.sh