Homebridge integration question

Third party integrations Homebridge
1

I have successfully setup homebridge following this guide:

I was wondering which speech options there are, I am able to turn on the lights but I cant seem to find what to tell Siri to use scenes and switches.

2

@p0nts
To use scene with Siri, you must set scene in third party app, where you connect Homebridge… They must have options to set scene. After set up, must say, “set my I"m home scene” or " set my good morning scene"

3

@toomeowns thank you, I will have a look at that!

4

Hi am having problems installing Homebridge on my RPI i am using the -

root@HomeAssistantPi:~# sudo npm install -g homebridge --unsafe-perm

And it works upto a point and tries looking for -

[email protected] install /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/node_modules/srp/node_modules/bignum
node-pre-gyp install --fallback-to-build

node-pre-gyp ERR! Tried to download: https://rvagg-node.s3-us-west-2.amazonaws.com/bignum/v0.12.5/bignum-v0.12.5-node-v14-linux-arm.tar.gz
node-pre-gyp ERR! Pre-built binaries not found for [email protected] and [email protected] (node-v14 ABI) (falling back to source compile with node-gyp)

npm ERR! [email protected] install: node-pre-gyp install --fallback-to-build
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] install script ‘node-pre-gyp install --fallback-to-build’.
npm ERR! This is most likely a problem with the bignum package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-pre-gyp install --fallback-to-build
npm ERR! You can get their info via:
npm ERR! npm owner ls bignum
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR! /root/npm-debug.log

Not sure if anyone else is having the same problems as me…

6

Well, first of all, you are using the OLD version of node, v0.12.6, so I wouldn’t try getting anything to work unless you upgrade to Node v4 or Node v6 and you’ll probably find many of your problems will resolve themselves.

Node v4 is the stable recommended version for most people, but if you are doing major node development and want the cutting edge features, you can use Node v6, though some projects will only work with Node v4, so I’d still recommend that instead.

For Node v4:
Run these two lines as root or use sudo

curl -sL https://deb.nodesource.com/setup_4.x | bash -

apt-get install -y nodejs

For Node v6:
Run these two lines as root or use sudo

curl -sL https://deb.nodesource.com/setup_6.x | bash -

apt-get install -y nodejs

7

Hi jbardi

Thanks but it seems that my hardware is not capable of running the Node V4.

I am on the Raspberry Pi B.

You appear to be running on ARMv6 hardware. Unfortunately this is not currently supported by the NodeSource Linux distributions. Please use the ‘linux-armv6l’ binary tarballs available directly from nodejs.org for Node.js v4 and later.

I will have to try on a new Pi.

8

@cameron You can still install the newer Node on that RPi, should work with these instructions:

9

Thanks Cameron (Good name)

I will try it tommorow.

10

Hi

@cbulock i tried that and then installed homebridge with the following errors-

pi@RPI3:~ $ sudo su
root@RPI3:/home/pi# cd
root@RPI3:~# npm install homebridge --unsafe-perm

[email protected] install /root/node_modules/homebridge/node_modules/hap-nodejs/node_modules/curve25519
node-gyp rebuild

make: Entering directory ‘/root/node_modules/homebridge/node_modules/hap-nodejs/node_modules/curve25519/build’
CXX(target) Release/obj.target/curve/node_curve.o
SOLINK_MODULE(target) Release/obj.target/curve.node
COPY Release/curve.node
make: Leaving directory ‘/root/node_modules/homebridge/node_modules/hap-nodejs/node_modules/curve25519/build’

[email protected] install /root/node_modules/homebridge/node_modules/hap-nodejs/node_modules/ed25519
node-gyp rebuild

