marcoraddatz / homebridge-docker Goto Github PK

View Code? Open in Web Editor NEW

This project forked from leachbj/homebridge-docker

127.0 127.0 47.0 1.98 MB

Dockerized Homebridge. No plugins pre-defined, hassle-free setup. Read instructions!

License: Apache License 2.0

Shell 79.27% Dockerfile 20.73%

docker homebridge homebridge-plugin qnap raspberry-pi synology

homebridge-docker's People

Contributors

Stargazers

Watchers

Forkers

danimal4326 mry shenmao1989 torstenek josepba sjtek bebeboy axemann benzman81 herveb crhan dsgrafiniert charleyzhu punditsharp skyblue huhubros stenehall dmryglod asaboss moifort lumoc anthrow mscreations captainigloo aaronmitti jcmbowman baehyoungmin gyulkiller redth lyf3 jacobheidelbach sanxk xmmwc adysan xenderblade razer4908 etchalon 33419936 nelsonjunior fcenobi gavinfoo mirki68 paks petschni heeapapa cheechpurlington ycao56

homebridge-docker's Issues

Homebridge Version Upgrade?

Hi!
I am using this good working docker image, but

I can´t install the homebrige-telegram plugin, because the plugin reports, that the homebrige Version (0.4.33) is too old, 0,4.35 is needed, the latest version is 0.4.38.

Is there an possibility for an update?

Plugins are not installing

Hi,

I would like to install 2 plugins:
homebridge-homematic and homebridge-netatmo

my install.sh:
npm install -g homebridge-homematic npm install -g homebridge-netatmo

both plugins are not installed and so homebridge does not find and plugins and shuts down itself.

what to do?

Error:

