Gree integration - devices become unavailable but not on the native app

[doppiaemme]

The problem

Gree devices often become unavailable and unreachable, however the same devices appear fine on the native Gree app.
It happens randomly and on different devices.

For some reasons it seems the app has the capability to still find them while the integration doesn't.

Note: both HA and devices are on the same VLAN

What version of Home Assistant Core has the issue?

2022.3.8

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Supervised

Integration causing the issue

Gree

Link to integration documentation on our website

https://www.home-assistant.io/integrations/gree/

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

2022-04-04 12:47:02 ERROR (MainThread) [homeassistant.components.gree.bridge] Timeout trying to bind to gree device: Device: XXXXXX @ 192.168XXXXXX (mac: XXXXXXXXXXX)
2022-04-04 12:48:22 ERROR (MainThread) [homeassistant.components.gree.bridge] Error fetching gree-XXXXX data: Device gree-XXXXXX is unavailable

Additional information

No response

[probot-home-assistant]

gree documentation
gree source
_{^{(message by IssueLinks)}}

[probot-home-assistant]

Hey there @cmroche, mind taking a look at this issue as it has been labeled with an integration (gree) you are listed as a code owner for? Thanks!
_{^{(message by CodeOwnersMention)}}

[csubakk]

Same problem.

6 gree air conditioners, they was installed one year ago, randomly 1/2/3 unavailable... All of them are okay on the mobile phone Gree app.

Quick solution, but for 1-2-3... days: Restart the integration

[mfriik]

Yup same here, initially I thought that something was wrong with the wifi connection. In my case restarting the integration works for couple of minutes and the device becomes unavailable again.

[cmroche]

It is possible that the devices’ ip addresses are changing when it become unavailable?

Also could you enable debug logging for homeassistant.components.gree and greeclimate both and attach logs please.

[mfriik]

Thanks for response! Assumed it might be related, so I assigned static IP to my AC. I had to leave the house for a while but when returned I re-checked it and it seems to be working fine again at least for now ;). But it seemed as if this happened randomly and not when the AC was reassigned new IP

[doppiaemme]