make: Entering directory ‘/root/node_modules/homebridge/node_modules/hap-nodejs/node_modules/ed25519/build’
CC(target) Release/obj.target/ed25519/src/ed25519/keypair.o
CC(target) Release/obj.target/ed25519/src/ed25519/sign.o
CC(target) Release/obj.target/ed25519/src/ed25519/open.o
CC(target) Release/obj.target/ed25519/src/ed25519/crypto_verify_32.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_double_scalarmult.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_frombytes.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_scalarmult_base.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_precomp_0.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_p2_0.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_p2_dbl.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_p3_0.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_p3_dbl.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_p3_to_p2.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_p3_to_cached.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_p3_tobytes.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_madd.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_add.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_msub.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_sub.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_p1p1_to_p3.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_p1p1_to_p2.o
CC(target) Release/obj.target/ed25519/src/ed25519/ge_tobytes.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_0.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_1.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_cmov.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_copy.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_neg.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_add.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_sub.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_mul.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_sq.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_sq2.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_invert.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_tobytes.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_isnegative.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_isnonzero.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_frombytes.o
CC(target) Release/obj.target/ed25519/src/ed25519/fe_pow22523.o
CC(target) Release/obj.target/ed25519/src/ed25519/sc_reduce.o
CC(target) Release/obj.target/ed25519/src/ed25519/sc_muladd.o
CXX(target) Release/obj.target/ed25519/src/ed25519.o
SOLINK_MODULE(target) Release/obj.target/ed25519.node
COPY Release/ed25519.node
make: Leaving directory ‘/root/node_modules/homebridge/node_modules/hap-nodejs/node_modules/ed25519/build’

[email protected] install /root/node_modules/homebridge/node_modules/hap-nodejs/node_modules/mdns
node-gyp rebuild

make: Entering directory ‘/root/node_modules/homebridge/node_modules/hap-nodejs/node_modules/mdns/build’
CXX(target) Release/obj.target/dns_sd_bindings/src/dns_sd.o
In file included from …/src/dns_sd.cpp:1:0:
…/src/mdns.hpp:32:20: fatal error: dns_sd.h: No such file or directory
#include <dns_sd.h>
^
compilation terminated.
dns_sd_bindings.target.mk:142: recipe for target ‘Release/obj.target/dns_sd_bindings/src/dns_sd.o’ failed
make: *** [Release/obj.target/dns_sd_bindings/src/dns_sd.o] Error 1
make: Leaving directory ‘/root/node_modules/homebridge/node_modules/hap-nodejs/node_modules/mdns/build’
gyp ERR! build error
gyp ERR! stack Error: make failed with exit code: 2
gyp ERR! stack at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:270:23)
gyp ERR! stack at emitTwo (events.js:87:13)
gyp ERR! stack at ChildProcess.emit (events.js:172:7)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:200:12)
gyp ERR! System Linux 4.4.13-v7+
gyp ERR! command “/usr/local/bin/node” “/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js” “rebuild”
gyp ERR! cwd /root/node_modules/homebridge/node_modules/hap-nodejs/node_modules/mdns
gyp ERR! node -v v4.0.0
gyp ERR! node-gyp -v v3.0.1
gyp ERR! not ok

[email protected] install /root/node_modules/homebridge/node_modules/hap-nodejs/node_modules/srp/node_modules/bignum
node-pre-gyp install --fallback-to-build

[bignum] Success: “/root/node_modules/homebridge/node_modules/hap-nodejs/node_modules/srp/node_modules/bignum/binding/bignum.node” is installed via remote
npm ERR! Linux 4.4.13-v7+
npm ERR! argv “/usr/local/bin/node” “/usr/local/bin/npm” “install” “homebridge” “–unsafe-perm”
npm ERR! node v4.0.0
npm ERR! npm v2.14.2
npm ERR! code ELIFECYCLE

npm ERR! [email protected] install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] install script ‘node-gyp rebuild’.
npm ERR! This is most likely a problem with the mdns package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-gyp rebuild
npm ERR! You can get their info via:
npm ERR! npm owner ls mdns
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR! /root/npm-debug.log

So its is a bit better. Oh and i got a new Pi3 as well.

Any help trying to get this working will be amazing.