Docker Homebridge

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

Guides

• Running Homebridge on a Raspberry Pi
• Running Homebridge on a Synology NAS

Compatibility

Homebridge requires full access to your local network to function correctly which can be achieved using the --net=host flag. Currently this image will not work when using Docker for Mac or Docker for Windows due to this and this.

Usage

docker run \
  --net=host \
  --name=homebridge \
  -e PUID=<UID> -e PGID=<GID> \
  -e TZ=<timezone> \
  -v </path/to/config>:/homebridge \
  oznu/homebridge

Raspberry Pi / ARMv6

This image will also run on a Raspberry Pi or other Docker-enabled ARMv6/7/8 devices by using the using the arm32v6 tag:

docker run --net=host --name=homebridge oznu/homebridge:arm32v6

This docker image has been tested on the following Raspberry Pi models:

• Raspberry Pi 1 Model B
• Raspberry Pi 3 Model B
• Raspberry Pi Zero W

See the wiki for a guide on getting Homebridge up and running on a Raspberry Pi.

AARCH64 / arm64v8

This image will also run on AARCH64/arm64v8 devices using the arm64v8 tag:

docker run --net=host --name=homebridge oznu/homebridge:arm64v8

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
• -e TZ - for timezone information e.g. -e TZ=Europe/London
• -e PGID - for GroupID - see below for explanation
• -e PUID - for UserID - see below for explanation

Optional Settings:

• -e PACKAGES - Additional packages to install (comma separated, no spaces) e.g. -e PACKAGES=ffmpeg,openssh
• -e TERMINATE_ON_ERROR=1 - If TERMINATE_ON_ERROR is set to 1 then the container will exit when the Homebridge process ends, otherwise it will be restarted.
• -e HOMEBRIDGE_INSECURE=1 - Start homebridge in insecure mode using the -I flag.
• -e HOMEBRIDGE_DEBUG=1 - Enable debug level logging using the -D flag.

Homebridge UI Options:

This is the only supported method of running homebridge-config-ui-x on oznu/homebridge.

• -e HOMEBRIDGE_CONFIG_UI=1 - Enable and configure homebridge-config-ui-x which allows you to manage and configure Homebridge from your web browser.
• -e HOMEBRIDGE_CONFIG_UI_PORT=8080 - The port to run homebridge-config-ui-x on. Defaults to port 8080.

User / Group Identifiers

Sometimes when using data volumes (-v flags) permissions issues can arise between the host OS and the container. We avoid this issue by allowing you to specify the user PUID and group PGID. Ensure the data volume directory on the host is owned by the same user you specify and it will "just work".

In this instance PUID=1001 and PGID=1001. To find yours use id user as below:

  $ id <dockeruser>
    uid=1001(dockeruser) gid=1001(dockergroup) groups=1001(dockergroup)

Homebridge Config

The Homebridge config file is located at </path/to/config>/config.json This file will be created the first time you run the container if it does not already exist.

Homebridge Plugins

Plugins should be defined in the </path/to/config>/package.json file in the standard NPM format. This file will be created the first time you run the container if it does not already exist.

Any plugins added to the package.json will be installed each time the container is restarted. Plugins can be uninstalled by removing the entry from the package.json and restarting the container.

You can also install plugins using npm which will automatically update the package.json file as you add and remove modules.

You must restart the container after installing or removing plugins for the changes to take effect.

To add plugins using npm:

docker exec <container name or id> npm install <module name>

Example:

docker exec homebridge npm install homebridge-dummy

To remove plugins using npm:

docker exec <container name or id> npm remove <module name>

Example:

docker exec homebridge npm remove homebridge-dummy

To add plugins using startup.sh script:

The first time you run the container a script named startup.sh will be created in your mounted /homebridge volume. This script is executed everytime the container is started, before Homebridge loads, and can be used to install plugins if you don't want to edit the package.json file manually.

To add plugins using the startup.sh script just use the npm install command:

#!/bin/sh

npm install homebridge-dummy

This container does NOT require you to install plugins globally (using npm install -g or yarn global add) and doing so is NOT recommended or supported.

Docker Compose

If you prefer to use Docker Compose:

version: '2'
services:
  homebridge:
    image: oznu/homebridge:latest  # use "arm32v6" instead of "latest" for arm devices
    restart: always
    network_mode: host
    environment:
      - TZ=Australia/Sydney
      - PGID=1000
      - PUID=1000
    volumes:
      - ./volumes/homebridge:/homebridge

Troubleshooting

1. Verify your config.json and package.json syntax

Many issues appear because of invalid JSON. A good way to verify your config is to use the jsonlint.com validator.

2. When running on Synology DSM set the DSM_HOSTNAME environment variable

You may need to provide the server name of your Synology NAS using the DSM_HOSTNAME environment variable to prevent hostname conflict errors. The value of the DSM_HOSTNAME environment should exactly match the server name as shown under Synology DSM Control Panel -> Info Centre -> Server name, it should contain no spaces or special characters.

3. Need ffmpeg?

You can enable ffmpeg by adding this environment variable to your run command or docker-compose.yml:

PACKAGES=ffmpeg

4. Try the debian tag

Some plugins don't like Alpine Linux so this project also provides a Debian based version of the image.

docker run oznu/homebridge:debian
docker run oznu/homebridge:debian-arm32v7

See the wiki for a list of image variants: https://github.com/oznu/docker-homebridge/wiki

5. Logs showing Service name conflict or Host name conflict

You may need to use a no-avahi version of this image to prevent conflicts with the Avahi service running on the host:

# Alpine
docker run oznu/homebridge:no-avahi
docker run oznu/homebridge:no-avahi-arm32v6
docker run oznu/homebridge:no-avahi-arm64v8

# Debian
docker run oznu/homebridge:debian-no-avahi
docker run oznu/homebridge:debian-no-avahi-arm32v7

See the wiki for a list of image variants: https://github.com/oznu/docker-homebridge/wiki

6. Ask on Slack

Join the Homebridge Slack chat and ask in the #docker channel.