Git Product home page Git Product logo

oznu / docker-homebridge Goto Github PK

View Code? Open in Web Editor NEW
2.5K 77.0 237.0 411 KB

Homebridge Docker. HomeKit support for the impatient using Docker on x86_64, Raspberry Pi (armhf) and ARM64. Includes ffmpeg + libfdk-aac.

Home Page: https://hub.docker.com/r/homebridge/homebridge/

License: GNU General Public License v3.0

Shell 66.06% Dockerfile 33.94%
homebridge docker raspberry-pi x86-64 homekit siri alpine-linux armhf homebridge-docker docker-homebridge rpi armv6 arm arm64 aarch64 arm6 ffmpeg libfdk-aac

docker-homebridge's Introduction

Donate Docker Build Status Docker Pulls Discord

Important Update

We have moved the hosting of the offical homebridge docker image from oznu/homebridge to homebridge/homebridge. Please update your environments as needed to pickup the latest image.

Homebridge Docker Image

This Ubuntu Linux based Docker image allows you to run Nfarina's Homebridge on your home network which emulates the iOS HomeKit API.

This is a multi-arch image and will run on x86_64, Raspberry Pi 2, 3, 4, Zero 2 W, or other Docker-enabled ARMv7/8 devices. Docker will automatically pull the correct image for your system.

Image Tag Architectures Base Image
latest, ubuntu amd64, arm32v7, arm64v8 Ubuntu 22.04

Step-By-Step Guides

Compatibility

Homebridge requires full access to your local network to function correctly which can be achieved using the --net=host flag.

This image will not work when using Docker for Mac or Docker for Windows due to this and this.

Usage

Using Docker Compose (recommended):

  1. Create the file docker-compose.yml
version: '2'
services:
  homebridge:
    image: homebridge/homebridge:latest
    restart: always
    network_mode: host
    volumes:
      - ./volumes/homebridge:/homebridge
    logging:
      driver: json-file
      options:
        max-size: '10m'
        max-file: '1'
    healthcheck:
      test: curl --fail localhost:8581 || exit 1
      interval: 60s
      retries: 5
      start_period: 300s
      timeout: 2s
  1. Start docker with
docker compose up

Or Command Line:

docker run --net=host --name=homebridge -v $(pwd)/homebridge:/homebridge homebridge/homebridge:latest

Parameters

The parameters are split into two halves, separated by a colon, the left hand side representing the host and the right the container side.

  • --net=host - Shares host networking with container, required
  • -v /homebridge - The Homebridge config and plugin location, required
Optional Settings:
  • -e TZ - for timezone information e.g. -e TZ=Australia/Canberra
  • -e ENABLE_AVAHI - default is 1; set to 0 to prevent the Avahi mDNS service running in the container

Homebridge UI

This image comes with the Homebridge UI pre-installed and is the easiest way to manage all aspects of Homebridge.

To manage Homebridge go to http://<ip of server>:8581 in your browser. For example, http://192.168.1.20:8581. From here you can install, remove and update plugins, modify the Homebridge config.json and restart Homebridge.

Automated Updates

Automated updates of the Homebridge Docker Image using tools such as Watchtower or similar are strongly discouraged and are done so at your own risk.

NOTE - The version of Homebridge IS NOT tied to the version of the container. You can update Homebridge, the Homebridge UI and the Node.js runtime from inside the container.

Troubleshooting

1. Need ffmpeg?

ffmpeg, with libfdk-aac audio support is included in this image.

2. Container will not start on older versions of Raspbian

If you're seeing errors like the following, your host operating system needs to be updated.

See #434 and #441 for potential solutions.

Node.js[445]: ../src/util.cc:188:double node::GetCurrentTimeInMicroseconds(): Assertion `(0) == (uv_gettimeofday(&tv))' failed.
Aborted (core dumped)
homebridge_1  | s6-svscan: warning: unable to iopause: Operation not permitted
homebridge_1  | s6-svscan: warning: executing into .s6-svscan/crash
homebridge_1  | s6-svscan crashed. Killing everything and exiting.
homebridge    | # Fatal error in , line 0
homebridge    | # unreachable code

3. Ask on Discord

Join the Official Homebridge Discord community and ask in the #docker channel.

License

Copyright (C) 2023 homebridge Copyright (C) 2017-2022 oznu

This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

docker-homebridge's People

Contributors

bdsoha avatar bpoetzschke avatar bwp91 avatar cyrussuen avatar donavanbecker avatar fish2 avatar g-arjones avatar gill6151 avatar lunaticmuch avatar nchieng avatar nick-chieng avatar northernman54 avatar oznu avatar pascalmtts avatar poweronoff avatar rafaelgaspar avatar raymondmouthaan avatar tylersatre avatar waypar avatar zackmuc avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

docker-homebridge's Issues

Host Name Conflict

Hi

Im totally new to using home bridge. I followed the guide to install it onto my Synology ds916+ so I can connect my nest thermostat to HomeKit.

For some reason it seems I get an error host name conflict. It keeps scrolling Homebridge-XX... forever. How can I fix this?.

Thanks

screen shot 2018-01-28 at 16 11 04

Restarting docker container results in multiple failures

I'm experiencing an issue with the image/container where any form of restart (manual or auto/policy) results in the system complaining about duplicate accessories (Error: Cannot add a bridged Accessory with the same UUID as another bridged Accessory). Stopping the container, removing /persist and /accessories before starting again seems to help, but then it seems as though HomeKit doesn't recognize the bridge anymore and I have to go through a removal/setup process on one of my devices to bring it all back.

Please tell me I'm doing something stupid and help me understand how to make the container/devices persist across restarts.

Host is a ReadyNAS box (v6.9.1.. which is Debian 8.9) with Docker CE 17.09. I build the container using:
docker create --net=host --name=homebridge -e PUID=98 -e PGID=98 -e TZ=America/Los_Angeles -v /home/admin/docker-homebridge-config:/homebridge --restart unless-stopped oznu/homebridge. I use this because I don't have Docker Compose installed on the host. The only plugin I have installed (using the yarn method) is Tplinksmarthome v3.10. I also have Portainer installed and thought maybe it was issuing funky commands behind the scenes that were causing me trouble, but the issue persists when using native CLI commands to start/stop/restart.

Help with mDNS / getaddrinfo issues

Hey there!

This is not a bug in your code or your fault in any way, but I wanted to see if you could help out. There are some people using docker-homebridge that are having issues with plugins that rely on syscalls to getaddrinfo. Specifically I'm trying to use homebridge-dacp to control Apple TV and iTunes.

Error: {"code":-3008,"errno":-3008,"syscall":"getaddrinfo"}

I believe its related to this code that calls getaddrinfo:

    const ResolverSequence = [
      mdns.rst.DNSServiceResolve(),
      'DNSServiceGetAddrInfo' in mdns.dns_sd ? mdns.rst.DNSServiceGetAddrInfo() : mdns.rst.getaddrinfo({ families: [0] }),
      mdns.rst.makeAddressesUnique()
    ];

I've also tried families: [4] to see if I could force IPv4. Basically it seems like Alpine is having trouble resolving the addresses. Do you have any insight what the issue might be or for a workaround? :)

grover/homebridge-dacp#10

DNS Issue When Starting homebridge

I have the docker container installed, but when it starts, homebridge crashes with the following

{"log":"/usr/local/share/.config/yarn/global/node_modules/mdns/lib/advertisement.js:56\n","stream":"stderr","time":"2017-07-04T03:51:35.236638739Z"}
{"log":" dns_sd.DNSServiceRegister(self.serviceRef, flags, ifaceIdx, name,\n","stream":"stderr","time":"2017-07-04T03:51:35.236670538Z"}
{"log":" ^\n","stream":"stderr","time":"2017-07-04T03:51:35.236676538Z"}
{"log":"\n","stream":"stderr","time":"2017-07-04T03:51:35.236681638Z"}
{"log":"Error: dns service error: unknown\n","stream":"stderr","time":"2017-07-04T03:51:35.236686638Z"}
{"log":" at Error (native)\n","stream":"stderr","time":"2017-07-04T03:51:35.236691638Z"}
{"log":" at new Advertisement (/usr/local/share/.config/yarn/global/node_modules/mdns/lib/advertisement.js:56:10)\n","stream":"stderr","time":"2017-07-04T03:51:35.236714838Z"}
{"log":" at Object.create [as createAdvertisement] (/usr/local/share/.config/yarn/global/node_modules/mdns/lib/advertisement.js:64:10)\n","stream":"stderr","time":"2017-07-04T03:51:35.236720938Z"}
{"log":" at Advertiser.startAdvertising (/usr/local/share/.config/yarn/global/node_modules/hap-nodejs/lib/Advertiser.js:43:30)\n","stream":"stderr","time":"2017-07-04T03:51:35.236737238Z"}
{"log":" at Bridge.Accessory._onListening (/usr/local/share/.config/yarn/global/node_modules/hap-nodejs/lib/Accessory.js:532:20)\n","stream":"stderr","time":"2017-07-04T03:51:35.236742638Z"}
{"log":" at emitOne (events.js:96:13)\n","stream":"stderr","time":"2017-07-04T03:51:35.236747638Z"}
{"log":" at HAPServer.emit (events.js:188:7)\n","stream":"stderr","time":"2017-07-04T03:51:35.236752538Z"}
{"log":" at HAPServer._onListening (/usr/local/share/.config/yarn/global/node_modules/hap-nodejs/lib/HAPServer.js:190:8)\n","stream":"stderr","time":"2017-07-04T03:51:35.236757338Z"}
{"log":" at emitOne (events.js:96:13)\n","stream":"stderr","time":"2017-07-04T03:51:35.236762438Z"}
{"log":" at EventedHTTPServer.emit (events.js:188:7)\n","stream":"stderr","time":"2017-07-04T03:51:35.236767038Z"}

Looks like its complaining that DNS registration is failing, but works fine for a non-docker instance of homebridge.

I have no clue what this actually is try

Permission Error on NPM Config

Hi,

I'm getting an endless loop of this error using the latest version.

│              npm update check failed              │
│        Try running with sudo or get access        │
│       to the local update config store via        │
│ sudo chown -R $USER:$(id -gn $USER) /root/.config │
└───────────────────────────────────────────────────┘
fs.js:675
  return binding.read(fd, buffer, offset, length, position);
                 ^

Error: EISDIR: illegal operation on a directory, read
    at Object.fs.readSync (fs.js:675:18)
    at tryReadSync (fs.js:540:20)
    at Object.fs.readFileSync (fs.js:583:19)
    at LocalStorage.parseDirSync (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/node_modules/node-persist/src/local-storage.js:637:35)
    at LocalStorage.parseDataDirSync (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/node_modules/node-persist/src/local-storage.js:572:21)
    at LocalStorage.initSync (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/node_modules/node-persist/src/local-storage.js:145:14)
    at Object.nodePersist.initSync (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/node_modules/node-persist/src/node-persist.js:41:29)
    at Object.init (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/index.js:29:13)
    at module.exports (/usr/local/lib/node_modules/homebridge/lib/cli.js:24:7)
    at Object.<anonymous> (/usr/local/lib/node_modules/homebridge/bin/homebridge:17:22)```

