[DNM] Gree Integration rewrite by p-monteiro · Pull Request #373 · RobHofmann/HomeAssistant-GreeClimateComponent

p-monteiro · 2025-09-23T20:20:16Z

[DO NOT MERGE]

⚠️ATTENTION ⚠

This PR changes the domain of the integration, so current users will lose their device configs!
The config schema also changed, so verify your YAML if you use it to configure the devices.

This PR introduces a rewrite of this integration. The main goal of this was to better align the integration with the Home Assistant (HA) development workflow with two main changes:

Completely separate device API code from HA code
Align with code style guidelines (mainly Ruff code formatting and full typing)

Other changes that are present in this PR:

Async device communication
Use a device coordinator to fetch data from the device
Device Features are user-selectable since the Gree API does not provide a reliable method of getting them
Improvements to entity creation and config flow with better errors and organization
Gree API functions are better structured and clearer to understand the logic, which is also reused when possible
Gree API is fully declarative, no string guessing
Gree API now provides a GreeDevice object to handle device logic
Implement Auto Encryption version
Expose entity restore behavior as a configuration
Properly allow to reconfigure a config entry (including device connection, useful for when a device changes IP)
Support for individual device removal
RestoreEntity support in ClimateEntity
Exposed all device sensors as entities
Allow to set the device temperature units (shown on the device display)
Support for diagnostics download in the config entries and the devices

I want full feature parity with the current integration and iron out some bugs before this is ready to merge (if you so wish). Currently missing and wishlist:

[Bug] Broken VRF Device Status

As you can see, there are a lot of changes, and I understand if this does not go through as is.
I am creating the PR mainly to gather feedback and track progress since most features are now present in this PR.
Don't treat this PR as blocking. I am tracking new changes and integrating them as they are committed.

Also, since this is a big rewrite, I wonder if we should use it to bump the major version (4?) and possibly change the domain to not replace the official integration (as I saw in the bug reports that it might impose some problems).

- Change config flow to: be multi step and allow setting the device features; allow to reconfigure an entry - Separate HA and Device API logic: device API is now declarative and handles device behaviour. HA entities expose the device - Implement a coordinator - Async device communication - More error handling

- Move consts around - Proper error report on config_flow - Proper translations on config_flow - Configuration of timeout - Fetch device info during binding

p-monteiro · 2025-09-24T21:05:16Z

@RobHofmann I was adding the temperature step back, but I'm not sure of its utility.
Is there any device that accepts non-integer ºC/ºF?

… and device comunication state

domialex · 2025-09-26T18:24:44Z

@p-monteiro
The temperature step should not be in the configuration entities anyways, it should be in the climate options. That was a mistake on my part.

p-monteiro · 2025-09-26T18:27:52Z

Hi @domialex, that's fine. I'm more interested in the real use case for it. Should it be locked to integers? I don't think any device supports half degrees or even 0.1 steps, as is the lower limit for the current slider...

rudizl · 2026-01-21T15:28:02Z

