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

doppiaemme · 2022-04-05T14:12:41Z

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 · 2022-04-05T14:12:46Z

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

probot-home-assistant · 2022-04-05T14:12:49Z

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 · 2022-04-06T15:57:16Z

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 · 2022-04-08T11:01:21Z

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 · 2022-04-08T17:24:37Z

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 · 2022-04-08T21:14:13Z

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 · 2022-04-09T19:00:52Z

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 · 2022-04-10T07:47:20Z

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 · 2022-04-13T12:58:27Z

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 · 2022-04-21T08:51:15Z

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 · 2022-04-21T09:13:07Z

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 · 2022-04-21T09:57:22Z

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 · 2022-04-21T10:06:05Z

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 · 2022-04-21T12:09:24Z

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 · 2022-04-21T12:58:47Z

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 · 2022-04-25T06:23:21Z

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 · 2022-04-25T20:49:02Z

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

meldarionqeusse · 2022-04-26T06:42:14Z

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 · 2022-04-26T07:38:12Z

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 · 2022-04-26T10:04:39Z

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 · 2022-05-18T11:07:26Z

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

Idan37S · 2022-05-18T12:07:24Z

@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 · 2022-05-24T18:08:53Z

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

arvaisandor1968 · 2022-05-24T19:14:01Z

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 · 2022-05-25T04:54:57Z

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 · 2022-05-25T06:25:39Z

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 · 2022-06-01T16:40:04Z

same problem, every time ha restart

stomko11 · 2022-06-07T19:53:55Z

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 · 2022-06-08T09:23:45Z

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

MichalBury · 2024-01-05T07:31:24Z

Hello, I have installed your component and testing it.
But there is a warning in HA log:
2024-01-05 08:14:20.357 WARNING (MainThread) [homeassistant.util.async_] Detected blocking call to sleep inside the event loop by custom integration 'gree_full' at custom_components/gree_full/entities/greeClimate.py, line 13: await self.greeClimateApi.initialize(), please report it to the author of the 'gree_full' custom integration

matizk144 · 2024-01-06T10:16:11Z

Hello @MichalBury. I know the issue. As I said, i'm new in python and I implemented pyrhon couroutine in wrong way. I wanted to launch IO calls in async way, but, seems, that is wrongly done. I'll try to fix it. Repo is new and not support fahrenheit degrees as well. If people interest integration missing parts will be added. As well as we could integrate it to offical plugin (by refactoring it)

Latulippe9 · 2024-01-06T21:59:17Z

I have the same problem here. My Gree integration get unavailable randomly.
Core 2024.1.2

MichalBury · 2024-01-08T06:31:37Z

Hello @matizk144, no problem with the warning at now. The integration runs without problems till now. The "weird" Thing is, now also the official "gree climate" integration has no problems. I have both intergrations running now on same system. As soon I remove "gree_full" the problem with timeout starts again.

issue-triage-workflows · 2024-04-07T11:05:28Z

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.

ic-dev21 · 2024-04-07T11:48:48Z

Still an issue. Le dim. 7 avr. 2024 à 07:05, issue-triage-workflows[bot] < ***@***.***> a écrit :

…

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. — Reply to this email directly, view it on GitHub <#69351 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AZZGCFKDZJLYURLYBH5TZM3Y4ESBJAVCNFSM5SS44KQ2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TEMBUGE2DGMJQG43Q> . You are receiving this because you commented.Message ID: ***@***.***>

omarkhali · 2024-04-07T21:14:27Z

I have the same problem here. My Gree integration get unavailable randomly.
Core 2024.4.1

codedesperate · 2024-04-30T08:29:25Z

Just setup gree integration for the first time on latest. I ran into this issue and found this upon googling it. Seems it's a very long standing problem.

I'm thinking to make an automation that just loops the command until it is successful.

ic-dev21 · 2024-04-30T10:28:52Z

I did that for a few of my automations that I don’t want to ever fail. I can share them if you want. Le mar. 30 avr. 2024 à 04:29, codedesperate ***@***.***> a écrit :

…

