3.2.5

• Fixed an exception when the plugin fails to reach the AirBase module at the last retry attempt #50

Thanks @longzheng for your contribution!

3.2.4

• Fixed a Homebridge warning when Homekit is fetching the Heater Cooler Target status while the aircon is in fan or dry mode #47

3.2.3

• Decreased logging level from info to debug for common logging events #41 Thanks @cemilbrowne !

3.2.2

• Patched node-fetch to version 2.6.7 for vulnerability.

3.2.1

• Fixed command sent to the Daikin Airbase when receiving chain of requests from Home app automations, resulting in wrong target temperature being set. #37

3.2.0

Added the ability to map zone control toggles to individual accessories (vs. being mapped as multiple services of a single accessory) so that each zone control switch can be placed in the room it controls in the Home app. #22

The new configuration is optional and not set by default:

Parameter	Type	Default	Note
useIndividualZoneControls	Boolean	false	Optional - Defines whether to map each zone switch to an individual accessory when a Daikin Zone Controller is available (true), or to map all zone switches to a single grouped accessory (false, default).

3.1.0

• Added the ability to override a limited number of Daikin Airbase properties, such as forcing the dry mode and fan mode support. This allows to hide the dry mode and/or fan mode switches by forcing their support property to false. See README file for more details. #30

3.0.2

• Fixes a bug where setting the Heater/Cooler threshold temperature via automations would fail to apply the temperature set. #27

3.0.1

• Fixes a bug with recent versions of HomeKit where the fan speed would be shown as zero when the fan is set to LOW mode on the A/C unit. #23

3.0.0

• Upgraded npm dependencies to the latest versions. The platform now requires homebridge version 1.0.0 or above to run.
• #18 The platform will now properly use cached homebridge accessories and restore them, instead of always re-creating them from scratch when homebridge starts.
• #18 The platform will no longer unregister accessories if it cannot reach the airbase module when homebridge starts. Instead the cached accessories will be still be available, and shown as "Not responding" in the Home app.
  If the platform fails to contact all the previously registered airbase modules when homebridge starts, it will re-attempt to reach them multiple times, with the last attempt made around 85 minutes after homebridge has started.
• Warning: due to the changes to the platform initialisation routine, your previous accessories will lose their homekit specific details once upgrading (room allocation, custom name, scenes and automations). You will have to redo these settings, as if it was the first time you used the plugin.