@akospasztor/homebridge-create-ceiling-fan 1.0.0

package/CHANGELOG.md

@@ -0,0 +1,5 @@
+# Changelog
+
+## 1.0.0 (2025-09-19)
+
+- Initial release

package/LICENSE

@@ -0,0 +1,176 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS

package/README.md

@@ -0,0 +1,151 @@
+<p align="center">
+  <img src="docs/homebridge-create-logo.png" alt="Homebridge Create Ceiling Fan Plugin Logo" width="450">
+</p>
+
+# Homebridge Create Ceiling Fan Plugin
+
+This plugin allows integrating the CREATE ceiling fans into HomeKit via
+HomeBridge.
+
+Although there are several HomeBridge plugins that provide similar
+functionality, this plugin aims to stand out via providing a smooth,
+user-friendly fan speed control mechanism in the HomeKit UI and a robust device
+communication mechanism with a mutex. It also reflects and updates the changes
+via the physical remote automatically in HomeKit.
+
+**Tested Devices:**
+
+- CREATE Wind Calm (with light, WiFi + Remote controller)
+
+## Contents
+
+- [Features](#features)
+- [Requirements](#requirements)
+- [Usage](#usage)
+- [Known issues](#known-issues)
+- [Acknowledgements](#acknowledgements)
+- [Developer documentation](#developer-documentation)
+
+## Features
+
+- [x] Support for devices with and without light
+- [x] User-friendly fan speed control via the HomeKit UI slider
+- [x] Local communication, does not require connection to the Tuya IoT cloud
+      platform [^1]
+- [x] Robust communication implementation
+- [x] Changes via physical remote controller and other applications are
+      automatically reflected in HomeKit
+- [ ] Add support for devices with dimmable light
+- [ ] Add support for toggling the beep sound feedback
+
+## Requirements
+
+### Getting the local key of the device
+
+The TinyTuya project has great step-by-step instructions
+[how to obtain the local key](https://github.com/jasonacox/tinytuya/tree/master?tab=readme-ov-file#setup-wizard---getting-local-keys)
+of a device.
+
+In order to obtain the local key of a device, it needs to be paired with the
+Smart Life App or Tuya Smart App. If the device has already been paired with the
+CREATE app, you can reset the device with its remote the following way:
+
+1. Power off the fan (i.e. cut the power by turning off its wall switch or with
+   the associated breaker depending on the installation).
+2. Power on the device.
+3. Press and hold the `1h` button on the remote until you hear a beep.
+4. Now the device is ready to be paired again.
+
+Note from the CREATE app: if you do not hear a beep after 10 seconds, press and
+hold the buttons `1h` and `2h` simultaneously at the same time.
+
+### Fixed IP address
+
+It's strongly recommended to set up a DHCP IP reservation for the device. This
+way the fan will always have a fixed IP address assigned. The TuyAPI library
+used for device communication works reliably when the IP address of the device
+is used alongside with the device ID.
+
+Note: the device used for the initial plugin development is a CREATE Wind Calm
+purchased in 2025, and it refuses most connection attempts via the TuyAPI when
+the IP address is not supplied (connection requests with ID only).
+
+## Usage
+
+### Installation
+
+### Configuration
+
+By default, one HomeKit tile is exposed in the Home application for a device.
+You can group or ungroup the different accessories of the fan (e.g. the fan
+slider and the light switch) in the group section of the accessory settings
+within the Home app.
+
+### Setting the rotation speed via the HomeKit slider
+
+The following UI slider inputs represent the different speed settings of the
+fan. The fan is turned off when the slider is set to zero.
+
+| Device fan speed | Corresponding UI slider value | User input range on the slider |
+| :--------------: | :---------------------------: | :----------------------------: |
+|        1         |              10               |            1 - 19              |
+|        2         |              30               |           20 - 39              |
+|        3         |              50               |           40 - 59              |
+|        4         |              70               |           60 - 79              |
+|        5         |              90               |           80 - 94              |
+|        6         |             100               |           95 - 100             |
+
+Whenever the user operates the slider, a so-called debouncing timer is set. When
+the timer expires (without the user changing the slider), the current state of
+the slider value is converted to the nearest value that corresponds to the
+device fan speed. The purpose of the debounce timer is to provide great user
+experience: without the debounce timer, the slider would jump around
+immediately, without waiting for the user to finish adjusting the speed.
+
+**Demo:**
+
+<p align="center">
+  <img src="docs/fan-speed-slider.gif" alt="Fan Speed Slider UI" width="300">
+</p>
+
+### Setting the rotation direction via the HomeKit button
+
+The Home app shows a small icon below the fan speed slider representing the
+rotation direction of the fan. The implementation follows the general convention
+that the direction is represented from the perspective when the user looks at
+the fan; i.e. standing below and looking up in the case of a ceiling fan.
+
+The counter-clockwise icon in the Home shows that the fan rotates
+counter-clockwise when looked at directly from below. In this mode the fan blows
+air downwards, called the "summer" mode. Changing the direction to clockwise
+rotation makes the fan rotate in the opposite direction, causing the air being
+pushed upwards. This mode is called the "winter" mode.
+
+## Known issues
+
+### Color temperature
+
+It appears that the color temperature of the CREATE Wind Calm ceiling fan
+(purchased in 2025) cannot be set properly. Regardless of using the physical
+remote, the mobile application or manually sending the commands via TinyTuya,
+the device simply cycles through the 3 different color temperatures and it does
+not remember it's previously set state. This issue has also been observed here:
+[https://github.com/velzend/create_ikohs_fan](https://github.com/velzend/create_ikohs_fan)
+
+Therefore, this plugin does not support setting the color temperature until this
+has been fixed by CREATE.
+
+## Acknowledgements
+
+- [TinyTuya](https://github.com/jasonacox/tinytuya)
+- [TuyAPI](https://github.com/codetheweb/tuyapi)
+
+## Developer documentation
+
+[https://akospasztor.github.io/homebridge-create-ceiling-fan/](https://akospasztor.github.io/homebridge-create-ceiling-fan/)
+
+<!-- Footnotes -->
+
+[^1]: Please note that the Tuya IoT cloud platform registration is still needed
+to obtain the local keys for the device. After obtaining the keys, the device
+can be blocked from accessing the internet.

package/config.schema.json

@@ -0,0 +1,55 @@
+{
+  "pluginAlias": "CreateCeilingFanPlatform",
+  "pluginType": "platform",
+  "singular": true,
+  "strictValidation": true,
+  "schema": {
+    "devices": {
+      "type": "array",
+      "title": "Devices",
+      "items": {
+        "type": "object",
+        "properties": {
+          "name": {
+            "title": "Name",
+            "description": "The accessory name that is displayed in the Home app",
+            "type": "string",
+            "default": "Ceiling Fan",
+            "required": true
+          },
+          "id": {
+            "title": "Device ID",
+            "description": "Device ID retrieved from the Tuya IoT Cloud Platform",
+            "type": "string",
+            "required": true
+          },
+          "key": {
+            "title": "Device key",
+            "description": "Local key of the device retrieved with tinytuya",
+            "type": "string",
+            "required": true
+          },
+          "ip": {
+            "title": "IP address",
+            "description": "IP address of the device (optional, but recommended to reserve a static address for this device on your LAN for better performance)",
+            "type": "string",
+            "required": true
+          },
+          "protocolVersion": {
+            "title": "Protocol version",
+            "description": "Tuya device protocol version",
+            "type": "string",
+            "default": "3.5",
+            "required": false
+          },
+          "hasLight": {
+            "title": "Fan with light",
+            "description": "Check this if the fan is equipped with light",
+            "type": "boolean",
+            "required": false
+          }
+        }
+      }
+    }
+  }
+}

package/dist/index.d.ts

@@ -0,0 +1,6 @@
+import type { API } from 'homebridge';
+/**
+ * This method registers the platform with Homebridge
+ */
+declare const _default: (api: API) => void;
+export default _default;

package/dist/index.js

@@ -0,0 +1,9 @@
+import { CreateCeilingFanPlatform } from './platform.js';
+import { PLATFORM_NAME } from './settings.js';
+/**
+ * This method registers the platform with Homebridge
+ */
+export default (api) => {
+    api.registerPlatform(PLATFORM_NAME, CreateCeilingFanPlatform);
+};
+//# sourceMappingURL=index.js.map

package/dist/index.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,wBAAwB,EAAE,MAAM,eAAe,CAAC;AACzD,OAAO,EAAE,aAAa,EAAE,MAAM,eAAe,CAAC;AAE9C;;GAEG;AACH,eAAe,CAAC,GAAQ,EAAE,EAAE;IAC1B,GAAG,CAAC,gBAAgB,CAAC,aAAa,EAAE,wBAAwB,CAAC,CAAC;AAChE,CAAC,CAAC"}

package/dist/mutex.d.ts

@@ -0,0 +1,61 @@
+/**
+ * Simple mutex with a waiting queue.
+ *
+ * The mutex can be acquired by calling the `lock()` method which returns a
+ * promise with a function pointing to the `unlock()` method. Afterwards the
+ * caller can carry out the operations that are protected by the mutex. Then
+ * the caller who holds the mutex must call the previously returned function
+ * to unlock the mutex. If the caller fails to do so, the mutex will remain
+ * locked.
+ *
+ * If the mutex is free to be locked, the locking happens immediately and the
+ * caller can carry out its prorected operations. When the mutex is locked,
+ * any subsequent caller that is trying to lock the mutex is forced to wait.
+ * In this case , the actual acquire functionality is not executed but pushed
+ * to the waiting queue. When the mutex is unlocked by the first caller, the
+ * queue is processed and the mutex is locked immediately for the next in
+ * waiting, i.e. resolving the promise by returning a function pointer (to the
+ * mutex unlock method) for the caller.
+ *
+ * @example
+ * // Create the mutex object
+ * this.mutex = new Mutex();
+ * ...
+ * // Attempt to lock the mutex
+ * // Note: the returned function pointer needs to be called to unlock the mutex
+ * const releaseMutex = await this.mutex.lock();
+ * // Do stuff protected by the mutex; this example just starts a timer with 3 seconds timeout
+ * await new Promise((resolve) => setTimeout(resolve, 3000));
+ * // Release the mutex
+ * releaseMutex();
+ */
+export declare class Mutex {
+    /** Track if the mutex is currently locked. */
+    private isLocked;
+    /** Queue for handling the lock requests when the mutex is already locked. */
+    private waitingQueue;
+    /**
+     * Lock the mutex.
+     *
+     * If the mutex is free to be locked, the locking happens immediately and the
+     * caller can carry out its prorected operations. When the mutex is locked,
+     * any subsequent caller that is trying to lock the mutex is forced to wait.
+     *
+     * @return A promise that is resolved when the mutex is given to the caller.
+     *         The returned promise (that is itself a function pointer) must be
+     *         called to free (unlock) the mutex.
+     */
+    lock(): Promise<() => void>;
+    /** Unlock the mutex.
+     *
+     * This method is returned to the caller indicating that the mutex is locked.
+     * After completing the operations protected by the mutex, the caller must
+     * call this method to unlock (release) the mutex. If the caller fails to do
+     * so, the mutex will remain locked.
+     *
+     * When the mutex is unlocked by the first caller and there are several
+     * callers waiting to lock the mutex, the waiting queue is processed and the
+     * mutex is locked immediately for the next caller in waiting.
+     */
+    private unlock;
+}

package/dist/mutex.js

@@ -0,0 +1,96 @@
+/**
+ * Simple mutex with a waiting queue.
+ *
+ * The mutex can be acquired by calling the `lock()` method which returns a
+ * promise with a function pointing to the `unlock()` method. Afterwards the
+ * caller can carry out the operations that are protected by the mutex. Then
+ * the caller who holds the mutex must call the previously returned function
+ * to unlock the mutex. If the caller fails to do so, the mutex will remain
+ * locked.
+ *
+ * If the mutex is free to be locked, the locking happens immediately and the
+ * caller can carry out its prorected operations. When the mutex is locked,
+ * any subsequent caller that is trying to lock the mutex is forced to wait.
+ * In this case , the actual acquire functionality is not executed but pushed
+ * to the waiting queue. When the mutex is unlocked by the first caller, the
+ * queue is processed and the mutex is locked immediately for the next in
+ * waiting, i.e. resolving the promise by returning a function pointer (to the
+ * mutex unlock method) for the caller.
+ *
+ * @example
+ * // Create the mutex object
+ * this.mutex = new Mutex();
+ * ...
+ * // Attempt to lock the mutex
+ * // Note: the returned function pointer needs to be called to unlock the mutex
+ * const releaseMutex = await this.mutex.lock();
+ * // Do stuff protected by the mutex; this example just starts a timer with 3 seconds timeout
+ * await new Promise((resolve) => setTimeout(resolve, 3000));
+ * // Release the mutex
+ * releaseMutex();
+ */
+export class Mutex {
+    /** Track if the mutex is currently locked. */
+    isLocked = false;
+    /** Queue for handling the lock requests when the mutex is already locked. */
+    waitingQueue = [];
+    /**
+     * Lock the mutex.
+     *
+     * If the mutex is free to be locked, the locking happens immediately and the
+     * caller can carry out its prorected operations. When the mutex is locked,
+     * any subsequent caller that is trying to lock the mutex is forced to wait.
+     *
+     * @return A promise that is resolved when the mutex is given to the caller.
+     *         The returned promise (that is itself a function pointer) must be
+     *         called to free (unlock) the mutex.
+     */
+    async lock() {
+        return new Promise(resolve => {
+            // The actual locking function will be called either:
+            // - immediately if the lock is free, or
+            // - later from the queue when the lock becomes free
+            const acquireLock = () => {
+                this.isLocked = true;
+                resolve(() => this.unlock());
+            };
+            // If the mutex is not yet locked, then lock it here and resolve the
+            // promise by returning the unlock function to the caller. If it's
+            // already locked, then do not resolve the promise and push the
+            // actual locking function to the waiting queue. As soon as the current
+            // lock is unlocked, the next in line waiting will be resolved.
+            if (!this.isLocked) {
+                acquireLock();
+            }
+            else {
+                this.waitingQueue.push(acquireLock);
+            }
+        });
+    }
+    /** Unlock the mutex.
+     *
+     * This method is returned to the caller indicating that the mutex is locked.
+     * After completing the operations protected by the mutex, the caller must
+     * call this method to unlock (release) the mutex. If the caller fails to do
+     * so, the mutex will remain locked.
+     *
+     * When the mutex is unlocked by the first caller and there are several
+     * callers waiting to lock the mutex, the waiting queue is processed and the
+     * mutex is locked immediately for the next caller in waiting.
+     */
+    unlock() {
+        // Check if there is a caller waiting in line for the mutex
+        if (this.waitingQueue.length > 0) {
+            // Pass the mutex to the next in line
+            const nextPending = this.waitingQueue.shift();
+            if (nextPending) {
+                nextPending();
+            }
+        }
+        else {
+            // Release the lock if noone is waiting for the mutex
+            this.isLocked = false;
+        }
+    }
+}
+//# sourceMappingURL=mutex.js.map

package/dist/mutex.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"mutex.js","sourceRoot":"","sources":["../src/mutex.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA8BG;AACH,MAAM,OAAO,KAAK;IAChB,8CAA8C;IACtC,QAAQ,GAAY,KAAK,CAAC;IAElC,6EAA6E;IACrE,YAAY,GAAmB,EAAE,CAAC;IAE1C;;;;;;;;;;OAUG;IACH,KAAK,CAAC,IAAI;QACR,OAAO,IAAI,OAAO,CAAC,OAAO,CAAC,EAAE;YAC3B,qDAAqD;YACrD,wCAAwC;YACxC,oDAAoD;YACpD,MAAM,WAAW,GAAG,GAAG,EAAE;gBACvB,IAAI,CAAC,QAAQ,GAAG,IAAI,CAAC;gBACrB,OAAO,CAAC,GAAG,EAAE,CAAC,IAAI,CAAC,MAAM,EAAE,CAAC,CAAC;YAC/B,CAAC,CAAC;YAEF,oEAAoE;YACpE,kEAAkE;YAClE,+DAA+D;YAC/D,uEAAuE;YACvE,+DAA+D;YAC/D,IAAI,CAAC,IAAI,CAAC,QAAQ,EAAE,CAAC;gBACnB,WAAW,EAAE,CAAC;YAChB,CAAC;iBAAM,CAAC;gBACN,IAAI,CAAC,YAAY,CAAC,IAAI,CAAC,WAAW,CAAC,CAAC;YACtC,CAAC;QACH,CAAC,CAAC,CAAC;IACL,CAAC;IAED;;;;;;;;;;OAUG;IACK,MAAM;QACZ,2DAA2D;QAC3D,IAAI,IAAI,CAAC,YAAY,CAAC,MAAM,GAAG,CAAC,EAAE,CAAC;YACjC,qCAAqC;YACrC,MAAM,WAAW,GAAG,IAAI,CAAC,YAAY,CAAC,KAAK,EAAE,CAAC;YAC9C,IAAI,WAAW,EAAE,CAAC;gBAChB,WAAW,EAAE,CAAC;YAChB,CAAC;QACH,CAAC;aAAM,CAAC;YACN,qDAAqD;YACrD,IAAI,CAAC,QAAQ,GAAG,KAAK,CAAC;QACxB,CAAC;IACH,CAAC;CACF"}

package/dist/platform.d.ts

@@ -0,0 +1,48 @@
+import type { API, Characteristic, DynamicPlatformPlugin, Logging, PlatformAccessory, PlatformConfig, Service } from 'homebridge';
+/**
+ * CreateCeilingFanPlatform: the platform implementation for CREATE ceiling fans.
+ *
+ * This class contains the platform implementation and follows the Homebridge
+ * plugin development recommendations.
+ *
+ * @see https://developers.homebridge.io/#/
+ * @see https://github.com/homebridge/homebridge-plugin-template/blob/latest/README.md
+ */
+export declare class CreateCeilingFanPlatform implements DynamicPlatformPlugin {
+    readonly log: Logging;
+    readonly config: PlatformConfig;
+    readonly api: API;
+    /** The HomeKit Accessory Protocol (HAP) service. */
+    readonly Service: typeof Service;
+    /** The HomeKit Accessory Protocol (HAP) characteristic. */
+    readonly Characteristic: typeof Characteristic;
+    /** Used for tracking the restored cached accessories. */
+    readonly accessories: Map<string, PlatformAccessory>;
+    /** Used for tracking the cached UUIDs. */
+    readonly discoveredCacheUUIDs: string[];
+    /**
+     * The CreateCeilingFanPlatform constructor.
+     *
+     * Note: This constructor is called by Homebridge.
+     *
+     * @param log    The logging object.
+     * @param config The platform configuration object.
+     * @param api    The API object.
+     */
+    constructor(log: Logging, config: PlatformConfig, api: API);
+    /**
+     * This function is invoked when Homebridge restores cached accessories from
+     * the disk at startup. It should be used to set up event handlers for
+     * characteristics and update respective values.
+     *
+     * @param accessory The accessory restored from the disk at startup.
+     */
+    configureAccessory(accessory: PlatformAccessory): void;
+    /**
+     * Register discovered accessories.
+     *
+     * Accessories must only be registered once, previously created accessories
+     * must not be registered again to prevent "duplicate UUID" errors.
+     */
+    private discoverDevices;
+}