Recent changes to hoobs require that node.js is on at least 10.17.0 while most installs on raspberry Pi are “stuck” on 10.15.2 or 10.16.0
I found that simply running standard updates for the raspberry Pi would not result in node.js getting updated and was being told 10.16.0 was the latest version despite hoobs telling me 12.16.2 was the latest. The small orange circle with exclamation informs a update is available but there is no mechanism from the UI to update.
I managed to upgrade using n – https://github.com/tj/n this is a node.js version manager and makes the upgrade process so simple.
Open Terminal in the UI from the top right three dots.
I deleted all npm cache, not ideal but I was still getting issues and this resolved:
sudo npm cache clean -f
Then I updated & installed n:
sudo npm install -g n sudo n stable
Now simply run n and the version number required to update
Hoobs is a simple Homebridge implementation, takes minuets to get up and running on a Raspberry Pi.
But as its on a Raspberry Pi you can also run other applications, for example AdGuard Home. AdGuard is a DNS AdBlocker, you simply run, configure and then set up your router with DNS IP of your AdGuard install. Your network devices will eventually start using this as their DNS. Its similar to piHole but better 🙂
Simply open your Hoobs Homebridge site which is usually http://hoobs.local/ From the three vertical dots on the far right select Terminal and install AdGuard
My commands are bold and this shows full output:
hoobs@hoobs:/var/lib/homebridge $ cd $HOME hoobs@hoobs:~ $ wget https://static.adguard.com/adguardhome/release/AdGuardHome_linux_arm.tar.gz --2019-10-09 13:52:29-- https://static.adguard.com/adguardhome/release/AdGuardHome_linux_arm.tar.gz Resolving static.adguard.com (static.adguard.com)... 22.214.171.124, 126.96.36.199, 2606:4700:10::6814:1e82, ... Connecting to static.adguard.com (static.adguard.com)|188.8.131.52|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 5280981 (5.0M) [application/octet-stream] Saving to: ‘AdGuardHome_linux_arm.tar.gz’
AdGuardHome_linux_arm.tar.gz 100%[========================================================>] 5.04M 6.61MB/s in 0.8s
hoobs@hoobs:~ $ tar xvf AdGuardHome_linux_arm.tar.gz AdGuardHome/ AdGuardHome/AdGuardHome AdGuardHome/LICENSE.txt AdGuardHome/README.md hoobs@hoobs:~ $ cd AdGuardHome/ hoobs@hoobs:~/AdGuardHome $ sudo ./AdGuardHome -s install 2019/10/09 13:53:03 [info] Service control action: install 2019/10/09 13:53:05 [info] Action install has been done successfully on linux-systemd 2019/10/09 13:53:05 [info] Service has been started 2019/10/09 13:53:05 [info] Almost ready! AdGuard Home is successfully installed and will automatically start on boot. There are a few more things that must be configured before you can use it. Click on the link below and follow the Installation Wizard steps to finish setup. 2019/10/09 13:53:05 [info] AdGuard Home is available on the following addresses: 2019/10/09 13:53:05 [info] Go to http://127.0.0.1:3000 2019/10/09 13:53:05 [info] Go to http://192.168.1.55:3000 hoobs@hoobs:~/AdGuardHome $
Thats’ it. AdGuard is now up and running at the IP address shown i the last output which is obviousy the same as your Hoobs IP. You then configure AdGuard via the web interface. The only setting to change is the interface port number as Hoobs is using 80 and 8080 so just pick something, I used 90. AdGuard will show in red if a conflict.