homebridge-deconz 0.1.20 → 1.0.0

package/README.md

@@ -18,19 +18,14 @@
 ## Homebridge plugin for deCONZ
 Copyright© 2022-2023 Erik Baauw. All rights reserved.
 
-### Work in Progress
-See [Future Development of Homebridge Hue](https://github.com/ebaauw/homebridge-hue/issues/1070) for positioning Homebridge deCONZ versus Homebridge Hue.
-
-Homebridge deCONZ is still under development.
-See [Releases](https://github.com/ebaauw/homebridge-deconz/releases) for more details.
-
-If you have a question, please post a message to the **#deconz** channel of the Homebridge community on [Discord](https://discord.gg/zUhSZSNb4P).
-
 ### Introduction
 This [Homebridge](https://github.com/homebridge/homebridge) plugin exposes to Apple's [HomeKit](http://www.apple.com/ios/home/) ZigBee devices (lights, plugs, sensors, switches, ...) and virtual devices on a deCONZ gateway by dresden elektronik.
 Homebridge deCONZ communicates with deCONZ over its [REST API](https://dresden-elektronik.github.io/deconz-rest-doc/), provided by its [REST API plugin](https://github.com/dresden-elektronik/deconz-rest-plugin).
 It runs independently from the Phoscon web app, see [deCONZ for Dummies](https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/deCONZ-for-Dummies).
 
+Homebridge deCONZ is the successor of Homebridge Hue for exposing Zigbee devices connected to a deCONZ gateway.
+See [Future Development of Homebridge Hue](https://github.com/ebaauw/homebridge-hue/issues/1070) for more details.
+
 ### Prerequisites
 You need a deCONZ gateway to connect Homebridge deCONZ to your ZigBee devices (lights, plugs, sensors, switches, ...).
 For Zigbee communication, the deCONZ gateway requires a [ConBee II](https://phoscon.de/en/conbee2) or [Conbee](https://phoscon.de/en/conbee) USB stick, or a [RaspBee II](https://phoscon.de/en/raspbee2) or [RaspBee](https://phoscon.de/en/raspbee) Raspberry Pi shield.  
@@ -41,42 +36,43 @@ You need a server to run Homebridge.
 This can be anything running [Node.js](https://nodejs.org): from a Raspberry Pi, a NAS system, or an always-on PC running Linux, macOS, or Windows.  
 I strongly recommend to use a standard Homebridge installation, see the [Homebridge Wiki](https://github.com/homebridge/homebridge/wiki) for details.
 I recommend to run deCONZ and Homebridge deCONZ on the same server, avoiding any network latency between deCONZ and Homebridge deCONZ, and preventing any potential network issues.
-I strongly recommend to run Homebridge deCONZ in a separate Homebridge installation, with the Homebridge UI as only other plugin, or in a separate [child bridge](https://github.com/homebridge/homebridge/wiki/Child-Bridges), in a Homebridge installation with other plugins.
+I strongly recommend to run Homebridge deCONZ in a separate [child bridge](https://github.com/homebridge/homebridge/wiki/Child-Bridges).
 
 To interact with HomeKit, you need an Apple device with Siri or a HomeKit app.  
 Please note that Siri and Apple's [Home](https://support.apple.com/en-us/HT204893) app only provide limited HomeKit support.
-To configure Homebridge deCONZ, and to use its full features, you need another HomeKit app, like [Eve](https://www.evehome.com/en/eve-app) (free) or Matthias Hochgatterer's [Home+](https://hochgatterer.me/home/) (paid).  
+To use the full features of Homebridge deCONZ, you need another HomeKit app, like [Eve](https://www.evehome.com/en/eve-app) (free) or Matthias Hochgatterer's [Home+](https://hochgatterer.me/home/) (paid).  
 As HomeKit uses mDNS (formally known as Bonjour) to discover Homebridge, the server running Homebridge must be on the same subnet as your Apple devices running HomeKit.
 Most cases of _Not Responding_ accessories are due to mDNS issues.  
 For remote access and for HomeKit automations (incl. support for wireless switches), you need to setup an Apple TV (4th generation or later), HomePod, or iPad as [home hub](https://support.apple.com/en-us/HT207057).  
-I recommend to use the latest released version of the Apple device OS: iOS, iPadOS, macOS, ...
+I recommend to use the latest released non-beta version of the Apple device OS: iOS, iPadOS, macOS, ...
 HomeKit doesn't seem to like using different Apple device OS versions.
 
 ### Configuration
-Most settings for Homebridge deCONZ can be changed at run-time from HomeKit, by the owner of the HomeKit home.
-These settings are persisted across Homebridge restarts.
-In config.json, you only need to specify the platform, and maybe the hostname or IP address and port of your deCONZ gateway(s).
-See the [Wiki](https://github.com/ebaauw/homebridge-deconz/wiki/Configuration) for details and examples.
-
-Homebridge deCONZ exposes a [gateway accessory](https://github.com/ebaauw/homebridge-deconz/wiki/Gateway-Accessory) for each deCONZ gateway.
-In Apple's Home app, this accessory looks like a wireless switch; you'll need another HomeKit app to configure the accessory.
+Most settings for Homebridge deCONZ, can be changed at run-time, including which devices to expose, how to expose these, and the level of logging.
+This keeps `config.json` extremely simple.
+Typically, you only need to specify the hostname and port of the deCONZ gateway(s) in `config.json`.
+See [`Configuration`](https://github.com/ebaauw/homebridge-deconz/wiki/Configuration) in the Wiki for details.
+I strongly recommended to run Homebridge deCONZ in a separate [child bridge](https://github.com/homebridge/homebridge/wiki/Child-Bridges).
+
+Homebridge deCONZ provides a Configuration API to change the run-time settings.
+These changes take effect immediately, and are persisted across Homebridge restarts.
+See [`Dynamic Configuration`](https://github.com/ebaauw/homebridge-deconz/wiki/Dynamic-Configuration) in the Wiki for details.
+For now, these dynamic settings are managed through the `ui` command-line tool.
+Eventually, Homebridge deCONZ might provide a configuration user interface to the Homebridge UI, using this configuration API.
 
 When it connects to a deCONZ gateway for the first time, Homebridge deCONZ will try to obtain an API key for two minutes, before exposing the gateway accessory.
 Unless Homebridge deCONZ runs on the same server as the deCONZ gateway, you need to unlock the gateway to allow Homebridge deCONZ to obtain an API key.
-After two minutes, Homebridge deCONZ will give up, exposing the gateway accessory anyways, but marking it inactive.
-Set _Expose_ on the _Gateway Settings_ service of the gateway accessory to retry obtaining an API key.
+If you don't, Homebridge deCONZ will give up, after two minutes.
+In this case, you need to set `expose` on the gateway dynamic settings, to retry obtaining an API key.
 Homebridge deCONZ will **not** retry to obtain an API key on Homebridge restart.
 
-After setting _Expose Lights_, _Expose Sensors_, or _Expose Groups_ on the _Gateway Settings_ service, Homebridge deCONZ will expose a [device accessory](https://github.com/ebaauw/homebridge-deconz/wiki/Device-Accessory) for each of the corresponding devices.
-When clearing the characteristic, the corresponding device accessories are removed from HomeKit.  
-Each device accessory has a _Device Settings_ service, to configure the device.
-Clear _Expose_ on that service, to blacklist the device, and remove the associated accessory from HomeKit.  
-The gateway accessory gains an additional _Device Settings_ service for each blacklisted device.
-To re-expose the corresponding accessory, set _Expose_ on that service.  
-Note that, unlike Homebridge Hue, Homebridge deCONZ handles blacklisting per device, instead of per resource.
-Setting _Expose Lights_ will include the ZHAConsumption and ZHAPower `/sensors` resources for smart plugs, and the ZHABattery for window covering devices; setting _Expose Sensors_ will exclude these.  
+Once it has obtained an API key, Homebridge deCONZ will expose all Zigbee devices connected to the gateway, by default. 
+Use the dynamic settings to exclude devices from being exposed, to change how devices are exposed, and to expose virtual devices like groups or CLIP sensors.  
+Homebridge deCONZ exposes a [gateway accessory](https://github.com/ebaauw/homebridge-deconz/wiki/Gateway-Accessory) for each deCONZ gateway.
+In Apple's Home app, this accessory looks like a wireless switch; you'll need another HomeKit app to use the other features of this accessory.
+
 Note that HomeKit doesn't like configuration changes.
-Allow ample time after exposing or removing accessories for HomeKit to sync the changed configuration to all Apple devices.
+After adding or removing accessories, allow ample time for HomeKit to sync the changed configuration to all Apple devices.
 
 ### Command-Line Utilities
 Homebridge deCONZ includes the following command-line utilities:
@@ -89,4 +85,44 @@ See [`Dynamic Configuration`](https://github.com/ebaauw/homebridge-deconz/wiki/D
 Each command-line tool takes a `-h` or `--help` argument to provide a brief overview of its functionality and command-line arguments.
 
 ### Troubleshooting
-- As mentioned above, Homebridge deCONZ is still under development.  Sometimes, cached accessories from an older version might confuse a newer version, causing all sorts of weird errors.  In this case, best un-expose the offending accessory, wait for HomeKit to remove it, and re-expose the accessory.  Note that this will cause HomeKit to see a new accessory, and lose any associations with HomeKit rooms, groups, scenes, and automations.
+Please check the [FAQ](https://github.com/ebaauw/homebridge-hue/wiki/FAQ) (for now still on Homebridge Hue Wiki).
+
+#### Check Dependencies
+If you run into Homebridge startup issues, please double-check what versions of Node.js and of Homebridge have been installed.
+Homebridge deCONZ has been developed and tested using the [latest LTS](https://nodejs.org/en/about/releases/) version of Node.js and the [latest](https://www.npmjs.com/package/homebridge) version of Homebridge.
+Other versions might or might not work - I simply don't have the bandwidth to test these.
+
+#### Run Homebridge deCONZ Solo
+If you run into Homebridge startup issues, please run Homebridge deCONZ in a separate [child bridge](https://github.com/homebridge/homebridge/wiki/Child-Bridges).
+
+#### Debug Log File
+Homebridge deCONZ outputs an info message to the Homebridge log, for each HomeKit characteristic value it sets and for each HomeKit characteristic value change notification it receives.  Make sure that `logLevel` of the corresponding accessory is at least 1, to see these info messages.
+
+Homebridge deCONZ outpits a debug message to the Homebridge log, for each interaction with a deCONZ gateway.
+Make sure to run Homebridge in DEBUG mode, and that `logLevel` of the corresponding accessory is at least 2, to see these debug messages.  Set `logLevel` to 3 to log the payload of the interaction with deCONZ as well.
+
+#### Debug Dump File
+To aid troubleshooting, on startup, Homebridge deCONZ dumps its environment, including its `config.json` settings, dynamic settings, and the full state of all gateways into a compresed json file, `homebridge-deconz.json.gz`.
+This file is located in the Homebridge user directory.
+
+#### Getting help
+If you have a question about Homebridge deCONZ, please post a message to the **#deconz** channel of the Homebridge community on [Discord](https://discord.gg/zUhSZSNb4P).
+
+If you encounter a problem with Homebridge deCONZ, please open an issue on [GitHub](https://github.com/ebaauw/homebridge-deconz/issues).
+Please attach a copy of `homebridge-deconz.json.gz` to the issue, see [**Debug Dump File**](#debug-dump-file).
+Please attach a copy of the (compressed) Homebridge log file to the issue, see [**Debug Log File**](#debug-log-file).
+Please do **not** copy/paste large amounts of log output.
+
+### Contributing
+Sometimes I get the question how people can support my work on Homebridge deCONZ.
+I created Homebridge deCONZ as a hobby project, for my own use.
+I share it on GitHub so others might benefit, and to give back to the open source community, without whom Homebridge Hue wouldn't have been possible.
+
+Having said that, adding support for new devices, in Homebridge deCONZ, and in the deCONZ REST API plugin, is very hard without having physical access to the device.
+Since this is a hobby project, I cannot afford to spend money on devices I won't be using myself, just to integrate them for the benefit of others.
+I am happy to receive small donations in the form of new devices to integrate, or the money to buy these devices myself.
+I am also happy to return the devices afterwards, if you provide the shipping costs.
+Please contact me by email or on Discord for shipping details.
+
+### Caveats
+Homebridge deCONZ is a hobby project of mine, provided as-is, with no warranty whatsoever.  I've been running it successfully at my home since May 2023, replacing Homebridge Hue, but your mileage might vary.

package/config.schema.json

@@ -94,8 +94,8 @@
       "title": "Advanced Settings",
       "description": "Don't change these, unless you understand what you're doing.",
       "items": [
-        "brightnessAdjustment",
         "forceHttp",
+        "noResponse",
         "parallelRequests",
         "stealth",
         "timeout",

package/lib/DeconzPlatform.js

@@ -25,7 +25,6 @@ class DeconzPlatform extends Platform {
 
   parseConfigJson (configJson) {
     this.config = {
-      brightnessAdjustment: 100,
       forceHttp: false,
       hosts: [],
       noResponse: false,

package/package.json

@@ -4,7 +4,7 @@
   "displayName": "Homebridge deCONZ",
   "author": "Erik Baauw",
   "license": "Apache-2.0",
-  "version": "0.1.20",
+  "version": "1.0.0",
   "keywords": [
     "homebridge-plugin",
     "homekit",
@@ -24,11 +24,11 @@
   "engines": {
     "deCONZ": "2.22.2",
     "homebridge": "^1.6.1",
-    "node": "18.17.0||^18||^16"
+    "node": "18.17.1||^18||^16"
   },
   "dependencies": {
-    "hb-deconz-tools": "~1.0.4",
-    "homebridge-lib": "~6.4.0"
+    "hb-deconz-tools": "~1.0.6",
+    "homebridge-lib": "~6.4.1"
   },
   "scripts": {
     "prepare": "standard && rm -rf out && jsdoc -c jsdoc.json",