OK, I’m not a programmer and not experienced with Linux/Unix but I definitely want to use Homebridge as soon as possible to control my 10 Photons around the house…
So, I took all my courage together and ordered a new Pi3 B+…
In one long day, I have …
- assembled my brandnew Pi with a SmartiPi touchscreen,
- set-up the Pi from scratch,
- learned to speek Linux ssh and VNC my Pi from my Mac and
- managed to set it’s resolution to such an incredibly small size that I could’nt configure it anymore and I
- escaped finally! (With a little help from great Linux minds!)
- set-up Particle Pi where
- managed the little green “D7” led using my iPhone App. Then
- started installing Homebridge by following the original Github instructions by nfarina which Jordy (@Moors7 ) mentioned in the previous post.
I am very happy I managed to install Homebridge that far already without any help, but now I’m afraid to be STUCK!
Can one of you, experienced Homebridge users, give me a tip how I could proceed?
This weekend I 'd like to make it work…
These are the last steps I took a few minutes ago:
All went well with trial & error…
Fnally I also managed to create a required “homebridge” system user using “sudo” as my authorization wasn’t right… However, I couldn’t check if this user can write to that directory.
All seemed to go well until I did this (From NFARINA 's Github procedure):
* Then Enable and run the service (first time) with the following commands:
systemctl daemon-reload
systemctl enable homebridge
systemctl start homebridge
What happened on the Pi’s terminal screen?
pi@raspberrypi:/var/lib/homebridge $ systemctl daemon-reload
=> OK, seems fine…
pi@raspberrypi:/var/lib/homebridge $ systemctl enable homebridge
Failed to enable unit: File homebridge.service: No such file or directory
=> ERROR! ???
When I check the homebridge directory and “config.json” file, they both exist:
pi@raspberrypi:/var/lib/homebridge $ ls
config.json
Checking the homebridge status:
pi@raspberrypi:/var/lib/homebridge $ systemctl status homebridge
Unit homebridge.service could not be found.
=> STUCK!