If I drop to a shell inside the container, /root/.config is owned by abc/abc which is odd and i'm not sure why. I do have PUID and PGID set to the output of my synology NAS user (which has R/W to /homebridge) and as far as I can tell, all the files in /homebridge have the proper permissions as well.

Any ideas? Thanks!

homebridge-mqtt-switch-tasmota - Can't install plugin

I manage to install a bunch of plugins today, mqtt-switch-tasmota can't seem to install ....

pi@raspberrypi:~/homebridge $ docker exec homebridge_homein_1 npm install homebridge-mqtt-switch-tasmota
npm WARN homebridge No description
npm WARN homebridge No repository field.
npm WARN homebridge No license field.

npm ERR! code EAI_AGAIN
npm ERR! errno EAI_AGAIN
npm ERR! request to https://registry.npmjs.org/pumpify/-/pumpify-1.4.0.tgz failed, reason: getaddrinfo EAI_AGAIN registry.npmjs.org:443

npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2018-02-15T09_17_08_971Z-debug.log
pi@raspberrypi:~/homebridge $

Update Node?

How do I update Node for this docker image? The old node won’t allow me to install some of my preferred plugins.

Cannot execute commands prior to homebridge startup

Great work on this container, it's fantastic.

My issue (a feature request really) specifically relates to the plugin homebridge-homeassistant, which connects homebridge to a running Home Assistant instance.

When Home Assistant is set up with SSL and a self-signed certificate, for homebridge to be able to connect to the Home Assistant instance, we must first do:

export NODE_TLS_REJECT_UNAUTHORIZED=0

So that homebridge will not fail to connect because of an SSL error.

Can we add a script to the volume /homebridge that contains code to be executed prior to homebridge startup?

Thanks in advance!

TypeError: unsupported operand type(s) for -=: 'Retry' and 'int'

I ran into a new error after running the following syntax to Install Docker Compose ... please see below. Could it be a Python issue?

sudo apt-get -y install python-setuptools && sudo easy_install pip && sudo pip install docker-compose

Exception:
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/pip/basecommand.py", line 215, in main
status = self.run(options, args)
File "/usr/lib/python2.7/dist-packages/pip/commands/install.py", line 353, in run
wb.build(autobuilding=True)
File "/usr/lib/python2.7/dist-packages/pip/wheel.py", line 749, in build
self.requirement_set.prepare_files(self.finder)
File "/usr/lib/python2.7/dist-packages/pip/req/req_set.py", line 380, in prepare_files
ignore_dependencies=self.ignore_dependencies))
File "/usr/lib/python2.7/dist-packages/pip/req/req_set.py", line 554, in _prepare_file
require_hashes
File "/usr/lib/python2.7/dist-packages/pip/req/req_install.py", line 278, in populate_link
self.link = finder.find_requirement(self, upgrade)
File "/usr/lib/python2.7/dist-packages/pip/index.py", line 465, in find_requirement
all_candidates = self.find_all_candidates(req.name)
File "/usr/lib/python2.7/dist-packages/pip/index.py", line 423, in find_all_candidates
for page in self._get_pages(url_locations, project_name):
File "/usr/lib/python2.7/dist-packages/pip/index.py", line 568, in _get_pages
page = self._get_page(location)
File "/usr/lib/python2.7/dist-packages/pip/index.py", line 683, in _get_page
return HTMLPage.get_page(link, session=self.session)
File "/usr/lib/python2.7/dist-packages/pip/index.py", line 792, in get_page
"Cache-Control": "max-age=600",
File "/usr/share/python-wheels/requests-2.12.4-py2.py3-none-any.whl/requests/sessions.py", line 501, in get
return self.request('GET', url, **kwargs)
File "/usr/lib/python2.7/dist-packages/pip/download.py", line 386, in request
return super(PipSession, self).request(method, url, *args, **kwargs)
File "/usr/share/python-wheels/requests-2.12.4-py2.py3-none-any.whl/requests/sessions.py", line 488, in request
resp = self.send(prep, **send_kwargs)
File "/usr/share/python-wheels/requests-2.12.4-py2.py3-none-any.whl/requests/sessions.py", line 609, in send
r = adapter.send(request, **kwargs)
File "/usr/share/python-wheels/CacheControl-0.11.7-py2.py3-none-any.whl/cachecontrol/adapter.py", line 47, in send
resp = super(CacheControlAdapter, self).send(request, **kw)
File "/usr/share/python-wheels/requests-2.12.4-py2.py3-none-any.whl/requests/adapters.py", line 423, in send
timeout=timeout
File "/usr/share/python-wheels/urllib3-1.19.1-py2.py3-none-any.whl/urllib3/connectionpool.py", line 643, in urlopen
_stacktrace=sys.exc_info()[2])
File "/usr/share/python-wheels/urllib3-1.19.1-py2.py3-none-any.whl/urllib3/util/retry.py", line 315, in increment
total -= 1
TypeError: unsupported operand type(s) for -=: 'Retry' and 'int'

Running as root

I'm trying to run homebridge-amazondash. It requires homebridge to be run as root to work, so I cannot get it to work with this docker image. Any thoughts on how to get this one working?

I'm getting the following in my log. I tried looking for alternative plugins but they all require root.

Error: socket: Operation not permitted
    at new PcapSession (/homebridge/node_modules/pcap/pcap.js:49:39)
    at Object.exports.createSession (/homebridge/node_modules/pcap/pcap.js:123:12)
    at create_session (/homebridge/node_modules/node-dash-button/index.js:24:28)
    at register (/homebridge/node_modules/node-dash-button/index.js:47:24)
    at DashPlatform.didFinishLaunching (/homebridge/node_modules/homebridge-amazondash/index.js:57:17)
    at emitNone (events.js:106:13)
    at API.emit (events.js:208:7)
    at Server.run (/usr/local/lib/node_modules/homebridge/lib/server.js:98:13)
    at module.exports (/usr/local/lib/node_modules/homebridge/lib/cli.js:40:10)
    at Object.<anonymous> (/usr/local/lib/node_modules/homebridge/bin/homebridge:17:22)
    at Module._compile (module.js:643:30)
    at Object.Module._extensions..js (module.js:654:10)
    at Module.load (module.js:556:32)
    at tryModuleLoad (module.js:499:12)
    at Function.Module._load (module.js:491:3)
    at Function.Module.runMain (module.js:684:10)
    at startup (bootstrap_node.js:187:16)
    at bootstrap_node.js:608:3
Failed to create pcap session: couldn't find devices to listen on.
Try running with elevated privileges via 'sudo'
/homebridge/node_modules/node-dash-button/index.js:28
        throw new Error('Error: No devices to listen');
        ^

