Skip to content


Switch branches/tags

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time

Home Automation Server

Home automation system based on Homebridge.

It includes a web interface for controlling accessories, activating and configuring scenes, automations and custom controls. Configuring accessories in the web interface and storing historical data is not supported yet.

It includes a plugin system to add accessories, accessory configuration, authentication and options for automations. All Homebridge plugins are supported.




  • Web interface
    • Layouts
      • Customisable by dragging sections and accessories in the web interface.
      • Scenes
      • Cameras
      • Custom sections with plugins
      • Service groups (one tile controls multiple accessories)
        • Group services into a single service with merged values
    • Basic accessory control (on/off)
    • Accessory control
    • Dark theme (system wide)
    • Notifications
    • Configuration
      • Add + configure accessories in the web interface
        • Set home/accessory/service names
      • Server status and output
      • Custom layouts
      • Manage users/permissions
      • Manage HomeKit bridges + choose accessories to expose
        • Per-user HomeKit bridges (see above)
      • Expose accessories via multiple bridges
      • Manage + name HomeKit pairings
  • Desktop app
    • Electron app that wraps the web interface and provides notifications in the background.
    • Supports all operating systems supported by Electron (though for macOS you probably want to use the built in Home app).
    • Uses a local copy of the web interface instead of using the server's.
  • Historical data
    • Store changes to an accessory's state
      • Enable with the --experimental-history flag. Currently only stores changes already visible to hap-server (when plugins (usually incorrectly) update without any subscribed clients, when controlled in hap-server or when a controller is subscribed to changes) and from all accessories.
    • Elgato Eve???
  • Security
    • Web interface authentication
      • Completely handled by plugins.
    • Permissions
      • Web interface permission checks
    • Per-user HomeKit bridges
      • This would allow you to configure all accessories in hap-server and then allow multiple people to create their own homes with read-only access (or no access) to other people's accessories instead of sharing a single home where everyone has permission to control all accessories. Also allows users to choose their own favourite accessories/scenes/colours and using multiple devices without an Apple ID.
    • Multiple pairings with a single bridge?
    • Process isolation (e.g. using a separate process for each plugin)
  • Scenes
    • Works with automations. (Scenes just run automation conditions to check if they're enabled and automation actions to activate/deactivate them.)
    • Simple scene editor. (Set accessories to create active conditions and activate/deactivate actions.)
    • Restore state before scene was enabled (using existing historical data)
  • Automations
    • Create automations that can run on the server
      • Useful if you don't have an Apple TV 4, HomePod or always home iPad.
      • Also could easily allow for more flexible automations than HomeKit allows.
    • Manage automations in the web interface
      • TODO:
        • Better error handling
        • Handle triggers/conditions/actions that don't have an editor component
        • Set characteristic action editor
    • Triggers
      • Cron expressions
      • Sunrise/sunset
      • Characteristic changes
        • Any change
        • Set to value
        • Set below/above value
    • Conditions
      • All/any
      • JavaScript
      • Check characteristic
    • Actions
      • Conditional
      • JavaScript
      • Set characteristic
        • Increment/decrement
        • Transitions
    • Automation history
  • Temporary scheduled actions
    • "Turn the lights off in 10 minutes."
  • Cameras
    • Basic support (use with HomeKit)
    • Snapshots in the web interface
    • Live streaming in the web interface
    • HomeKit Secure Video??
    • Recording??
  • Routers
    • Basic support (use with HomeKit)
      • For routers and HomeKit Accessory Security: no support as the TLV format isn't known yet.
      • For Wi-Fi extenders (or satellites as they are called internally) - these are very basic (only provides a connected/not connected status): supported in hap-nodejs, but not yet in hap-server until Homebridge also updates hap-nodejs.
    • Visible in the web interface
    • Controllable in the web interface
  • Merged accessories
    • Merge services from multiple accessories into a single accessory to add functionality with multiple plugins.
  • Add HomeKit accessories
    • HomeKit over IP
    • HomeKit over BLE
  • Plugins
    • Accessories
    • Accessory platforms
    • All current Homebridge accessories + accessory platforms
    • Web interface plugins
      • Layout sections
      • Basic accessory control
      • Accessory control
      • Accessory + accessory platform discovery + setup
      • Accessory + accessory platform configuration
      • Authentication
      • User management
      • Automation trigger configuration
      • Automation condition configuration
      • Automation action configuration
      • Custom routes and menu items
      • Custom modals
    • Web interface themes?
    • Automation plugins
      • Automation plugins can run other automation conditions/actions.
      • Automation triggers
      • Automation conditions
      • Automation actions
    • Install + manage plugins in the web interface?
      • Like server output???
  • Performance and stability features
    • Cached accessories
      • Accessory configuration can be cached so the server can run immediately and have accessories load in the background.
      • This works differently to Homebridge - plugins can just create accessories as normal instead of restoring event handlers to a restored accessory object. Plugins can use the restored accessory object if they want to though.
    • HAP time warnings
      • hap-server will output a warning when an accessory takes more than 2 seconds to get a value, or 5 seconds to set a value.
  • Configuration reloading
    • Global plugin configuration cannot be reloaded.
    • Accessories + accessory platforms
    • HAP bridges
    • Server hostname
    • Listening addresses and HTTPS configuration
    • Automations
  • Platform compatibility
    • macOS
    • Linux??
    • Windows??
  • Full compatibility with Homebridge
    • Run instead of Homebridge and use all Homebridge plugins with the web interface. Homebridge accessories appear and can be controlled in the web interface, by automations on the server and with hap-server's HAP bridges.


npm install -g @hap-server/hap-server

# Or if that doesn't work
sudo npm install -g @hap-server/hap-server

This will install hap-server and link the hap-server executable.

You can now run hap-server with your configuration. Once you've tested your configuration you'll probably want to set it up as a system service with systemd (Debian), launchd (macOS) or whatever service manager you have installed.

hap-server requires a plugin to authenticate access to the web interface. You can use the authenticate-pam plugin to allow local users on the server to access the web interface. If you don't install an authentication handler you won't be able to access the web interface, but you'll still be able to configure hap-server using it's configuration file.

npm install -g @hap-server/authenticate-pam

By default users with the IDs root and cli-token (the user used when running CLI commands) are administrators. When using the authenticate-pam plugin you'll need to assign your user an ID the first time you use it. (A proper setup workflow will be added soon.) Once you have an account setup you can make your account an administrator.

hap-server make-admin {user-id}
# Or with the path to the configuration file
hap-server make-admin {user-id} --config data/config.yaml

GitHub Package Registry

By default npm will install from You can configure npm to install hap-server from GitHub Package Registry by adding this to your npmrc:


Run this to configure npm to use GitHub Package Registry for @hap-server scoped packages globally:

echo "@hap-server:registry=" >> `npm --global prefix`/etc/npmrc

GitLab Package Registry (

You can also configure npm to install hap-server from GitLab Package Registry by adding this to your npmrc:


Run this to configure npm to use GitLab Package Registry for @hap-server scoped packages globally:

echo "@hap-server:registry=" >> `npm --global prefix`/etc/npmrc

GitLab Package Registry (

You can also configure npm to install hap-server from GitLab Package Registry by adding this to your npmrc:


Run this to configure npm to use GitLab Package Registry for @hap-server scoped packages globally:

echo "@hap-server:registry=" >> `npm --global prefix`/etc/npmrc

Development builds

Every change to the main branch is published to the next tag on GitLab Package Registry (on and After configuring npm to install from one of those registries, you can install from main with this:

npm install -g @hap-server/hap-server@next

To switch back to the latest stable version specify the latest tag:

npm install -g @hap-server/hap-server@latest

Alternatively you can install from the git repository (or a mirror). When installing from git npm will build hap-server locally.

npm install -g git+
# Or from GitHub
npm install -g git+
# Or from
npm install -g git+


To run hap-server, just run hap-server.

Samuels-MacBook-Air:~ samuel$ hap-server
[28/02/2019, 01:56:01] Starting hap-server with configuration file /Users/samuel/.homebridge/config.json

hap-server will exit with an error if the configuration file doesn't exist. To use a custom configuration file path pass it as the first argument. hap-server allows you to write your configuration file in either JSON or YAML.

Samuels-MacBook-Air:~ samuel$ hap-server data/config.yaml
[28/02/2019, 01:56:01] Starting hap-server with configuration file /Users/samuel/Documents/Projects/hap-server/data/config.yaml

hap-server can automatically setup HTTPS with a self signed certificate and advertise the web interface with Bonjour. To use this add the --advertise-web-interface flag.

Samuels-MacBook-Air:~ samuel$ hap-server data/config.yaml --advertise-web-interface
[27/07/2019, 01:00:03] You can access the web interface on your local network at https://hap-server-12b083b6-dd04-49a7-abac-171388e99db2.local:51820/,
[27/07/2019, 01:00:03]     (remember to install the TLS certificate at /Users/samuel/Documents/Projects/hap-server/data/certificates/12b083b6-dd04-49a7-abac-171388e99db2.pem,
[27/07/2019, 01:00:03]         fingerprint: c9:01:0c:f7:54:80:3d:b4:57:fd:33:27:c0:2f:f2:d2:de:b8:22:de:9a:ef:9e:56:ec:7f:c9:05:c9:72:34:a4)

All Homebridge command line flags work with hap-server.

Samuels-MacBook-Air:~ samuel$ hap-server help
hap-server [config]

Run the HAP and web server

  hap-server [config]                       Run the HAP and web server [default]
  hap-server make-admin <user>              Promote a user to administrator
  hap-server get-characteristics <config>   Get characteristics
  hap-server set-characteristic <config>    Set a characteristic
  <characteristic> <value>
  hap-server validate-configuration         Validates a configuration file
  hap-server version                        Show version number

  config  The configuration file to use                       [string] [default:

  --debug, -D                     Enable debug level logging
                                                      [boolean] [default: false]
  --timestamps, -T                Add timestamps to logs
                                                       [boolean] [default: true]
  --force-colour, -C              Force colour in logs[boolean] [default: false]
  --help                          Show help                            [boolean]
  --advertise-web-interface       Automatically setup a HTTP server with a self
                                  signed TLS certificate for the web interface
                                  and advertise it through Bonjour
                                                      [boolean] [default: false]
  --advertise-web-interface-port  Port to listen on for the automatically
                                  advertised web interface
                                                       [number] [default: 51820]
  --data-path, -U                 Path to store data                    [string]
  --plugin-path, -P               Additional paths to look for plugins at as
                                  well as the default location ([path] can also
                                  point to a single plugin)              [array]
  --print-setup, -Q               Print setup information
                                                      [boolean] [default: false]
  --allow-unauthenticated, -I     Allow unauthenticated requests (for easier
                                  hacking)            [boolean] [default: false]
  --user, -u                      User to run as after starting
  --group, -g                     Group to run as after starting

To show the version number run hap-server version.

Samuels-MacBook-Air:~ samuel$ hap-server version
hap-server version 0.11.0 release
homebridge version 0.4.50, API 2.4
hap-nodejs version 0.4.51
Node.js version 12.10.0, v8 7.6.303.29-node.16, native modules 72
npm version 6.11.3


hap-server stores data in a platform-specific default location (falling back to the same location as Homebridge) and supports the same configuration format as Homebridge, as well as YAML. Using the same configuration as Homebridge, hap-server will behave exactly like Homebridge but will have a web interface for controlling accessories. Using Homebridge and hap-server plugins at the same time are supported, however you shouldn't run multiple instances of hap-server/Homebridge using the same data location.

Platform Directory
macOS ~/Library/Application Support/hap-server, ~/.homebridge, /Library/Application Support/hap-server
Linux ~/.config/hap-server, ~/.homebridge, /var/lib/hap-server

For other platforms ~/.homebridge is used.

See docs/

You can also use hap-server programmatically with Server.createServer.

import {Server} from '@hap-server/hap-server';

const server = await Server.createServer({
    config: ...,
    data_path: ...,

// See src/cli/server.ts to see what you can do with the Server object


# Clone the git repository
git clone
cd hap-server

# Install dependencies
npm install

# Build/watch the backend and example plugins
npx gulp build-backend watch-backend build-example-plugins watch-example-plugins &

# Copy the example configuration
mkdir -p data
cp example-config/config.yaml data

# Run the server (this will build the frontend)
bin/hap-server data/config.yaml

To build the frontend in Gulp instead of the hap-server process (and disable webpack hot module replacement) add watch-frontend to the Gulp command and add the --no-webpack-hot flag to the hap-server command.

To use the standalone Vue devtools run npx vue-devtools and pass the --vue-devtools-port flag to hap-server.

npx vue-devtools &

bin/hap-server data/config.yaml --vue-devtools-port 8098
# Also pass --vue-devtools-host if you want to use the Vue devtools to work on other devices
bin/hap-server data/config.yaml --vue-devtools-host samuels-macbook-air.local --vue-devtools-port 8098


hap-server supports all Homebridge plugins, but also has it's own plugin API that allows plugins to use hap-server features.

See docs/

Credits + License

hap-server is built on Apple HomeKit/HAP, HAP-NodeJS and Homebridge.

hap-server is released under the MIT license.

If you'd like to contribute to hap-server please create an account on my GitLab server and contact me (Tor).