v1.1.9

Bump the package.json engine version to indicate that the plugin is compatible with Homebridge 2.0.

v1.1.8

Exposes the option to change the frequency at which the plugin refreshes the state of each device from the hub, and increases the default interval from 5 to 10 seconds. Addresses the request in issue #31.

v1.1.7

Made two new configuration options available: the number of times to retry a failed request, and the delay between retries. These can be adjusted if the hub does not respond in a timely manner, or in cases where attempts to control a large number of devices simultaneously results in some devices failing to move, as described in #28.

v1.1.6

Fixes the behaviour of the plugin for unidirectional blinds, which do not report explicit position information. They will now correctly reflect the open or closed position of the blinds as cached by the hub or set by the Home app. In cases where an external app is used to stop the blinds midway through opening or closing, the plugin will approximate this state by showing the blinds as 50% open since their exact position cannot be determined.

v1.1.5

Fixes an issue whereby some brands of blinds, contrary to the standard network protocol spec, require the AccessToken to be supplied on read requests as well as write requests. See #26 for details.

v1.1.4

• In addition to periodically scanning for new devices registered with the Connector+ or other vendor app, the plugin will now automatically remove devices from Homebridge and Homekit when they are de-registered from the app.
• Added the ability to reverse device direction. This can be used for any device models or brands which move in the opposite of the expected direction when using the plugin.
• Reduced the verbosity of log messages generated by the plugin when not in debug mode.
• Improved the config screen layout by separating settings into different sections.
• Fixed a minor bug which caused problems when generating device names.

v1.1.3

• Fixed a bug introduced in 1.1.2 where certain devices would receive incorrect messages claiming that the user's app key was invalid (see #17, #18).

v1.1.2

• Added a new code for previously-unrecognised Hub devices per #14
• Fixed an issue where binary-state devices were logging spurious "invalid ack" messages

v1.1.1

Minor update that improves the discovery process and more gracefully handles the scenario where an invalid App Key is supplied; previously, this would result in a crash.

v1.1.0

• Implemented support for Top-Down Bottom-Up blinds. Two accessories will be created for such blinds, one controlling the bottom part and the other controlling the top.
• Introduced a new device discovery mechanism. This should work better in multicast environments, for hubs with more than 15 devices, and for configurations with more than one hub. The plugin will now also periodically scan for new devices that have been added to the hub since startup.