Skip to content
This repository has been archived by the owner on Aug 24, 2021. It is now read-only.

.env Options

Jump to bottom
Marco Raddatz edited this page Jul 4, 2019 · 1 revision

If you intend to develop a plugin or Homebridge is not running as it's supposed to, you might want to start Homebridge with debugging options. To do so, copy the sample .env file to /volume1/docker/homebridge and set the desired environment. Don't forget to place your plugins manually under /volume1/docker/homebridge/plugins and (re-) start the container. See the Homebridge docs for details.

.env options

All .env variables are optional.

HOMEBRIDGE_ENV

  • production (default)
    Starts Homebridge without any options.
  • development
    Starts Homebridge with plugin support.
  • debug
    Starts Homebridge with plugin support and maximum debugging info.
  • production-insecure
    Starts Homebridge with HTTP support.
  • development-insecure
    Starts Homebridge with plugin support and HTTP support.
  • debug-insecure
    Starts Homebridge with plugin support, HTTP support and maximum debugging info.

HOMEBRIDGE_TIMEZONE

Manually set a timezone. (This environment variable is equal to Linux' TZ variable.) See https://en.wikipedia.org/wiki/List_of_tz_database_time_zones for valid options. If no timezone is set, UTC will be used.

HOMEBRIDGE_VERSION

To avoid breaks with either new Homebridge releases or iOS updates, you can force the installation of a specific Homebridge version. HOMEBRIDGE_VERSION accepts any release tag (f.e "0.4.17") or valid NPM version range.

DS_HOSTNAME

Set the DiskStation hostname. This can be helpful, if Homekit doesn't find your local DiskStation. The value 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.

Home

Clone this wiki locally