I`ve installed your code, everything works- the 1-st is GEH18AAXF-K6DNA1 and the second is GWH12AVCXD-K6DNA1A. Both with FW 1.31.

chkr1011 · 2026-01-21T17:50:59Z

I tried your code as well but I am not able to connect the devices any longer. With the "original" version it worked fine. It says that it was not able to obtain the encryption key. The "original" code is capable of doing this (encryption version = 2).

I also picked the encryption keys from the logs from the original version but it did not help. The devices are also no auto discovered anymore. None of the 3 devices is found. The original integration was able to find these but adding still required manual input.

p-monteiro · 2026-01-21T18:31:20Z

@chkr1011 Sorry, I didn't have much time lately to continue this code, apart from minor tweaks.

Can you provide more information about your case, if it is the latest code, what kind of setup you have (normal or VRF), and if possible, the logs from the integration (enable debug mode before searching or adding a device).

Hopefully, next month I'll be able to take a deeper look into the issues.

chkr1011 · 2026-01-21T18:52:26Z

Here is what I get when trying to discover the devices:

2026-01-21 19:38:58.691 ERROR (MainThread) [aiohttp.server] Error handling request from 192.168.1.159
Traceback (most recent call last):
  File "/usr/local/lib/python3.13/site-packages/aiohttp/web_protocol.py", line 510, in _handle_request
    resp = await request_handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/aiohttp/web_app.py", line 569, in _handle
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/aiohttp/web_middlewares.py", line 117, in impl
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 92, in security_filter_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 87, in forwarded_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 26, in request_context_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 86, in ban_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 242, in auth_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/headers.py", line 41, in headers_middleware
    response = await handler(request)
               ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/http.py", line 73, in handle
    result = await handler(request, **request.match_info)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/decorators.py", line 83, in with_admin
    return await func(self, request, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 234, in post
    return await super().post(request, flow_id)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/data_validator.py", line 74, in wrapper
    return await method(view, request, data, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py", line 121, in post
    result = await self._flow_mgr.async_configure(flow_id, data)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 346, in async_configure
    result = await self._async_configure(flow_id, user_input)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 393, in _async_configure
    result = await self._async_handle_step(
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        flow, cur_step["step_id"], user_input
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 493, in _async_handle_step
    result: _FlowResultT = await getattr(flow, method)(user_input)
                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/gree_custom/config_flow.py", line 579, in async_step_user
    return await self.async_step_manual_discovery()
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/gree_custom/config_flow.py", line 622, in async_step_manual_discovery
    self._discovered_devices = await self._discover_devices(self.hass)
                               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/gree_custom/config_flow.py", line 893, in _discover_devices
    return await discover_gree_devices(broadcast_addresses, 5)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/gree_custom/aiogree/api.py", line 813, in discover_gree_devices
    data = get_gree_response_data(
        response,
        gree_get_default_cipher(EncryptionVersion.V1),
        EncryptionVersion.V1,
    )
  File "/config/custom_components/gree_custom/aiogree/api.py", line 393, in get_gree_response_data
    decryptedPack = cipher.decrypt(pack)
  File "/usr/local/lib/python3.13/site-packages/Crypto/Cipher/_mode_ecb.py", line 196, in decrypt
    raise ValueError("Data must be aligned to block boundary in ECB mode")
ValueError: Data must be aligned to block boundary in ECB mode

To me this looks like that the integration is not trying encryption version 2 when auto discovering devices.

The following log is from the manual config flow:

2026-01-21 19:49:03.145 ERROR (MainThread) [custom_components.gree_custom.config_flow] Cannot connect
Traceback (most recent call last):
  File "/config/custom_components/gree_custom/aiogree/api.py", line 765, in gree_get_device_info
    data: dict = await get_result_pack(
                 ^^^^^^^^^^^^^^^^^^^^^^
    ...<7 lines>...
    )
    ^
  File "/config/custom_components/gree_custom/aiogree/api.py", line 420, in get_result_pack
    data = await fetch_result(
           ^^^^^^^^^^^^^^^^^^^
    ...<7 lines>...
    )
    ^
  File "/config/custom_components/gree_custom/aiogree/api.py", line 375, in fetch_result
    data = get_gree_response_data(received_json, cipher, encryption_version)
  File "/config/custom_components/gree_custom/aiogree/api.py", line 393, in get_gree_response_data
    decryptedPack = cipher.decrypt(pack)
  File "/usr/local/lib/python3.13/site-packages/Crypto/Cipher/_mode_ecb.py", line 196, in decrypt
    raise ValueError("Data must be aligned to block boundary in ECB mode")
ValueError: Data must be aligned to block boundary in ECB mode

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/config/custom_components/gree_custom/aiogree/device.py", line 148, in bind_device
    self._raw_info = await gree_get_device_info(
                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ...<3 lines>...
    )
    ^
  File "/config/custom_components/gree_custom/aiogree/api.py", line 776, in gree_get_device_info
    raise ValueError("Error retrieving basic device info") from err
ValueError: Error retrieving basic device info

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/config/custom_components/gree_custom/config_flow.py", line 686, in async_step_manual_add
    self._discovered_subdevices = await self._devices[
                                  ^^^^^^^^^^^^^^^^^^^^
        _main_device.mac_address_sub
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ].fetch_sub_devices()
    ^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/gree_custom/aiogree/device.py", line 175, in fetch_sub_devices
    await self.bind_device()
  File "/config/custom_components/gree_custom/aiogree/device.py", line 155, in bind_device
    raise CannotConnect(
        f"Not able to connect to the device {self._ip_addr}"
    ) from e
custom_components.gree_custom.aiogree.device.CannotConnect: Not able to connect to the device 192.168.1.74

For the manual config flow I filled IP, MAC, Encryption Version 2 and the Encryption Key as well. These were working properly with the original version.

The device is a Vaillant Vai5. I don't know which regular gree model this is. But no VRF.

p-monteiro · 2026-01-21T18:58:14Z

@chkr1011 Thanks for the logs, will take a look when I can. I think the original code did discovery using V1 only and V2 was only used for binding/communicating, will investigate.

rudizl · 2026-01-21T19:18:05Z

Ive added my ACs manually with IP and MAC. The encryption was discovered automatically after thah and for both is V2. Didn`t filled the encryption key, as I saw thaht the field is already with ****** :)

Inspired by github.com/cmroche/greeclimate

p-monteiro · 2026-03-12T18:34:59Z

@RobHofmann @domialex
What are your official stance in this: 0010. Integration configuration
Would this be something you are OK complying with or you really want the YAML configuration?

p-monteiro · 2026-03-12T18:36:18Z

I kindly ask the people who where having problems with this branch to retry once again.

If failures happen, please provide logs in DEBUG mode and if possible try the "Download Diagnostics" for both config entries and devices.

RobHofmann · 2026-03-13T16:38:19Z

can we somehow break this PR up in smaller pieces. I'm really not happy with 1 big PR overhauling everything. I'd like to keep the agile approach.

p-monteiro · 2026-03-13T16:54:59Z

@RobHofmann I don't mind breaking it up, but I'm not sure how much can be separated.

It mainly touches these points:

Separates Gree code from HA code, which touches almost every file
Changes the Domain
Changes the config entry and config flow - a lot!
Changes Translations
Adds some quality of life features.

Do you have any suggestions on how to go about it?
The good part is that, as is, it's working well on my part.
The bad is that I don't know how to break it without having at least 1 big PR.

domialex · 2026-03-14T00:13:10Z

It’s essentially a full rewrite, and I don’t have the time to test or review all the changes in detail.
I’m guessing this is a breaking upgrade, meaning every entity and configuration will need to be recreated. If that’s the case, you have to be ready to support the project until the release is stable, because I won't be able to.

@RobHofmann I don't recommend breaking the PR into smaller pieces since this is a rewrite, but I do recommend making a beta release instead and see how it goes. Put the release as a "pre-release", HACS should handle the rest.

RobHofmann · 2026-03-14T00:20:33Z

@domialex Thats fair.

@p-monteiro do you know if this is a breaking release (will entities be recreated or have different names for example)? And I need some insights on feature parity with the current version.

I will do some testing on my side when we clean the above things up.

p-monteiro · 2026-03-14T11:33:06Z

@RobHofmann This is very much a breaking release, because configs cannot be migrated (change in Domain).
Some entities might keep their name after configs are recreated, but I wouldn't count on it.

I didn't know HACS supported pre-preleases; that would be sweet because it's missing testing.

