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[bot]]

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

[probot-home-assistant[bot]]

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: https://github.com/tomikaa87/gree-remote/issues/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_oninterface 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.

[goxofy]

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_oninterface 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.

Hi, @Idan37S What shoud I do if i have 3 climates?

[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_oninterface 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.

Hi, @Idan37S What shoud I do if i have 3 climates?

Just add both lines to the same place like:

await self.send({"t": "scan"}, ("192.168.30.21", 7000)) await self.send({"t": "scan"}, ("192.168.30.22", 7000))

[Shurov]

I have an automation in Node-Red to turn off the lightning indication on the AC unit during night. So, it's been triggered twice a day (turn off before night and turn back on in the morning). Having implemented this automation, at least for a month already, HVAC hasn't disappeared from Home Assistant

[Nedevski]

Same issue as @arvaisandor1968.

I have 3 ACs which are available in the app but seem to go online/offline at regular intervals. All have static local IPs.

[WRLPDZ]

Hi, I have the same problem, but AC is available in network. Its not disconnecting. Only integration error appear. I'm pinging AC all the time.

Logger: homeassistant.components.gree.bridge
Source: helpers/update_coordinator.py:223
Integration: Gree Climate ([documentation](https://www.home-assistant.io/integrations/gree), [issues](https://github.com/home-assistant/home-assistant/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+gree%22))
First occurred: 15:32:38 (1 occurrences)
Last logged: 15:32:38

Error fetching gree-c67a321c data: Device gree-c67a321c is unavailable

[parski]

I have this problem as well. Three HVACs, all from Innova. At first I only saw two of them in Home Assistant and since they are part of the same duplex setup I figured the last unit was defective. However, it was always working in the Ewpe app, even when unavailable in Home Assistant.

Last thursday I had an electrician replace my electricity meter so we had a power outage for a minute or two. When the electricity came back on I noticed my previously unavailable AC was working perfectly but the other two were unavailable. Having read the thread above I tried reloading the integration but one unit is still unavailable. I think I might have awoken one of the unavailable ones since I had pretty recently used in in the Ewpe app.

They all have static IPs. mDNS enabled on the VLAN. As a part of troubleshooting I've disabled all firewall rules to see if it helps but it only seems to be an issue with the integration.

Red arrow is where electricity came back on.

[omgrech]

Same problem here. I re-installed Gree Integration, reloaded, reconfigured the AC and many other things and still shows offline. On one ocassion the only thing that worked (for a few hours) was literally powering off the AC from the outlet for few mins and then on again (+configuration etc). On the native gree app, it works like a charm.

[Nedevski]

Update - different ACs at different times start to work properly and not lose the connection as well... for some time. I have not noticed any meaningful pattern to that.

Oddest thing is that the most inconcistent AC is the one closest to the router... Go figure.

[omgrech]

"Oddest thing is that the most inconcistent AC is the one closest to the router... "

Mine is exactly the same scenario, closes AC to the router :(

[cmroche]

General questions to help isolate the issues:

1) Make / model of the device(s) and how many Gree devices on your network? 2) Is the device able to access Gree cloud? 3) Enable debug logs for homeassistant.components.gree and greeclimate and post them. 4) Are you using static or dynamic IP?

Unfortunately I do not see this problem, and every case where it's been reported network logs show that the integration legitimately isn't getting data back on the network. The only theory I have for why Gree+ continues to work is that it either ignores errors, or more likely falls back to just using the cloud service once the device is identified. In at least one case the AC firmware was different, in that it would respond to discovery but be fully unusable on the local network and required cloud services to function (specific manufacturer, don't recall offhand which at the moment).

[Nedevski]

@cmroche Here is more detailed info:

All 3 AC units are on static IP with an 1h lease time. All of the devices work when I try to use them via the Gree Cloud. The full device info screen sometimes lags a lot when trying to load it, but the small Power switch button on the thumbnail works every time.

I have two Gree Fairy 9's (gwh09acc-k6dna1a/i), marked on the floorplan as F9, firmware v1.00. The third one is Gree Amber Nordic 12 (gwh12yd-s6dba1a/i) marked with AN12 and firmware v3.73 ("Living Room AC") The R on the map is the router (Mi 3Gv1 + OpenWrt, so the signal is strong). Left F9 is "Guest Room AC", right F9 is "Bedroom AC" on my previous screenshots.

Sometimes the units go for a couple of hours with 100% availability. Sometimes they go a bit patchy like today (screenshot below). On other occasions they go absolutely 50:50 on and off on regular intervals as on my previous screenshots above. It's seemingly at random and I was not able to find any correlation between anything.

All I have in the logs now is this, I will turn debug on and post more info later.

[alamoudimoh]

i am welcoming myself to the club. same issue,

custom works better i would say, but i have no luck with xfan and other optional components

[Nedevski]

My update on this is that for some reason the two 9's are now working a lot better after enabling debug mode.

Not sure if this is a coincidence or it's just a matter of increasing the timeout somewhere, but => I got more stable connection for some reason. The big one, the Amber Nordic is still spotty.

[cdemi]

Just to chime in that I too have the same problem. The Gree AC has a static IP (given by DHCP). The AC is also always online as I can see it from the Unifi portal. I can also ping the device and communicate with it via the native app.

A restart of the home-assistant VM sometimes brings the integration working again

[cdemi]

I have recorded a small video to show how I know that the problem is not with the WiFi network or with the AC but with the Home Assistant integration.

As you can see in the video, the Gree AC is showing as unavailable. I can control the AC with the Gree app. As soon as I restart the Gree integration the AC immediately comes online on Home Assistant and is usable

https://user-images.githubusercontent.com/8025435/180507239-f92e7bed-dd90-4820-b759-e949a2f20c77.mp4

[jiridostal]

For me it behaves like this, I believe it's the same issue so posting here.

[stomko11]

For now, I am using automation to reload gree integration if any of my devices is unavailable for more than 2 minutes. Usually they do recover, but if they don't, automation will do it. But I would certainly be happier if there was a real fix for that.

[goxofy]

@stomko11 Hi, could you share your automation yaml file for reload gree integration? thanks a lot!

[mfriik]

So for me the issue did not go away in the end. It still becomes unavailable from time to time. But @stomko11 would love to see the automation yaml as @goxofy mentioned as I struggle with a long term solution myself.

[WRLPDZ]

Reload of integration in my case is not the solution. When they become unavailable for HA and I reload integration not all AC's are visible again. Most of the case restart of whole host helps but not always. Before upgrade to 2022.7.7 they ware available not available in random time. Now when whey disconnect from integration or integration can not connect with them is stays that way till full restart of host. Even restart of HA it selves do not help.

[Nedevski]

It's me again. Since I'm doing a migration from scratch, I currently have two HA instances that both use the Gree integration. Looks like they do NOT go offline at the same time, which again points that the issue is with the integration, rather than with the Gree cloud itself. See attached screenshot.

I have to say that in the last month I have less and less blips, not sure if that's due to HA updates or Gree Cloud updates. Also sometimes when using the Gree app, I get around 5-8 seconds of "lag" before the commands come through.

Is there an option to increase the timeout on the requests that fetch the status of the AC? I'm guessing if that's increased to 10 or 15s those blips will go away. Same goes for sending commands to Gree from HA, just a bigger timeout.

On top is my main instance (Hyper-V VM), debug mode is on. On the bottom is a fresh bare metal install.