Error: Error: No devices to listen
    at create_session (/homebridge/node_modules/node-dash-button/index.js:28:15)
    at register (/homebridge/node_modules/node-dash-button/index.js:47:24)
    at DashPlatform.didFinishLaunching (/homebridge/node_modules/homebridge-amazondash/index.js:57:17)
    at emitNone (events.js:106:13)
    at API.emit (events.js:208:7)
    at Server.run (/usr/local/lib/node_modules/homebridge/lib/server.js:98:13)
    at module.exports (/usr/local/lib/node_modules/homebridge/lib/cli.js:40:10)
    at Object.<anonymous> (/usr/local/lib/node_modules/homebridge/bin/homebridge:17:22)
    at Module._compile (module.js:643:30)
    at Object.Module._extensions..js (module.js:654:10)
    at Module.load (module.js:556:32)
    at tryModuleLoad (module.js:499:12)
    at Function.Module._load (module.js:491:3)
    at Function.Module.runMain (module.js:684:10)
    at startup (bootstrap_node.

Post-install ffmpeg to synology docker homebridge container

I'm working with the docker on Synology NAS supported by the homebridge-config-ui package (really stable, user-friendly, great work!)

I'd like to add the homebridge-camera-ffmpeg plugin to the docker which loads but fails when triggered by the IOS home.app. I imagine that the container cannot work with the standard synology ffmpeg package (unlike other packages like mosquitto), and that ffmpeg needs to be installed within the docker container.

The docker-homebridge readme says: 3. Need ffmpeg? You can enable ffmpeg by adding this environment variable to your run command or docker-compose.yml: PACKAGES=ffmpeg,ffmpeg-libs

Can I add ffmpeg to the Synology container in a non-destructive way ie without losing config.json and installed plugins? I can't find a docker-compose.yml file but I do have an empty startup.sh file in my /volume1/docker/homebridge.

If possible, I'd appreciate any help! Thanks

ps4-waker not working

Trying to get ps4-waker working with cmdSwitch2, but cannot call ps4-waker properly.

Added "npm install ps4-waker" to startup.sh and it does install. Tried adding "npm rebuild" to startup.sh to see if that fixes, but no. Also tried stopping docker, removing container, recreating. Tried removing node_modules folder as well.

I get this:
docker exec -it homebridge ps4-waker
OCI runtime exec failed: exec failed: container_linux.go:296: starting container process caused "exec: \"ps4-waker\": executable file not found in $PATH": unknown

It does work like this:
docker exec -it homebridge /homebridge/node_modules/ps4-waker/bin/cmd.js
No credentials; Use the PS4 Second Screen App and try to connect to PS4-Waker
(yes, I have done the credentials setup... asking for credentials now because I just tried to reset everything to see if that was issue)

Any other info you need, let me know.

Edit - added more info

Error removing falkbulb

Thank you developer for your effort!
I've successfully turned my Raspberry Pi 3 into a Homebridge running on Docker to control my Yeelight lightbulb. 👍

However I'm new to Docker and Homebridge and I'm not sure how to completely remove the fakebulb.
Is there a way to completely remove it before getting the container running?
I've got an error when running the cmd for the docker container to remove the fakebulb as well.
Here is the log:

pi@raspberrypi:~/docker-images$ docker exec 2ddf2ba19865 yarn remove homebridge-fakebulb
yarn remove v0.24.4
[1/2] Removing module homebridge-fakebulb...
[2/2] Regenerating lockfile and installing missing dependencies...
warning No license field
warning [email protected]: The engine "homebridge" appears to be invalid.
success Uninstalled packages.
Done in 3.45s.
pi@raspberrypi:~/docker-images$ cd docker-homebridge/
pi@raspberrypi:~/docker-images/docker-homebridge$ ls
2  default.config.json	docker-compose.yml  Dockerfile	Dockerfile.raspberry-pi  init.d  README.md
pi@raspberrypi:~/docker-images/docker-homebridge$ docker ps
CONTAINER ID        IMAGE                          COMMAND                  CREATED             STATUS              PORTS               NAMES
2ddf2ba19865        oznu/homebridge:raspberry-pi   "/init.d/entrypoin..."   19 minutes ago      Up 19 minutes                           dockerhomebridge_homebridge_1
pi@raspberrypi:~/docker-images/docker-homebridge$ docker-compose down
Stopping dockerhomebridge_homebridge_1 ... done
Removing dockerhomebridge_homebridge_1 ... done
pi@raspberrypi:~/docker-images/docker-homebridge$ docker-compose up
Creating dockerhomebridge_homebridge_1
Attaching to dockerhomebridge_homebridge_1
homebridge_1  | sh: Kong": unknown operand
homebridge_1  | Removing old plugins...
homebridge_1  | npm WARN package.json @ No description
homebridge_1  | npm WARN package.json @ No repository field.
homebridge_1  | npm WARN package.json @ No README data
homebridge_1  | npm WARN package.json @ No license field.
homebridge_1  | Installing plugins...
homebridge_1  | yarn install v0.24.4
homebridge_1  | warning No license field
homebridge_1  | [1/4] Resolving packages...
homebridge_1  | success Already up-to-date.
homebridge_1  | Done in 1.47s.
homebridge_1  | *** WARNING *** The program 'node' uses the Apple Bonjour compatibility layer of Avahi.
homebridge_1  | *** WARNING *** Please fix your application to use the native API of Avahi!
homebridge_1  | *** WARNING *** For more information see <http://0pointer.de/avahi-compat?s=libdns_sd&e=node>
homebridge_1  | *** WARNING *** The program 'node' called 'DNSServiceRegister()' which is not supported (or only supported partially) in the Apple Bonjour compatibility layer of Avahi.
homebridge_1  | *** WARNING *** Please fix your application to use the native API of Avahi!
homebridge_1  | *** WARNING *** For more information see <http://0pointer.de/avahi-compat?s=libdns_sd&e=node&f=DNSServiceRegister>
homebridge_1  | failed to load BLE module!
homebridge_1  | [6/22/2017, 9:02:29 AM] Loaded plugin: homebridge-yeelight
homebridge_1  | [6/22/2017, 9:02:29 AM] Registering platform 'homebridge-yeelight.yeelight'
homebridge_1  | [6/22/2017, 9:02:29 AM] ---
homebridge_1  | [6/22/2017, 9:02:29 AM] Loaded config.json with 1 accessories and 0 platforms.
homebridge_1  | [6/22/2017, 9:02:29 AM] ---
homebridge_1  | [6/22/2017, 9:02:29 AM] Loading 0 platforms...
homebridge_1  | [6/22/2017, 9:02:29 AM] Loading 1 accessories...
homebridge_1  | /usr/local/lib/node_modules/homebridge/lib/api.js:64
homebridge_1  |       throw new Error("The requested accessory '" + name + "' was not registered by any plugin.");
homebridge_1  |       ^
homebridge_1  | 
homebridge_1  | Error: The requested accessory 'FakeBulb' was not registered by any plugin.
homebridge_1  |     at API.accessory (/usr/local/lib/node_modules/homebridge/lib/api.js:64:13)
homebridge_1  |     at Server._loadAccessories (/usr/local/lib/node_modules/homebridge/lib/server.js:254:42)
homebridge_1  |     at Server.run (/usr/local/lib/node_modules/homebridge/lib/server.js:81:38)
homebridge_1  |     at module.exports (/usr/local/lib/node_modules/homebridge/lib/cli.js:40:10)
homebridge_1  |     at Object.<anonymous> (/usr/local/lib/node_modules/homebridge/bin/homebridge:17:22)
homebridge_1  |     at Module._compile (module.js:570:32)
homebridge_1  |     at Object.Module._extensions..js (module.js:579:10)
homebridge_1  |     at Module.load (module.js:487:32)
homebridge_1  |     at tryModuleLoad (module.js:446:12)
homebridge_1  |     at Function.Module._load (module.js:438:3)
dockerhomebridge_homebridge_1 exited with code 1

Cannot start service homebridge: OCI runtime create failed

I appreciate all your work here. It looks great! However, I am unable to get the docker container to start. Please see the terminal output below:

pi@raspberrypi:~/homebridge $ docker-compose up -d
Starting homebridge_homebridge_1 ...
Starting homebridge_homebridge_1 ... error

ERROR: for homebridge_homebridge_1 Cannot start service homebridge: OCI runtime create failed: unable to retrieve OCI runtime error (open /run/docker/containerd/daemon/io.containerd.runtime.v1.linux/moby/81c92b582a1966519a9e6f4ff71e1be5c0faa42c141dc2c184327750c71fb38b/log.json: no such file or directory): docker-runc did not terminate sucessfully: unknown

ERROR: for homebridge Cannot start service homebridge: OCI runtime create failed: unable to retrieve OCI runtime error (open /run/docker/containerd/daemon/io.containerd.runtime.v1.linux/moby/81c92b582a1966519a9e6f4ff71e1be5c0faa42c141dc2c184327750c71fb38b/log.json: no such file or directory): docker-runc did not terminate sucessfully: unknown
ERROR: Encountered errors while bringing up the project.

pi@raspberrypi:~/homebridge $ docker-compose restart homebridge
Restarting homebridge_homebridge_1 ... error

ERROR: for homebridge_homebridge_1 Cannot restart container 81c92b582a1966519a9e6f4ff71e1be5c0faa42c141dc2c184327750c71fb38b: OCI runtime create failed: unable to retrieve OCI runtime error (open /run/docker/containerd/daemon/io.containerd.runtime.v1.linux/moby/81c92b582a1966519a9e6f4ff71e1be5c0faa42c141dc2c184327750c71fb38b/log.json: no such file or directory): docker-runc did not terminate sucessfully: unknown

pi@raspberrypi:~/homebridge $ docker-compose logs -f
Attaching to homebridge_homebridge_1
homebridge_homebridge_1 exited with code 128

pi@raspberrypi:~/homebridge/config $ docker-compose pull homebridge
Pulling homebridge (oznu/homebridge:raspberry-pi)...
raspberry-pi: Pulling from oznu/homebridge
Digest: sha256:d6f0653b085cf16b6b0cf05813f21f0226f253e630170d320611cb5f155e00f7
Status: Image is up to date for oznu/homebridge:raspberry-pi

Host name conflict Raspberry pi

Hi, I kind of have the same problem on the Raspberry pi as Synology guys are having.

Withdrawing address record for 10.0.1.105 on wlan0.
Host name conflict, retrying with raspberrypi-17
Registering new address record for 172.17.0.1 on docker0.IPv4.
Registering new address record for 10.0.1.105 on wlan0.IPv4.

Maybe relevant?

*** WARNING *** The program 'node' 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=node>
*** WARNING *** The program 'node' 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=node&f=DNSServiceRegister>

IPv6 is disabled on my pi:

cat /etc/modprobe.d/ipv6.conf
# Don't load ipv6 by default
alias net-pf-10 off
#alias ipv6 off

# added to disable ipv6
options ipv6 disable_ipv6=1
# added to prevent ipv6 driver from loading
blacklist ipv6

I'm using a fresh install of Raspbian stretch lite and installing everything with the tutorial.

Multiple Docker Instances – I screwed up!

So after getting the first Oznu Docker up and running I wanted to created a second docker on the same pi to have a separate instance of Homebridge running to keep certain plug ins away from each other. I saw another post in here and tried to piece it all together.

For the 1st (initial) install of oznu/docker I followed these step:
https://github.com/oznu/docker-homebridge/wiki/Homebridge-on-Raspberry-Pi

Again I got everything working! Then to get another docker image going I started from step #3 with a couple of changes:

mkdir /home/pi/homebridge-two
cd /home/pi/homebridge-two

nano docker-compose.yml

put in the following contents:

version: '2'
services:
  homebridge:
    image: oznu/homebridge:raspberry-pi
    restart: always
    network_mode: host
    volumes:
      - ./config:/homebridge-two
    environment:
      - PGID=1000
      - PUID=1000

CTRL+X

docker-compose up -d

docker-compose logs -f

The logs come up with the QR code and everything. However, I noticed that no config.json was ever created inside my Homebridge-two folder.

I then realized that the docker-compose.yml had a mistake in it " - ./config:/homebridge-two" and changed that line to " - ./config-two:/homebridge" for this:

version: '2'
services:
  homebridge:
    image: oznu/homebridge:raspberry-pi
    restart: always
    network_mode: host
    volumes:
      - ./config-two:/homebridge
    environment:
      - PGID=1000
      - PUID=1000

I ran this command again:

docker-compose up -d

But it didn't make a difference. There is still no config.json and even creating my own config.json in homebridge-two/config doesn't make a difference. The second docker install seems to be reading its configuration from somewhere else.

Here is the log that I get when running docker-compose logs -f inside pi@raspberrypi:~/homebridge-two:

Attaching to homebridgetwo_homebridge_1
homebridge_1  | [s6-init] making user provided files available at /var/run/s6/etc...exited 0.
homebridge_1  | [s6-init] ensuring user provided files have correct perms...exited 0.
homebridge_1  | [fix-attrs.d] applying ownership & permissions fixes...
homebridge_1  | [fix-attrs.d] done.
homebridge_1  | [cont-init.d] executing container initialization scripts...
homebridge_1  | [cont-init.d] 10-adduser: executing... 
homebridge_1  | 
homebridge_1  | -------------------------------------
homebridge_1  | GID/UID
homebridge_1  | -------------------------------------
homebridge_1  | User uid:    1000
homebridge_1  | User gid:    1000
homebridge_1  | -------------------------------------
homebridge_1  | 
homebridge_1  | [cont-init.d] 10-adduser: exited 0.
homebridge_1  | [cont-init.d] 20-set-timezone: executing... 
homebridge_1  | [cont-init.d] 20-set-timezone: exited 0.
homebridge_1  | [cont-init.d] 30-packages: executing... 
homebridge_1  | [cont-init.d] 30-packages: exited 0.
homebridge_1  | [cont-init.d] 40-dbus-avahi: executing... 
homebridge_1  | [cont-init.d] 40-dbus-avahi: exited 0.
homebridge_1  | [cont-init.d] 45-user-data: executing... 
homebridge_1  | [cont-init.d] 45-user-data: exited 0.
homebridge_1  | [cont-init.d] 50-plugins: executing... 
homebridge_1  | Homebridge: Installing plugins...
homebridge_1  | npm WARN homebridge No description
homebridge_1  | npm WARN homebridge No repository field.
homebridge_1  | npm WARN homebridge No license field.
homebridge_1  | 
homebridge_1  | up to date in 0.382s
homebridge_1  | npm WARN homebridge No description
homebridge_1  | npm WARN homebridge No repository field.
homebridge_1  | npm WARN homebridge No license field.
homebridge_1  | 
homebridge_1  | up to date in 0.435s
homebridge_1  | [cont-init.d] 50-plugins: exited 0.
homebridge_1  | [cont-init.d] 55-config-ui: executing... 
homebridge_1  | [cont-init.d] 55-config-ui: exited 0.
homebridge_1  | [cont-init.d] done.
homebridge_1  | [services.d] starting services
homebridge_1  | Starting dbus-daemon
homebridge_1  | [services.d] done.
homebridge_1  | Starting Avahi daemon
homebridge_1  | Found user 'avahi' (UID 86) and group 'avahi' (GID 86).
homebridge_1  | Successfully dropped root privileges.
homebridge_1  | avahi-daemon 0.6.32 starting up.
homebridge_1  | WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
homebridge_1  | Loading service file /etc/avahi/services/sftp-ssh.service.
homebridge_1  | Loading service file /etc/avahi/services/ssh.service.
homebridge_1  | *** WARNING: Detected another IPv4 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. ***
homebridge_1  | Joining mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1.
homebridge_1  | New relevant interface docker0.IPv4 for mDNS.
homebridge_1  | Joining mDNS multicast group on interface eth0.IPv4 with address 10.0.1.11.
homebridge_1  | New relevant interface eth0.IPv4 for mDNS.
homebridge_1  | Network interface enumeration completed.
homebridge_1  | Registering new address record for 172.17.0.1 on docker0.IPv4.
homebridge_1  | Registering new address record for fe80::adf3:bbd0:ae26:99a4 on eth0.*.
homebridge_1  | Registering new address record for 10.0.1.11 on eth0.IPv4.
homebridge_1  | Server startup complete. Host name is raspberrypi.local. Local service cookie is 19093884.
homebridge_1  | Service "raspberrypi" (/etc/avahi/services/ssh.service) successfully established.
homebridge_1  | Service "raspberrypi" (/etc/avahi/services/sftp-ssh.service) successfully established.
homebridge_1  | *** WARNING *** The program 'node' uses the Apple Bonjour compatibility layer of Avahi.
homebridge_1  | *** WARNING *** Please fix your application to use the native API of Avahi!
homebridge_1  | *** WARNING *** For more information see <http://0pointer.de/avahi-compat?s=libdns_sd&e=node>
homebridge_1  | *** WARNING *** The program 'node' called 'DNSServiceRegister()' which is not supported (or only supported partially) in the Apple Bonjour compatibility layer of Avahi.
homebridge_1  | *** WARNING *** Please fix your application to use the native API of Avahi!
homebridge_1  | *** WARNING *** For more information see <http://0pointer.de/avahi-compat?s=libdns_sd&e=node&f=DNSServiceRegister>
homebridge_1  | [2018-1-27 01:26:55] Loaded plugin: homebridge-dummy
homebridge_1  | [2018-1-27 01:26:55] Registering accessory 'homebridge-dummy.DummySwitch'
homebridge_1  | [2018-1-27 01:26:55] ---
homebridge_1  | [2018-1-27 01:26:56] Loaded plugin: homebridge-config-ui-x
homebridge_1  | [2018-1-27 01:26:56] Registering platform 'homebridge-config-ui-x.config'
homebridge_1  | [2018-1-27 01:26:56] ---
homebridge_1  | [2018-1-27 01:26:56] Loaded config.json with 0 accessories and 0 platforms.
homebridge_1  | [2018-1-27 01:26:56] ---
homebridge_1  | [2018-1-27 01:26:56] Loading 0 platforms...
homebridge_1  | [2018-1-27 01:26:56] Loading 0 accessories...
homebridge_1  | Setup Payload:
homebridge_1  | X-HM://0023ISYWYH44A
homebridge_1  | Scan this code with your HomeKit app on your iOS device to pair with Homebridge:
homebridge_1  |                                                       
homebridge_1  |                                                       
homebridge_1  |                                                       
homebridge_1  |                                                       
homebridge_1  |                                                       
homebridge_1  |                                                       
homebridge_1  |                                                       
homebridge_1  |                                                       
homebridge_1  |                                                       
homebridge_1  |                                                       
homebridge_1  |                                                       
homebridge_1  |                                                       
homebridge_1  |                                                       
homebridge_1  |                                                       
homebridge_1  |                                                       
homebridge_1  |                                                       
homebridge_1  |                                                       
homebridge_1  |                                                       
homebridge_1  |                                                       
homebridge_1  |                                                       
homebridge_1  |                                                       
homebridge_1  |                                                       
homebridge_1  |                                                       
homebridge_1  |                                                       
homebridge_1  |                                                       
homebridge_1  |                                                       
homebridge_1  |                                                       
homebridge_1  | Or enter this code with your HomeKit app on your iOS device to pair with Homebridge:
homebridge_1  |                        
homebridge_1  |     ┌────────────┐     
homebridge_1  |     │ 031-45-154 │     
homebridge_1  |     └────────────┘     
homebridge_1  |                        
homebridge_1  | [2018-1-27 01:26:56] Homebridge is running on port 51826.
homebridge_1  | Disconnected from D-Bus, exiting.
homebridge_1  | Got SIGTERM, quitting.
homebridge_1  | Leaving mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1.
homebridge_1  | Leaving mDNS multicast group on interface eth0.IPv4 with address 10.0.1.11.
homebridge_1  | avahi-daemon 0.6.32 exiting.
homebridge_1  | 
homebridge_1  | /usr/local/lib/node_modules/homebridge/node_modules/mdns/lib/advertisement.js:42
homebridge_1  |     var error = dns_sd.buildException(errorCode);
homebridge_1  |                        ^
homebridge_1  | Error: dns service error: unknown
homebridge_1  |     at Advertisement.on_service_registered (/usr/local/lib/node_modules/homebridge/node_modules/mdns/lib/advertisement.js:42:24)
homebridge_1  |     at SocketWatcher.MDNSService.self.watcher.callback (/usr/local/lib/node_modules/homebridge/node_modules/mdns/lib/mdns_service.js:18:40)
homebridge_1  | [cont-finish.d] executing container finish scripts...
homebridge_1  | [cont-finish.d] done.
homebridge_1  | [s6-finish] syncing disks.
homebridge_1  | [s6-finish] sending all processes the TERM signal.
homebridge_1  | [s6-finish] sending all processes the KILL signal and exiting.
homebridge_1  | [s6-init] making user provided files available at /var/run/s6/etc...exited 0.
homebridge_1  | [s6-init] ensuring user provided files have correct perms...exited 0.
homebridge_1  | [fix-attrs.d] applying ownership & permissions fixes...
homebridge_1  | [fix-attrs.d] done.
homebridge_1  | [cont-init.d] executing container initialization scripts...
homebridge_1  | [cont-init.d] 10-adduser: executing... 
homebridge_1  | usermod: no changes
homebridge_1  | 
homebridge_1  | -------------------------------------
homebridge_1  | GID/UID
homebridge_1  | -------------------------------------
homebridge_1  | User uid:    1000
homebridge_1  | User gid:    1000
homebridge_1  | -------------------------------------
homebridge_1  | 
homebridge_1  | [cont-init.d] 10-adduser: exited 0.
homebridge_1  | [cont-init.d] 20-set-timezone: executing... 
homebridge_1  | [cont-init.d] 20-set-timezone: exited 0.
homebridge_1  | [cont-init.d] 30-packages: executing... 
homebridge_1  | [cont-init.d] 30-packages: exited 0.
homebridge_1  | [cont-init.d] 40-dbus-avahi: executing... 
homebridge_1  | [cont-init.d] 40-dbus-avahi: exited 0.
homebridge_1  | [cont-init.d] 45-user-data: executing... 
homebridge_1  | [cont-init.d] 45-user-data: exited 0.
homebridge_1  | [cont-init.d] 50-plugins: executing... 
homebridge_1  | Homebridge: Installing plugins...
homebridge_1  | npm WARN homebridge No description
homebridge_1  | npm WARN homebridge No repository field.
homebridge_1  | npm WARN homebridge No license field.
homebridge_1  | 
homebridge_1  | up to date in 0.38s
homebridge_1  | npm WARN homebridge No description
homebridge_1  | npm WARN homebridge No repository field.
homebridge_1  | npm WARN homebridge No license field.
homebridge_1  | 
homebridge_1  | up to date in 0.425s
homebridge_1  | [cont-init.d] 50-plugins: exited 0.
homebridge_1  | [cont-init.d] 55-config-ui: executing... 
homebridge_1  | [cont-init.d] 55-config-ui: exited 0.
homebridge_1  | [cont-init.d] done.
homebridge_1  | [services.d] starting services
homebridge_1  | Starting dbus-daemon
homebridge_1  | [services.d] done.
homebridge_1  | Starting Avahi daemon
homebridge_1  | Found user 'avahi' (UID 86) and group 'avahi' (GID 86).
homebridge_1  | Successfully dropped root privileges.
homebridge_1  | avahi-daemon 0.6.32 starting up.
homebridge_1  | WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
homebridge_1  | Loading service file /etc/avahi/services/sftp-ssh.service.
homebridge_1  | Loading service file /etc/avahi/services/ssh.service.
homebridge_1  | *** WARNING: Detected another IPv4 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. ***
homebridge_1  | Joining mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1.
homebridge_1  | New relevant interface docker0.IPv4 for mDNS.
homebridge_1  | Joining mDNS multicast group on interface eth0.IPv4 with address 10.0.1.11.
homebridge_1  | New relevant interface eth0.IPv4 for mDNS.
homebridge_1  | Network interface enumeration completed.
homebridge_1  | Registering new address record for 172.17.0.1 on docker0.IPv4.
homebridge_1  | Registering new address record for fe80::adf3:bbd0:ae26:99a4 on eth0.*.
homebridge_1  | Registering new address record for 10.0.1.11 on eth0.IPv4.
homebridge_1  | Server startup complete. Host name is raspberrypi.local. Local service cookie is 2227238789.
homebridge_1  | Service "raspberrypi" (/etc/avahi/services/ssh.service) successfully established.
homebridge_1  | Service "raspberrypi" (/etc/avahi/services/sftp-ssh.service) successfully established.
homebridge_1  | *** WARNING *** The program 'node' uses the Apple Bonjour compatibility layer of Avahi.
homebridge_1  | *** WARNING *** Please fix your application to use the native API of Avahi!
homebridge_1  | *** WARNING *** For more information see <http://0pointer.de/avahi-compat?s=libdns_sd&e=node>
homebridge_1  | *** WARNING *** The program 'node' called 'DNSServiceRegister()' which is not supported (or only supported partially) in the Apple Bonjour compatibility layer of Avahi.
homebridge_1  | *** WARNING *** Please fix your application to use the native API of Avahi!
homebridge_1  | *** WARNING *** For more information see <http://0pointer.de/avahi-compat?s=libdns_sd&e=node&f=DNSServiceRegister>
homebridge_1  | [2018-1-27 01:40:36] Loaded plugin: homebridge-dummy
homebridge_1  | [2018-1-27 01:40:36] Registering accessory 'homebridge-dummy.DummySwitch'
homebridge_1  | [2018-1-27 01:40:36] ---
homebridge_1  | [2018-1-27 01:40:37] Loaded plugin: homebridge-config-ui-x
homebridge_1  | [2018-1-27 01:40:37] Registering platform 'homebridge-config-ui-x.config'
homebridge_1  | [2018-1-27 01:40:37] ---
homebridge_1  | [2018-1-27 01:40:37] Loaded config.json with 0 accessories and 0 platforms.
homebridge_1  | [2018-1-27 01:40:37] ---
homebridge_1  | [2018-1-27 01:40:37] Loading 0 platforms...
homebridge_1  | [2018-1-27 01:40:37] Loading 0 accessories...
homebridge_1  | Setup Payload:
homebridge_1  | X-HM://0023ISYWYH44A
homebridge_1  | Scan this code with your HomeKit app on your iOS device to pair with Homebridge:
homebridge_1  |                                                       
homebridge_1  |                                                       
homebridge_1  |                                                       
homebridge_1  |                                                       
homebridge_1  |                                                       
homebridge_1  |                                                       
homebridge_1  |                                                       
homebridge_1  |                                                       
homebridge_1  |                                                       
homebridge_1  |                                                       
homebridge_1  |                                                       
homebridge_1  |                                                       
homebridge_1  |                                                       
homebridge_1  |                                                       
homebridge_1  |                                                       
homebridge_1  |                                                       
homebridge_1  |                                                       
homebridge_1  |                                                       
homebridge_1  |                                                       
homebridge_1  |                                                       
homebridge_1  |                                                       
homebridge_1  |                                                       
homebridge_1  |                                                       
homebridge_1  |                                                       
homebridge_1  |                                                       
homebridge_1  |                                                       
homebridge_1  |                                                       
homebridge_1  | Or enter this code with your HomeKit app on your iOS device to pair with Homebridge:
homebridge_1  |                        
homebridge_1  |     ┌────────────┐     
homebridge_1  |     │ 031-45-154 │     
homebridge_1  |     └────────────┘     
homebridge_1  |                        
homebridge_1  | [2018-1-27 01:40:37] Homebridge is running on port 51826.

My initial docker image is still running fine and I apparently have a second docker image running somewhere as well but I don't know where! So I somehow SCREWED UP!

Is there any way I can get rid of this second docker image and then re-create it the correct way? Any instructions would be so very much appreciated!

How to change timezone

Hey,

I have this up an running now but the timestamps in my logs are all incorrect. Do you know how to change the timezone of the docker image after install? I saw some instructions on how to set it during install but I'm unsure what SSH command to issue inside the docker image so that it will set the time zone to Los Angeles.

Thanks so much!

AppleTV upgrade caused problems

Yesterday evening I upgraded my AppleTV to the very latest iOS. Since then my Wemo devices which I am running under Homebridge are not responding anymore. Everything was working fine until the upgrade. Knowing that the AppleTV is the HomeKit hub......
Any ideas ?

file owner changes to uid or gid

I have the strange issue that the file owner:group of the mounted files is changing on the host to 911, which is the uid and gid I have set in the env.

docker-compose
  homebridge:
    image: oznu/homebridge:raspberry-pi
    restart: always
    network_mode: host
    environment:
      - TZ=Europe/Vienna
      - PGID=911
      - PUID=911
    volumes:
      - /home/pirate/docker-libertas/homebridge:/homebridge
bash
drwxr-xr-x 5    911    911 4096 Jul 20 19:24 homebridge

It is doing this continuously. I've change the permissions while the container was running and after some time it changed just back.

homebridge-people not working

Thanks for the work you do for this docker. I like the web interface feature.

I recently had my homebridge installed in a Lubuntu install. Switched over to docker since it is easier to mange config files and updating, etc. This was all working fine before my switch (of course, that is how it also goes). Using exact same config and config has to errors. I do not believe this is an issue with the plugin, since it worked fine like previously mentioned.

Container can ping my resolve DNS name and ping device ok, see below:

docker exec -it homebridge ping xxxxxxxxx.xxxxxx.net
PING xxxxxxxxx.xxxxxx.net (10.0.0.107): 56 data bytes
64 bytes from 10.0.0.107: seq=0 ttl=64 time=105.091 ms
64 bytes from 10.0.0.107: seq=1 ttl=64 time=26.441 ms
64 bytes from 10.0.0.107: seq=2 ttl=64 time=50.085 ms

Tried both IP and hostname in config for testing, still no go.

        {
            "platform": "People",
            "threshold": 15,
            "anyoneSensor": true,
            "nooneSensor": false,
            "webhookPort": 51828,
            "pingInterval": 10000,
            "ignoreReEnterExitSeconds": 0,
            "people": [
                {
                    "name": "xxxxx",
                    "target": "10.0.0.107",
                    "threshold": 15,
                    "pingInterval": 10000,
                    "ignoreReEnterExitSeconds": 0
                },
                {
                    "name": "xxxxx",
                    "target": "xxxxxxx.xxxxx.net",
                    "threshold": 15,
                    "pingInterval": 10000,
                    "ignoreReEnterExitSeconds": 0
                }
            ]

Any other info needed, let me know.

Config plugin doesn't work by default or when configured

By default when the config ui is enabled nothing starts up. I added the plugin and I just keep getting this error:
[2018-1-13 20:21:20] Error: Cannot find module '../build/Release/pty.node'

When I disable the config ui I no longer continue to get the errors but for some reason it still happens once while starting up which also seems fairly odd.

Why docker?

Sorry I’m a n00b to the Pi! I currently have homebridge running on my Mac but want to try a Homebridge Pi Installation instead. I have two questions about docker-homebridge:

  1. what’s the benefit of installing homebridge inside of docker instead of just installing it straight onto the Pi as described here: https://github.com/nfarina/homebridge/wiki/Running-HomeBridge-on-a-Raspberry-Pi

  2. is this the same build as the “original” homebridge built? Once installed will an update always pull the latest homebridge data directly or will it first have to be integrated into this package again? I guess what I’m asking is this: if docker-homebridge is no longer maintend does that mean I won’t be getting any further homebridge updates?

Lastly I’m wondering if there any downsides to using homebridge inside of docker.

Thanks so much! ;)

Synology: Host name conflict

A fresh install (latest image, latest Synology DSM, latest iOS 11) of homebridge does not work for me. The logs show this:

Withdrawing address record for fe80::42:4cff:fea6:2530 on docker0.
Withdrawing address record for 172.17.0.1 on docker0.
Withdrawing address record for 172.16.1.200 on eth0.
Host name conflict, retrying with homebridge-48
Registering new address record for fe80::42:4cff:fea6:2530 on docker0.*.
Registering new address record for 172.17.0.1 on docker0.IPv4.
Registering new address record for 169.254.175.241 on eth1.IPv4.
Registering new address record for 172.16.1.200 on eth0.IPv4.

As you can see, it's already at -48 and this keeps going on forever.

The relevant log messages are:

Starting Avahi daemon
Found user 'avahi' (UID 86) and group 'avahi' (GID 86).
Successfully dropped root privileges.
avahi-daemon 0.6.32 starting up.
WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
Loading service file /etc/avahi/services/sftp-ssh.service.
Loading service file /etc/avahi/services/ssh.service.
*** WARNING: Detected another IPv4 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. ***
*** WARNING: Detected another IPv6 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. ***
Joining mDNS multicast group on interface docker0.IPv6 with address fe80::42:4cff:fea6:2530.
New relevant interface docker0.IPv6 for mDNS.
Joining mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1.
New relevant interface docker0.IPv4 for mDNS.
Joining mDNS multicast group on interface eth1.IPv4 with address 169.254.175.241.
New relevant interface eth1.IPv4 for mDNS.
Joining mDNS multicast group on interface eth0.IPv4 with address 172.16.1.200.
New relevant interface eth0.IPv4 for mDNS.
Network interface enumeration completed.

I have no other Docker images running on the Synology, but there is (native) Plex and a few other services. Is something else running an mDNS service that causes this?

My iOS 11 device is not able to find the homebridge. Entering the code manually just shows a loading spinner that is there forever.

Error - Homebridge on my Synology NAS

Having followed the set-up to the dot I am getting when starting the container the following error
message.
Being a novice I am not sure where to lock to get this resolved.

[2018-1-20 16:18:01] Loaded plugin: homebridge-dummy
[2018-1-20 16:18:01] Registering accessory 'homebridge-dummy.DummySwitch'
[2018-1-20 16:18:01] ---
[2018-1-20 16:18:02] Loaded plugin: homebridge-platform-wemo
[2018-1-20 16:18:02] Registering platform 'homebridge-platform-wemo.BelkinWeMo'
[2018-1-20 16:18:02] ---
[2018-1-20 16:18:02] Loaded plugin: homebridge-config-ui-x
[2018-1-20 16:18:02] Registering platform 'homebridge-config-ui-x.config'
[2018-1-20 16:18:02] ---
[2018-1-20 16:18:02] Loaded config.json with 3 accessories and 0 platforms.
[2018-1-20 16:18:02] ---
[2018-1-20 16:18:02] Loading 0 platforms...
[2018-1-20 16:18:02] Loading 3 accessories...

/usr/local/lib/node_modules/homebridge/lib/api.js:64
throw new Error("The requested accessory '" + name + "' was not registered by any plugin.");
^
Error: The requested accessory 'Guest room' was not registered by any plugin.
at API.accessory (/usr/local/lib/node_modules/homebridge/lib/api.js:64:13)
at Server._loadAccessories (/usr/local/lib/node_modules/homebridge/lib/server.js:264:42)
at Server.run (/usr/local/lib/node_modules/homebridge/lib/server.js:86:38)
at module.exports (/usr/local/lib/node_modules/homebridge/lib/cli.js:40:10)
at Object. (/usr/local/lib/node_modules/homebridge/bin/homebridge:17:22)
at Module._compile (module.js:643:30)
at Object.Module._extensions..js (module.js:654:10)
at Module.load (module.js:556:32)
at tryModuleLoad (module.js:499:12)
at Function.Module._load (module.js:491:3)
at Function.Module.runMain (module.js:684:10)
at startup (bootstrap_node.js:187:16)
at bootstrap_node.js:608:3
*** WARNING *** The program 'node' 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=node
*** WARNING *** The program 'node' 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=node&f=DNSServiceRegister

Homebridge Not Running Error

Hi,

I have three docker instances of Homebridge running on my Pi. Everything worked well for a while but not two of my instances show "not running" in the UI-X interface and all accessories in those instances are offline:

screen shot 2018-02-19 at 10 03 13 am

The two containers that don't have homebridge running are "Homebridge-Misc" and "Homebridge:

screen shot 2018-02-19 at 9 44 13 am

Any idea on how to get those up and running?

Thanks!

Philipp

PS: maybe this will help as well?

screen shot 2018-02-19 at 10 17 03 am

Installation on Raspberry Pi / Stretch

Hi

I've just installed this image on a RasPi with Stretch, and the Docker installation is a little different.

Is it worth updating the docs, or creating a version for Stretch?

Not seeing Homebridge on Network

Hi, I have deploy your container on my host and I'm not able to pair it through my iPhone running iOS 11

Host configuration :

  • Hostname : skynet
  • Custom build with Ryzen 5 1600
  • OS : Ubuntu Server 17.10
  • Docker version : 17.12.0 with Portainer as web ui.

Other containers that I have :

  • Plex
  • OpenVPN
  • Transmission
  • Sonarr
  • Radarr
  • phpVirtualBox

I can confirm that this is the only running Homebridge setup over the network.

Here is the stderr output :

npm WARN homebridge No description
npm WARN homebridge No repository field.
npm WARN homebridge No license field.

npm WARN homebridge No description
npm WARN homebridge No repository field.
npm WARN homebridge No license field.

Found user 'avahi' (UID 86) and group 'avahi' (GID 86).
Successfully dropped root privileges.
avahi-daemon 0.6.32 starting up.
WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
Loading service file /etc/avahi/services/sftp-ssh.service.
Loading service file /etc/avahi/services/ssh.service.
*** WARNING: Detected another IPv4 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. ***
Joining mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1.
New relevant interface docker0.IPv4 for mDNS.
Joining mDNS multicast group on interface enp6s0.IPv4 with address 192.168.2.10.
New relevant interface enp6s0.IPv4 for mDNS.
Network interface enumeration completed.
Registering new address record for fe80::c4cf:f8ff:fe87:725a on veth002441e.*.
Registering new address record for fe80::c8a1:4dff:feae:cc10 on vetha67438e.*.
Registering new address record for fe80::84ab:9fff:fe3f:a7a1 on veth5e055a7.*.
Registering new address record for fe80::fc4d:fbff:febf:1202 on vethe472e49.*.
Registering new address record for fe80::18ae:9dff:fe03:c781 on vethe7a39a4.*.
Registering new address record for fe80::42:1fff:fe58:e380 on docker0.*.
Registering new address record for 172.17.0.1 on docker0.IPv4.
Registering new address record for fe80::e2d5:5eff:fe23:5a7e on enp6s0.*.
Registering new address record for 192.168.2.10 on enp6s0.IPv4.
Server startup complete. Host name is skynet.local. Local service cookie is 4088301714.
Withdrawing address record for fe80::c4cf:f8ff:fe87:725a on veth002441e.
Withdrawing address record for fe80::c8a1:4dff:feae:cc10 on vetha67438e.
Withdrawing address record for fe80::84ab:9fff:fe3f:a7a1 on veth5e055a7.
Withdrawing address record for fe80::fc4d:fbff:febf:1202 on vethe472e49.
Withdrawing address record for fe80::18ae:9dff:fe03:c781 on vethe7a39a4.
Withdrawing address record for fe80::42:1fff:fe58:e380 on docker0.
Withdrawing address record for fe80::e2d5:5eff:fe23:5a7e on enp6s0.
Withdrawing address record for 192.168.2.10 on enp6s0.
Host name conflict, retrying with skynet-2
Registering new address record for fe80::c4cf:f8ff:fe87:725a on veth002441e.*.
Registering new address record for fe80::c8a1:4dff:feae:cc10 on vetha67438e.*.
Registering new address record for fe80::84ab:9fff:fe3f:a7a1 on veth5e055a7.*.
Registering new address record for fe80::fc4d:fbff:febf:1202 on vethe472e49.*.
Registering new address record for fe80::18ae:9dff:fe03:c781 on vethe7a39a4.*.
Registering new address record for fe80::42:1fff:fe58:e380 on docker0.*.
Registering new address record for 172.17.0.1 on docker0.IPv4.
Registering new address record for fe80::e2d5:5eff:fe23:5a7e on enp6s0.*.
Registering new address record for 192.168.2.10 on enp6s0.IPv4.
Withdrawing address record for fe80::c4cf:f8ff:fe87:725a on veth002441e.
Withdrawing address record for fe80::c8a1:4dff:feae:cc10 on vetha67438e.
Withdrawing address record for fe80::84ab:9fff:fe3f:a7a1 on veth5e055a7.
Withdrawing address record for fe80::fc4d:fbff:febf:1202 on vethe472e49.
Withdrawing address record for fe80::18ae:9dff:fe03:c781 on vethe7a39a4.
Withdrawing address record for fe80::42:1fff:fe58:e380 on docker0.
Withdrawing address record for fe80::e2d5:5eff:fe23:5a7e on enp6s0.
Withdrawing address record for 192.168.2.10 on enp6s0.
Host name conflict, retrying with **skynet-3**
// And so on testing skynet-...

I have saw the *** WARNING: Detected another IPv4 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. *** message but things is, when I run nmap localhost -p 5353 It outputs

PORT     STATE  SERVICE
5353/tcp closed mdns

I don't see where the "another IPv4 mDNS stack" could be.

Any help?

Thanks!

Homebridge v0.4.22 on Raspberry Pi

Hey,
I'm running the latest version on a pi3

$ docker-compose pull homebridge Pulling homebridge (oznu/homebridge:raspberry-pi)... raspberry-pi: Pulling from oznu/homebridge Digest: sha256:5aa6177e2752a08ff1a8d8f27039d71c775d191d4da4c32fb09036a6ac349b31 Status: Image is up to date for oznu/homebridge:raspberry-pi

but getting this error when trying to use the hue plugin:

[7/10/2017, 4:00:04 AM] Error: Plugin /homebridge/node_modules/homebridge-hue requires a HomeBridge version of ^0.4.22 which does not satisfy the current HomeBridge version of 0.4.20. You may need to upgrade your installation of HomeBridge.

Will you update?

Can't start Homebridge (cannot import name ReadTimeoutError)

Hi - sorry, I don't know where to go with this, I'm just following the instructions! I've tried google and that's not working for me, any suggestions please?

docker-compose up -d
Traceback (most recent call last):
File "/usr/local/bin/docker-compose", line 7, in
from compose.cli.main import main
File "/usr/local/lib/python2.7/dist-packages/compose/cli/main.py", line 17, in
from . import errors
File "/usr/local/lib/python2.7/dist-packages/compose/cli/errors.py", line 15, in
from requests.packages.urllib3.exceptions import ReadTimeoutError
ImportError: cannot import name ReadTimeoutError

pip freeze
backports.ssl-match-hostname==3.5.0.1
blinker==1.3
cached-property==1.3.1
chardet==2.3.0
colorama==0.3.2
docker==2.5.1
docker-compose==1.16.1
docker-pycreds==0.2.1
dockerpty==0.4.1
docopt==0.6.2
enum34==1.1.6
Flask==0.10.1
functools32==3.2.3.post2
gpiozero==1.4.0
html5lib==0.999
ipaddress==1.0.18
itsdangerous==0.24
Jinja2==2.7.3
jsonschema==2.6.0
lxkeymap==0.1
MarkupSafe==0.23
mcpi==0.1.1
ndg-httpsclient==0.3.2
numpy==1.8.2
picamera==1.13
picraft==1.0
pifacecommon==4.2.1
pifacedigitalio==3.1.0
pigpio==1.35
Pillow==2.6.1
pyasn1==0.1.7
pygame==1.9.2a0
pygobject==3.14.0
pyinotify==0.9.4
pyOpenSSL==0.13.1
pyserial==2.6
python-apt==0.9.3.12
PyYAML==3.12
requests==2.4.3
RPi.GPIO==0.6.3
RTIMULib==7.2.1
sense-emu==1.0
sense-hat==2.2.0
six==1.8.0
smbus==1.1
spidev==3.0
texttable==0.9.1
twython==3.1.2
urllib3==1.9.1
websocket-client==0.44.0
Werkzeug==0.9.6

Install failure - rPi Zero W

Getting a failure while installing on brand new Raspberry Pi Zero W, running Raspbian Stretch Light

Command was sudo apt-get update && sudo apt-get install docker-ce

`invoke-rc.d: initscript docker, action "start" failed.
● docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: core-dump) since Sat 2017-09-23 18:55:21 UTC; 182ms ago
Docs: https://docs.docker.com
Process: 16506 ExecStart=/usr/bin/dockerd -H fd:// (code=dumped, signal=SEGV)
Main PID: 16506 (code=dumped, signal=SEGV)
CPU: 44ms

Sep 23 18:55:21 homebridge systemd[1]: Failed to start Docker Application C…ine.
Sep 23 18:55:21 homebridge systemd[1]: docker.service: Unit entered failed …ate.
Sep 23 18:55:21 homebridge systemd[1]: docker.service: Failed with result '…mp'.
Sep 23 18:55:22 homebridge systemd[1]: docker.service: Service hold-off tim…art.
Hint: Some lines were ellipsized, use -l to show in full.
dpkg: error processing package docker-ce (--configure):
subprocess installed post-installation script returned error exit status 1
Processing triggers for libc-bin (2.24-11+deb9u1) ...
Processing triggers for systemd (232-25+deb9u1) ...
Errors were encountered while processing:
docker-ce
E: Sub-process /usr/bin/dpkg returned an error code (1)
`

Any help would be greatly appreciated.

Why not to merge with homebridge repo

Hi,

Thank you very much for sharing this. It works flawlessly.

I wonder if you have considered to actually merge this with Nfarina's homebridge repo. I think having all together makes more sense so you can build the container based on the latest code as well.

Best Regards,
Rafael Lorenzo.

Can not find the config.json on WD PR4100

I have installed in docker on my WD PR4100 and it shows up on my iPhone and I can add the home bridge just can not see the plugins and not sure how to get to the config.json and also how to verify the plugins

I installed

docker create --name=homebridge --net=host -e PGID=1001 -e PUID=1001 --restart=always -v /mnt/HD/HD_a2/docker-config/homebridge-config:/config -e TZ=Asia/Phnom_Penh oznu/homebridge

then added plugin

docker exec homebridge yarn add homebridge-tado-ac

but get this result

root@NAS config # docker exec homebridge yarn add homebridge-tado-ac
yarn add v1.3.2
warning package.json: No license field
warning No license field
[1/4] Resolving packages...
[2/4] Fetching packages...
warning [email protected]: The engine "homebridge" appears to be invalid.
warning [email protected]: The engine "homebridge" appears to be invalid.
warning [email protected]: The engine "homebridge" appears to be invalid.
[3/4] Linking dependencies...
[4/4] Building fresh packages...
success Saved lockfile.
success Saved 1 new dependency.
└─ [email protected]
warning No license field
Done in 4.80s.

also when adding the config ui

docker exec homebridge yarn add homebridge-config-ui-x

yarn add v1.3.2
warning package.json: No license field
warning No license field
[1/4] Resolving packages...
warning homebridge-config-ui-x > read-last-lines > [email protected]: Use mz or fs-extra^3.0 with Promise Support
[2/4] Fetching packages...
warning [email protected]: The engine "homebridge" appears to be invalid.
warning [email protected]: The engine "homebridge" appears to be invalid.
warning [email protected]: The engine "homebridge" appears to be invalid.
[3/4] Linking dependencies...
[4/4] Building fresh packages...
success Saved lockfile.
success Saved 143 new dependencies.
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
├─ [email protected]
└─ [email protected]
warning No license field
Done in 17.76s.

homebridge-people not working. how 2 debug

Hey there,
i am very satisfied, but homebridge people doesn't recognize any of my devices. Not with IP or Hostname, so i wanted to try do debug this but don't know how. Ping command in docker container is working and my devices can be pinged out of de container.
I thing this must be a problem with this Docker Container becaus on my RasPi it worked formerly.

Thanks for any hint =)