Just setup gree integration for the first time on latest. I ran in to this issue and found this upon googling it. Seems it a very long standing problem. I'm thinking to make a automation that just loops the command until it is successful. image.png (view on web) <https://github.com/home-assistant/core/assets/29740063/554d0b6c-3b23-4531-a345-7199f6d2b87f> — Reply to this email directly, view it on GitHub <#69351 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AZZGCFIOEOTP7J3XECURBXDY75JAHAVCNFSM5SS44KQ2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TEMBYGQ3TAMJZHA2A> . You are receiving this because you commented.Message ID: ***@***.***>

codedesperate · 2024-04-30T11:47:01Z

I did that for a few of my automations that I don’t want to ever fail. I can share them if you want.

Please do, that would be helpful 👍

EDIT
Actually, I've just done it myself now. I used a while repeat, and a 30 second delay :)

repeat:
  sequence:
    - delay:
        hours: 0
        minutes: 0
        seconds: 30
        milliseconds: 0
  while:
    - condition: state
      entity_id: climate.1edeb718
      state: unavailable
      ```

WallK · 2024-05-10T14:21:09Z

I've blocked internet for my Gree ACs and the started behaving like this (but with lower frequency)

But restoring the internet access to one of them made connection dead stable (for more than an hour test)

mikko · 2024-05-10T16:00:25Z

I had this problem for a long time after I blocked the AC from calling home to China. After configuring a mock server for the AC it started working properly and it has been working for months already with absolutely no disconnects.

WallK · 2024-05-10T16:07:29Z

@mikko > After configuring a mock server for the AC
Could you elaborate how you did that?

mikko · 2024-05-10T16:46:17Z

@WallK
I'm running this on my home server with appropriate DNS configuration on my router
https://github.com/emtek-at/GreeAC-DummyServer

IIRC You need to be able to change the server domain of the AC and for my unit this worked

https://github.com/makemeafirewall/GreeAC-ConfigTool

It was quite a hassle to make working but worth it

WallK · 2024-05-10T17:06:46Z

@mikko thank you!
I will try this by overriding DNS for domain I've sniffed from the ACs calls home
Changing domain in the AC does seem like a hassle haha

Update: adding info-acq.gree.com and dis.gree.com in DNS records and putting dis.gree.com in the mock server env var did the trick! Thank you very much!

galandilias · 2024-05-28T04:43:31Z

2024-05-27 08:30:07.360 WARNING (MainThread) [homeassistant.components.gree.bridge] Device is unavailable: gree-c699a74a (Device: c699a74a @ 192.168.12.42:7000 (mac: 502cc699a74a)) 2024-05-27 08:30:07.361 ERROR (MainThread) [homeassistant.components.gree.bridge] Error fetching gree-c699a74a data: Device gree-c699a74a is unavailable 2024-05-27 08:32:27.360 WARNING (MainThread) [homeassistant.components.gree.bridge] Device is unavailable: gree-c699a74a (Device: c699a74a @ 192.168.12.42:7000 (mac: 502cc699a74a)) 2024-05-27 08:32:27.360 ERROR (MainThread) [homeassistant.components.gree.bridge] Error fetching gree-c699a74a data: Device gree-c699a74a is unavailable 2024-05-27 08:34:47.360 WARNING (MainThread) [homeassistant.components.gree.bridge] Device is unavailable: gree-c699a74a (Device: c699a74a @ 192.168.12.42:7000 (mac: 502cc699a74a)) 2024-05-27 08:34:47.360 ERROR (MainThread) [homeassistant.components.gree.bridge] Error fetching gree-c699a74a data: Device gree-c699a74a is unavailable 2024-05-27 08:50:30.045 WARNING (MainThread) [homeassistant.helpers.service] Referenced entities fan.mi_smart_standing_fan_2_lite are missing or not currently available 2024-05-27 13:09:21.485 WARNING (MainThread) [homeassistant.components.gree.bridge] Device is unavailable: gree-c699a74a (Device: c699a74a @ 192.168.12.42:7000 (mac: 502cc699a74a)) 2024-05-27 13:09:21.485 ERROR (MainThread) [homeassistant.components.gree.bridge] Error fetching gree-c699a74a data: Device gree-c699a74a is unavailable 2024-05-27 13:12:31.484 WARNING (MainThread) [homeassistant.components.gree.bridge] Device is unavailable: gree-c699a74a (Device: c699a74a @ 192.168.12.42:7000 (mac: 502cc699a74a)) 2024-05-27 13:12:31.484 ERROR (MainThread) [homeassistant.components.gree.bridge] Error fetching gree-c699a74a data: Device gree-c699a74a is unavailable 2024-05-27 13:14:51.483 WARNING (MainThread) [homeassistant.components.gree.bridge] Device is unavailable: gree-c699a74a (Device: c699a74a @ 192.168.12.42:7000 (mac: 502cc699a74a)) 2024-05-27 13:14:51.483 ERROR (MainThread) [homeassistant.components.gree.bridge] Error fetching gree-c699a74a data: Device gree-c699a74a is unavailable 2024-05-27 13:19:12.485 WARNING (MainThread) [homeassistant.components.gree.bridge] Device is unavailable: gree-c699a74a (Device: c699a74a @ 192.168.12.42:7000 (mac: 502cc699a74a)) 2024-05-27 13:19:12.485 ERROR (MainThread) [homeassistant.components.gree.bridge] Error fetching gree-c699a74a data: Device gree-c699a74a is unavailable 2024-05-27 17:04:22.483 WARNING (MainThread) [homeassistant.components.gree.bridge] Device is unavailable: gree-c699a74a (Device: c699a74a @ 192.168.12.42:7000 (mac: 502cc699a74a)) 2024-05-27 17:04:22.483 ERROR (MainThread) [homeassistant.components.gree.bridge] Error fetching gree-c699a74a data: Device gree-c699a74a is unavailable 2024-05-27 17:52:32.482 WARNING (MainThread) [homeassistant.components.gree.bridge] Device is unavailable: gree-c699a74a (Device: c699a74a @ 192.168.12.42:7000 (mac: 502cc699a74a)) 2024-05-27 17:52:32.482 ERROR (MainThread) [homeassistant.components.gree.bridge] Error fetching gree-c699a74a data: Device gree-c699a74a is unavailable 2024-05-27 17:54:52.483 WARNING (MainThread) [homeassistant.components.gree.bridge] Device is unavailable: gree-c699a74a (Device: c699a74a @ 192.168.12.42:7000 (mac: 502cc699a74a)) 2024-05-27 17:54:52.483 ERROR (MainThread) [homeassistant.components.gree.bridge] Error fetching gree-c699a74a data: Device gree-c699a74a is unavailable 2024-05-27 17:57:12.484 WARNING (MainThread) [homeassistant.components.gree.bridge] Device is unavailable: gree-c699a74a (Device: c699a74a @ 192.168.12.42:7000 (mac: 502cc699a74a)) 2024-05-27 17:57:12.485 ERROR (MainThread) [homeassistant.components.gree.bridge] Error fetching gree-c699a74a data: Device gree-c699a74a is unavailable 2024-05-27 18:01:33.483 WARNING (MainThread) [homeassistant.components.gree.bridge] Device is unavailable: gree-c699a74a (Device: c699a74a @ 192.168.12.42:7000 (mac: 502cc699a74a)) 2024-05-27 18:01:33.483 ERROR (MainThread) [homeassistant.components.gree.bridge] Error fetching gree-c699a74a data: Device gree-c699a74a is unavailable

Anything of above resolves the problem? I currently let the device to connect to the producer server - but still HA logs a lot of unavailability - what is even worse - device beeps randomly (single beep from time to time...) - I bet this is related to sth like reconnect or sth

WallK · 2024-05-28T04:57:05Z

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

stomko11 · 2024-05-28T09:52:15Z

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 · 2024-06-10T08:27:37Z

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 · 2024-06-10T08:47:07Z

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

AdrianFasie · 2024-06-10T10:51:00Z

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 · 2024-06-22T20:42:57Z

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 · 2024-07-06T10:40:27Z

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 · 2024-07-06T15:16:07Z

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 · 2024-07-12T09:50:45Z

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

JongsmaSimon · 2024-07-20T10:51:19Z

I found a solution that at least works for me. In my network I have several nodes in a WiFi6 mesh.
One of my Airco’s (Cooper&Hunter) was connected to the same node as my Home Assistant, the other was not. I noticed that the second was often ‘unavailable’ and the first wasn’t.
I forced the problem Airco (in my router) to connect to the same node as Home Assistant.
Problem Solved (although with weaker WiFi signal strength).
This maybe gives some indication to what the problem might be. Firmware v3.75.

war4peace · 2024-07-20T12:45:25Z

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 · 2024-07-20T13:52:13Z

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.

Yes correct my Home Assistant is connected via WiFi.

probot-home-assistant bot added the integration: gree label Apr 5, 2022

issue-triage-workflows bot added the stale label Apr 7, 2024

issue-triage-workflows bot removed the stale label Apr 8, 2024

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

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

Comments

doppiaemme commented Apr 5, 2022 • edited Loading

The problem

What version of Home Assistant Core has the issue?

What was the last working version of Home Assistant Core?

What type of installation are you running?

Integration causing the issue

Link to integration documentation on our website

Diagnostics information

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

probot-home-assistant bot commented Apr 5, 2022

probot-home-assistant bot commented Apr 5, 2022

csubakk commented Apr 6, 2022

mfriik commented Apr 8, 2022

cmroche commented Apr 8, 2022

mfriik commented Apr 8, 2022 • edited Loading

doppiaemme commented Apr 9, 2022 • edited Loading

csubakk commented Apr 10, 2022 • edited Loading

reyo commented Apr 13, 2022 • edited Loading

Idan37S commented Apr 21, 2022 • edited Loading

reyo commented Apr 21, 2022

doppiaemme commented Apr 21, 2022

Idan37S commented Apr 21, 2022

doppiaemme commented Apr 21, 2022

cmroche commented Apr 21, 2022

meldarionqeusse commented Apr 25, 2022

cmroche commented Apr 25, 2022

meldarionqeusse commented Apr 26, 2022

csubakk commented Apr 26, 2022

Idan37S commented Apr 26, 2022

jodewee commented May 18, 2022

Idan37S commented May 18, 2022

SalemCat commented May 24, 2022

arvaisandor1968 commented May 24, 2022

kingtao1024 commented May 25, 2022

arvaisandor1968 commented May 25, 2022

goxofy commented Jun 1, 2022

stomko11 commented Jun 7, 2022

cheny95 commented Jun 8, 2022

MichalBury commented Jan 5, 2024

matizk144 commented Jan 6, 2024

Latulippe9 commented Jan 6, 2024

MichalBury commented Jan 8, 2024

issue-triage-workflows bot commented Apr 7, 2024

ic-dev21 commented Apr 7, 2024 via email

omarkhali commented Apr 7, 2024

codedesperate commented Apr 30, 2024 • edited Loading

ic-dev21 commented Apr 30, 2024 via email

codedesperate commented Apr 30, 2024 • edited Loading

WallK commented May 10, 2024

mikko commented May 10, 2024

WallK commented May 10, 2024

mikko commented May 10, 2024

WallK commented May 10, 2024 • edited Loading

galandilias commented May 28, 2024

WallK commented May 28, 2024

stomko11 commented May 28, 2024

AdrianFasie commented Jun 10, 2024

codedesperate commented Jun 10, 2024

AdrianFasie commented Jun 10, 2024 • edited Loading

User8395 commented Jun 22, 2024

lifey commented Jul 6, 2024 • edited Loading

lbartal commented Jul 6, 2024

war4peace commented Jul 12, 2024

JongsmaSimon commented Jul 20, 2024

war4peace commented Jul 20, 2024

JongsmaSimon commented Jul 20, 2024

doppiaemme commented Apr 5, 2022 •

edited

Loading

mfriik commented Apr 8, 2022 •

edited

Loading

doppiaemme commented Apr 9, 2022 •

edited

Loading

csubakk commented Apr 10, 2022 •

edited

Loading

reyo commented Apr 13, 2022 •

edited

Loading

Idan37S commented Apr 21, 2022 •

edited

Loading

codedesperate commented Apr 30, 2024 •

edited

Loading

codedesperate commented Apr 30, 2024 •

edited

Loading

WallK commented May 10, 2024 •

edited

Loading

AdrianFasie commented Jun 10, 2024 •

edited

Loading

lifey commented Jul 6, 2024 •

edited

Loading