homebridge-gree-ac 2.1.1 → 2.1.3

package/CHANGELOG.md

@@ -1,5 +1,61 @@
 # Changelog
 
+## [2.1.3] - 2024-11-05
+
+**<ins>Reminder:</ins> New (v2) network encryption protocol supported since v2.1.0**
+
+When upgrading from v2.0.0 - v2.1.1 to v2.1.2 or later configuration settings should be updated.
+
+#### Updated dependencies
+- added Node.js v22 to supported versions (18.15.0 or later, 20.7.0 or later and 22.0.0 or later are supported)
+
+### New features
+- new optional IP address parameter to support devices on different subnets
+- new optional device port parameter to support cases when automatic port assigment is not appropriate
+
+### Fixes
+- consistent xFan default setting in configuration UI and in plugin behaviour
+
+## [2.1.2] - 2024-10-01
+
+**<ins>Reminder:</ins> New (v2) network encryption protocol supported since v2.1.0**
+
+When upgrading from v2.0.0 - v2.1.1 to v2.1.2 configuration settings should be updated.
+
+#### Configuration update steps
+
+- <ins>Recommended:</ins> Using the graphical user interface of Homebridge ([Homebridge Config UI X](https://www.npmjs.com/package/homebridge-config-ui-x))
+  1) Open plugin configuration
+  1) Review and update settings if needed
+  1) Save changes _(pressing the Save button is required to update the configuration to new version even if no changes needed in the displayed values)_
+  1) Restart Homebridge
+- **OR** <ins>Alternative:</ins> Edit the configuration file directly
+  1) Remove the following parameters from the platform section:
+     - port _(it may be kept if you want to set the UDP port manually)_
+     - scanAddress
+     - scanCount
+     - scanTimeout
+  1) Optionally you can add the following parameter to the platform section:
+     - scanInterval _(default is 60 if missing, needed only if other value required)_
+  1) Save changes
+  1) Restart Homebridge
+
+#### Updated dependencies
+- homebridge-config-ui-x 4.59.0 or later required
+- added homebridge 2.0.0-beta.0 and later to supported versions
+
+### New features
+
+- Simplified configuration
+  - Broadcast address not needed any more
+  - UDP port is optional
+  - Scan count and scan timeout replaced with scan interval parameter
+- AC units can have dynamic addresses
+
+### Fixes
+
+- Fixed "Failed to save cached accessories to disk: Converting circular structure to JSON" error
+
 ## [2.1.1] - 2024-06-25
 
 **New (v2) network encryption protocol supported since v2.1.0**

package/README.md