Can't pair homebridge with iOS11

I am running the container using windows 10.

All of my configurations seems to be fine, I have managed to install plugins and they find the accessories I have.

The issue is that I am unable to pair it with my phone, I have noticed that homebridge is running on a different subnet than my phone, did anyone managed to get this running on Windows 10?

I am attaching the log file and my config file and hoping someone can help me get this up and running!
homebridgelog.txt

Thanks,

image

image

homebridge-camera-ffmpeg howto?

Sorry for the noob-question, but I'd like to use the homebridge-camera-ffmpeg module with home bridge. Is there any HowTo which shows how to add ffmpeg to the container?

Thanks!
Michael

Can’t install new plugin via config-ui-x

I wondering if installing plug ins via the Config-UI-X interface is not possible? If I try to install a plugin via the web interface I get the following error message:

4be38a3d-f2cc-4d6b-af78-f72356533afe

Installing plugins via the terminal (yarn) works. Would love to be able to install plugins right from the web GUI, though!

Plugins do not install on image update

When I upgrade to the latest docker image, I get an error that a plugin i installed does not exist. It shows up in the list of plugins in the web GUI, so I use that GUI to delete the plugin and then re-install it and then everything works. But this happens every time there is a new version of the docker image and I was wondering if there would be a more permanent fix to this.