�[37;40mnpm�[0m �[0m�[31;40mERR!�[0m�[35m�[0m Cannot read property 'path' of null
stdout
13:42:57

ffmpeg compiled with --enable-libfdk-aac / Audio

Hey, is there a way to install/compile ffmpeg with the flag --enable-libfdk-aac?
I need it for Audio support within ffmpeg.
Will try a apt-get install libfdk-aac-dev in the Dockerfile hopefully today and give feedback.

just found something: speedyyellow@14cbc35

Got error during Updating Homebridge.

I got this error during container start up. anyone could help?

EXDEV: cross-device link not permitted, rename '/usr/lib/node_modules/homebridge/node_modules/mkdirp' -> '/usr/lib/node_modules/homebridge/node_modules/.mkdirp.DELETE'

No status response to iOS-Device

Hey,

I messing around with homebridge a long time for now. Also developed a plugin but that's just for information.

After developing process I tried to put it all together in a docker image on my synology, but there my iOS devices didn't get a response from homebridge. This means I see my accessories but everyone has the state "no answer". In a VM in Virtual Box there is no problem homebridge and plugin fully working.

In my opinion there can only be two problem sources.

Docker
Synology it self (tried to disable firewall)

Did you have any suggestions?

Greetz, Xanta

Error: Cannot find module 'commander'

Each time I start your homebridge-docker-image, a error appears:

Error: Cannot find module 'commander'

I have to restart the container and then the error disappears.

Do you have an idea?

docker-compose.yml

    homebridge:
        container_name: homebridge
        expose:
            - "51826"
            - "5353"
        ports:
            - "51826:51826"
            - "5353:5353"
        image: marcoraddatz/homebridge:develop
        volumes:
            - ./homebridge/data/:/root/.homebridge
        network_mode: "host"

install.sh

#!/bin/bash

# This file gets executed as root, so you can use it to
# install or update any plugin dependencies.
# See https://github.com/marcoraddatz/homebridge-docker#installsh

npm install -g homebridge-fhem

config.json

{
  "bridge": {
    "name": "Homebridge FHEM",
    "username": "xx:xx:xx:xx:xx:3xx9",
    "port": 51826,
    "pin": "0xx-xx-xxx"
  },
  "platforms": [
    {
      "platform": "FHEM",
      "name": "FHEM",
      "server": "127.0.0.1",
      "port": "8083",
      "filter": "room=Homekit"
    }
  ],
  "accessories": []
}

Error

npm info it worked if it ends with ok
npm info using [email protected]
npm info using [email protected]
npm http fetch GET 200 https://registry.npmjs.org/homebridge 261ms
npm http fetch GET 200 https://registry.npmjs.org/qrcode-terminal 17ms
npm http fetch GET 200 https://registry.npmjs.org/chalk 131ms
npm http fetch GET 200 https://registry.npmjs.org/commander 186ms
npm http fetch GET 200 https://registry.npmjs.org/semver 242ms
npm http fetch GET 200 https://registry.npmjs.org/hap-nodejs 298ms
npm http fetch GET 304 https://registry.npmjs.org/node-persist 415ms (from cache)
npm http fetch GET 200 https://registry.npmjs.org/ansi-styles 113ms
npm http fetch GET 304 https://registry.npmjs.org/escape-string-regexp 362ms (from cache)
npm http fetch GET 304 https://registry.npmjs.org/has-ansi 406ms (from cache)
npm http fetch GET 304 https://registry.npmjs.org/strip-ansi 450ms (from cache)
npm http fetch GET 304 https://registry.npmjs.org/supports-color 495ms (from cache)
npm http fetch GET 304 https://registry.npmjs.org/ansi-regex 110ms (from cache)
npm http fetch GET 304 https://registry.npmjs.org/graceful-readlink 126ms (from cache)
npm http fetch GET 200 https://registry.npmjs.org/debug 147ms
npm http fetch GET 200 https://registry.npmjs.org/ip 224ms
npm http fetch GET 200 https://registry.npmjs.org/decimal.js 359ms
npm http fetch GET 304 https://registry.npmjs.org/buffer-shims 371ms (from cache)
npm http fetch GET 304 https://registry.npmjs.org/curve25519-n2 375ms (from cache)
npm http fetch GET 304 https://registry.npmjs.org/mdns 551ms (from cache)
npm http fetch GET 304 https://registry.npmjs.org/ed25519 599ms (from cache)
npm http fetch GET 304 https://registry.npmjs.org/fast-srp-hap 643ms (from cache)
npm http fetch GET 200 https://registry.npmjs.org/nan 126ms
npm http fetch GET 304 https://registry.npmjs.org/bindings 172ms (from cache)
npm http fetch GET 304 https://registry.npmjs.org/ms 117ms (from cache)
npm http fetch GET 200 https://registry.npmjs.org/mkdirp 80ms
npm http fetch GET 304 https://registry.npmjs.org/q 215ms (from cache)
npm http fetch GET 200 https://registry.npmjs.org/minimist 77ms
npm http fetch GET 200 https://registry.npmjs.org/homebridge/-/homebridge-0.4.31.tgz 44ms
npm http fetch GET 200 https://registry.npmjs.org/qrcode-terminal/-/qrcode-terminal-0.11.0.tgz 57ms
npm http fetch GET 200 https://registry.npmjs.org/hap-nodejs/-/hap-nodejs-0.4.36.tgz 110ms
npm info lifecycle [email protected]~preuninstall: [email protected]
npm info lifecycle [email protected]~uninstall: [email protected]
npm info lifecycle [email protected]~postuninstall: [email protected]
npm info lifecycle [email protected]~preuninstall: [email protected]
npm info lifecycle [email protected]~uninstall: [email protected]
npm info lifecycle [email protected]~postuninstall: [email protected]
npm info lifecycle [email protected]~preinstall: [email protected]
npm info lifecycle [email protected]~preinstall: [email protected]
npm info lifecycle [email protected]~preinstall: [email protected]
npm info linkStuff [email protected]
npm info linkStuff [email protected]
npm info linkStuff [email protected]
npm info lifecycle [email protected]~install: [email protected]
npm info lifecycle [email protected]~install: [email protected]
npm info lifecycle [email protected]~install: [email protected]
npm info lifecycle [email protected]~postinstall: [email protected]
npm info lifecycle [email protected]~postinstall: [email protected]
npm info lifecycle [email protected]~postinstall: [email protected]
�
 ok 
npm info it worked if it ends with ok
npm info using [email protected]
npm info using [email protected]
npm http fetch GET 200 https://registry.npmjs.org/homebridge-fhem 137ms
npm http fetch GET 200 https://registry.npmjs.org/request 19ms
npm http fetch GET 200 https://registry.npmjs.org/aws-sign2 25ms
npm http fetch GET 200 https://registry.npmjs.org/is-typedarray 17ms
npm http fetch GET 200 https://registry.npmjs.org/aws4 72ms
npm http fetch GET 200 https://registry.npmjs.org/extend 71ms
npm http fetch GET 200 https://registry.npmjs.org/caseless 74ms
npm http fetch GET 200 https://registry.npmjs.org/forever-agent 74ms
npm http fetch GET 200 https://registry.npmjs.org/combined-stream 76ms
npm http fetch GET 200 https://registry.npmjs.org/http-signature 72ms
npm http fetch GET 200 https://registry.npmjs.org/form-data 76ms
npm http fetch GET 200 https://registry.npmjs.org/isstream 33ms
npm http fetch GET 200 https://registry.npmjs.org/har-validator 78ms
npm http fetch GET 200 https://registry.npmjs.org/hawk 81ms
npm http fetch GET 200 https://registry.npmjs.org/json-stringify-safe 48ms
npm http fetch GET 200 https://registry.npmjs.org/oauth-sign 43ms
npm http fetch GET 200 https://registry.npmjs.org/performance-now 45ms
npm http fetch GET 200 https://registry.npmjs.org/mime-types 49ms
npm http fetch GET 200 https://registry.npmjs.org/safe-buffer 45ms
npm http fetch GET 200 https://registry.npmjs.org/stringstream 45ms
npm http fetch GET 200 https://registry.npmjs.org/qs 50ms
npm http fetch GET 200 https://registry.npmjs.org/tough-cookie 53ms
npm http fetch GET 200 https://registry.npmjs.org/tunnel-agent 37ms
npm http fetch GET 200 https://registry.npmjs.org/uuid 27ms
npm http fetch GET 200 https://registry.npmjs.org/delayed-stream 20ms
npm http fetch GET 200 https://registry.npmjs.org/asynckit 17ms
npm http fetch GET 200 https://registry.npmjs.org/mime-db 18ms
npm http fetch GET 200 https://registry.npmjs.org/har-schema 18ms
npm http fetch GET 200 https://registry.npmjs.org/ajv 23ms
npm http fetch GET 200 https://registry.npmjs.org/fast-deep-equal 24ms
npm http fetch GET 200 https://registry.npmjs.org/fast-json-stable-stringify 23ms
npm http fetch GET 200 https://registry.npmjs.org/co 26ms
npm http fetch GET 200 https://registry.npmjs.org/json-schema-traverse 28ms
npm http fetch GET 200 https://registry.npmjs.org/sntp 22ms
npm http fetch GET 200 https://registry.npmjs.org/hoek 23ms
npm http fetch GET 200 https://registry.npmjs.org/boom 25ms
npm http fetch GET 200 https://registry.npmjs.org/cryptiles 25ms
npm http fetch GET 200 https://registry.npmjs.org/jsprim 20ms
npm http fetch GET 200 https://registry.npmjs.org/sshpk 20ms
npm http fetch GET 200 https://registry.npmjs.org/assert-plus 23ms
npm http fetch GET 200 https://registry.npmjs.org/verror 19ms
npm http fetch GET 200 https://registry.npmjs.org/extsprintf 20ms
npm http fetch GET 200 https://registry.npmjs.org/json-schema 25ms
npm http fetch GET 200 https://registry.npmjs.org/core-util-is 17ms
npm http fetch GET 200 https://registry.npmjs.org/tweetnacl 38ms
npm http fetch GET 200 https://registry.npmjs.org/asn1 40ms
npm http fetch GET 200 https://registry.npmjs.org/jsbn 45ms
npm http fetch GET 200 https://registry.npmjs.org/bcrypt-pbkdf 44ms
npm http fetch GET 200 https://registry.npmjs.org/dashdash 47ms
npm http fetch GET 200 https://registry.npmjs.org/getpass 47ms
npm http fetch GET 200 https://registry.npmjs.org/ecc-jsbn 47ms
npm http fetch GET 200 https://registry.npmjs.org/punycode 17ms
npm http fetch GET 200 https://registry.npmjs.org/hoek/-/hoek-4.2.0.tgz 214ms
npm http fetch GET 200 https://registry.npmjs.org/json-schema-traverse/-/json-schema-traverse-0.3.1.tgz 212ms
npm http fetch GET 200 https://registry.npmjs.org/caseless/-/caseless-0.12.0.tgz 228ms
npm http fetch GET 200 https://registry.npmjs.org/aws-sign2/-/aws-sign2-0.7.0.tgz 229ms
npm http fetch GET 200 https://registry.npmjs.org/dashdash/-/dashdash-1.14.1.tgz 228ms
npm http fetch GET 200 https://registry.npmjs.org/cryptiles/-/cryptiles-3.1.2.tgz 224ms
npm http fetch GET 200 https://registry.npmjs.org/jsbn/-/jsbn-0.1.1.tgz 223ms
npm http fetch GET 200 https://registry.npmjs.org/assert-plus/-/assert-plus-1.0.0.tgz 231ms
npm http fetch GET 200 https://registry.npmjs.org/co/-/co-4.6.0.tgz 229ms
npm http fetch GET 200 https://registry.npmjs.org/delayed-stream/-/delayed-stream-1.0.0.tgz 229ms
npm http fetch GET 200 https://registry.npmjs.org/aws4/-/aws4-1.6.0.tgz 230ms
npm http fetch GET 200 https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.2.tgz 229ms
npm http fetch GET 200 https://registry.npmjs.org/fast-json-stable-stringify/-/fast-json-stable-stringify-2.0.0.tgz 227ms
npm http fetch GET 200 https://registry.npmjs.org/fast-deep-equal/-/fast-deep-equal-1.0.0.tgz 229ms
npm http fetch GET 200 https://registry.npmjs.org/har-schema/-/har-schema-2.0.0.tgz 228ms
npm http fetch GET 200 https://registry.npmjs.org/boom/-/boom-5.2.0.tgz 227ms
npm http fetch GET 200 https://registry.npmjs.org/is-typedarray/-/is-typedarray-1.0.0.tgz 226ms
npm http fetch GET 200 https://registry.npmjs.org/ecc-jsbn/-/ecc-jsbn-0.1.1.tgz 226ms
npm http fetch GET 200 https://registry.npmjs.org/har-validator/-/har-validator-5.0.3.tgz 226ms
npm http fetch GET 200 https://registry.npmjs.org/boom/-/boom-4.3.1.tgz 229ms
npm http fetch GET 200 https://registry.npmjs.org/json-stringify-safe/-/json-stringify-safe-5.0.1.tgz 226ms
npm http fetch GET 200 https://registry.npmjs.org/json-schema/-/json-schema-0.2.3.tgz 236ms
npm http fetch GET 200 https://registry.npmjs.org/extsprintf/-/extsprintf-1.3.0.tgz 240ms
npm http fetch GET 200 https://registry.npmjs.org/performance-now/-/performance-now-2.1.0.tgz 237ms
npm http fetch GET 200 https://registry.npmjs.org/asn1/-/asn1-0.2.3.tgz 250ms
npm http fetch GET 200 https://registry.npmjs.org/combined-stream/-/combined-stream-1.0.5.tgz 247ms
npm http fetch GET 200 https://registry.npmjs.org/forever-agent/-/forever-agent-0.6.1.tgz 247ms
npm http fetch GET 200 https://registry.npmjs.org/isstream/-/isstream-0.1.2.tgz 244ms
npm http fetch GET 200 https://registry.npmjs.org/extend/-/extend-3.0.1.tgz 249ms
npm http fetch GET 200 https://registry.npmjs.org/asynckit/-/asynckit-0.4.0.tgz 251ms
npm http fetch GET 200 https://registry.npmjs.org/getpass/-/getpass-0.1.7.tgz 252ms
npm http fetch GET 200 https://registry.npmjs.org/form-data/-/form-data-2.3.1.tgz 246ms
npm http fetch GET 200 https://registry.npmjs.org/oauth-sign/-/oauth-sign-0.8.2.tgz 251ms
npm http fetch GET 200 https://registry.npmjs.org/punycode/-/punycode-1.4.1.tgz 251ms
npm http fetch GET 200 https://registry.npmjs.org/mime-types/-/mime-types-2.1.17.tgz 257ms
npm http fetch GET 200 https://registry.npmjs.org/mime-db/-/mime-db-1.30.0.tgz 263ms
npm http fetch GET 200 https://registry.npmjs.org/safe-buffer/-/safe-buffer-5.1.1.tgz 261ms
npm http fetch GET 200 https://registry.npmjs.org/bcrypt-pbkdf/-/bcrypt-pbkdf-1.0.1.tgz 263ms
npm http fetch GET 200 https://registry.npmjs.org/stringstream/-/stringstream-0.0.5.tgz 271ms
npm http fetch GET 200 https://registry.npmjs.org/tunnel-agent/-/tunnel-agent-0.6.0.tgz 269ms
npm http fetch GET 200 https://registry.npmjs.org/hawk/-/hawk-6.0.2.tgz 272ms
npm http fetch GET 200 https://registry.npmjs.org/sntp/-/sntp-2.1.0.tgz 276ms
npm http fetch GET 200 https://registry.npmjs.org/qs/-/qs-6.5.1.tgz 278ms
npm http fetch GET 200 https://registry.npmjs.org/verror/-/verror-1.10.0.tgz 274ms
npm http fetch GET 200 https://registry.npmjs.org/jsprim/-/jsprim-1.4.1.tgz 274ms
npm http fetch GET 200 https://registry.npmjs.org/tough-cookie/-/tough-cookie-2.3.3.tgz 286ms
npm http fetch GET 200 https://registry.npmjs.org/tweetnacl/-/tweetnacl-0.14.5.tgz 284ms
npm http fetch GET 200 https://registry.npmjs.org/uuid/-/uuid-3.1.0.tgz 283ms
npm http fetch GET 200 https://registry.npmjs.org/sshpk/-/sshpk-1.13.1.tgz 290ms
npm http fetch GET 200 https://registry.npmjs.org/http-signature/-/http-signature-1.2.0.tgz 63ms
npm http fetch GET 200 https://registry.npmjs.org/homebridge-fhem/-/homebridge-fhem-0.3.7.tgz 65ms
npm http fetch GET 200 https://registry.npmjs.org/request/-/request-2.83.0.tgz 68ms
npm http fetch GET 200 https://registry.npmjs.org/ajv/-/ajv-5.3.0.tgz 342ms
npm info lifecycle [email protected]~preinstall: [email protected]
npm info lifecycle [email protected]~preinstall: [email protected]
npm info lifecycle [email protected]~preinstall: [email protected]
npm info lifecycle [email protected]~preinstall: [email protected]
npm info lifecycle [email protected]~preinstall: [email protected]
npm info lifecycle [email protected]~preinstall: [email protected]
npm info lifecycle [email protected]~preinstall: [email protected]
npm info lifecycle [email protected]~preinstall: [email protected]
npm info lifecycle [email protected]~preinstall: [email protected]
npm info lifecycle [email protected]~preinstall: [email protected]
npm info lifecycle [email protected]~preinstall: [email protected]
npm info lifecycle [email protected]~preinstall: [email protected]
npm info lifecycle [email protected]~preinstall: [email protected]
npm info lifecycle [email protected]~preinstall: [email protected]
npm info lifecycle [email protected]~preinstall: [email protected]
npm info lifecycle [email protected]~preinstall: [email protected]
npm info lifecycle [email protected]~preinstall: [email protected]
npm info lifecycle [email protected]~preinstall: [email protected]
npm info lifecycle [email protected]~preinstall: [email protected]
npm info lifecycle [email protected]~preinstall: [email protected]
npm info lifecycle [email protected]~preinstall: [email protected]
npm info lifecycle [email protected]~preinstall: [email protected]
npm info lifecycle [email protected]~preinstall: [email protected]
npm info lifecycle [email protected]~preinstall: [email protected]
npm info lifecycle [email protected]~preinstall: [email protected]
npm info lifecycle [email protected]~preinstall: [email protected]
npm info lifecycle [email protected]~preinstall: [email protected]
npm info lifecycle [email protected]~preinstall: [email protected]
npm info lifecycle [email protected]~preinstall: [email protected]
npm info lifecycle [email protected]~preinstall: [email protected]
npm info lifecycle [email protected]~preinstall: [email protected]
npm info lifecycle [email protected]~preinstall: [email protected]
npm info lifecycle [email protected]~preinstall: [email protected]
npm info lifecycle [email protected]~preinstall: [email protected]
npm info lifecycle [email protected]~preinstall: [email protected]
npm info lifecycle [email protected]~preinstall: [email protected]
npm info lifecycle [email protected]~preinstall: [email protected]
npm info lifecycle [email protected]~preinstall: [email protected]
npm info lifecycle [email protected]~preinstall: [email protected]
npm info lifecycle [email protected]~preinstall: [email protected]
npm info lifecycle [email protected]~preinstall: [email protected]
npm info lifecycle [email protected]~preinstall: [email protected]
npm info lifecycle [email protected]~preinstall: [email protected]
npm info lifecycle [email protected]~preinstall: [email protected]
npm info lifecycle [email protected]~preinstall: [email protected]
npm info lifecycle [email protected]~preinstall: [email protected]
npm info lifecycle [email protected]~preinstall: [email protected]
npm info lifecycle [email protected]~preinstall: [email protected]
npm info lifecycle [email protected]~preinstall: [email protected]
npm info lifecycle [email protected]~preinstall: [email protected]
npm info lifecycle [email protected]~preinstall: [email protected]
npm info lifecycle [email protected]~preinstall: [email protected]
npm info lifecycle [email protected]~preinstall: [email protected]
npm info linkStuff [email protected]
npm info linkStuff [email protected]
npm info linkStuff [email protected]
npm info linkStuff [email protected]
npm info linkStuff [email protected]
npm info linkStuff [email protected]
npm info linkStuff [email protected]
npm info linkStuff [email protected]
npm info linkStuff [email protected]
npm info linkStuff [email protected]
npm info linkStuff [email protected]
npm info linkStuff [email protected]
npm info linkStuff [email protected]
npm info linkStuff [email protected]
npm info linkStuff [email protected]
npm info linkStuff [email protected]
npm info linkStuff [email protected]
npm info linkStuff [email protected]
npm info linkStuff [email protected]
npm info linkStuff [email protected]
npm info linkStuff [email protected]
npm info linkStuff [email protected]
npm info linkStuff [email protected]
npm info linkStuff [email protected]
npm info linkStuff [email protected]
npm info linkStuff [email protected]
npm info linkStuff [email protected]
npm info linkStuff [email protected]
npm info linkStuff [email protected]
npm info linkStuff [email protected]
npm info linkStuff [email protected]
npm info linkStuff [email protected]
npm info linkStuff [email protected]
npm info linkStuff [email protected]
npm info linkStuff [email protected]
npm info linkStuff [email protected]
npm info linkStuff [email protected]
npm info linkStuff [email protected]
npm info linkStuff [email protected]
npm info linkStuff [email protected]
npm info linkStuff [email protected]
npm info linkStuff [email protected]
npm info linkStuff [email protected]
npm info linkStuff [email protected]
npm info linkStuff [email protected]
npm info linkStuff [email protected]
npm info linkStuff [email protected]
npm info linkStuff [email protected]
npm info linkStuff [email protected]
npm info linkStuff [email protected]
npm info linkStuff [email protected]
npm info linkStuff [email protected]
npm info linkStuff [email protected]
npm info lifecycle [email protected]~install: [email protected]
npm info lifecycle [email protected]~install: [email protected]
npm info lifecycle [email protected]~install: [email protected]
npm info lifecycle [email protected]~install: [email protected]
npm info lifecycle [email protected]~install: [email protected]
npm info lifecycle [email protected]~install: [email protected]
npm info lifecycle [email protected]~install: [email protected]
npm info lifecycle [email protected]~install: [email protected]
npm info lifecycle [email protected]~install: [email protected]
npm info lifecycle [email protected]~install: [email protected]
npm info lifecycle [email protected]~install: [email protected]
npm info lifecycle [email protected]~install: [email protected]
npm info lifecycle [email protected]~install: [email protected]
npm info lifecycle [email protected]~install: [email protected]
npm info lifecycle [email protected]~install: [email protected]
npm info lifecycle [email protected]~install: [email protected]
npm info lifecycle [email protected]~install: [email protected]
npm info lifecycle [email protected]~install: [email protected]
npm info lifecycle [email protected]~install: [email protected]
npm info lifecycle [email protected]~install: [email protected]
npm info lifecycle [email protected]~install: [email protected]
npm info lifecycle [email protected]~install: [email protected]
npm info lifecycle [email protected]~install: [email protected]
npm info lifecycle [email protected]~install: [email protected]
npm info lifecycle [email protected]~install: [email protected]
npm info lifecycle [email protected]~install: [email protected]
npm info lifecycle [email protected]~install: [email protected]
npm info lifecycle [email protected]~install: [email protected]
npm info lifecycle [email protected]~install: [email protected]
npm info lifecycle [email protected]~install: [email protected]
npm info lifecycle [email protected]~install: [email protected]
npm info lifecycle [email protected]~install: [email protected]
npm info lifecycle [email protected]~install: [email protected]
npm info lifecycle [email protected]~install: [email protected]
npm info lifecycle [email protected]~install: [email protected]
npm info lifecycle [email protected]~install: [email protected]
npm info lifecycle [email protected]~install: [email protected]
npm info lifecycle [email protected]~install: [email protected]
npm info lifecycle [email protected]~install: [email protected]
npm info lifecycle [email protected]~install: [email protected]
npm info lifecycle [email protected]~install: [email protected]
npm info lifecycle [email protected]~install: [email protected]
npm info lifecycle [email protected]~install: [email protected]
npm info lifecycle [email protected]~install: [email protected]
npm info lifecycle [email protected]~install: [email protected]
npm info lifecycle [email protected]~install: [email protected]
npm info lifecycle [email protected]~install: [email protected]
npm info lifecycle [email protected]~install: [email protected]
npm info lifecycle [email protected]~install: [email protected]
npm info lifecycle [email protected]~install: [email protected]
npm info lifecycle [email protected]~install: [email protected]
npm info lifecycle [email protected]~install: [email protected]
npm info lifecycle [email protected]~install: [email protected]
npm info lifecycle [email protected]~postinstall: [email protected]
npm info lifecycle [email protected]~postinstall: [email protected]
npm info lifecycle [email protected]~postinstall: [email protected]
npm info lifecycle [email protected]~postinstall: [email protected]
npm info lifecycle [email protected]~postinstall: [email protected]
npm info lifecycle [email protected]~postinstall: [email protected]
npm info lifecycle [email protected]~postinstall: [email protected]
npm info lifecycle [email protected]~postinstall: [email protected]
npm info lifecycle [email protected]~postinstall: [email protected]
npm info lifecycle [email protected]~postinstall: [email protected]
npm info lifecycle [email protected]~postinstall: [email protected]
npm info lifecycle [email protected]~postinstall: [email protected]
npm info lifecycle [email protected]~postinstall: [email protected]
npm info lifecycle [email protected]~postinstall: [email protected]
npm info lifecycle [email protected]~postinstall: [email protected]
npm info lifecycle [email protected]~postinstall: [email protected]
npm info lifecycle [email protected]~postinstall: [email protected]
npm info lifecycle [email protected]~postinstall: [email protected]
npm info lifecycle [email protected]~postinstall: [email protected]
npm info lifecycle [email protected]~postinstall: [email protected]
npm info lifecycle [email protected]~postinstall: [email protected]
npm info lifecycle [email protected]~postinstall: [email protected]
npm info lifecycle [email protected]~postinstall: [email protected]
npm info lifecycle [email protected]~postinstall: [email protected]
npm info lifecycle [email protected]~postinstall: [email protected]
npm info lifecycle [email protected]~postinstall: [email protected]
npm info lifecycle [email protected]~postinstall: [email protected]
npm info lifecycle [email protected]~postinstall: [email protected]
npm info lifecycle [email protected]~postinstall: [email protected]
npm info lifecycle [email protected]~postinstall: [email protected]
npm info lifecycle [email protected]~postinstall: [email protected]
npm info lifecycle [email protected]~postinstall: [email protected]
npm info lifecycle [email protected]~postinstall: [email protected]
npm info lifecycle [email protected]~postinstall: [email protected]
npm info lifecycle [email protected]~postinstall: [email protected]
npm info lifecycle [email protected]~postinstall: [email protected]
npm info lifecycle [email protected]~postinstall: [email protected]
npm info lifecycle [email protected]~postinstall: [email protected]
npm info lifecycle [email protected]~postinstall: [email protected]
npm info lifecycle [email protected]~postinstall: [email protected]
npm info lifecycle [email protected]~postinstall: [email protected]
npm info lifecycle [email protected]~postinstall: [email protected]
npm info lifecycle [email protected]~postinstall: [email protected]
npm info lifecycle [email protected]~postinstall: [email protected]
npm info lifecycle [email protected]~postinstall: [email protected]
npm info lifecycle [email protected]~postinstall: [email protected]
npm info lifecycle [email protected]~postinstall: [email protected]
npm info lifecycle [email protected]~postinstall: [email protected]
npm info lifecycle [email protected]~postinstall: [email protected]
npm info lifecycle [email protected]~postinstall: [email protected]
npm info lifecycle [email protected]~postinstall: [email protected]
npm info lifecycle [email protected]~postinstall: [email protected]
npm info lifecycle [email protected]~postinstall: [email protected]
�
 ok 
module.js:529
    throw err;
    ^

Error: Cannot find module 'commander'
    at Function.Module._resolveFilename (module.js:527:15)
    at Function.Module._load (module.js:476:23)
    at Module.require (module.js:568:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (/usr/local/lib/node_modules/homebridge/lib/cli.js:1:77)
    at Module._compile (module.js:624:30)
    at Object.Module._extensions..js (module.js:635:10)
    at Module.load (module.js:545:32)
    at tryModuleLoad (module.js:508:12)
    at Function.Module._load (module.js:500:3)

Home App does not find my homebridge anymore

Hi there,

frist my Homebridge was running on a Raspberry Pi2 - but I had a lot of stability problems.
So I installed your Hombridge docker container on my Synology and it really worked perfectly!

But since a few days my home app (2 iPhones an 1 iPad) does not find my homebridge any more... Any clue why?

Is there a known problem with iOS 11.2?
Or is there a known problem with the new DSM 6.1.4-15217 Update 2 from November 2017?

How can I see if I am running the latest version of your hombebridge-docker?
I have chosen "latest" for downloading - but this was weeks (or months) ago. Does the docker container update itself? or do I have to update it manually? How?

Thank you?

ios device No status

hello, marcoraddatz

i got some trouble when i using homebridge-docker.
here is error information.
any help or tips will be appreciated.
thanks.

ver

ios ver.10.3.2   
synology ver.6.1-15047 Update 2
marcoraddatz/homebridge-docker latest ver
Docker version 1.11.2 (docker --version)

error

2017-05-20 14:14:13	stdout	[37m[5/20/2017, 2:14:13 PM][39m [36m[Diskstation][39m An error occured while getting CpuLoad: null
2017-05-20 14:14:13	stdout	[37m[5/20/2017, 2:14:13 PM][39m [36m[Diskstation][39m An error occured while getting DiskUsage: null
2017-05-20 14:14:12	stdout	[37m[5/20/2017, 2:14:12 PM][39m [36m[Diskstation][39m An error occured while getting CpuLoad: null
2017-05-20 14:14:12	stdout	[37m[5/20/2017, 2:14:12 PM][39m [36m[Diskstation][39m An error occured while getting DiskUsage: null
2017-05-20 14:14:06	stdout	[37m[5/20/2017, 2:14:06 PM][39m Homebridge is running on port 51826.
2017-05-20 14:14:06	stdout	[30m[47m                       [49m[39m
2017-05-20 14:14:06	stdout	[30m[47m    └────────────┘     [49m[39m
2017-05-20 14:14:06	stdout	[30m[47m    │ 031-45-154 │     [49m[39m
2017-05-20 14:14:06	stdout	[30m[47m    ┌────────────┐     [49m[39m
2017-05-20 14:14:06	stdout	[30m[47m                       [49m[39m
2017-05-20 14:14:06	stdout	Scan this code with your HomeKit App on your iOS device to pair with Homebridge:
2017-05-20 14:14:06	stdout	[37m[5/20/2017, 2:14:06 PM][39m [36m[Diskstation][39m Initializing Synology accessory...
2017-05-20 14:14:06	stdout	[37m[5/20/2017, 2:14:06 PM][39m Loading 1 accessories...
2017-05-20 14:14:06	stdout	[37m[5/20/2017, 2:14:06 PM][39m ---
2017-05-20 14:14:06	stdout	[37m[5/20/2017, 2:14:06 PM][39m Loaded config.json with 1 accessories and 0 platforms.
2017-05-20 14:14:06	stdout	[37m[5/20/2017, 2:14:06 PM][39m ---
2017-05-20 14:14:06	stdout	[37m[5/20/2017, 2:14:06 PM][39m Registering accessory 'homebridge-synology.Synology'
2017-05-20 14:14:06	stdout	[37m[5/20/2017, 2:14:06 PM][39m Loaded plugin: homebridge-synology
2017-05-20 14:14:05	stdout	npm info ok 
2017-05-20 14:14:05	stdout	npm info using [email protected]
2017-05-20 14:14:05	stdout	npm info using [email protected]
2017-05-20 14:14:05	stdout	npm info it worked if it ends with ok

install.sh

#!/bin/sh

npm install -g homebridge-synology

config.js

{
    "bridge": {
        "name": "Homebridge",
        "username": "CC:22:3D:E3:CE:51",
        "port": 51826,
        "pin": "031-45-154"
    },
    "description": "This is an example configuration file for homebridge synology plugin",
    "hint": "Always paste into jsonlint.com validation page before starting your homebridge, saves a lot of frustration",
    "accessories": [
        {
            "accessory": "Synology",
            "name": "Diskstation",
            "ip": "192.168.1.21",
            "mac": "00:11:32:XX:XX:XX",
            "port": "5000",
            "secure": false,
            "account": "admin",
            "password": "password",
            "version": 5,
            "timeout": 5000,
            "disabled": ["switch", "temp"]
        }
    ]
}

Build for Raspberry Pi

The README says the Docker image works for Raspberry Pi, but as far as I can see there’s only a build for the amd64 architecture. Do I have to build my own to get it going on an ARM device or did I miss something?

Enhancement request:select image version as HOMEBRIDGE_VERSION

i noticed that you can force specific versions in the .env file
the versions to choose from are either the npm range or the release tag.
however it would be easier to choose the package version

eg : image version 4.1 seems to correspond with 0.4.33 so why can we not choose 4.1 as HOMEBRIDGE_VERSION

otherwise is there a list so we know which image version corresponds with which release tag

EISDIR error after minor change to config.json

After adding an SSL Cert to my Synology I decided to add SSL options in config.json for Homebridge, they didn’t work so I changed them back. Now I get the following EISDIR error everytime I try to loads Homebridge and the docker stops.

https://hastebin.com/kawuwikoyu.js

I’ve downloaded the docker again and checked and double checked the config.json and can’t see an issue. Help!

Doesn't not work with VPN - help

Hello

Homebridge through docker works really well on my Synology. However, as soon as I turn on the vpn on my Synology, homebridge stops working.

is there any way around it where I can use vpn and also have homebridge working?

Any help will be appreciated.

thanks again to Marco for making this docker image. KUDOS :)

How can I change it to use the latest homebridge release?

Starting the docker shows v0.4.6, but latest is v0.4.16.

Is it possible to change it on my side, if not, could you update it?

Homebridge Docker stopping unexpectedly every minute.

I've been using Homebridge successfully for half a year. Last week I updated DSM to 6.1.4-15217 Update 2 and Docker version 17.05.0-0349 to and now I can't get homebridge to run. According to the log, it doesn't appear to be installing the most recent versions of Homebridge or npm. Can anyone provide some insight?

I'm running marcoraddatz/homebridge: latest .

My install.sh:

#!/bin/bash

npm install -g homebridge-synology
npm install -g homebridge-lifx-lan
npm install -g homebridge-platform-wemo

My config.jsaon:

{
  "bridge": {
    "name": "Homebridge",
    "username": "CC:22:3D:E3:CE:30",
    "port": 51826,
    "pin": "031-45-154"
  },
  "description": "Muh Hoom",
  "platforms": [
    {
     "platform": "BelkinWeMo",
     "name": "WeMo Platform"
    },
    {
      "platform": "Lifx-Lan",
      "name": "LiFx",
      "access_token": "cee1a73f9e81c67e00294ce90750461dd8cd921aa2a2fdf10db4063ebdca6c24"
    }
  ]
}

The log file (is long... sorry):
marcoraddatz-homebridge1_Log.pdf

Add option to run under specific UID/GID

Is this possible right now? Can't find. I'm not all too comfortable running it as root. That would be a great addition!

Upgrade to Debian stretch

Currently jessie is used, but for some addons I need the actual stabel veriosn of Debian "stretch".
Any plans to upgrade?

homebridge command not found

hi, I just restarted my Synology after a few weeks and homebridge is no more working. I diddnt do any changes, it have been working foor some months now.
In the logfile of the container I can see:

/root/run.sh: line 69: homebridge: command not found
stdout
06:56:11
Logged in as:
stdout
06:56:11
root
stdout
06:56:11
/root/.homebridge/.env not found.
stdout
06:56:11
Default env variables will be used.
stdout
06:56:11
Updating Homebridge.

This is repeated every time after the homepridge plugin installation succeeded, so the starting process is in an endless loop.

what could i do?

Starting homebridge with elevated privileges

I am trying to run the plugin homebridge-amazondash. To use this plugin, homebridge needs to be run with elevated privileges (sudo). Is there any way to autostart homebridge with sudo?

By the way I installed sudo (apt-get install sudo), but when I runsudo homebridge, I get the following error:
sudo: unable to send audit message: Unknown error -1
sudo: pam_open_session: System error
sudo: policy plugin failed session initialization

Auto-update Node.js to newer version

is there an way to update the node.js to 7.6 ?

Home App under iOS 11.2.1 does not find device

Hello,

I am currently using the Homebridge on a Raspberry Pi 3 in combination with the following plugins:

homebridge-config-ui
homebridge-homematic
homebridge-broadlink-rm
homebridge-http-simple-switch
homebridge-fritz

Everything is up to date and works fine so far.

Now, I planned to move the Homebridge into a Docker container on my DS718+. The installation worked flawlessly and the Homebridge started without any error message (except from the well known warnings). See here and here for more details. However, my problem is that in contrast to the Raspi installation now the Home App under iOS 11.2.1 can not find the respective device anymore. I have installed no firewall under DSM 6.1. Do you have any idea what to do?

Cheers,

Thorsten

node.js version

I have a problem while startup the npm - homebridge-broadlink-rm. The Author suggested me to upgrade node to the latest version. Could you please share me some hints? Sorry that I am not good at programming stuff.

After update to DSM 6.2 beta, the home APP can't pair with homebridge.

Just tried DSM 6.2 beta and reset up homebridge. After all the docker homebridge setting up, home app in iOS 11 can't find homebridge.

Homebridge has been set up properly.

I tried to change the name and the port of homebridge, still doesn't work.

Problem running docker version 4.0

Hello,

I have problem running docker version 4.0.

I have one old "latest" which is working fine and all just start.
If I want to start 4.0 package with same settings and same plugins and all instead of older one.

In image section of docker I have this:
one container with latest - this one works for me (782 MB)
one container with 3.1 - this one stops after 1 min.(784 MB)
one container with 4.0 - this stops after 1 min. (1 GB)

do you have hint why ?
I believe I need to use some new version due to iOS 11 coz current version is not reachable on my phone.

Any hints ? Is there any difference between install.sh and directory location ? See mine. 3.0 works fine.
I have just 3 plugins.

I found in the log this:
This is related to npm not being able to find a file. Q: was there change in this between 3.0 and 3.1 or 4.0 ?
and end error: Error: The requested platform 'Nest' was not registered by any plugin.

thank you !

Milan

No response in my iPhone

I download the latest version of the image, Run with you step by step. But nothing happens on my iPhone

here goes the config.json

{
"bridge": {
"name": "Homebridge",
"username": "CC:22:3D:E3:CE:72",
"port": 51826,
"pin": "031-45-154"
},
"description": "This is an example configuration file with one fake accessory and one fake platform. You can use this as a template for creating your own configuration file containing devices you actually own.",
"accessories": [
]
}

and the install.sh is empty

logs in the docker's terminal

*** WARNING *** The program 'nodejs' uses the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see http://0pointer.de/avahi-compat?s=libdns_sd&e=nodejs
*** WARNING *** The program 'nodejs' called 'DNSServiceRegister()' which is not supported (or only supported partially) in the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see http://0pointer.de/avahi-compat?s=libdns_sd&e=nodejs&f=DNSServiceRegister
[4/18/2017, 6:35:39 PM] No plugins found. See the README for information on installing plugins.
[4/18/2017, 6:35:39 PM] Loaded config.json with 0 accessories and 0 platforms.
[4/18/2017, 6:35:39 PM] ---
[4/18/2017, 6:35:39 PM] Loading 0 accessories...
Scan this code with your HomeKit App on your iOS device to pair with Homebridge:
┌────────────┐                                                                                                                                                          
│ 031-45-154 │                                                                                                                                                          
└────────────┘                                                                                                                                                          
[4/18/2017, 6:35:39 PM] Homebridge is running on port 51826.

everything seems well but I can't find the bridge in my iPhone, and find it immediate by Mac homebridge server.

run docker ps

try many times... T_T

QNAP setup using Container Station

Thanks for this project! Adding instructions for QNAP setup.

Setting up Homebridge using QNAP Containers

Ensure that Container Station is installed via the QNAP App Center
Create a new container for using this projects docker container
Create a friendly name (can be anything), make sure "auto start" is selected, and adjust the container's resources based on that you can afford allocating.
Click Advanced Settings > Network and change the Network Mode to Bridge. I found if you do not do this your phone will not be able to communicate w Homebridge, and scanning the QR Code will result in the iOS Homekit app spinning.
Click Advanced Settings > Shared Folders and map a QNAP folder to /root/.homebridge. If you want to create a special folder, open QNAP's File Station, and make a new folder (I created one named "Homebridge". This shared folder will let you modify the Homebridge config files without dealing ssh'ing into the docker container.
Create the docker container; this may take some time (its 1.1GB) so check the Container Station background tasks to quickly see the status.
Once the container is up, SFTP your homebridge files into the shared folder (Step 5), and restart the container via the Container Station WebUI, and watch the console until the QR Code appears.
- install.sh
- config.json
Open Homekit app on your iOS (making sure that the iOS device is on the same network at the QNAP adapter bridged to this container in Step 4) scan the QR code in the container console and everything should link up!

how do i know what ports to forward before running the container?

I have two platforms in my config.json file. On running the container I see something like this

[2018-6-26 15:59:59] Homebridge is running on port 51826.
[2018-6-26 15:59:59] Camera Name is running on port 34575.

How do I know what port the camera is going to run on? I dont think there in a way to port forward on an existing container, is there?

Using apt-get upgrade

Looking at the best practices for a Docker container, the use of apt-get upgrade is not recommended

Source: https://docs.docker.com/engine/userguide/eng-image/dockerfile_best-practices/

Homebridge not showing up in Home App

Hi guys, I really need help... I'm trying to deploy your docker image on my server which is a CentOS 7 host with docker running a Portainer web ui to deploy containers. Everything seems to go well on the container side. But I can't the the homebridge in my phone's Home App.

What I tried :

Change username (MAC address)
Change PIN code
With or without accessories
Deleting persist folder

Here is my config.json:

{
    "bridge": {
        "name": "Homebridge",
        "username": "CC:22:3D:E3:CE:20",
        "port": 51826,
        "pin": "031-45-140"
    },

    "description": "This is an example configuration file with one fake accessory and one fake platform. You can use this as a template for creating your own configuration file containing devices you actually own.",

    "accessories": [
        {
                "accessory": "mqtt-switch-tasmota",
                "name": "Lamp",
                "url": "mqtt://192.168.2.19",
                "username": "",
                "password": "",
                "topics": {
                        "statusGet": "stat/sonoff/POWER",
                        "statusSet": "cmnd/sonoff/POWER"
                }
        }
    ],

    "platforms": [
    ]
}

My install.sh file :

#!/bin/bash

# npm install -g homebridge-camera-ffmpeg
npm install -g homebridge-mqtt-switch-tasmota

What the container outputs :

/root/.homebridge/.env not found.
Default env variables will be used.
/root/.homebridge/package.json not found.
Installing plugins from /root/.homebridge/install.sh.
+ [email protected]
updated 1 package in 3.692s
[2018-2-1 03:18:16] Loaded plugin: homebridge-mqtt-switch-tasmota
[2018-2-1 03:18:16] Registering accessory 'homebridge-mqtt-switch-tasmota.mqtt-switch-tasmota'
[2018-2-1 03:18:16] ---
[2018-2-1 03:18:16] Loaded config.json with 1 accessories and 0 platforms.
[2018-2-1 03:18:16] ---
[2018-2-1 03:18:16] Loading 0 platforms...
[2018-2-1 03:18:16] Loading 1 accessories...
[2018-2-1 03:18:16] [Lamp] Initializing mqtt-switch-tasmota accessory...
[2018-2-1 03:18:16] [Lamp] Nazwa do RESULT  POWER
Setup Payload:
X-HM://0023ISYWK0CLL
Scan this code with your HomeKit app on your iOS device to pair with Homebridge:
[QR Code]
Or enter this code with your HomeKit app on your iOS device to pair with Homebridge:
                       
    ┌────────────┐     
    │ 031-45-140 │     
    └────────────┘     
                       
[2018-2-1 03:18:16] Homebridge is running on port 51826.

Ports :

51826/tcp  0.0.0.0:51826
5353/tcp  0.0.0.0:5353
5353/udp  0.0.0.0:5353

At first when I started the container with the UDP protocol, it conflicted with the host ou is having a avahi-daemon for mDNS but I tried without the UDP port and killed the avah-daemon on the host also.

I don't what other information that could help you. I once ran a Homebridge server on a Virtual Machine and it once worked. But I killed it to dockerize it (I changed both username and PIN from the vm). I'm not able to see the hap._tcp in Discovery DNS-SD Browser

Thank you for your help.

homebridge -D can't run properly

when run homebridge -D , it always show some errors like this:

events.js:163                                                                                
      throw er; // Unhandled 'error' event                                                   
      ^                                                                                      
                                                                                             
Error: listen EADDRINUSE :::53699                                                            
    at Object.exports._errnoException (util.js:1050:11)                                      
    at exports._exceptionWithHostPort (util.js:1073:20)                                      
    at Server.setupListenHandle [as _listen2] (net.js:1263:14)                               
    at listenInCluster (net.js:1304:12)                                                      
    at Server.listen (net.js:1402:7)                                                         
    at EventedHTTPServer.listen (/usr/local/lib/node_modules/homebridge/node_modules/hap-node
js/lib/util/eventedhttp.js:60:19)                                                            
    at HAPServer.listen (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/H
APServer.js:158:20)                                                                          
    at Bridge.Accessory.publish (/usr/local/lib/node_modules/homebridge/node_modules/hap-node
js/lib/Accessory.js:509:16)                                                                  
    at Server._publish (/usr/local/lib/node_modules/homebridge/lib/server.js:114:16)         
    at Server.run (/usr/local/lib/node_modules/homebridge/lib/server.js:91:10)

Stopping and restarting container results in duplicate UUID

Hello,

I have my Synology NAS configured to go to a power down state at night and restart the next day.
When it does I am getting the following error:

[2017-11-27 19:24:12] Homebridge is running on port 51826.
[2017-11-27 19:24:12] [Domoticz] Could not register platform accessory! (Thermostaat)
Error: Cannot add a bridged Accessory with the same UUID as another bridged Accessory: f196f105-67c9-4c7b-9495-ba6f125d15fa

After this error occurred I can manually restart the container and the UUID error will be gone and everything will function correctly. Is this an issue with Homebridge or is the Domoticz plugin the culprit? Either way would it be possible for you to give me some advise how to possibly fix this?

Can't connect to Homebridge

Hello,

I have been trying to the last few days to get your latest Homebridge image 2.1 running within Docker on my Synology 1512+ running latest DSM 6.0.2-8451 Update 9.

I can't connect to homebridge although I get no errors building the container. I do get the final message that homebridge is running and to scan this code on your IOS device.

It will not show up in the IOS home app so I downloaded a bonjour browser and don't see the advertisement, so I assume something on the synology is preventing it. I walked through your instructions and made sure to tick off use same network as docker host. I have Synology VPN off, I turned off IPv6 on synology IP interface as I read this could cause issues.
The only warning messages I see in the log are the "the program 'node.js' uses the Apple Bonjour... " messages which I have read are ok.

I did get homebridge working on my windows machine in Hyper-V and Ubunto so as to rule out my network being the cause. Is there anywhere else I can look for clues as to why its not broadcasting what its supposed to?

any thoughts are welcome

My configs are very simple just trying to control my garage door for now.

install.sh:

npm install -g git+https://github.com/luisiam/homebridge-liftmaster2.git

config.json:

{
"bridge": {
"name": "Homebridge_OnSynology",
"username": "CC:22:33:11:EE:39",
"port": "51826",
"pin": "121-34-999"
},

"description": "Homebridge On Synology",

"platforms": [

{
"platform": "LiftMaster2",
"name": "Chamberlin MyQ",
"username": "[email protected]",
"password": "xxxxxx",
"openDuration": 20,
"closeDuration": 25,
"polling": true,
"longPoll": 300,
"shortPoll": 5,
"shortPollDuration": 120
}

]
}

No Response when away from home

I have an issue where my homebridge devices show "no response" when I am away from the house (using an Apple TV as a resident HomeKit hub). Any ideas why this happens?

4.1 running but lots of empty lines in log

DSM version 6.1.4.15217 update 3
docker version 17.05.0-0349
homebridge v4.1

i managed to install the latest 4.1 homebridge version but there seems to be a lot of empty lines in the log files. Also i see some code i did not see before.

at first 4.1 was running but nothing was detected. this was caused by the bonjour service running
here are my findings
4.0 bug with duplicate UUID error is there
4.1 bug with duplicate UUID error is STILL there

4.0 running fine, even with bonjour service active
4.1 running fine but only after disabling bonjour service(before that nothing was detected

4.0 local time was not working
4.1 confirmation that local time is working, EVEN WITHOUT .env file present(how can this be)

4.0 log file looking normal. every line has a time stamp and an entry
scrolling up and down looks normal

4.1 logfile not normal. lot's of empty lines with only timestamps. 1 mean really a lot of empty lines.(total 500+ lines) screenshot only shows part of it with some weird code about payload.
scrolling inside log looks weird. lines with no timestamp and no std out appear.
it looks like the screen has problems with some strange code
scrolling down goes ok but scrolling vack up makes lines disappear

ip camera stream doesn't work

Hi,

Thanks a lot for your software!
I successfully installed ffmpeg and homebridge, but I can't get the streaming in HomeKit working.
I checked if ffmpeg was installed by executing ffmpeg.
The snapshot works great. Here's my config:
{
"bridge": {
"name": "Homebridge Synology",
"username": "AC:22:3D:E3:CE:31",
"port": 51826,
"pin": "031-45-154"
},

"description": "This is an example configuration file. You can use this as a template for creating your own configuration file containing devices you actually own.",

"accessories": [
],

"platforms": [{

"platform": "Camera-IP",
"cameras": [
{
"name": "Camera",
"videoConfig": {
"source": "-re -i http://192.168.0.130:8081",
"stillImageSource": "-i http://192.168.0.130/picture/1/current/",
"maxStreams": 2,
"maxWidth": 1280,
"maxHeight": 720,
"maxFPS": 25
}
}
]
}
]
}
In my log I can see:

-re -i http://192.168.0.130:8081 -threads 0 -vcodec libx264 -an -pix_fmt yuv420p -r 30 -f rawvideo -tune zerolatency -vf scale=1280:720 -b:v 299k -bufsize 299k -payload_type 99 -ssrc 1 -f rtp -srtp_out_suite AES_CM_128_HMAC_SHA1_80 -srtp_out_params 4pXKX4bLVc0+SbPl8bUTDv8JW6+mqyEMZwJI4z/c srtp://192.168.0.184:58441?rtcpport=58569&localrtcpport=58569&pkt_size=1378

Any ideas?

works incorrectly after a while

Hi!

It works fine, but after a while I see my accessories state corectly if I turn the lamps manually on or off, but if I turn the lights off and on from the phone, their status changes only on the phone, the real device does not turn on or off.

After homebridge restart it works again for a while.

Any suggestion?

Thanks

also not working after a while

fixed

Cannot run on Raspberry Pi?

standard_init_linux.go:178: exec user process caused "exec format error"

container 2 hours behind

this seems to be a very old issue.
do not know if this is realted to docker or setting a TZ environment in the docker file

is there a way to set the timezone for this container or perhaps copy it from the system.

it is using UTC while i am in CEST(europe)

FFmpeg support

Hey, great plugin. Love your work. Working flawless for me!

How can I add ffmpeg to the package? I want to control a camera via homebridge and this needs ffmpeg installed.

Is volume1 a mandatory path

Hi,
I have installed Docker on my Synology on volume2.
Now Homebridge comp,ains upon starting that it can‘t find the the config.json and install.sh files which I have put under /docker/homebridge on volume2.

Might i t be that your container expect to have everything under volume1??
Tia,
Jens

log file flooded with temp readings after docker upgrade 17.05.0-370

Hello,

upgrade docker to the latest version yesterday.
Now the log is flooded with entries coming from 2 domoticz z-wave devices(probably through MQTT)
used RAM is growing

i was running homebridge v4.2 fine but think it is now running the latest version
is this new functionality

also when running 4.2 38MB of ram is consumed(HOMEBRIDGE_VERSION=0.4.32 is in the .ENV)
when running the latest version 68MB of ram is consumed(#HOMEBRIDGE_VERSION=0.4.32 is in the .ENV)

Container closes automatically after short time

Hi Marco,

I followed the instruction and set it up, but after launching the container it stops always after a short time. I have this in my log file:

Thanks for your help.

marcoraddatz-homebridge.pdf

Homebridge_OPTS=-I

I would like to install the below plugin, but I have to start homebridge in the insecure mode

https://www.npmjs.com/package/homebridge-alexa

but i cannot find the file homebridge in the folder /etc/default?
I search the homebridge.services?

where is the log file ?

Is the log file support in /var/log/homebridge.log ?
I can only view it from the Docker terminal.

thanks

version 0.4.28

Could you please update your docker version to 0.4.28? Or is there a way I can do it myself?

Add config to enable debug

Would be nice to be able to turn on debug mode via configuration.

homebridge -I mode

Hey,

I need to run homebridge with -I flag for accessing the HTTP API of Homebridge.
run.sh revealed, that this is not possible. Can you add a new flag?

"production-http" or something like that, which runs "homebridge -I ;;"?

Greets

SFTP ?

David,

I'm a noob on a mac how do do what you said below? Lets pretend my network settings for the container is at 192.168.1.35

Once the container is up, SFTP your homebridge files into the shared folder (Step 5), and restart the
container via the Container Station WebUI, and watch the console until the QR Code appears.

install.sh
config.json

Install ffmpeg

To use homebridge-camera-ffmpeg I need ffmpeg on the image. Could you pre-install it?
The following lines where neded:

echo 'deb http://ftp.uk.debian.org/debian jessie-backports main' >> /etc/apt/sources.list

apt-get update

apt-get -y install ffmpeg

Tried it in the install.sh, but somehow it didn't work.

Homebridge-Platform-Ring-Video-Doorbell

Hello - I am running Homebridge-docker on a QNAP 451+ in Container and cannot get this plugin to load. I think its because it is run in a docker container but I don't know enough about this - where are the files loaded for node_modules or how I can fix this. When I look up usr/local/lib/node_modules/homebridge-platform-ring-video-doorbell/node_modules/pcap2/ it says the director does not exist.

It is throwing this error:

�ERROR LOADING PLUGIN homebridge-platform-ring-video-doorbell:
[2017-9-3 23:17:45] Error: Cannot find module './build/Release/pcap_binding'
at Function.Module._resolveFilename (module.js:485:15)
at Function.Module._load (module.js:437:25)
at Module.require (module.js:513:17)
at require (internal/module.js:11:18)
at Object. (/usr/local/lib/node_modules/homebridge-platform-ring-video-doorbell/node_modules/pcap2/index.js:6:22)
at Module._compile (module.js:569:30)
at Object.Module._extensions..js (module.js:580:10)
at Module.load (module.js:503:32)
at tryModuleLoad (module.js:466:12)
at Function.Module._load (module.js:458:3)

marcoraddatz / homebridge-docker Goto Github PK

homebridge-docker's People

Contributors

Stargazers

Watchers

Forkers

homebridge-docker's Issues

Setting up Homebridge using QNAP Containers

Recommend Projects

Recommend Topics

Recommend Org