@@ -6,35 +6,39 @@
 > _*** Breaking changes ***_
 > 
 > Please read the [**Upgrade section**](#upgrade) before upgrading from version earlier than **v2.0.0** !
+>
+> _It is also recommended to read the upgrade section before any upgrade. It contains useful information regarding the latest version._
 
 # Homebridge GREE Air Conditioner Platform Plugin
 
-[Homebridge GREE Air Conditioner Platform Plugin](https://github.com/eibenp/homebridge-gree-airconditioner) is a dynamic platform plugin for [Homebridge](https://github.com/homebridge/homebridge) which allows control of GREE Air Conditioner devices from [Apple's Home App](https://www.apple.com/home-app/). (Make GREE Air Conditioner HomeKit compatible.)
+[Homebridge GREE Air Conditioner Platform Plugin](https://github.com/eibenp/homebridge-gree-airconditioner) is a dynamic platform plugin for [Homebridge](https://github.com/homebridge/homebridge) which allows control of GREE Air Conditioner devices from [Apple's Home App](https://www.apple.com/home-app/). (Makes GREE Air Conditioner HomeKit compatible.)
 
-You can add all of your GREE Air Conditioner devices to the Home App by specifying the network broadcast address, and Homebridge will find all connected devices. Each device appears in the Home App as a Heater Cooler device. It is also possible to add a separate Termperature Sensor (if temperature sensor is supported by the physical device). This allows to define automations (e.g. turn on) based on current temperature in the room. Be careful, if the device does not support internal temperature sensor but is added as a separate accessory, Home App will display the target temperature not the measured one. Child accessory does not appear in Home App if physical sensor is not available in the AC unit.
+You can add all of your GREE Air Conditioner devices to the Home App by specifying the device's MAC address, and Homebridge will find all connected devices. Each device appears in the Home App as a Heater Cooler device. It is also possible to add a separate Termperature Sensor (if temperature sensor is supported by the physical device). This allows to define automations (e.g. turn on) based on current temperature in the room. Be careful, if the device does not support internal temperature sensor but is added as a separate accessory, Home App will display the target temperature not the measured one. Child accessory does not appear in Home App if physical sensor is not available in the AC unit.
 
 Quiet / Auto / Powerful mode is supported by the fan speed control. Zero means off. Minimum value turns on Quiet mode. Next value is Auto mode. Maximum value is Powerful mode. All other values between them are exact fan speeds (Low, MediumLow**, Medium, MediumHigh**, High)
 
 ** these values are supported only on 5-speed models
 
-You have to add all devices to the Homebridge configuration, so that you can control all their parameters. If you don't want to control all of the devices in Home App, then you need to add to the configuration and disable the ones you don't need. Devices are identified by MAC Address (Serial Number). It can be queried using the official [GREE+ mobile app](https://apps.apple.com/us/app/gree/id1167857672). (The app is required to connect the devices to the local WiFi network for the first time.)
+You have to add all devices to the Homebridge configuration. Devices are identified by MAC Address (Serial Number). It can be queried using the official [GREE+ mobile app](https://apps.apple.com/us/app/gree/id1167857672). (The app is required to connect the devices to the local WiFi network for the first time.) If an AC unit's MAC address is not added to the configuration then it will be skipped by the plugin. You can also skip a device by adding it to the configuration and setting the "disabled" parameter to true. _(This is useful if you want to temporarily remove the device but you want to keep it's parameters, e.g. changing the name is not possible without removal.)_
 
 xFan function is also supported, but it works automatically if enabled in Homebridge configuration. If xFan is enabled for the device, it is automatically turned on when you select a supported operating mode in Home App. If xFan is disabled, the Home App will not modify its actual setting in any case.
 
 Temperature display units of the physical device can be controlled using the Home App. (Configuration settings are required to be specified always in Degrees Celsius, independently from the display units.)
 
-Vertical swing mode can be turned on/off, but special swing settings can't be controlled using the Home App. If device default vertical swing position is not acceptable in disabled swing mode it can be overridden to a pre selected position by configuration settings. (Only default position is overridden when this feature is enabled. Other positions selected by remote control are kept and not modified by Home App.)
+Vertical swing mode can be turned on/off, but special swing settings can't be controlled using the Home App. If device default vertical swing position is not acceptable in disabled swing mode, it can be overridden to a pre selected position by configuration settings. (Only default position is overridden when this feature is enabled. Other positions selected by remote control are kept and not modified by Home App. The AC unit may keep the actual vertical swing position on turning off oscillation in Home App.)
 
 This plugin is designed to be as simple and clear as possible and supports primarily the functions of the Home App's Heater Cooler accessory.
 
 ## Requirements
 
-* Node.js (>= 18.15.0 || >= 20.8.0) with NPM
-* Homebridge (>= 1.8.0)
+* Node.js (>= 18.15.0 || >= 20.7.0 || >= 22.0.0) with NPM
+* Homebridge (>= 1.8.0 || >= 2.0.0-beta.0)
+
+The plugin finds all supported units automatically if they are located on the same subnet but controls only those which MAC address is added to the configuration. AC units on different subnets are also supported if the unit's IP address is set in the configuration. (MAC address have to be set correctly in this case also.)
 
-You need to specify the local network broadcast address (192.168.1.255 in many home environments) and it is also recommended to add the device and specify its MAC address (Serial Number) in the configuration file. Homebridge and all AC units have to be on the same subnet.
+IPv4 address is required. GREE Air Conditioners do not support IPv6 nor other network protocols.
 
-It is highly recommended to use static IP addresses for connected devices. Using a dynamic IP address may require a restart of the Homebridge service on an address change to reconnect the device. Most routers offer static DHCP leases. (Please look at your router's documentation!)
+This is not plugin dependency but its good to know that Homebridge server host address must be static. If the host address changes Homebridge looses connection with Home App and only Homebridge restart restores the connection.
 
 ## Supported devices
 
@@ -44,7 +48,7 @@ It is highly recommended to use static IP addresses for connected devices. Using
  
 > If you get _"error:1C80006B:Provider routines::wrong final block length"_ error message then your device is not supported.
 >
-> If you get _"Device not bound:..."_ warning message then your device is not supported.
+> If you don't get _"Device is bound ..."_ message within a few minutes after Homebridge startup and the correct MAC address is added to the configuration and the AC unit is accessible on the network then your device is not supported.
 
 By default this plugin tries to auto detect the network protocol encryption version. If not the right version is selected there can get errors and the AC device will not correctly work. It is possible to force a network protocol encryption version in configuration file. If auto detection does not work then it is recommended to try all possible values to check if the device is compatible or not.
 
@@ -60,7 +64,6 @@ This plugin was designed to support the Home App's Heater Cooler functionality u
 * Not all half a degree values are supported in °C mode (GREE AC units are designed to support only integer °C and °F values). Unsupported values are automatically updated to the nearest supported values.
 * There is no way to get current heating-cooling state from the AC unit in auto mode, so displayed state in the Home App is based on temperature measurement, but internal sensor is not precise enough to always display the correct state.
 * Cooling / Heating temperature threshold limits (minimum and maximum values) can only be set in active cooling / heating mode. So the gauge in Home App may show invalid minimum and maximum values for the first use of cooling and heating modes. If so please restart Home App. Next time the correct values will be displayed.
-* Homebridge and AC unit on different subnets is a not supported configuration.
 * Devices without a built-in temperature sensor display the target temperature as current temperature not the measured one. (Some AC firmware versions do not report the measured temperature but the unit has a built-in sensor. They are handled by the plugin as devices without a sensor.)
 
 ## Installation instructions
@@ -75,15 +78,39 @@ If successfully installed and configured, your devices will appear on the Homebr
 
 ## Upgrade
 
+### v2.0.0 - v2.1.1 to v2.1.2 or later
+
+The upgrade is automatic by installing the latest version but configuration settings should be updated.
+
+#### Configuration update steps
+
+- <ins>Recommended:</ins> Using the graphical user interface of Homebridge ([Homebridge Config UI X](https://www.npmjs.com/package/homebridge-config-ui-x))
+  1) Open plugin configuration
+  1) Review and update settings if needed
+  1) Save changes _(pressing the Save button is required to update the configuration to new version even if no changes needed in the displayed values)_
+  1) Restart Homebridge
+- **OR** <ins>Alternative:</ins> Edit the configuration file directly
+  1) Remove the following parameters from the platform section:
+     - port _(it may be kept if you want to set the UDP port manually)_
+     - scanAddress
+     - scanCount
+     - scanTimeout
+  1) Optionally you can add the following parameter to the platform section:
+     - scanInterval _(default is 60 if missing, needed only if other value required)_
+  1) Save changes
+  1) Restart Homebridge
+
+### v1.x.x to v2.0.0 or later
+
 There is no clean way to update the plugin to release v2.0.0 or later if you are using an older version (v1.x.x). You need to remove and reinstall the plugin during upgrade.
 
