Unable to run Homebridge on Bootup Raspberry Pi
See original GitHub issueI followed the instruction [https://github.com/nfarina/homebridge/wiki/Running-HomeBridge-on-a-Raspberry-Pi] to set up auto start on boot.
When I type sudo /etc/init.d/homebridge start
, it just doesn’t do anything
Issue Analytics
- State:
- Created 8 years ago
- Comments:22 (3 by maintainers)
Top Results From Across the Web
Program does not start after reboot - Raspberry Pi Forums
Program does not start after reboot ; Check the program is working correctly: Code: Select all sudo /etc/init.d/homebridge start · Code: Select ...
Read more >no longer starting after reboot of Raspberry Pi? : r/homebridge
If it restarts manually, it's not likely any corruption issues. Check the systemd settings and make sure it is still enabled for start...
Read more >Setup Homebridge to Start on Bootup | by Tim - Medium
I've recently been playing with Homebridge on my Raspberry Pi. I've setup my Harmony Hub and my wireless power outlets to be controlled...
Read more >How to install HomeBridge on a RaspberryPi and ... - YouTube
Install HomeBridge on a RaspberryPi and fix all of these is... ... try restarting your device. Your browser can't play this video.
Read more >How to Install Homebridge on a Raspberry Pi - MakeUseOf
This communication allows users to operate devices via Apple Home that they wouldn't be able to control natively. That opens up quite a...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Personally, I prefer to run Homebridge with forever.
Here’s my script in
/etc/init.d/homebridge
Just a quick tip, on latest Node, Homebridge is not located on /usr/local/lib but in /usr/lib. Just change the line
cmd="DEBUG=* /usr/local/bin/homebridge"
intocmd="DEBUG=* /usr/bin/homebridge"
and it works like a charm