Startup Issue

Hi, Since the most recent update homebridge is no longer starting up and I'm seeing the following error (its reversed) and seems related to the harmonyhub plugin:

8-01-11 08:48:53 | stdout | at Function.Module._load (module.js:491:3)
-- | -- | --
2018-01-11 08:48:53 | stdout | at tryModuleLoad (module.js:499:12)
2018-01-11 08:48:53 | stdout | at Module.load (module.js:556:32)
2018-01-11 08:48:53 | stdout | at Object.Module._extensions..js (module.js:654:10)
2018-01-11 08:48:53 | stdout | at Module._compile (module.js:643:30)
2018-01-11 08:48:53 | stdout | at Object.<anonymous> (/homebridge/node_modules/node-xmpp-core/lib/Stanza.js:4:15)
2018-01-11 08:48:53 | stdout | at require (internal/module.js:11:18)
2018-01-11 08:48:53 | stdout | at Module.require (module.js:587:17)
2018-01-11 08:48:53 | stdout | at Function.Module._load (module.js:468:25)
2018-01-11 08:48:53 | stdout | at Function.Module._resolveFilename (module.js:538:15)
2018-01-11 08:48:53 | stdout | Error: Cannot find module 'ltx/lib/Element'
2018-01-11 08:48:53 | stdout |  
2018-01-11 08:48:53 | stdout | ^
2018-01-11 08:48:53 | stdout | throw err;
2018-01-11 08:48:53 | stdout | module.js:540
2018-01-11 08:48:53 | stdout | [2018-1-11 08:48:53] Loaded plugin: homebridge-harmonyhub
2018-01-11 08:48:53 | stdout | [2018-1-11 08:48:53] ---
2018-01-11 08:48:53 | stdout | [2018-1-11 08:48:53] Registering platform 'homebridge-flic.Flic'
2018-01-11 08:48:53 | stdout | [2018-1-11 08:48:53] Loaded plugin: homebridge-flic
2018-01-11 08:48:53 | stdout | [2018-1-11 08:48:53] ---
2018-01-11 08:48:53 | stdout | [2018-1-11 08:48:53] Registering platform 'homebridge-edomoticz.eDomoticz'
2018-01-11 08:48:53 | stdout | [2018-1-11 08:48:53] Loaded plugin: homebridge-edomoticz
2018-01-11 08:48:53 | stdout | └───────────────────────────────────────────────────┘
2018-01-11 08:48:53 | stdout | │ sudo chown -R $USER:$(id -gn $USER) /root/.config │
2018-01-11 08:48:53 | stdout | │       to the local update config store via        │
2018-01-11 08:48:53 | stdout | │        Try running with sudo or get access        │
2018-01-11 08:48:53 | stdout | │              npm update check failed              │

I did have issues with harmonyhub plugin when i updated npm on a local install which is why I switched to your docker, any ideas?

Logging

Hey - sorry, this may be more of a homebridge question, but I am trying to troubleshoot issues using Homebridge and I cant find the logs as stated in the homebridge docs (.log and .err). I know I can get some logs from docker and the containers folder, but is that all of them or is there additional logging that can be enabled? Thanks

homebridge-config-ui not work

docker exec Homebridge yarn add homebridge-config-ui
I installed this plugin, but the path in the plugin is/usr/lib/node_modules, not compatible with your Homebridge, what is the solution?

'Socket Closed'

Thanks for your great work with this package.

Everything was working as expected (no config changes), until I recently attempted to access the Terminal within a Container. I get the error 'Socket Closed'. Is there anything that might be causing this?

Docker & Homebridge

Not a issue... What is the benefit of running docker with homebridge? I'm new to docker and I'm trying to understand it's function in a project like this.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.