-### Upgrade steps
+#### Upgrade steps
 
-1. Check out your current settings in Homebridge and also in Homekit (including scenes and automation rules)
+1. Check out your current settings in Homebridge and also in Home App (including scenes and automation rules)
 2. Uninstall the old version (this will remove all settings also)
 3. Install the new version
 4. Configure plugin in Homebridge
-5. Assign accessories to rooms and recreate scenes and automations in Homekit
+5. Assign accessories to rooms and recreate scenes and automations in Home App
 
 ## Example configuration
 _Only the relevant part of the configuration file is displayed:_
@@ -93,22 +120,22 @@ _Only the relevant part of the configuration file is displayed:_
             "name": "Gree Air Conditioner",
             "platform": "GREEAirConditioner",
             "port": 7002,
-            "scanAddress": "192.168.1.255",
-            "scanCount": 5,
-            "scanTimeout": 10,
+            "scanInterval": 60,
             "devices": [
                 {
                     "mac": "502cc6000000",
                     "name": "Living room AC",
+                    "ip": "192.168.1.2",
+                    "port": 7003
+                    "statusUpdateInterval": 10,
+                    "encryptionVersion": 0,
                     "model": "Pulse 3.2kW GWH12AGB-K6DNA1A/I",
                     "speedSteps": 5,
-                    "encryptionVersion": 0,
-                    "statusUpdateInterval": 10,
-                    "sensorOffset": 40,
                     "minimumTargetTemperature": 16,
                     "maximumTargetTemperature": 30,
-                    "xFanEnabled": true,
+                    "sensorOffset": 40,
                     "temperatureSensor": "disabled",
+                    "xFanEnabled": true,
                     "overrideDefaultVerticalSwing": 0,
                     "defaultVerticalSwing": 0,
                     "disabled": false
@@ -117,27 +144,31 @@ _Only the relevant part of the configuration file is displayed:_
         }
     ]
 ```
+_It's not recommended to add the port and ip parameters. The above example contains them but only for showing all optional parameters also._
+
 * name - Unique name of the platform plugin
 * platform - **GREEAirConditioner** (fixed name, it identifies the plugin)
-* port - free UDP port (homebridge will use this port for network communication; it is recommended to select a port which is not used and the next 256 ports are also available because devices will be bound to a separate port based on the last part of the device's IPv4 address and the port specified in the configuration; valid values: 1025 - 65279)
-* scanAddress - local network broadcast address (some network knowledge is required to determine this address; in many cases its default value is 192.168.1.255)
-* scanCount - number of retries for locating devices on the network (minimum 3 retries have to be specified)
-* scanTimeout - time period in seconds between device query retries
+* port - free UDP port (optional) (plugin will use this port for network communication; valid values: 1025 - 65535) **Do not specify a port unless you have trouble with automatic port assignment!**
+* scanInterval - time period in seconds between device query retries (defaults to 60 sec if missing)
 * devices - devices should be listed in this block (specify as many devices as you have on your network)
-* mac - MAC address (Serial Number) of the device
-* name - custom name of the device (optional)
-* model - model name, information only (optional)
-* speedSteps - fan speed steps of the unit (valid values are: 3 and 5)
-* encryptionVersion - Auto (0) is fine for most AC units. If auto does not work then you can force v1 (1) or v2 (2) encryption version to use in network communication
-* statusUpdateInterval - device status will be refreshed based on this interval (in seconds)
-* sensorOffset - device temperature sensor offset value for current temperature calibration (default is 40 °C, must be specified in °C)
-* minimumTargetTemperature - minimum target temperature accepted by the device (default is 16 °C, must be specified in °C, valid values: 16-30)
-* maximumTargetTemperature - maximum target temperature accepted by the device (default is 30 °C, must be specified in °C, valid values: 16-30)
-* xFanEnabled - automatically turn on xFan functionality in supported device modes (xFan actual setting is not modified by the Home App if disabled)
-* temperatureSensor - control additional temperature sensor accessory in Home App (disabled = do not add to Home App / child = add as a child accessory / separate = add as a separate (independent) accessory)
-* overrideDefaultVerticalSwing - by default this plugin does not change the vertical swing position of the AC unit but some devices do not keep the original vertical position set by the remote control if controlled from Homebridge and return back to device default position; this setting allows to override the default position -> if AC unit is set to default vertical swing position Homebridge modifies it to a predefined position (set by defaultVerticalSwing) (Never (0) = turn off override, let device use default / After power on (1) = override default position on each power on / After power on and swing disable (2) = override default position on each power on and each time when swing is switched to disabled)
-* defaultVerticalSwing - specify the vertical swing position to be used instead of device default when overriding is enabled (Device default (0) = use device default, same position as used by device by default without overriding / one of the following 5 positions: fixed Highest (2), fixed Higher (3), fixed Middle (4), fixed Lower (5), fixed Lowest (6))
-* disabled - set to true if you do not want to control this device in the Home App (old devices can be removed using this parameter)
+  * mac - MAC address (Serial Number) of the device
+  * name - custom name of the device (optional) Please use only alphanumeric, space, and apostrophe characters. Ensure it starts and ends with an alphabetic or numeric character, and avoid emojis.
+  * ip - device IP address (optional) Address is auto detected if this parameter is missing. **Specify only if device is located on a different subnet then homebridge!**
+  * port - free UDP port (optional) (plugin will listen on this port for data received from the device; valid values: 1025 - 65535) **Do not specify a port unless you have trouble with automatic port assignment!**
+  * statusUpdateInterval - device status will be refreshed based on this interval (in seconds)
+  * encryptionVersion - Auto (0) is fine for most AC units. If auto does not work then you can force v1 (1) or v2 (2) encryption version to use in network communication
+  * model - model name, information only (optional)
+  * speedSteps - fan speed steps of the unit (valid values are: 3 and 5)
+  * minimumTargetTemperature - minimum target temperature accepted by the device (default is 16 °C, must be specified in °C, valid values: 16-30)
+  * maximumTargetTemperature - maximum target temperature accepted by the device (default is 30 °C, must be specified in °C, valid values: 16-30)
+  * sensorOffset - device temperature sensor offset value for current temperature calibration (default is 40 °C, must be specified in °C)
+  * temperatureSensor - control additional temperature sensor accessory in Home App (disabled = do not add to Home App / child = add as a child accessory / separate = add as a separate (independent) accessory)
+  * xFanEnabled - automatically turn on xFan functionality in supported device modes (xFan actual setting is not modified by the Home App if disabled)
+  * overrideDefaultVerticalSwing - by default this plugin does not change the vertical swing position of the AC unit but some devices do not keep the original vertical position set by the remote control if controlled from Homebridge and return back to device default position; this setting allows to override the default position -> if AC unit is set to default vertical swing position Homebridge modifies it to a predefined position (set by defaultVerticalSwing) (Never (0) = turn off override, let device use default / After power on (1) = override default position on each power on / After power on and swing disable (2) = override default position on each power on and each time when swing is switched to disabled)
+  * defaultVerticalSwing - specify the vertical swing position to be used instead of device default when overriding is enabled (Device default (0) = use device default, same position as used by device by default without overriding / one of the following 5 positions: fixed Highest (2), fixed Higher (3), fixed Middle (4), fixed Lower (5), fixed Lowest (6))
+  * disabled - set to true if you do not want to control this device in the Home App _(can be used also to temporarily remove the device from Home App but not if the device is not responding any more on the network)_
+
+Recommended configuration:
 
 ![Homebridge UI](./uiconfig.jpg)
 
@@ -149,25 +180,19 @@ Open selected device and in the upper right corner select menu symbol:
 
 ![AC device](./greedevice.jpg)![MAC Address](./greemac.jpg)
 
-### Network broadcast address
+### MAC address alternative detection method
 
-All devices on the local network use the same broadcast address. The broadcast address can be calculated from the IP address and the subnet mask of any device which is connected to the LAN. (E.g. your router or computer) You can find several online calculators which help to determine the broadcast address.
+If you are not familiar with the GREE+ mobile app there is an alternative method to detect the MAC address of your devices:
 
-On Unix-like systems you can query the broadcast address using the following command:
-```bash
-ifconfig | grep broadcast
-# result
-# inet 192.168.1.10 netmask 0xffffff00 broadcast 192.168.1.255
-```
-On Windows there is no easy way to read the broadcast address. You can query the IP address and the subnet mask using the following command:
-```cmd
-ipconfig
-# result
-# IPv4 Address. . . . . . . . . . . : 192.168.1.10
-# Subnet Mask . . . . . . . . . . . : 255.255.255.0
-# Default Gateway . . . . . . . . . : 192.168.1.254
-```
-You have to calculate the broadcast address from the IP address and the Subnet mask.
+- Install the plugin
+- Do not configure AC unit devices
+- (Re)start Homebridge
+- GREE Air Conditioner Platform Plugin will auto detect all accessible devices and write an entry to the log
+- The log entry contains the MAC address of the device E.g.: MAC address is 502cc6000000 in the following log entry:
+
+> Accessory **502cc6000000** not configured - skipped
+
+Unfortunaltely if you have multiple devices you will not know which MAC address belongs to which AC unit. In this case you have to test it. This may require some adding - removal - re-adding cycle before final configuration.
 
 ### Device settings
 
@@ -179,17 +204,30 @@ Some settings are initialized by Home App only once (when enabling the device).
 
 All other settings are applied when starting up Homebridge. You have to restart Homebridge to apply changes in configuration settings.
 
+### IP address
+
+IP addresses of the AC units are determined automatically by the plugin. However this auto detection works only if the AC unit is on the same subnet as homebridge. There is an optional IP address parameter which can be used to specifiy the unit's IP address if it is on a different subnet. (Routing should be correctly set up to communicate with units on different subnets.)
+
+### Port
+
+Network communication uses UDP ports. There are two kind of ports:
+
+- Plugin port. This port is used by the plugin to communicate on the network.
+- Device specific port. The plugin is listening for data received from the device using this port.
+
+All ports are set up automatically by default. In some cases auto detection is not appropriate. (E.g. when firewall rules should be set up) It is possible to overwrite the default ports by optional port parameters (for the plugin and also for each devices).
+
 ### Temperature display units
 
 Home App allows to set the device temperature display units but it is independent from the temperature units shown in Home App. Home App always displays temperature values as specified by iOS/MacOS (can be changed in Preferences / Regional settings section). Display unit conversion is made by the Home App device (e.g. iPhone).
 
 ### Temperature measurement
 
-Temperature measurement is not perfect if using the built-in sensor. It is highly affected by current operation and can differ from actual temperature of other places in the room. It is recommended to use a sperarate temperature sensor and place it not too close to the AC unit if you plan to set up automations based on temperature values.
+Temperature measurement is not perfect if using the built-in sensor. It is highly affected by current operation and can differ from actual temperature of other places in the room. It is recommended to use a sperarate HomeKit compatible temperature sensor and place it not too close to the AC unit if you plan to set up automations based on temperature values.
 
 ### Invalid room temperature
 
-Some AC units have a built-in temperature sensor but the actual room temperature is not displayed in Home App. This is an AC firmware problem. Older firware versions do not report temperature values at all and there are some firmware versions which report a fixed value (e.g. zero) instead of the measured one. This plugin replaces the missing value and the fixed zero value by the desired target temperature. To get the correct measured temperature please try to upgrade or downgrade the AC firmware.
+Some AC units have a built-in temperature sensor but the actual room temperature is not displayed in Home App. This is an AC firmware problem. Older firmware versions do not report temperature values at all and there are some firmware versions which report a fixed value (e.g. zero) instead of the measured one. This plugin replaces the missing value and the fixed zero value by the desired target temperature. To get the correct measured temperature please try to upgrade or downgrade the AC firmware.
 
 ### Fan speed
 
@@ -201,6 +239,47 @@ Slider description: Zero means off. Minimum value turns on Quiet mode. Next valu
 
 ** these values are supported only on 5-speed models
 
+### Accessory removal
+
+If an AC unit is still working and accessible on the network you can remove the associated accessory by setting the device's "disabled" parameter to true and restarting Homebridge.
+
+If you need to remove an old AC unit which is not accessible any more (e.g hardware failure or device was replaced with a new one) you need to use the graphical user interface of Homebridge ([Homebridge Config UI X](https://www.npmjs.com/package/homebridge-config-ui-x)). Follow these steps:
+1) Open Homebridge GUI
+1) Go to Settings page
+1) Go to Accessories section
+1) Select Remove Single Accessory
+1) Search for the accessory to be removed in list
+1) Click on the waste icon of the selected accessory
+
+On some platforms the graphical user interface of Homebridge does not support accessory removal. In this case you have to remove and reinstall the plugin to remove a deprecated accessory or you need to manually edit the cache file (it requires advanced Homebridge technical knowledge).
+
+### Troubleshouting
+
+Most known errors are fixed by later versions. If so yo can upgrade to the latest version and it will solve the problem. Some errors may require some additional steps.
+
+#### "Failed to save cached accessories to disk: Converting circular structure to JSON" error
+
+This error is fixed in v2.1.2 and later. First upgrade the plugin to the latest version and restart Homebridge twice. Wait a few minutes between restarts. If it does not solve the problem follow these steps:
+
+1) Uninstall the plugin (and remove the child bridge if a dedicated child bridge was added)
+1) Go through all cached accessories and delete every instance of accessories created by this plugin:
+   - Homebridge GUI > Settings page
+   - Accessories section > Remove Single Accessory
+   - Click the waste icon of the selected accessory
+1) Restart Homebridge
+1) Install the latest version of the plugin
+1) Configure the plugin
+
+Do not try to restore Homebridge configuration from backup because this error means that the cached configuration is corrupt and all the backups contain also the corrupt configuration! Restoring settings from backup will restore the error also.
+
+#### Unusual behaviour
+
+Check if you are using the correct version of configuration settings. It is always recommended to open and save the actual configuration settings using the graphical user interface of Homebridge. Pressing the Save button on the GUI automatically converts the configuration settings to the actual version. It is useful to re-save the configuration after each upgrade or downgrade even if there are no visible changes in the parameters.
+
+#### Device not responding
+
+If an AC unit device is not supported it may be added successfully to the Home App as an accessory but never appears the "Device is bound ..." message in the Homebridge log. Unbound devices can't respond to network requests so they are unresponsive in Home App. There is no way to decide if the unresponsive device is only turned off (no AC power) or it has a not supported firmware version. It means that a missing error message does not mean that the device is supported. You can check the Homebrdige log. All supported devices write a "Device is bound ..." message into the Homebridge log after successful configuration upon Homebridge startup.
+
 ## Refs & Credits
 
 Special thanks to [tomikaa87](https://github.com/tomikaa87) and [kongkx](https://github.com/kongkx) for GREE network protocol information and code samples. Thank you [mateuszm7](https://github.com/mateuszm7) and [zivanek](https://github.com/zivanek) for helping to implement the version 2 network protocol.

package/config.schema.json

@@ -12,27 +12,14 @@
       },
       "port": {
         "type": "integer",
-        "required": true,
-        "default": 7002,
+        "required": false,
         "minimum": 1025
       },
-      "scanAddress": {
-        "type": "string",
-        "required": true,
-        "default": "192.168.1.255",
-        "format": "ipv4"
-      },
-      "scanCount": {
-        "type": "integer",
-        "required": true,
-        "default": 10,
-        "minimum": 3
-      },
-      "scanTimeout": {
+      "scanInterval": {
         "type": "integer",
-        "required": true,
-        "default": 3,
-        "minimum": 1
+        "required": false,
+        "default": 60,
+        "minimum": 5
       },
       "devices": {
         "type": "array",
@@ -75,28 +62,28 @@
               "type": "integer",
               "required": false,
               "minimum": 1,
-              "default": 10
+              "placeholder": 10
             },
             "sensorOffset": {
               "type": "integer",
               "required": false,
-              "default": 40
+              "placeholder": 40
             },
             "minimumTargetTemperature": {
               "type": "integer",
               "required": false,
               "minimum": 16,
-              "default": 16
+              "placeholder": 16
             },
             "maximumTargetTemperature": {
               "type": "integer",
               "required": false,
               "maximum": 30,
-              "default": 30
+              "placeholder": 30
             },
             "xFanEnabled": {
               "type": "boolean",
-              "default": false
+              "default": true
             },
             "temperatureSensor": {
               "type": "string",
@@ -218,6 +205,16 @@
                   ]
                 }
               ]
+            },
+            "port": {
+              "type": "integer",
+              "required": false,
+              "minimum": 1025
+            },
+            "ip": {
+              "type": "string",
+              "required": false,
+              "format": "ipv4"
             }
           }
         }
@@ -233,28 +230,17 @@
       "type": "flex",
       "flex-flow": "row wrap",
       "items": [
-        {
-          "key": "scanAddress",
-          "flex": "1 1 50%",
-          "title": "Scan address:",
-          "description": "Local network broadcast address"
-        },
         {
           "key": "port",
           "flex": "1 1 50%",
-          "title": "Port:"
+          "title": "Port:",
+          "description": "Platform level UDP port (auto if empty)"
         },
         {
-          "key": "scanCount",
+          "key": "scanInterval",
           "flex": "1 1 50%",
-          "title": "Scan count:",
-          "description": "Initial device discovery retry count"
-        },
-        {
-          "key": "scanTimeout",
-          "flex": "1 1 50%",
-          "title": "Scan timeout:",
-          "description": "Timeout in seconds between device discovery retries"
+          "title": "Scan interval:",
+          "description": "Interval in seconds between device discovery retries (60 sec if empty)"
         }
       ]
     },
@@ -281,7 +267,7 @@
               "key": "devices[].name",
               "flex": "1 1 50%",
               "title": "Device name:",
-              "description": "Custom name of the device"
+              "description": "Custom name of the device. Please use only alphanumeric, space, and apostrophe characters. Ensure it starts and ends with an alphabetic or numeric character, and avoid emojis."
             },
             {
               "key": "devices[].disabled",
@@ -293,17 +279,19 @@
               }
             },
             {
-              "key": "devices[].model",
+              "key": "devices[].ip",
               "flex": "1 1 50%",
-              "title": "Device model:",
+              "title": "IP address:",
+              "description": "Device IP address (auto if empty)",
               "condition": {
                 "functionBody": "return (model.devices && model.devices[arrayIndices] && model.devices[arrayIndices].mac && /^[a-f0-9]{12}$/.test(model.devices[arrayIndices].mac) && model.devices[arrayIndices].disabled !== true);"
               }
             },
             {
-              "key": "devices[].speedSteps",
+              "key": "devices[].port",
               "flex": "1 1 50%",
-              "title": "Fan speed steps:",
+              "title": "Port:",
+              "description": "Device specific UDP port (auto if empty)",
               "condition": {
                 "functionBody": "return (model.devices && model.devices[arrayIndices] && model.devices[arrayIndices].mac && /^[a-f0-9]{12}$/.test(model.devices[arrayIndices].mac) && model.devices[arrayIndices].disabled !== true);"
               }
@@ -326,6 +314,22 @@
                 "functionBody": "return (model.devices && model.devices[arrayIndices] && model.devices[arrayIndices].mac && /^[a-f0-9]{12}$/.test(model.devices[arrayIndices].mac) && model.devices[arrayIndices].disabled !== true);"
               }
             },
+            {
+              "key": "devices[].model",
+              "flex": "1 1 50%",
+              "title": "Device model:",
+              "condition": {
+                "functionBody": "return (model.devices && model.devices[arrayIndices] && model.devices[arrayIndices].mac && /^[a-f0-9]{12}$/.test(model.devices[arrayIndices].mac) && model.devices[arrayIndices].disabled !== true);"
+              }
+            },
+            {
+              "key": "devices[].speedSteps",
+              "flex": "1 1 50%",
+              "title": "Fan speed steps:",
+              "condition": {
+                "functionBody": "return (model.devices && model.devices[arrayIndices] && model.devices[arrayIndices].mac && /^[a-f0-9]{12}$/.test(model.devices[arrayIndices].mac) && model.devices[arrayIndices].disabled !== true);"
+              }
+            },
             {
               "key": "devices[].minimumTargetTemperature",
               "flex": "1 1 50%",
@@ -353,15 +357,6 @@
                 "functionBody": "return (model.devices && model.devices[arrayIndices] && model.devices[arrayIndices].mac && /^[a-f0-9]{12}$/.test(model.devices[arrayIndices].mac) && model.devices[arrayIndices].disabled !== true);"
               }
             },
-            {
-              "key": "devices[].xFanEnabled",
-              "flex": "1 1 50%",
-              "title": "xFan enabled",
-              "description": "If enabled, then xFan functionality is turned on automatically on the device",
-              "condition": {
-                "functionBody": "return (model.devices && model.devices[arrayIndices] && model.devices[arrayIndices].mac && /^[a-f0-9]{12}$/.test(model.devices[arrayIndices].mac) && model.devices[arrayIndices].disabled !== true);"
-              }
-            },
             {
               "key": "devices[].temperatureSensor",
               "flex": "1 1 50%",
@@ -372,7 +367,10 @@
               }
             },
             {
-              "flex": "1 1 50%",
+              "key": "devices[].xFanEnabled",
+              "flex": "1 1 100%",
+              "title": "xFan enabled",
+              "description": "If enabled, then xFan functionality is turned on automatically on the device",
               "condition": {
                 "functionBody": "return (model.devices && model.devices[arrayIndices] && model.devices[arrayIndices].mac && /^[a-f0-9]{12}$/.test(model.devices[arrayIndices].mac) && model.devices[arrayIndices].disabled !== true);"
               }

package/dist/platform.d.ts

@@ -1,5 +1,4 @@
 import { API, DynamicPlatformPlugin, Logger, PlatformAccessory, PlatformConfig, Service, Characteristic } from 'homebridge';
-import { GreeAirConditioner } from './platformAccessory';
 /**
  * HomebridgePlatform
  * This class is the main constructor for your plugin, this is where you should
@@ -15,8 +14,7 @@ export declare class GreeACPlatform implements DynamicPlatformPlugin {
     private initializedDevices;
     private skippedDevices;
     private socket;
-    private timer;
-    private scanCount;
+    private pluginAddresses;
     constructor(log: Logger, config: PlatformConfig, api: API);
     /**
      * This function is invoked when homebridge restores cached accessories from disk at startup.
@@ -27,9 +25,11 @@ export declare class GreeACPlatform implements DynamicPlatformPlugin {
      * Accessories must only be registered once, previously created accessories
      * must not be registered again to prevent "duplicate UUID" errors.
      */
+    bindCallback(): void;
     discoverDevices(): void;
     handleMessage: (msg: any, rinfo: any) => void;
-    registerDevice: (deviceInfo: any) => GreeAirConditioner | undefined;
+    registerDevice: (deviceInfo: any) => void;
     broadcastScan(): void;
+    getNetworkAddresses(): {};
 }
 //# sourceMappingURL=platform.d.ts.map

package/dist/platform.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"platform.d.ts","sourceRoot":"","sources":["../src/platform.ts"],"names":[],"mappings":"AAEA,OAAO,EAAE,GAAG,EAAE,qBAAqB,EAAE,MAAM,EAAE,iBAAiB,EAAE,cAAc,EAAE,OAAO,EAAE,cAAc,EAAc,MAAM,YAAY,CAAC;AAGxI,OAAO,EAAE,kBAAkB,EAAE,MAAM,qBAAqB,CAAC;AAIzD;;;;GAIG;AACH,qBAAa,cAAe,YAAW,qBAAqB;aAaxC,GAAG,EAAE,MAAM;aACX,MAAM,EAAE,cAAc;aACtB,GAAG,EAAE,GAAG;IAd1B,SAAgB,OAAO,EAAE,OAAO,OAAO,CAAwB;IAC/D,SAAgB,cAAc,EAAE,OAAO,cAAc,CAA+B;IAGpF,OAAO,CAAC,OAAO,CAAoC;IACnD,OAAO,CAAC,kBAAkB,CAA0B;IACpD,OAAO,CAAC,cAAc,CAA0B;IAChD,OAAO,CAAC,MAAM,CAAe;IAC7B,OAAO,CAAC,KAAK,CAA6B;IAC1C,OAAO,CAAC,SAAS,CAAS;gBAGR,GAAG,EAAE,MAAM,EACX,MAAM,EAAE,cAAc,EACtB,GAAG,EAAE,GAAG;IAqB1B;;;OAGG;IACH,kBAAkB,CAAC,SAAS,EAAE,iBAAiB;IAgB/C;;;OAGG;IACH,eAAe;IAyCf,aAAa,iCA2CX;IAEF,cAAc,sDAoGZ;IAEF,aAAa;CASd"}
+{"version":3,"file":"platform.d.ts","sourceRoot":"","sources":["../src/platform.ts"],"names":[],"mappings":"AAEA,OAAO,EAAE,GAAG,EAAE,qBAAqB,EAAE,MAAM,EAAE,iBAAiB,EAAE,cAAc,EAAE,OAAO,EAAE,cAAc,EAAc,MAAM,YAAY,CAAC;AAUxI;;;;GAIG;AACH,qBAAa,cAAe,YAAW,qBAAqB;aAYxC,GAAG,EAAE,MAAM;aACX,MAAM,EAAE,cAAc;aACtB,GAAG,EAAE,GAAG;IAb1B,SAAgB,OAAO,EAAE,OAAO,OAAO,CAAwB;IAC/D,SAAgB,cAAc,EAAE,OAAO,cAAc,CAA+B;IAGpF,OAAO,CAAC,OAAO,CAAoC;IACnD,OAAO,CAAC,kBAAkB,CAA0B;IACpD,OAAO,CAAC,cAAc,CAA0B;IAChD,OAAO,CAAC,MAAM,CAAe;IAC7B,OAAO,CAAC,eAAe,CAA8B;gBAGnC,GAAG,EAAE,MAAM,EACX,MAAM,EAAE,cAAc,EACtB,GAAG,EAAE,GAAG;IAsC1B;;;OAGG;IACH,kBAAkB,CAAC,SAAS,EAAE,iBAAiB;IAe/C;;;OAGG;IACH,YAAY;IAQZ,eAAe;IAUf,aAAa,iCA4CX;IAEF,cAAc,4BA+IZ;IAEF,aAAa;IAiBb,mBAAmB;CAoDpB"}