Hi, my IP are all static (or better, they are reserved on the DHCP server as I couldn't find a way to set static addresses on the Gree app).

rebooting HA to enable the logs, now i have 5 units out of 7 unavailable:

here the logs. please note that the two devices which are available are the only ones in the file where a Key is exchanged!
gree (1).txt

[csubakk]

2 MAC adresses on gree climate devices???

I have a TPLINK deco mesh system on the pension. All devices are renamed (ex: tasmota room 01, ot climate room 01...), and all with own IP from the start. I discovered some ESP devices on the network. For example ESP_9E302D

After a google search: tomikaa87/gree-remote#16

For now: blakclisted (3 from 6). And waiting.

Can You check your network???

[reyo]

Hi! Joining in, same problem, one Gree AC (Cooper & Hunter Supreme) unavailable. Has static IP (DHCP reservation as this is the only go to choice), working on the EWPE app. Checked for device firmware update using the EWPE app and got an update from v3.71 to v3.72.

Network is Ubiquiti, nearest AP is U6-Lite. The AC is locket to that AP. Signal strenght is stable 100%.

I tried to fix the availability via integration deletion, but now can't add it back because:

[Idan37S]

Is it possible to add support for adding gree devices by entering manual IP instead of discovery?
The discovery doesn't work for me and I have no option but to use the custom integration of gree (which works with manual IP) instead of the built-in integration.

[reyo]

Is it possible to add adding gree devices by entering manual ip instead of discovery? The discovery doesn't work for me and I have no option but to use the custom integration of gree (which works with manual ip) instead of the built-in integration.

Same. The custom one works flawlessy with manual IP.

[doppiaemme]

Is it possible to add adding gree devices by entering manual ip instead of discovery? The discovery doesn't work for me and I have no option but to use the custom integration of gree (which works with manual ip) instead of the built-in integration.

Same. The custom one works flawlessy with manual IP.

But I had the “unavailable” issue even whe le I used the custom component.
I think that may be a solution for discovery but wasn’t behaving any better than now

[Idan37S]

Is it possible to add adding gree devices by entering manual ip instead of discovery? The discovery doesn't work for me and I have no option but to use the custom integration of gree (which works with manual ip) instead of the built-in integration.

Same. The custom one works flawlessy with manual IP.

But I had the “unavailable” issue even whe le I used the custom component. I think that may be a solution for discovery but wasn’t behaving any better than now

The unavailable is a different issue,
For me it was resolved by setting a Static IP and from then it was pretty much ok.
Anyway, i think it's better to have 2 of those options (discovery, manual ip) in the built-in integration as for some the discovery just doesn't work.

[doppiaemme]

Ah ok so it doesn’t have anything to do with the topic of this thread then. As I have static IPs but they are often unavailable, that is not a solution for me.
Regarding failed auto discovery 99% of the times is the local network (different VLANs or some network equipment stopping mDNS etc)

[cmroche]

It's something I would like to do sooner then later, support manually adding devices with this integration, however it's just a matter of when I will have time time to tackle this.

[meldarionqeusse]

This has been happening to me for over a year but I was still figuring out Home assistant at the time. At first it used to happen randomly on all my Gree devices I used to go into the Gree app click on each one and then they would start appearing on Home assistant. Eventually I fixed the IP address of the devices and the system was very stable.

However, I have noticed that devices become unavailable if: I reboot my server, power is lost or I restart my home assistant. The strange thing is that out of 5 gree devices 4 usually connect immediately but one particular device which is the closest to my main router/modem does not connect no matter how many times I reload the integration, go into the gree app or restart home assistant. The device still works on the gree app however which is strange. The only "solution" which I found is to restart my router/modem and reload the integration once everything has booted.

[cmroche]

@meldarionqeusse Someone else mentioned the possibility of using two mac addresses, possible in your case?

[meldarionqeusse]

I looked a bit into I don't think it is using a different MAC address but I am not convinced cause I noticed that in my router it shows that it is connected via ethernet when it works and when it becomes unavailable it changes to wireless

[csubakk]

I looked a bit into I don't think it is using a different MAC address but I am not convinced cause I noticed that in my router it shows that it is connected via ethernet when it works and when it becomes unavailable it changes to wireless

My Tplink Deco mesh system: DHCP settings: Gree, Room 13 MAC: F4-91-1E-75-XX-XX IP is reserved to 192.168.XX.113. On the devices list for this device, for this MAC is assigned the 192.168.XX.121. a total of 30 devices are configured this way, 6 of which are GREE, but I only discovered this bug in this one.

i changed the dhcp reservation settings but there are only differences for this device

[Idan37S]

In the meantime for anyone who the auto discovery doesn't work and wants a workaround,
I added an hardcoded code for my use case:
I added await self.send({"t": "scan"}, ("192.168.30.21", 7000)) in the function search_on_interface the file discovery.py,
And now it works for me, though i will have a problem when updating and i will need to re-add this code again probably.

I hope manual ip support will get added soon as it may fix a lot of issues for a lot of people.

[jodewee]

@Idan37S where do i find the discovery.py file?

[Idan37S]

@Idan37S where do i find the discovery.py file?

Mine is at: ./usr/local/lib/python3.9/site-packages/greeclimate/discovery.py
I'm using the HA container installation.
Depending on your installation type of HA,
You will have to get in the files of HA itself and change it.

[SalemCat]

How to add device if integration does not recognise it even it’s connected to wifi and native app?

[arvaisandor1968]

Hi. from last change i have a problem with this integration.

Error fetching gree-1e8e79ec data: Device gree-1e8e79ec is unavailable
21:11:02 – (HIBA) Gree Climate - először előfordult: 20:52:22, később 9 alkalommal újra megjelent
Device is unavailable: gree-1e8e79ec (Device: 1e8e79ec @ 192.168.1.69:7000 (mac: f4911e8e79ec))
21:11:02 – (FIGYELMEZTETÉS) Gree Climate - először előfordult: 20:52:22, később 9 alkalommal újra megjelent
Timeout send state update to: gree-1e8e79ec (Device: 1e8e79ec @ 192.168.1.69:7000 (mac: f4911e8e79ec))
21:01:42 – (FIGYELMEZTETÉS) Gree Climate

[kingtao1024]

I also have the same problem, which has plagued me for more than a year. Before, I solved the problem through various restarts. Now I have a device that has become completely unavailable. Now I need to look at the log to solve this problem.

[arvaisandor1968]

Hi! It's the part of log. Maybe help for you solve the problem.

2022-05-25 08:04:11 INFO (MainThread) [custom_components.xiaomi_miot.sensor] Get xiaomi message for 6485819471 failed: {'code': 0, 'message': 'ok', 'result': {'messages': None}}
2022-05-25 08:04:12 INFO (MainThread) [greeclimate.device] Starting device binding to Device: 1e8e79ec @ 192.168.1.69:7000 (mac: f4911e8e79ec)
2022-05-25 08:04:22 WARNING (MainThread) [homeassistant.components.gree.bridge] Device is unavailable: gree-1e8e79ec (Device: 1e8e79ec @ 192.168.1.69:7000 (mac: f4911e8e79ec))
2022-05-25 08:04:22 ERROR (MainThread) [homeassistant.components.gree.bridge] Error fetching gree-1e8e79ec data: Device gree-1e8e79ec is unavailable
2022-05-25 08:04:26 INFO (MainThread) [custom_components.xiaomi_miot.sensor] Get xiaomi message for 6485819471 failed: {'code': 0, 'message': 'ok', 'result': {'messages': None}}
2022-05-25 08:04:41 INFO (MainThread) [custom_components.xiaomi_miot.sensor] Get xiaomi message for 6485819471 failed: {'code': 0, 'message': 'ok', 'result': {'messages': None}}
2022-05-25 08:04:56 INFO (MainThread) [custom_components.xiaomi_miot.sensor] Get xiaomi message for 6485819471 failed: {'code': 0, 'message': 'ok', 'result': {'messages': None}}
2022-05-25 08:05:06 WARNING (MainThread) [homeassistant.components.dlna_dms] Failed connecting to recently alive device at http://[fe80::14af:2ac0:ac68:4f63%3]:2869/upnphost/udhisapi.dll?content=uuid:940d2c00-4f35-48a7-9c1f-3b23ccecb982: UpnpResponseError('Did not receive HTTP 200 but 400')
2022-05-25 08:05:11 INFO (MainThread) [custom_components.xiaomi_miot.sensor] Get xiaomi message for 6485819471 failed: {'code': 0, 'message': 'ok', 'result': {'messages': None}}
2022-05-25 08:05:22 INFO (MainThread) [greeclimate.device] Starting device binding to Device: 1e8e79ec @ 192.168.1.69:7000 (mac: f4911e8e79ec)
2022-05-25 08:05:26 INFO (MainThread) [custom_components.xiaomi_miot.sensor] Get xiaomi message for 6485819471 failed: {'code': 0, 'message': 'ok', 'result': {'messages': None}}
2022-05-25 08:05:32 INFO (MainThread) [homeassistant.components.gree.bridge] Fetching gree-1e8e79ec data recovered
2022-05-25 08:05:41 INFO (MainThread) [custom_components.xiaomi_miot.sensor] Get xiaomi message for 6485819471 failed: {'code': 0, 'message': 'ok', 'result': {'messages': None}}
2022-05-25 08:05:51 INFO (MainThread) [greeclimate.discovery] Scanning for Gree devices ...
2022-05-25 08:05:56 INFO (MainThread) [custom_components.xiaomi_miot.sensor] Get xiaomi message for 6485819471 failed: {'code': 0, 'message': 'ok', 'result': {'messages': None}}
2022-05-25 08:06:11 INFO (MainThread) [custom_components.xiaomi_miot.sensor] Get xiaomi message for 6485819471 failed: {'code': 0, 'message': 'ok', 'result': {'messages': None}}
2022-05-25 08:06:26 INFO (MainThread) [custom_components.xiaomi_miot.sensor] Get xiaomi message for 6485819471 failed: {'code': 0, 'message': 'ok', 'result': {'messages': None}}
2022-05-25 08:06:32 INFO (MainThread) [greeclimate.device] Starting device binding to Device: 1e8e79ec @ 192.168.1.69:7000 (mac: f4911e8e79ec)
2022-05-25 08:06:41 INFO (MainThread) [custom_components.xiaomi_miot.sensor] Get xiaomi message for 6485819471 failed: {'code': 0, 'message': 'ok', 'result': {'messages': None}}
2022-05-25 08:06:42 WARNING (MainThread) [homeassistant.components.gree.bridge] Device is unavailable: gree-1e8e79ec (Device: 1e8e79ec @ 192.168.1.69:7000 (mac: f4911e8e79ec))
2022-05-25 08:06:42 ERROR (MainThread) [homeassistant.components.gree.bridge] Error fetching gree-1e8e79ec data: Device gree-1e8e79ec is unavailable
2022-05-25 08:06:56 INFO (MainThread) [custom_components.xiaomi_miot.sensor] Get xiaomi message for 6485819471 failed: {'code': 0, 'message': 'ok', 'result': {'messages': None}}
2022-05-25 08:07:11 INFO (MainThread) [custom_components.xiaomi_miot.sensor] Get xiaomi message for 6485819471 failed: {'code': 0, 'message': 'ok', 'result': {'messages': None}}
2022-05-25 08:07:26 INFO (MainThread) [custom_components.xiaomi_miot.sensor] Get xiaomi message for 6485819471 failed: {'code': 0, 'message': 'ok', 'result': {'messages': None}}
2022-05-25 08:07:41 INFO (MainThread) [custom_components.xiaomi_miot.sensor] Get xiaomi message for 6485819471 failed: {'code': 0, 'message': 'ok', 'result': {'messages': None}}
2022-05-25 08:07:42 INFO (MainThread) [greeclimate.device] Starting device binding to Device: 1e8e79ec @ 192.168.1.69:7000 (mac: f4911e8e79ec)
2022-05-25 08:07:52 INFO (MainThread) [homeassistant.components.gree.bridge] Fetching gree-1e8e79ec data recovered
2022-05-25 08:07:56 INFO (MainThread) [custom_components.xiaomi_miot.sensor] Get xiaomi message for 6485819471 failed: {'code': 0, 'message': 'ok', 'result': {'messages': None}}
2022-05-25 08:08:11 INFO (MainThread) [custom_components.xiaomi_miot.sensor] Get xiaomi message for 6485819471 failed: {'code': 0, 'message': 'ok', 'result': {'messages': None}}
2022-05-25 08:08:26 INFO (MainThread) [custom_components.xiaomi_miot.sensor] Get xiaomi message for 6485819471 failed: {'code': 0, 'message': 'ok', 'result': {'messages': None}}
2022-05-25 08:08:41 INFO (MainThread) [custom_components.xiaomi_miot.sensor] Get xiaomi message for 6485819471 failed: {'code': 0, 'message': 'ok', 'result': {'messages': None}}
2022-05-25 08:08:52 INFO (MainThread) [greeclimate.device] Starting device binding to Device: 1e8e79ec @ 192.168.1.69:7000 (mac: f4911e8e79ec)
2022-05-25 08:08:56 INFO (MainThread) [custom_components.xiaomi_miot.sensor] Get xiaomi message for 6485819471 failed: {'code': 0, 'message': 'ok', 'result': {'messages': None}}
2022-05-25 08:09:02 WARNING (MainThread) [homeassistant.components.gree.bridge] Device is unavailable: gree-1e8e79ec (Device: 1e8e79ec @ 192.168.1.69:7000 (mac: f4911e8e79ec))
2022-05-25 08:09:02 ERROR (MainThread) [homeassistant.components.gree.bridge] Error fetching gree-1e8e79ec data: Device gree-1e8e79ec is unavailable
2022-05-25 08:09:11 INFO (MainThread) [custom_components.xiaomi_miot.sensor] Get xiaomi message for 6485819471 failed: {'code': 0, 'message': 'ok', 'result': {'messages': None}}
2022-05-25 08:09:26 INFO (MainThread) [custom_components.xiaomi_miot.sensor] Get xiaomi message for 6485819471 failed: {'code': 0, 'message': 'ok', 'result': {'messages': None}}
2022-05-25 08:09:41 INFO (MainThread) [custom_components.xiaomi_miot.sensor] Get xiaomi message for 6485819471 failed: {'code': 0, 'message': 'ok', 'result': {'messages': None}}
2022-05-25 08:09:56 INFO (MainThread) [custom_components.xiaomi_miot.sensor] Get xiaomi message for 6485819471 failed: {'code': 0, 'message': 'ok', 'result': {'messages': None}}
2022-05-25 08:10:02 INFO (MainThread) [greeclimate.device] Starting device binding to Device: 1e8e79ec @ 192.168.1.69:7000 (mac: f4911e8e79ec)
2022-05-25 08:10:11 INFO (MainThread) [custom_components.xiaomi_miot.sensor] Get xiaomi message for 6485819471 failed: {'code': 0, 'message': 'ok', 'result': {'messages': None}}
2022-05-25 08:10:12 INFO (MainThread) [homeassistant.components.gree.bridge] Fetching gree-1e8e79ec data recovered
2022-05-25 08:10:21 WARNING (MainThread) [homeassistant.components.dlna_dms] Failed connecting to recently alive device at http://192.168.1.76:2869/upnphost/udhisapi.dll?content=uuid:940d2c00-4f35-48a7-9c1f-3b23ccecb982: UpnpResponseError('Error during async_call(), status: 500, body: ')
2022-05-25 08:10:26 INFO (MainThread) [custom_components.xiaomi_miot.sensor] Get xiaomi message for 6485819471 failed: {'code': 0, 'message': 'ok', 'result': {'messages': None}}
2022-05-25 08:10:29 WARNING (MainThread) [homeassistant.components.dlna_dms] Failed connecting to recently alive device at http://[fe80::14af:2ac0:ac68:4f63%3]:2869/upnphost/udhisapi.dll?content=uuid:940d2c00-4f35-48a7-9c1f-3b23ccecb982: UpnpResponseError('Did not receive HTTP 200 but 400')
2022-05-25 08:10:41 INFO (MainThread) [custom_components.xiaomi_miot.sensor] Get xiaomi message for 6485819471 failed: {'code': 0, 'message': 'ok', 'result': {'messages': None}}
2022-05-25 08:10:51 INFO (MainThread) [greeclimate.discovery] Scanning for Gree devices ...
2022-05-25 08:10:56 INFO (MainThread) [custom_components.xiaomi_miot.sensor] Get xiaomi message for 6485819471 failed: {'code': 0, 'message': 'ok', 'result': {'messages': None}}
2022-05-25 08:11:11 INFO (MainThread) [custom_components.xiaomi_miot.sensor] Get xiaomi message for 6485819471 failed: {'code': 0, 'message': 'ok', 'result': {'messages': None}}
2022-05-25 08:11:12 INFO (MainThread) [greeclimate.device] Starting device binding to Device: 1e8e79ec @ 192.168.1.69:7000 (mac: f4911e8e79ec)
2022-05-25 08:11:22 WARNING (MainThread) [homeassistant.components.gree.bridge] Device is unavailable: gree-1e8e79ec (Device: 1e8e79ec @ 192.168.1.69:7000 (mac: f4911e8e79ec))
2022-05-25 08:11:22 ERROR (MainThread) [homeassistant.components.gree.bridge] Error fetching gree-1e8e79ec data: Device gree-1e8e79ec is unavailable
2022-05-25 08:11:26 INFO (MainThread) [custom_components.xiaomi_miot.sensor] Get xiaomi message for 6485819471 failed: {'code': 0, 'message': 'ok', 'result': {'messages': None}}
2022-05-25 08:11:41 INFO (MainThread) [custom_components.xiaomi_miot.sensor] Get xiaomi message for 6485819471 failed: {'code': 0, 'message': 'ok', 'result': {'messages': None}}
2022-05-25 08:11:56 INFO (MainThread) [custom_components.xiaomi_miot.sensor] Get xiaomi message for 6485819471 failed: {'code': 0, 'message': 'ok', 'result': {'messages': None}}
2022-05-25 08:12:11 INFO (MainThread) [custom_components.xiaomi_miot.sensor] Get xiaomi message for 6485819471 failed: {'code': 0, 'message': 'ok', 'result': {'messages': None}}
2022-05-25 08:12:22 INFO (MainThread) [greeclimate.device] Starting device binding to Device: 1e8e79ec @ 192.168.1.69:7000 (mac: f4911e8e79ec)
2022-05-25 08:12:26 INFO (MainThread) [custom_components.xiaomi_miot.sensor] Get xiaomi message for 6485819471 failed: {'code': 0, 'message': 'ok', 'result': {'messages': None}}
2022-05-25 08:12:32 INFO (MainThread) [homeassistant.components.gree.bridge] Fetching gree-1e8e79ec data recovered
2022-05-25 08:12:41 INFO (MainThread) [custom_components.xiaomi_miot.sensor] Get xiaomi message for 6485819471 failed: {'code': 0, 'message': 'ok', 'result': {'messages': None}}
2022-05-25 08:12:56 INFO (MainThread) [custom_components.xiaomi_miot.sensor] Get xiaomi message for 6485819471 failed: {'code': 0, 'message': 'ok', 'result': {'messages': None}}
2022-05-25 08:13:11 INFO (MainThread) [custom_components.xiaomi_miot.sensor] Get xiaomi message for 6485819471 failed: {'code': 0, 'message': 'ok', 'result': {'messages': None}}
2022-05-25 08:13:26 INFO (MainThread) [custom_components.xiaomi_miot.sensor] Get xiaomi message for 6485819471 failed: {'code': 0, 'message': 'ok', 'result': {'messages': None}}
2022-05-25 08:13:32 INFO (MainThread) [greeclimate.device] Starting device binding to Device: 1e8e79ec @ 192.168.1.69:7000 (mac: f4911e8e79ec)
2022-05-25 08:13:41 INFO (MainThread) [custom_components.xiaomi_miot.sensor] Get xiaomi message for 6485819471 failed: {'code': 0, 'message': 'ok', 'result': {'messages': None}}
2022-05-25 08:13:42 WARNING (MainThread) [homeassistant.components.gree.bridge] Device is unavailable: gree-1e8e79ec (Device: 1e8e79ec @ 192.168.1.69:7000 (mac: f4911e8e79ec))
2022-05-25 08:13:42 ERROR (MainThread) [homeassistant.components.gree.bridge] Error fetching gree-1e8e79ec data: Device gree-1e8e79ec is unavailable
2022-05-25 08:13:47 INFO (MainThread) [zigpy_znp.zigbee.application] ZDO device announce: nwk=0x8F2C, ieee=00:3c:84:ff:fe:ae:bc:0b, capabilities=128
2022-05-25 08:13:47 INFO (MainThread) [zigpy.application] Device 0x8f2c (00:3c:84:ff:fe:ae:bc:0b) joined the network
2022-05-25 08:13:47 INFO (MainThread) [zigpy_znp.zigbee.application] TC device join: ZDO.TCDevInd.Callback(SrcNwk=0x8F2C, SrcIEEE=00:3c:84:ff:fe:ae:bc:0b, ParentNwk=0x0000)
2022-05-25 08:13:47 INFO (MainThread) [zigpy.application] Device 0x8f2c (00:3c:84:ff:fe:ae:bc:0b) joined the network
2022-05-25 08:13:56 INFO (MainThread) [custom_components.xiaomi_miot.sensor] Get xiaomi message for 6485819471 failed: {'code': 0, 'message': 'ok', 'result': {'messages': None}}
2022-05-25 08:14:11 INFO (MainThread) [custom_components.xiaomi_miot.sensor] Get xiaomi message for 6485819471 failed: {'code': 0, 'message': 'ok', 'result': {'messages': None}}
2022-05-25 08:14:26 INFO (MainThread) [custom_components.xiaomi_miot.sensor] Get xiaomi message for 6485819471 failed: {'code': 0, 'message': 'ok', 'result': {'messages': None}}
2022-05-25 08:14:41 INFO (MainThread) [custom_components.xiaomi_miot.sensor] Get xiaomi message for 6485819471 failed: {'code': 0, 'message': 'ok', 'result': {'messages': None}}
2022-05-25 08:14:42 INFO (MainThread) [greeclimate.device] Starting device binding to Device: 1e8e79ec @ 192.168.1.69:7000 (mac: f4911e8e79ec)
2022-05-25 08:14:52 INFO (MainThread) [homeassistant.components.gree.bridge] Fetching gree-1e8e79ec data recovered
2022-05-25 08:14:56 INFO (MainThread) [custom_components.xiaomi_miot.sensor] Get xiaomi message for 6485819471 failed: {'code': 0, 'message': 'ok', 'result': {'messages': None}}
2022-05-25 08:15:11 INFO (MainThread) [custom_components.xiaomi_miot.sensor] Get xiaomi message for 6485819471 failed: {'code': 0, 'message': 'ok', 'result': {'messages': None}}
2022-05-25 08:15:26 INFO (MainThread) [custom_components.xiaomi_miot.sensor] Get xiaomi message for 6485819471 failed: {'code': 0, 'message': 'ok', 'result': {'messages': None}}
2022-05-25 08:15:41 INFO (MainThread) [custom_components.xiaomi_miot.sensor] Get xiaomi message for 6485819471 failed: {'code': 0, 'message': 'ok', 'result': {'messages': None}}
2022-05-25 08:15:51 INFO (MainThread) [greeclimate.discovery] Scanning for Gree devices ...
2022-05-25 08:15:52 INFO (MainThread) [greeclimate.device] Starting device binding to Device: 1e8e79ec @ 192.168.1.69:7000 (mac: f4911e8e79ec)
2022-05-25 08:15:56 INFO (MainThread) [custom_components.xiaomi_miot.sensor] Get xiaomi message for 6485819471 failed: {'code': 0, 'message': 'ok', 'result': {'messages': None}}
2022-05-25 08:16:02 WARNING (MainThread) [homeassistant.components.gree.bridge] Device is unavailable: gree-1e8e79ec (Device: 1e8e79ec @ 192.168.1.69:7000 (mac: f4911e8e79ec))
2022-05-25 08:16:02 ERROR (MainThread) [homeassistant.components.gree.bridge] Error fetching gree-1e8e79ec data: Device gree-1e8e79ec is unavailable
2022-05-25 08:16:11 INFO (MainThread) [custom_components.xiaomi_miot.sensor] Get xiaomi message for 6485819471 failed: {'code': 0, 'message': 'ok', 'result': {'messages': None}}
2022-05-25 08:16:26 INFO (MainThread) [custom_components.xiaomi_miot.sensor] Get xiaomi message for 6485819471 failed: {'code': 0, 'message': 'ok', 'result': {'messages': None}}
2022-05-25 08:16:41 INFO (MainThread) [custom_components.xiaomi_miot.sensor] Get xiaomi message for 6485819471 failed: {'code': 0, 'message': 'ok', 'result': {'messages': None}}
2022-05-25 08:16:56 INFO (MainThread) [custom_components.xiaomi_miot.sensor] Get xiaomi message for 6485819471 failed: {'code': 0, 'message': 'ok', 'result': {'messages': None}}
2022-05-25 08:17:02 INFO (MainThread) [greeclimate.device] Starting device binding to Device: 1e8e79ec @ 192.168.1.69:7000 (mac: f4911e8e79ec)
2022-05-25 08:17:11 INFO (MainThread) [custom_components.xiaomi_miot.sensor] Get xiaomi message for 6485819471 failed: {'code': 0, 'message': 'ok', 'result': {'messages': None}}
2022-05-25 08:17:12 INFO (MainThread) [homeassistant.components.gree.bridge] Fetching gree-1e8e79ec data recovered
2022-05-25 08:17:26 INFO (MainThread) [custom_components.xiaomi_miot.sensor] Get xiaomi message for 6485819471 failed: {'code': 0, 'message': 'ok', 'result': {'messages': None}}
2022-05-25 08:17:41 INFO (MainThread) [custom_components.xiaomi_miot.sensor] Get xiaomi message for 6485819471 failed: {'code': 0, 'message': 'ok', 'result': {'messages': None}}
2022-05-25 08:17:56 INFO (MainThread) [custom_components.xiaomi_miot.sensor] Get xiaomi message for 6485819471 failed: {'code': 0, 'message': 'ok', 'result': {'messages': None}}
2022-05-25 08:18:11 INFO (MainThread) [custom_components.xiaomi_miot.sensor] Get xiaomi message for 6485819471 failed: {'code': 0, 'message': 'ok', 'result': {'messages': None}}
2022-05-25 08:18:12 INFO (MainThread) [greeclimate.device] Starting device binding to Device: 1e8e79ec @ 192.168.1.69:7000 (mac: f4911e8e79ec)
2022-05-25 08:18:22 WARNING (MainThread) [homeassistant.components.gree.bridge] Device is unavailable: gree-1e8e79ec (Device: 1e8e79ec @ 192.168.1.69:7000 (mac: f4911e8e79ec))
2022-05-25 08:18:22 ERROR (MainThread) [homeassistant.components.gree.bridge] Error fetching gree-1e8e79ec data: Device gree-1e8e79ec is unavailable
2022-05-25 08:18:26 INFO (MainThread) [custom_components.xiaomi_miot.sensor] Get xiaomi message for 6485819471 failed: {'code': 0, 'message': 'ok', 'result': {'messages': None}}
2022-05-25 08:18:41 INFO (MainThread) [custom_components.xiaomi_miot.sensor] Get xiaomi message for 6485819471 failed: {'code': 0, 'message': 'ok', 'result': {'messages': None}}
2022-05-25 08:18:56 INFO (MainThread) [custom_components.xiaomi_miot.sensor] Get xiaomi message for 6485819471 failed: {'code': 0, 'message': 'ok', 'result': {'messages': None}}
2022-05-25 08:19:11 INFO (MainThread) [custom_components.xiaomi_miot.sensor] Get xiaomi message for 6485819471 failed: {'code': 0, 'message': 'ok', 'result': {'messages': None}}
2022-05-25 08:19:22 INFO (MainThread) [greeclimate.device] Starting device binding to Device: 1e8e79ec @ 192.168.1.69:7000 (mac: f4911e8e79ec)
2022-05-25 08:19:26 INFO (MainThread) [custom_components.xiaomi_miot.sensor] Get xiaomi message for 6485819471 failed: {'code': 0, 'message': 'ok', 'result': {'messages': None}}
2022-05-25 08:19:32 INFO (MainThread) [homeassistant.components.gree.bridge] Fetching gree-1e8e79ec data recovered
2022-05-25 08:19:41 INFO (MainThread) [custom_components.xiaomi_miot.sensor] Get xiaomi message for 6485819471 failed: {'code': 0, 'message': 'ok', 'result': {'messages': None}}
2022-05-25 08:19:56 INFO (MainThread) [custom_components.xiaomi_miot.sensor] Get xiaomi message for 6485819471 failed: {'code': 0, 'message': 'ok', 'result': {'messages': None}}
2022-05-25 08:20:11 INFO (MainThread) [custom_components.xiaomi_miot.sensor] Get xiaomi message for 6485819471 failed: {'code': 0, 'message': 'ok', 'result': {'messages': None}}
2022-05-25 08:20:26 INFO (MainThread) [custom_components.xiaomi_miot.sensor] Get xiaomi message for 6485819471 failed: {'code': 0, 'message': 'ok', 'result': {'messages': None}}
2022-05-25 08:20:32 INFO (MainThread) [greeclimate.device] Starting device binding to Device: 1e8e79ec @ 192.168.1.69:7000 (mac: f4911e8e79ec)
2022-05-25 08:20:41 INFO (MainThread) [custom_components.xiaomi_miot.sensor] Get xiaomi message for 6485819471 failed: {'code': 0, 'message': 'ok', 'result': {'messages': None}}
2022-05-25 08:20:42 WARNING (MainThread) [homeassistant.components.gree.bridge] Device is unavailable: gree-1e8e79ec (Device: 1e8e79ec @ 192.168.1.69:7000 (mac: f4911e8e79ec))
2022-05-25 08:20:42 ERROR (MainThread) [homeassistant.components.gree.bridge] Error fetching gree-1e8e79ec data: Device gree-1e8e79ec is unavailable

[goxofy]

same problem, every time ha restart

[stomko11]

I am having the same problem with my Gree ACs. I have 3 units, all of them with static IP, no duplicate MAC address or anything. They are available via official app all the time, and reachable on the network during the time when HA reports they are unavailable.
Today, I experienced that 2 of them were showing unavailable, while 3rd was working OK. Reloading integration immediately resolves that issue.

[cheny95]

same problem, I have 3 Gree ACs, which will become unavailable at random.

[WallK]

@galandilias mock server should resolve this
Mine didn't beep, but disconnected all the time

[stomko11]

I have been having issues, until certain point when one of ACs failed to connect at all (it was always unavailable, while OK in app). I switched to alternative integration https://github.com/RobHofmann/HomeAssistant-GreeClimateComponent which works OK for me

[AdrianFasie]

Hello all,

I have a info that maybe could help you to identify the issue.
Last year I bought an AC model gwh12agb-k6dna1a which could be easily added in Home assistant using the oficial Gree Integration.
2 weeks ago I bought a second one (model gwh12agbxb-k6dna1a) and I have the well known issue with availability (mostly not available / accessible from HA).
As can be seen in the image below, even if they have the same MID, the firmware is different and I cannot update the second one to 2.06. Is there a way to force to update it? Or maybe the hardware is different and this is why it is not possible...

Using GREE+ app, both work fine.
On the official GREE website, they provide GREE WIFI Smart app. After installing this app, I got a pop-up info saying that for Europe I need to use EWPE Smart which is 100% identical with GREE+

It would be great if someone could fix the issue in the official Home Assistant Integration for AC with firmware V1.21

Thank you,
Adrian

[codedesperate]

Hmm,
I have firmware 3.75 and I have this issue too.

[AdrianFasie]

It is amazing how devices with the same MID have different Firmware versions. I am wondering how do they decide which firmware to use if not based on MID? It could be based on model number which it is not shown in APP, but only written on device.
As I mentioned, I have 2 models (gwh12agbxb-k6dna1a and gwh12agb-k6dna1a) both having different Firmware versions.
@codedesperate: Could you please let us know what is your model? As long as you have 3.75, I suppose you have a different model than me.

[User8395]

I have this issue too. We set up three more Gree ACs yesterday to make a total of 4 ACs and only the one set up a while ago works fine. The 3 new ACs connect but don't show temperature. Changing the mode from Home Assistant doesn't do anything on the AC itself.
It also becomes unavailable after about 30 seconds with the error "This entity is no longer being provided by the Gree integration". Control works fine from Gree+.
An error is shown from the core logs "Timeout trying to bind to gree device".

[lifey]

Same happening for me @User8395 i have one AC with firmware version v1.21 which is not recognized properly and 3 ACs with v1.16 which work just fine

[lbartal]

I guess with v1.21 Gree changed encryption. In https://github.com/RobHofmann/HomeAssistant-GreeClimateComponent README config part there is an attribute for that

encryption_version: <OPTIONAL: should be set to 2 for V1.21>

[war4peace]

I don't think this integration is being actively worked on any more.

[war4peace]

Is your Home Assistant connected via Wi-Fi?
Mine isn't, and the integration worked perfectly for both my ACs until recently.
There was no AC firmware update, at all.

[JongsmaSimon]

I finally solved it. I reset the WiFi connection for both my (Cooper & Hunter) airco’s. Then tried to connect to the Gree+ app which is more actively maintained. This only succeeded when I connected them to my (visitor) 2,4 GHz network. Then both were seen by Gree+ and also connection to Home Assistant is rock solid now.
So connecting to a combined 2,4 GHz + 5 GHz network (what I had before) is causing the problems.

[User8395]

I finally solved it. I reset the WiFi connection for both my (Cooper & Hunter) airco’s. Then tried to connect to the Gree+ app which is more actively maintained. This only succeeded when I connected them to my (visitor) 2,4 GHz network. Then both were seen by Gree+ and also connection to Home Assistant is rock solid now.
So connecting to a combined 2,4 GHz + 5 GHz network (what I had before) is causing the problems.

How did you reset the connection?

[JongsmaSimon]

I finally solved it. I reset the WiFi connection for both my (Cooper & Hunter) airco’s. Then tried to connect to the Gree+ app which is more actively maintained. This only succeeded when I connected them to my (visitor) 2,4 GHz network. Then both were seen by Gree+ and also connection to Home Assistant is rock solid now.
So connecting to a combined 2,4 GHz + 5 GHz network (what I had before) is causing the problems.

How did you reset the connection?

Well reset depends on your airco & remote control, but in my case it involved setting airco to “off” and pressing “mode” and “wifi” buttons together until a “beep” is heard. Then wait approx. 2 minutes until the airco access point appears on WiFi (name is derived from MAC address). Then remove airco defintion from Gree+ app (if it was there) and add it anew. Follow the instructions in the Gree+ app.

[User8395]

I finally solved it. I reset the WiFi connection for both my (Cooper & Hunter) airco’s. Then tried to connect to the Gree+ app which is more actively maintained. This only succeeded when I connected them to my (visitor) 2,4 GHz network. Then both were seen by Gree+ and also connection to Home Assistant is rock solid now.
So connecting to a combined 2,4 GHz + 5 GHz network (what I had before) is causing the problems.

How did you reset the connection?

Well reset depends on your airco & remote control, but in my case it involved setting airco to “off” and pressing “mode” and “wifi” buttons together until a “beep” is heard. Then wait approx. 2 minutes until the airco access point appears on WiFi (name is derived from MAC address). Then remove airco defintion from Gree+ app (if it was there) and add it anew. Follow the instructions in the Gree+ app.

Sadly that didn't work for me, the AC still responds with unavailable

[JongsmaSimon]

Sadly that didn't work for me, the AC still responds with unavailable
Did you actually use a 2,4 GHz-only network?

[User8395]

Sadly that didn't work for me, the AC still responds with unavailable
Did you actually use a 2,4 GHz-only network?

I think my network is both

[JongsmaSimon]

My estimate is that you need a 2,4GHz only network (most routers can create a “guest” network on 2,4 GHz).
The mixed mode (2,4 + 5 GHz) creates the problem.

[User8395]

I'll try creating a hidden network that's 2.4 GHz

[User8395]

@JongsmaSimon unfortunately even after turning of 5 GHz the issue still persists.

It's weird because I have an AC connected that works perfectly fine..

[AdrianFasie]

Hello all,

In my opinion trying this is waste of time. I confirm that I have 2 ACs connected to the same 2.4/5G router and one of them it is working, the other not, depending on the version, as I described in a previous post.

Could be that in some scenarios/workarounds to get them working, but this should not be taken as a general solution because most probably it will not work for the others.

We need a solution to rely on it, and this could be archived only by correcting the integration.

I am wondering if it is possible to contact the Gree team to get support.

Regards, Adrian

[defaultsecurity]

I often find myself in a similar situation.

• I turned off 5G and it worked.
• Then it stopped working.
• Then it worked with 5G turned on for months.
• To this day 1 AC out of 3 often looses connection to HA while maintaining connection to the Gree App.
• I'm forced to rerun the Gree setup for this problematic AC, then it works again for a couple weeks.

This integration is along the most installed climate integrations.

Many people are still having connection problems.

Can we please finally add IP based connection?

[issue-triage-workflows]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[wosiu]

Dear bot, this issue is definitely not stale. I just had problem like this ~2 weeks ago.
And I agree that solution to it would be to add IP-based connection instead or next to the existing broadcast auto-discovery.

[User8395]

I am pleased to say that on HA 2024.10.4, all my other Gree ACs are operational via HA

[wosiu]

I am pleased to say that on HA 2024.10.4, all my other Gree ACs are operational via HA

Hold you horses, nothing really has changed in the gree integration since August 6th:
https://github.com/home-assistant/core/commits/dev/homeassistant/components/gree

So HA core release probably doesn't matter here?

[User8395]

I am pleased to say that on HA 2024.10.4, all my other Gree ACs are operational via HA

Hold you horses, nothing really has changed in the gree integration since August 6th:

https://github.com/home-assistant/core/commits/dev/homeassistant/components/gree

So HA core release probably doesn't matter here?

I think the problem was I connected my new ACs to our other network. We have a direct connection to our ISP for smart devices like cameras, and a TP-Link Deco for faster WiFi. I think I accidentally connected the ACs to the Deco, so after I connected the HA to the Deco, they now work fine with HA.

As of writing this, I noticed a firmware update for the AC's WiFi module, with the changelog "We have fixed some known issues".

@everyone please try to update your ACs now.

[maciejtarmas]

Anyone knows if the units update themselves automatically when connected to the internet or do I have to update manually through the app? I deleted the app as soon as I configured WiFi on my units and cut them off from internet access.

Mine are currently working fine, by the way.

I suspect that there could have been a problem with network discovery in HA at some point, which might be fixed now.

[User8395]

Anyone knows if the units update themselves automatically when connected to the internet or do I have to update manually through the app? I deleted the app as soon as I configured WiFi on my units and cut them off from internet access.

Mine are currently working fine, by the way.

I suspect that there could have been a problem with network discovery in HA at some point, which might be fixed now.

Mine didn't, I had to update each one manually.