@domialex, I am trying to support it as best as I can, from what I gather in this PR, VRF is an issue, and discovery seems to fail in encryption v1 (?). I need people to test and send logs, because my multisplit is working well, as is. I'd love to make more meaningful logs, but I'm not sure how, because when it fails, it basically gives an exception communicating with the device, probably because a bad request was made. But the device is a bit of a black box.

Regarding feature regressions, I don't think there are any more. Some things might be configured differently during the flow, but the end result should be good.

ChillingSilence · 2026-03-15T08:51:58Z

I'm getting the following error:

Logger: custom_components.gree_custom.config_flow
Source: custom_components/gree_custom/config_flow.py:686
integration: Gree A/C ([documentation](https://github.com/RobHofmann/HomeAssistant-GreeClimateComponent))
First occurred: 9:38:33 PM (1 occurrence)
Last logged: 9:38:33 PM

Error while binding
Traceback (most recent call last):
  File "/config/custom_components/gree_custom/aiogree/api.py", line 364, in fetch_result
    received_json = await udp_request_async(
                    ^^^^^^^^^^^^^^^^^^^^^^^^
        ip_addr, port, json_data, max_connection_attempts, timeout
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/config/custom_components/gree_custom/aiogree/api.py", line 294, in udp_request_async
    raise ValueError(
        f"Failed to communicate with device '{ip_addr}:{port}' after {max_retries} attempts"
    )
ValueError: Failed to communicate with device '192.168.22.120:7000' after 2 attempts

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/config/custom_components/gree_custom/aiogree/api.py", line 598, in gree_get_device_key
    result = await get_result_pack(
             ^^^^^^^^^^^^^^^^^^^^^^
    ...<7 lines>...
    )
    ^
  File "/config/custom_components/gree_custom/aiogree/api.py", line 420, in get_result_pack
    data = await fetch_result(
           ^^^^^^^^^^^^^^^^^^^
    ...<7 lines>...
    )
    ^
  File "/config/custom_components/gree_custom/aiogree/api.py", line 368, in fetch_result
    raise ValueError(f"Error communicating with {ip_addr}: {err}") from err
ValueError: Error communicating with 192.168.22.120: Failed to communicate with device '192.168.22.120:7000' after 2 attempts

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/config/custom_components/gree_custom/aiogree/device.py", line 116, in bind_device
    ) = await gree_get_device_key(
        ^^^^^^^^^^^^^^^^^^^^^^^^^^
    ...<7 lines>...
    )
    ^
  File "/config/custom_components/gree_custom/aiogree/api.py", line 629, in gree_get_device_key
    raise ValueError("Error getting device encryption key") from error
ValueError: Error getting device encryption key

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/config/custom_components/gree_custom/config_flow.py", line 686, in async_step_manual_add
    self._discovered_subdevices = await self._devices[
                                  ^^^^^^^^^^^^^^^^^^^^
        _main_device.mac_address_sub
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ].fetch_sub_devices()
    ^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/gree_custom/aiogree/device.py", line 175, in fetch_sub_devices
    await self.bind_device()
  File "/config/custom_components/gree_custom/aiogree/device.py", line 127, in bind_device
    raise GreeDeviceNotBoundError("Unable to obtain device key") from e
custom_components.gree_custom.aiogree.device.GreeDeviceNotBoundError: Unable to obtain device key

I ran a git pull to ensure I had the latest, on the gree-rewrite branch, and then restarted HA.
I have confirmed the IP and MAC address, it's on the WiFi responding to pings. First I tried with the auto discovery, then I tried manually entering it.

When I download the logs from Home Assistant rather than just clicking on the error binding, I get:

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun home-assistant (no readiness notification)
s6-rc: info: service legacy-services successfully started
2026-03-15 21:25:51.641 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration ac_infinity which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2026-03-15 21:25:51.642 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration gree_custom which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2026-03-15 21:25:51.642 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration intesishome which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2026-03-15 21:25:51.643 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2026-03-15 21:31:01.140 DEBUG (MainThread) [custom_components.gree_custom.config_flow] Found broadcast addresses from HA: ['255.255.255.255']
2026-03-15 21:31:01.140 DEBUG (MainThread) [custom_components.gree_custom.aiogree.api] Sending broadcast to 255.255.255.255
2026-03-15 21:31:01.141 DEBUG (MainThread) [custom_components.gree_custom.aiogree.api] Sending broadcast to 192.168.255.255
2026-03-15 21:31:01.142 DEBUG (MainThread) [custom_components.gree_custom.aiogree.api] Sending broadcast to 10.255.255.255
2026-03-15 21:31:01.142 DEBUG (MainThread) [custom_components.gree_custom.aiogree.api] Sending broadcast to 172.31.255.255
2026-03-15 21:31:01.143 DEBUG (MainThread) [custom_components.gree_custom.aiogree.api] Sent broadcast packets, waiting for replies... 
2026-03-15 21:31:06.148 DEBUG (MainThread) [custom_components.gree_custom.aiogree.api] Got 0 responses in 5 seconds: {}
2026-03-15 21:31:08.706 ERROR (MainThread) [custom_components.ac_infinity.core] Error fetching ac_infinity data: 
2026-03-15 21:38:24.362 INFO (MainThread) [custom_components.gree_custom.aiogree.device] Initialize the GREE Device API for: 58:0d:0d:34:74:fc (192.168.22.120:7000)
2026-03-15 21:38:24.362 DEBUG (MainThread) [custom_components.gree_custom.aiogree.device] Version: None, Key: [omitted]
2026-03-15 21:38:24.362 DEBUG (MainThread) [custom_components.gree_custom.aiogree.device] Trying to get subdevices
2026-03-15 21:38:24.362 INFO (MainThread) [custom_components.gree_custom.aiogree.api] Trying to retrieve device encryption key v1
2026-03-15 21:38:24.363 DEBUG (MainThread) [custom_components.gree_custom.aiogree.api] Bind Pack: {"mac": "580d0d3474fc", "t": "bind", "uid": 0}
2026-03-15 21:38:24.372 DEBUG (MainThread) [custom_components.gree_custom.aiogree.api] Payload: {'cid': 'app', 'i': 1, 'pack': 'Fo0NJVLzyhX4Qh3bOqWhT4QPXnuPS0a5W/exMkAoHz3IfE1fYVsWM5kifDBw/LN1', 't': 'pack', 'tcid': '580d0d3474fc', 'uid': 0}
2026-03-15 21:38:24.373 DEBUG (MainThread) [custom_components.gree_custom.aiogree.api] Fetching data from 192.168.22.120
2026-03-15 21:38:26.374 WARNING (MainThread) [custom_components.gree_custom.aiogree.api] Error communicating with 192.168.22.120. Attempt 1/2 | 
2026-03-15 21:38:28.878 WARNING (MainThread) [custom_components.gree_custom.aiogree.api] Error communicating with 192.168.22.120. Attempt 2/2 | 
2026-03-15 21:38:28.878 ERROR (MainThread) [custom_components.gree_custom.aiogree.api] Error getting device encryption key with version 1:
Error communicating with 192.168.22.120: Failed to communicate with device '192.168.22.120:7000' after 2 attempts
2026-03-15 21:38:28.878 INFO (MainThread) [custom_components.gree_custom.aiogree.api] Trying to retrieve device encryption key v2
2026-03-15 21:38:28.879 DEBUG (MainThread) [custom_components.gree_custom.aiogree.api] Bind Pack: {"cid": "580d0d3474fc", "mac": "580d0d3474fc", "t": "bind", "uid": 0}
2026-03-15 21:38:28.925 DEBUG (MainThread) [custom_components.gree_custom.aiogree.api] Payload: {'cid': 'app', 'i': 1, 'pack': 'Jtod3XIt89Dxs8SHPnkRBJt2vIVBwAvmIgk1XvjRhurELj0L3QVtft+hse+GRsWcl72qEoTtZbgS4JbKYrud0qPFjVyn', 't': 'pack', 'tcid': '580d0d3474fc', 'uid': 0, 'tag': 'qKWestnLPk4VGayIhFfpRg=='}
2026-03-15 21:38:28.925 DEBUG (MainThread) [custom_components.gree_custom.aiogree.api] Fetching data from 192.168.22.120
2026-03-15 21:38:30.926 WARNING (MainThread) [custom_components.gree_custom.aiogree.api] Error communicating with 192.168.22.120. Attempt 1/2 | 
2026-03-15 21:38:33.429 WARNING (MainThread) [custom_components.gree_custom.aiogree.api] Error communicating with 192.168.22.120. Attempt 2/2 | 
2026-03-15 21:38:33.430 ERROR (MainThread) [custom_components.gree_custom.aiogree.api] Error getting device encryption key with version 2:
Error communicating with 192.168.22.120: Failed to communicate with device '192.168.22.120:7000' after 2 attempts
2026-03-15 21:38:33.430 ERROR (MainThread) [custom_components.gree_custom.config_flow] Error while binding
Traceback (most recent call last):
  File "/config/custom_components/gree_custom/aiogree/api.py", line 364, in fetch_result
    received_json = await udp_request_async(
                    ^^^^^^^^^^^^^^^^^^^^^^^^
        ip_addr, port, json_data, max_connection_attempts, timeout
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/config/custom_components/gree_custom/aiogree/api.py", line 294, in udp_request_async
    raise ValueError(
        f"Failed to communicate with device '{ip_addr}:{port}' after {max_retries} attempts"
    )
ValueError: Failed to communicate with device '192.168.22.120:7000' after 2 attempts

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/config/custom_components/gree_custom/aiogree/api.py", line 598, in gree_get_device_key
    result = await get_result_pack(
             ^^^^^^^^^^^^^^^^^^^^^^
    ...<7 lines>...
    )
    ^
  File "/config/custom_components/gree_custom/aiogree/api.py", line 420, in get_result_pack
    data = await fetch_result(
           ^^^^^^^^^^^^^^^^^^^
    ...<7 lines>...
    )
    ^
  File "/config/custom_components/gree_custom/aiogree/api.py", line 368, in fetch_result
    raise ValueError(f"Error communicating with {ip_addr}: {err}") from err
ValueError: Error communicating with 192.168.22.120: Failed to communicate with device '192.168.22.120:7000' after 2 attempts

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/config/custom_components/gree_custom/aiogree/device.py", line 116, in bind_device
    ) = await gree_get_device_key(
        ^^^^^^^^^^^^^^^^^^^^^^^^^^
    ...<7 lines>...
    )
    ^
  File "/config/custom_components/gree_custom/aiogree/api.py", line 629, in gree_get_device_key
    raise ValueError("Error getting device encryption key") from error
ValueError: Error getting device encryption key

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/config/custom_components/gree_custom/config_flow.py", line 686, in async_step_manual_add
    self._discovered_subdevices = await self._devices[
                                  ^^^^^^^^^^^^^^^^^^^^
        _main_device.mac_address_sub
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ].fetch_sub_devices()
    ^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/gree_custom/aiogree/device.py", line 175, in fetch_sub_devices
    await self.bind_device()
  File "/config/custom_components/gree_custom/aiogree/device.py", line 127, in bind_device
    raise GreeDeviceNotBoundError("Unable to obtain device key") from e
custom_components.gree_custom.aiogree.device.GreeDeviceNotBoundError: Unable to obtain device key
2026-03-15 21:38:33.437 DEBUG (MainThread) [custom_components.gree_custom.config_flow] Building main schema with previous values: {'host': '192.168.22.120', 'mac': '58:0d:0d:34:74:fc', 'advanced': {'port': 7000, 'encryption_version': 'Auto-Detect', 'encryption_key': '', 'uid': 0, 'disable_available_check': False, 'max_online_attempts': 5, 'timeout': 10}}

Let me know if I can get further logs

p-monteiro · 2026-03-15T18:21:07Z

@ChillingSilence Thanks for the report, will look into it. Do you know the correct encryption version of your device?

ChillingSilence · 2026-03-15T19:05:41Z

Do you know the correct encryption version of your device?

I don't sorry @p-monteiro but if you have a link to how I can extract that info, I've tried the luc10/gree-api-client but I don't believe that tells me the encryption version:

I have two of these devices, both showing the same symptoms. Is there a way for me to extract that info from the app?

p-monteiro · 2026-03-15T19:14:12Z

I have two of these devices, both showing the same symptoms. Is there a way for me to extract that info from the app?

Not that I am aware of. You can try manually adding the device using that key and testing both versions.
I'm trying to clean up the logging and logic a bit to better understand these errors in the meantime.
The packets being sent are the same as in the stable version, so I guess there is an issue in the communication.

ChillingSilence · 2026-03-16T02:01:38Z

I tried it again after doing a git pull, then restarted HA:

Logger: custom_components.gree_custom.config_flow
Source: custom_components/gree_custom/config_flow.py:686
integration: Gree A/C (documentation)
First occurred: 2:55:50 PM (2 occurrences)
Last logged: 2:56:05 PM

Error while binding
Traceback (most recent call last):
  File "/config/custom_components/gree_custom/aiogree/api.py", line 364, in fetch_result
    received_json = await udp_request_async(
                    ^^^^^^^^^^^^^^^^^^^^^^^^
        ip_addr, port, json_data, max_connection_attempts, timeout
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/config/custom_components/gree_custom/aiogree/api.py", line 294, in udp_request_async
    raise ValueError(
        f"Failed to communicate with device '{ip_addr}:{port}' after {max_retries} attempts"
    )
ValueError: Failed to communicate with device '192.168.22.120:7000' after 2 attempts

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/config/custom_components/gree_custom/aiogree/api.py", line 598, in gree_get_device_key
    result = await get_result_pack(
             ^^^^^^^^^^^^^^^^^^^^^^
    ...<7 lines>...
    )
    ^
  File "/config/custom_components/gree_custom/aiogree/api.py", line 420, in get_result_pack
    data = await fetch_result(
           ^^^^^^^^^^^^^^^^^^^
    ...<7 lines>...
    )
    ^
  File "/config/custom_components/gree_custom/aiogree/api.py", line 368, in fetch_result
    raise ValueError(f"Error communicating with {ip_addr}: {err}") from err
ValueError: Error communicating with 192.168.22.120: Failed to communicate with device '192.168.22.120:7000' after 2 attempts

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/config/custom_components/gree_custom/aiogree/device.py", line 116, in bind_device
    ) = await gree_get_device_key(
        ^^^^^^^^^^^^^^^^^^^^^^^^^^
    ...<7 lines>...
    )
    ^
  File "/config/custom_components/gree_custom/aiogree/api.py", line 629, in gree_get_device_key
    raise ValueError("Error getting device encryption key") from error
ValueError: Error getting device encryption key

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/config/custom_components/gree_custom/config_flow.py", line 686, in async_step_manual_add
    self._discovered_subdevices = await self._devices[
                                  ^^^^^^^^^^^^^^^^^^^^
        _main_device.mac_address_sub
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ].fetch_sub_devices()
    ^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/gree_custom/aiogree/device.py", line 175, in fetch_sub_devices
    await self.bind_device()
  File "/config/custom_components/gree_custom/aiogree/device.py", line 127, in bind_device
    raise GreeDeviceNotBoundError("Unable to obtain device key") from e
custom_components.gree_custom.aiogree.device.GreeDeviceNotBoundError: Unable to obtain device key

I tried initially to autodiscover. That failed, so I used the output from the gree-api-client:

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun home-assistant (no readiness notification)
s6-rc: info: service legacy-services successfully started
2026-03-16 14:53:13.806 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration ac_infinity which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2026-03-16 14:53:13.807 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration gree_custom which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2026-03-16 14:53:13.807 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration intesishome which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2026-03-16 14:53:13.807 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2026-03-16 14:55:16.084 DEBUG (MainThread) [custom_components.gree_custom.config_flow] Found broadcast addresses from HA: ['255.255.255.255']
2026-03-16 14:55:16.085 DEBUG (MainThread) [custom_components.gree_custom.aiogree.api] Sending broadcast to 255.255.255.255
2026-03-16 14:55:16.085 DEBUG (MainThread) [custom_components.gree_custom.aiogree.api] Sending broadcast to 192.168.255.255
2026-03-16 14:55:16.086 DEBUG (MainThread) [custom_components.gree_custom.aiogree.api] Sending broadcast to 10.255.255.255
2026-03-16 14:55:16.086 DEBUG (MainThread) [custom_components.gree_custom.aiogree.api] Sending broadcast to 172.31.255.255
2026-03-16 14:55:16.087 DEBUG (MainThread) [custom_components.gree_custom.aiogree.api] Sent broadcast packets, waiting for replies...
2026-03-16 14:55:21.092 DEBUG (MainThread) [custom_components.gree_custom.aiogree.api] Got 0 responses in 5 seconds: {}
2026-03-16 14:55:41.165 INFO (MainThread) [custom_components.gree_custom.aiogree.device] Initialize the GREE Device API for: 580d0d3474fc (192.168.22.120:7000)
2026-03-16 14:55:41.165 DEBUG (MainThread) [custom_components.gree_custom.aiogree.device] Version: None, Key: cJS3J[omitted]
2026-03-16 14:55:41.165 DEBUG (MainThread) [custom_components.gree_custom.aiogree.device] Trying to get subdevices
2026-03-16 14:55:41.165 INFO (MainThread) [custom_components.gree_custom.aiogree.api] Trying to retrieve device encryption key v1
2026-03-16 14:55:41.167 DEBUG (MainThread) [custom_components.gree_custom.aiogree.api] Bind Pack: {"mac": "580d0d3474fc", "t": "bind", "uid": 0}
2026-03-16 14:55:41.173 DEBUG (MainThread) [custom_components.gree_custom.aiogree.api] Payload: {'cid': 'app', 'i': 1, 'pack': 'Fo0NJVLzyhX4Qh3bOqWhT4QPXnuPS0a5W/exMkAoHz3IfE1fYVsWM5kifDBw/LN1', 't': 'pack', 'tcid': '580d0d3474fc', 'uid': 0}
2026-03-16 14:55:41.173 DEBUG (MainThread) [custom_components.gree_custom.aiogree.api] Fetching data from 192.168.22.120
2026-03-16 14:55:43.175 WARNING (MainThread) [custom_components.gree_custom.aiogree.api] Error communicating with 192.168.22.120. Attempt 1/2 |
2026-03-16 14:55:45.679 WARNING (MainThread) [custom_components.gree_custom.aiogree.api] Error communicating with 192.168.22.120. Attempt 2/2 |
2026-03-16 14:55:45.680 ERROR (MainThread) [custom_components.gree_custom.aiogree.api] Error getting device encryption key with version 1:
Error communicating with 192.168.22.120: Failed to communicate with device '192.168.22.120:7000' after 2 attempts
2026-03-16 14:55:45.680 INFO (MainThread) [custom_components.gree_custom.aiogree.api] Trying to retrieve device encryption key v2
2026-03-16 14:55:45.680 DEBUG (MainThread) [custom_components.gree_custom.aiogree.api] Bind Pack: {"cid": "580d0d3474fc", "mac": "580d0d3474fc", "t": "bind", "uid": 0}
2026-03-16 14:55:45.694 DEBUG (MainThread) [custom_components.gree_custom.aiogree.api] Payload: {'cid': 'app', 'i': 1, 'pack': 'Jtod3XIt89Dxs8SHPnkRBJt2vIVBwAvmIgk1XvjRhurELj0L3QVtft+hse+GRsWcl72qEoTtZbgS4JbKYrud0qPFjVyn', 't': 'pack', 'tcid': '580d0d3474fc', 'uid': 0, 'tag': 'qKWestnLPk4VGayIhFfpRg=='}
2026-03-16 14:55:45.694 DEBUG (MainThread) [custom_components.gree_custom.aiogree.api] Fetching data from 192.168.22.120
2026-03-16 14:55:47.697 WARNING (MainThread) [custom_components.gree_custom.aiogree.api] Error communicating with 192.168.22.120. Attempt 1/2 |
2026-03-16 14:55:50.200 WARNING (MainThread) [custom_components.gree_custom.aiogree.api] Error communicating with 192.168.22.120. Attempt 2/2 |
2026-03-16 14:55:50.201 ERROR (MainThread) [custom_components.gree_custom.aiogree.api] Error getting device encryption key with version 2:
Error communicating with 192.168.22.120: Failed to communicate with device '192.168.22.120:7000' after 2 attempts
2026-03-16 14:55:50.201 ERROR (MainThread) [custom_components.gree_custom.config_flow] Error while binding
Traceback (most recent call last):
  File "/config/custom_components/gree_custom/aiogree/api.py", line 364, in fetch_result
    received_json = await udp_request_async(
                    ^^^^^^^^^^^^^^^^^^^^^^^^
        ip_addr, port, json_data, max_connection_attempts, timeout
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/config/custom_components/gree_custom/aiogree/api.py", line 294, in udp_request_async
    raise ValueError(
        f"Failed to communicate with device '{ip_addr}:{port}' after {max_retries} attempts"
    )
ValueError: Failed to communicate with device '192.168.22.120:7000' after 2 attempts

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/config/custom_components/gree_custom/aiogree/api.py", line 598, in gree_get_device_key
    result = await get_result_pack(
             ^^^^^^^^^^^^^^^^^^^^^^
    ...<7 lines>...
    )
    ^
  File "/config/custom_components/gree_custom/aiogree/api.py", line 420, in get_result_pack
    data = await fetch_result(
           ^^^^^^^^^^^^^^^^^^^
    ...<7 lines>...
    )
    ^
  File "/config/custom_components/gree_custom/aiogree/api.py", line 368, in fetch_result
    raise ValueError(f"Error communicating with {ip_addr}: {err}") from err
ValueError: Error communicating with 192.168.22.120: Failed to communicate with device '192.168.22.120:7000' after 2 attempts

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/config/custom_components/gree_custom/aiogree/device.py", line 116, in bind_device
    ) = await gree_get_device_key(
        ^^^^^^^^^^^^^^^^^^^^^^^^^^
    ...<7 lines>...
    )
    ^
  File "/config/custom_components/gree_custom/aiogree/api.py", line 629, in gree_get_device_key
    raise ValueError("Error getting device encryption key") from error
ValueError: Error getting device encryption key

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/config/custom_components/gree_custom/config_flow.py", line 686, in async_step_manual_add
    self._discovered_subdevices = await self._devices[
                                  ^^^^^^^^^^^^^^^^^^^^
        _main_device.mac_address_sub
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ].fetch_sub_devices()
    ^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/gree_custom/aiogree/device.py", line 175, in fetch_sub_devices
    await self.bind_device()
  File "/config/custom_components/gree_custom/aiogree/device.py", line 127, in bind_device
    raise GreeDeviceNotBoundError("Unable to obtain device key") from e
custom_components.gree_custom.aiogree.device.GreeDeviceNotBoundError: Unable to obtain device key
2026-03-16 14:55:50.206 DEBUG (MainThread) [custom_components.gree_custom.config_flow] Building main schema with previous values: {'host': '192.168.22.120', 'mac': '580d0d3474fc', 'advanced': {'port': 7000, 'encryption_version': 'Auto-Detect', 'encryption_key': 'cJS3JDim581t3914', 'uid': 0, 'disable_available_check': False, 'max_online_attempts': 5, 'timeout': 10}}
2026-03-16 14:55:56.078 INFO (MainThread) [custom_components.gree_custom.aiogree.device] Initialize the GREE Device API for: 580d0d3474fc (192.168.22.120:7000)
2026-03-16 14:55:56.078 DEBUG (MainThread) [custom_components.gree_custom.aiogree.device] Version: None, Key: cJS3J[omitted]
2026-03-16 14:55:56.078 DEBUG (MainThread) [custom_components.gree_custom.aiogree.device] Trying to get subdevices
2026-03-16 14:55:56.078 INFO (MainThread) [custom_components.gree_custom.aiogree.api] Trying to retrieve device encryption key v1
2026-03-16 14:55:56.079 DEBUG (MainThread) [custom_components.gree_custom.aiogree.api] Bind Pack: {"mac": "580d0d3474fc", "t": "bind", "uid": 0}
2026-03-16 14:55:56.079 DEBUG (MainThread) [custom_components.gree_custom.aiogree.api] Payload: {'cid': 'app', 'i': 1, 'pack': 'Fo0NJVLzyhX4Qh3bOqWhT4QPXnuPS0a5W/exMkAoHz3IfE1fYVsWM5kifDBw/LN1', 't': 'pack', 'tcid': '580d0d3474fc', 'uid': 0}
2026-03-16 14:55:56.079 DEBUG (MainThread) [custom_components.gree_custom.aiogree.api] Fetching data from 192.168.22.120
2026-03-16 14:55:58.083 WARNING (MainThread) [custom_components.gree_custom.aiogree.api] Error communicating with 192.168.22.120. Attempt 1/2 |
2026-03-16 14:56:00.586 WARNING (MainThread) [custom_components.gree_custom.aiogree.api] Error communicating with 192.168.22.120. Attempt 2/2 |
2026-03-16 14:56:00.587 ERROR (MainThread) [custom_components.gree_custom.aiogree.api] Error getting device encryption key with version 1:
Error communicating with 192.168.22.120: Failed to communicate with device '192.168.22.120:7000' after 2 attempts
2026-03-16 14:56:00.587 INFO (MainThread) [custom_components.gree_custom.aiogree.api] Trying to retrieve device encryption key v2
2026-03-16 14:56:00.587 DEBUG (MainThread) [custom_components.gree_custom.aiogree.api] Bind Pack: {"cid": "580d0d3474fc", "mac": "580d0d3474fc", "t": "bind", "uid": 0}
2026-03-16 14:56:00.589 DEBUG (MainThread) [custom_components.gree_custom.aiogree.api] Payload: {'cid': 'app', 'i': 1, 'pack': 'Jtod3XIt89Dxs8SHPnkRBJt2vIVBwAvmIgk1XvjRhurELj0L3QVtft+hse+GRsWcl72qEoTtZbgS4JbKYrud0qPFjVyn', 't': 'pack', 'tcid': '580d0d3474fc', 'uid': 0, 'tag': 'qKWestnLPk4VGayIhFfpRg=='}
2026-03-16 14:56:00.590 DEBUG (MainThread) [custom_components.gree_custom.aiogree.api] Fetching data from 192.168.22.120
2026-03-16 14:56:02.594 WARNING (MainThread) [custom_components.gree_custom.aiogree.api] Error communicating with 192.168.22.120. Attempt 1/2 |
2026-03-16 14:56:05.099 WARNING (MainThread) [custom_components.gree_custom.aiogree.api] Error communicating with 192.168.22.120. Attempt 2/2 |
2026-03-16 14:56:05.100 ERROR (MainThread) [custom_components.gree_custom.aiogree.api] Error getting device encryption key with version 2:
Error communicating with 192.168.22.120: Failed to communicate with device '192.168.22.120:7000' after 2 attempts
2026-03-16 14:56:05.100 ERROR (MainThread) [custom_components.gree_custom.config_flow] Error while binding
Traceback (most recent call last):
  File "/config/custom_components/gree_custom/aiogree/api.py", line 364, in fetch_result
    received_json = await udp_request_async(
                    ^^^^^^^^^^^^^^^^^^^^^^^^
        ip_addr, port, json_data, max_connection_attempts, timeout
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/config/custom_components/gree_custom/aiogree/api.py", line 294, in udp_request_async
    raise ValueError(
        f"Failed to communicate with device '{ip_addr}:{port}' after {max_retries} attempts"
    )
ValueError: Failed to communicate with device '192.168.22.120:7000' after 2 attempts

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/config/custom_components/gree_custom/aiogree/api.py", line 598, in gree_get_device_key
    result = await get_result_pack(
             ^^^^^^^^^^^^^^^^^^^^^^
    ...<7 lines>...
    )
    ^
  File "/config/custom_components/gree_custom/aiogree/api.py", line 420, in get_result_pack
    data = await fetch_result(
           ^^^^^^^^^^^^^^^^^^^
    ...<7 lines>...
    )
    ^
  File "/config/custom_components/gree_custom/aiogree/api.py", line 368, in fetch_result
    raise ValueError(f"Error communicating with {ip_addr}: {err}") from err
ValueError: Error communicating with 192.168.22.120: Failed to communicate with device '192.168.22.120:7000' after 2 attempts

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/config/custom_components/gree_custom/aiogree/device.py", line 116, in bind_device
    ) = await gree_get_device_key(
        ^^^^^^^^^^^^^^^^^^^^^^^^^^
    ...<7 lines>...
    )
    ^
  File "/config/custom_components/gree_custom/aiogree/api.py", line 629, in gree_get_device_key
    raise ValueError("Error getting device encryption key") from error
ValueError: Error getting device encryption key

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/config/custom_components/gree_custom/config_flow.py", line 686, in async_step_manual_add
    self._discovered_subdevices = await self._devices[
                                  ^^^^^^^^^^^^^^^^^^^^
        _main_device.mac_address_sub
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ].fetch_sub_devices()
    ^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/gree_custom/aiogree/device.py", line 175, in fetch_sub_devices
    await self.bind_device()
  File "/config/custom_components/gree_custom/aiogree/device.py", line 127, in bind_device
    raise GreeDeviceNotBoundError("Unable to obtain device key") from e
custom_components.gree_custom.aiogree.device.GreeDeviceNotBoundError: Unable to obtain device key
2026-03-16 14:56:05.105 DEBUG (MainThread) [custom_components.gree_custom.config_flow] Building main schema with previous values: {'host': '192.168.22.120', 'mac': '580d0d3474fc', 'advanced': {'port': 7000, 'encryption_version': 'Auto-Detect', 'encryption_key': 'cJS3JDim581t3914', 'uid': 0, 'disable_available_check': True, 'max_online_attempts': 5, 'timeout': 10}}

p-monteiro · 2026-03-16T09:12:07Z

@ChillingSilence I suspected it was happening, but you are NOT on the latest commit. Try updating to the latest commit on the correct branch (0468123)

If you are on it, check the folders, delete the 2 pycache folders inside the integration and restart HA

p-monteiro added 23 commits September 23, 2025 20:24

Add support for external temperature and humidity sensors

187ef3c

Make manifest compliant with HA requirements

1188118

Cleanup old code in preparation for backporting features

c71392f

Use encryption version as enum and cleanup

73ebfe2

Multiple config_flow enhancements:

e0d9886

- Move consts around - Proper error report on config_flow - Proper translations on config_flow - Configuration of timeout - Fetch device info during binding

Listen to external sensor states if using them

74809e9

Try to fix external entities not being unselectable

f088882

Reimplement Auto Light and X-Fan

9a78e8f

Remove timeout from the coordinator

29cbd31

Feature: Restore entity states configurable by user

97201de

Change set_fan debug

03b9597

Fix auto x-fan logic

98ce923

Improve Temperature Units select and restore state

5425b80

Realign with main branch for easier migrations

8686f44

Add API support for device discovery

4f0876b

Gree API: Reuse pack decryption code

ce79013

Fix translations

3adef52

Fix imports

f779529

Bring back add device by discovery

3a9f0b2

Fix Temperature Unit selector

034c93d

Fix current temperature units in Climate Entity

6ff856d

Request a update when system units are changed

4622516

p-monteiro added 3 commits September 24, 2025 23:41

Implement RestoreEntity in GreeClimate

fd5a17e

Use _attr_ instead of the cached property

e013a19

Implement availability check based on coordinator data update success…

58856aa

… and device comunication state

Improve README

6181526

p-monteiro added 3 commits January 20, 2026 22:59

Add missing manifest iot_class and dependencies

0b1cef1

Updated pt Translation

58c2518

Sort manifest keys

88d772e

p-monteiro added 5 commits March 2, 2026 16:24

Ignore and log case when temperature is set with AUTO mode

1471b1c

Abstract the encryption to a Cipher class

2c6d6d4

Inspired by github.com/cmroche/greeclimate

Add suport for diagnostics

9d2b313

Add custom branding

a6b64ef

General cleanup

1e630dd

Fix Beeper on newer firmwares

3581ec0

Fix: Don't change config entry on diagnostics download

f52c4ac

Improve error handling and file organization

0468123

Conversation

p-monteiro commented Sep 23, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

p-monteiro commented Sep 24, 2025

Uh oh!

domialex commented Sep 26, 2025

Uh oh!

p-monteiro commented Sep 26, 2025

Uh oh!

rudizl commented Jan 21, 2026

Uh oh!

chkr1011 commented Jan 21, 2026

Uh oh!

p-monteiro commented Jan 21, 2026

Uh oh!

chkr1011 commented Jan 21, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

p-monteiro commented Jan 21, 2026

Uh oh!

rudizl commented Jan 21, 2026

Uh oh!

p-monteiro commented Mar 12, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

p-monteiro commented Mar 12, 2026

Uh oh!

RobHofmann commented Mar 13, 2026

Uh oh!

p-monteiro commented Mar 13, 2026

Uh oh!

domialex commented Mar 14, 2026

Uh oh!

RobHofmann commented Mar 14, 2026

Uh oh!

p-monteiro commented Mar 14, 2026

Uh oh!

ChillingSilence commented Mar 15, 2026

Uh oh!

p-monteiro commented Mar 15, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

ChillingSilence commented Mar 15, 2026

Uh oh!

p-monteiro commented Mar 15, 2026

Uh oh!

ChillingSilence commented Mar 16, 2026

Uh oh!

p-monteiro commented Mar 16, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

7 participants

p-monteiro commented Sep 23, 2025 •

edited

Loading

chkr1011 commented Jan 21, 2026 •

edited

Loading

p-monteiro commented Mar 12, 2026 •

edited

Loading

p-monteiro commented Mar 15, 2026 •

edited

Loading