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

[stomko11]

@mfriik so for me, reloading integration works all the time. Since I have 3 AC units, sometimes all 3 come back, sometimes not, so my automation, if any of ACs is unavailable for 2 minutes, will reload until all are back on. Majority of the time, they recover within 2 minutes, that is why I kick off the automation after 2 minutes. Alternatively, you can just create a button that will reload it.

1st piece is to handle actual reload. Put this into configuration.yaml, replace YOURLOCALIP with your local IP and IDOFINTEGRATION with the ID of integration, LONGLIVETOKEN is the token you generate, do not remove work Bearer:

rest_command:
  reload_gree:
    url: http://YOURLOCALIP:8123/api/config/config_entries/entry/IDOFINTEGRATION/reload 
    method: POST
    headers:
      authorization: Bearer LONGLIVETOKEN
      content-type: application/json

To find the ID, go to settings, devices and integrations, then in chrome open developer tools and switch to network tab. The on the gree integration, click "..." and select "reload integration". You should see a pop up in developer tools - "reload" - that should show "request URL" which is what you will paste in that rest command.

And that's it. It is up to you if you automate it, or just create a button that will fire this.

[nawafbana]

Same problem. 8 Gree air conditioners, randomly unavailable, all of them are working fine on the mobile phone Gree app. not all time restarting integration will help,

Dose automation effects the HA performance?

[cmroche]

greeclimate 1.3.0 was released with some improvements to the broadcast and discovery, I'm not 100% certain this will address all issues raised, but might improve discoverability for some users. Should come as a bug fix soon.

[parski]

Looking forward to trying it.

[goxofy]

core 8.2 is released

[gszigethy]

2022.8.2 completely broke the Gree integration after pulling https://github.com/home-assistant/core/pull/75812

My HA VM has 2 interfaces, a primary for most communications and a secondary in the IOT VLAN for some limited purpose communications, one being the stupid broadcast implementation of Gree. As soon as I upgraded to 2022.8.2 all 6 aircos went unavailable. Rolling back to 2022.8.1 brought them back to life. Tried the upgrade again to see if it's consistently breaking it, it does.

Pulling https://github.com/home-assistant/core/pull/75812 makes in much worse.

[parski]

My Gree integration did not completely break after upgrading to 8.2. Unsure if it fixed anything either, time will tell.

[gszigethy]

2022.8.2 completely broke the Gree integration after pulling #75812

My HA VM has 2 interfaces, a primary for most communications and a secondary in the IOT VLAN for some limited purpose communications, one being the stupid broadcast implementation of Gree. As soon as I upgraded to 2022.8.2 all 6 aircos went unavailable. Rolling back to 2022.8.1 brought them back to life. Tried the upgrade again to see if it's consistently breaking it, it does.

So if people will have the same issue: I went to Settings, System. Network, unchecked auto-configure and there, end enabled both interfaces manually. Then the integration works again.

[WRLPDZ]

I have update to: Home Assistant 2022.8.4 Supervisor 2022.08.3 Operating System 8.4 And for now its start working without problem. I hope i will stay that way.

[Idan37S]

Does the new version of Gree works for anyone who has VLANs?

[nawafbana]

I have update to: Home Assistant 2022.8.4 Supervisor 2022.08.3 Operating System 8.4 And for now its start working without problem. I hope i will stay that way.

Yes finally :), all are working fine now after updated 2022.8.4

[omgrech]

I confirm my issue was also solved after the last update. So far still stable and good. Thanks a million

[stomko11]

I observe no improvement. They still go unavailable randomly.

[nawafbana]

I observe no improvement. They still go unavailable randomly.

what i did is make them static ip first, and then update home assistant..

[urbinek]

I have same problem. Gree integration just stopped working.

Setting static network adapters solved issue for now

[parski]

My HVACs also go unavailable from time to time.

[maciejtarmas]

Could you guys disable your internet connection or drop all outgoing WAN connections from your HVAC at the firewall and see if it triggers the problem?

I had this same "unavailable" log entry for a couple of minutes each single morning. Turns out, according to my RIPE Atlas probe, that my ISP was going down at the same time.

So I disabled all outgoing connections from the unit to the internet and my logbook immediately started filling up with "unavailable" entries every 120 seconds. Every other 120 seconds it was available again.

I have a rather crude automation that checks the status of the thermostat every 60 seconds and either turns on or off the HVAC, so the unit is probed quite often.

Looks like the unit locks up at 2 minute intervals when it can't reach it's Chinese cloud service, then becomes available again.

I'm no programmer, but probably increasing some probing timeout in the integration would stop this logbook spam.

[urbinek]

Could you guys disable your internet connection or drop all outgoing WAN connections from your HVAC at the firewall and see if it triggers the problem?

Internet connectivity play no role with my case

[formiification]

2022.8.2 completely broke the Gree integration after pulling #75812 My HA VM has 2 interfaces, a primary for most communications and a secondary in the IOT VLAN for some limited purpose communications, one being the stupid broadcast implementation of Gree. As soon as I upgraded to 2022.8.2 all 6 aircos went unavailable. Rolling back to 2022.8.1 brought them back to life. Tried the upgrade again to see if it's consistently breaking it, it does.

So if people will have the same issue: I went to Settings, System. Network, unchecked auto-configure and there, end enabled both interfaces manually. Then the integration works again.

This solved my issue, thank you!

[Tamas-Toth-ebola]

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.

Yay! You simply made my day! (Just 2 minutes before midnight) I just found your tip/solution before I started to sleep, and with a quick work from my mobile through Termux in the bed I got my brand new Amber Royal configured with official Gree integration, which could not be auto-discovered before.

Marvelous! Fantastic! Thank you very much!

The integration really needs to allow to manually configure the IP address of the climate device...

[OrBin]

2022.8.2 completely broke the Gree integration after pulling #75812 My HA VM has 2 interfaces, a primary for most communications and a secondary in the IOT VLAN for some limited purpose communications, one being the stupid broadcast implementation of Gree. As soon as I upgraded to 2022.8.2 all 6 aircos went unavailable. Rolling back to 2022.8.1 brought them back to life. Tried the upgrade again to see if it's consistently breaking it, it does.

So if people will have the same issue: I went to Settings, System. Network, unchecked auto-configure and there, end enabled both interfaces manually. Then the integration works again.

I've had this issue for a long time now (a few months), seeing the HVACs as unavailable consistently. This seems to solve my issue, I hope it will persist. Thank you!

[Tamas-Toth-ebola]

Just to report my current state about the 'incorrect' auto-discovery, I had oursorced the greeclimate Python package of my HA installation as a Docker volume, modified the discovery.py files corresponding line...

await self.send({"t": "scan"}, (str(bcast_iface), 7000))

to

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

...and voila, the quick hacking solution seems to be working finely as this case can survive also the container reboot. Tried it, works (yet), so I'm happy.

Of course I have to watch any news on the greeclimate Python package, but I can live with it.

---

Now I just have to figure out how could I expand the 'Gree Climate' integration with 3 more switches, one for 'health mode' (cold plasma function), and 2 for 'fixed blade positions', what are already available in the underlying library (in the greeclimate Python package https://github.com/cmroche/greeclimate , and also in the original development https://github.com/tomikaa87/gree-remote).

(greeclimate) (tomikaa87)

I'd already saw that https://github.com/home-assistant/core/blob/dev/homeassistant/components/gree/switch.py has these standalone switch definitions but sadly do not know yet how the lying on the greeclimate package functions, as I know almost nothing about Python programming.

[Tamas-Toth-ebola]

Hi All!

I know this is off-topic for 'unavailable' problems, but my previous communications were here, some news:

Now, that I/we have the previously 'undetected' device with the help of @Idan37S , I had 'implemented' into the core Gree integration the missing 'heath' function (anion) also as discrete switch based on the others. I had also changed all switch icon visuals to something like the Gree originals (on the remote or in the documentation) to stay familiar, and I also made them to follow their states dynamically (where there is possible with available MDI icons).

With 'off' states:

With 'on' states:

The next challenge will be to handle the 'fixed position blade state's with discrete horizontal/vertical attributes (with exact direction + swing mode values), but that will be a little harder for me while now have no more time for it.

[znack14]

the air conditioner falls off, regardless of the network settings in the system. After restarting the integration, sometimes more than once, appears in the management

[monghuz]

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))

@Idan37S sorry for the lame question, but where should I find the file to do the above updates?

I'm using Home Assistant in a VM and I according some articles I should see components folder in my HA root, but I don't :(

I want to integrate 2 Cascade ACs. With the Gree+ mobile app both were recognized without any issue so I'm pretty puzzled with this. I thought the failed discovery would be logged somewhere, but I cant see it. Since the integration won't get added I'm not sure where could I see logs / further settings... if there is any.

I already changed network settings as mentioned by @gszigethy in his [comment](the https://github.com/home-assistant/core/issues/69351#issuecomment-1207812857) and I also have avahi docker to relay mdns between my VLANs. Ping works fine, ports are open, but no luck with the discovery :(

[cmroche]

Gree devices don't use MDNS, they use UDP broadcast. You will need a broadcast relay, and to configure managed switches (or other network equipment that might be blocking broadcast) to allow the traffic to pass.

[Tamas-Toth-ebola]

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))

@Idan37S sorry for the lame question, but where should I find the file to do the above updates?

I'm using Home Assistant in a VM and I according some articles I should see components folder in my HA root, but I don't :(

I want to integrate 2 Cascade ACs. With the Gree+ mobile app both were recognized without any issue so I'm pretty puzzled with this. I thought the failed discovery would be logged somewhere, but I cant see it. Since the integration won't get added I'm not sure where could I see logs / further settings... if there is any.

I already changed network settings as mentioned by @gszigethy in his [comment](the #69351 (comment)) and I also have avahi docker to relay mdns between my VLANs. Ping works fine, ports are open, but no luck with the discovery :(

Hi @monghuz !

Sorry for the late answer, but I did not have any time for it yet, while sadly I think my answer will not perfect enough for you, as I use HA through my own managed Docker containers, instead of discrete VM-s. As I wrote before, we have to...

Just to report my current state about the 'incorrect' auto-discovery, I had oursorced the greeclimate Python package of my HA installation as a Docker volume, modified the discovery.py files corresponding line...

...so..., based on that, theoretically in any type of HA installations there should be a directory where the corresponding 3rd party Python packages are. The file you should modify is not a HA file, but a greeclimate Python package which used by HA. If you could find a greeclimate directory in your installation (should be at something like: /usr/local/lib/python3.10/site-packages/greeclimate/), that is the directory which stores the 3rd party Python package and which package contains the mentioned discovery.py.

Almost at the end of the file, in the search_on_interface function definition you will find the required line, which have to be changed.

I hope it could help you.

[zevele]

Hi I'm having the same issue with my 3 Gree ACs. I've tried assigning them static IP and edit discovery.py as suggested here. But I'm still experiencing this issue they are randomly "unavailable" from time to time. Unlike before the period of them being "unavailable" is exactly 1 minute (I guess this is the delay between running the search_on_interface function. I cannot do the other solution suggested here (changing the setting under the Network setting menu) because I get empty page with my version. I'm running the latest home assistant core addition on an old RPI. BTW, the mentioned files on my installation are located under: ~/.local/lib/python3.10/site-packages/greeclimate/ Any ideas what else can I do to solve this?

p.s. I'm connected using wifi and I have a single local network

[parski]

The problem was fixed for me in 1.3.0.

I have two Innova IGZL09NI-1 and one other Innova with a model number I can't see when it's mounted but it's marketed as a Titanium 12.

Just wanted to loop back after having tested it for like half a year.

[maciejtarmas]

Any ideas what else can I do to solve this?

Yes. You probably blocked your units off from the internet and they're trying hard to phone home and failing. After a couple of days they will reset their network settings to factory.

You need this:

https://github.com/emtek-at/GreeAC-DummyServer

Than you need to redirect the requests to your fake server. Easy to do if you're running PiHole or AdGuard Home in your network.

[zevele]

Thanks @parski and @maciejtarmas I have the latest update on the units (it is Tadiran branded so I don't know the exact version - but it's the latest suggested by the app). The units aren't blocked from the internet and I can still access them through their application. Even when I'm away from home so it must be through their server. So I don't think that's the problem.

[maciejtarmas]

@zevele

It still looks like your units are trying to ping the Gree server and somehow failing. My 3 Cooper&Hunter units started doing the unavailable thing at 2 minute intervals I believe exactly 24 hours after I cut their internet access off. Providing them with a local fake Gree server and redirecting the requests was what fixed the issue for me.

[zevele]

I've found that the gree integration has a constant defining DISCOVERY_TIMEOUT and MAX_ERRORS (according to the code exactly for this kind of problem - # Under normal conditions GREE units timeout every once in a while), under ~/.local/lib/python3.10/site-packages/homeassistant/components/gree/const.py. They are used in _async_update_data function (in bridge.py). I tried to increase them, but it doesn't seem to have any effect on the issue - however, I'm not sure what is the side effect of increasing these values and I'm not sure my changes are really imported into Home Assistant - can anyone confirm this?

[Revo7]

Same here, timeout home-assistant_gree_2023-03-03T12-41-25.247Z.log

when i "refresh integration" the sinclair (gree hw) ac are restarting wifi (renew connection to the wifi network), static IP (dhcp reservation), always the same ip. the problem are starting in this year, in 2022 are working perfectly.

[zevele]

Editing of the integration files as suggested here, does not seem to have any effect (not for me)- I think for it to work, you have to copy the integration file to the custom integration folder and override the original integration. I Didn't try that. But what eventually sort of worked for me (at least for the past few days) is adding an automation that is triggered when any of the AC becomes unavailable and reloads the Gree integration. The result is that there is no period of unavailable state in the dashboard (there is still a log entry). At least not something I could observed. As I wrote in a previous post - before that I would get a one minute (exactly) period where the device was unavailable in HA.

Here's the integration if anyone is interested:

trigger:
  - platform: state
    entity_id:
      - climate.ac1
      - climate.ac2
    to: unavailable
condition: []
action:
  - service: homeassistant.reload_config_entry
    data: {}
    target:
      entity_id: climate.ac1
mode: single

[ic-dev21]

Same problem. I've been trying to reach the home assistant files with my docker installation to disable broadcast and go straight to the IP but I am unable to get to them.

How do I get there? ~/.local/lib/python3.10/site-packages/homeassistant/components/gree/const.py

[randavidovitz]

Same issue for months, I have 6-8 devices btw

Anyone was able to permanently resolve it ?

[issue-triage-workflows[bot]]

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]

Still an issue.

Le dim. 9 juill. 2023 à 14:07, 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 https://github.com/home-assistant/core/issues/69351#issuecomment-1627786348, or unsubscribe https://github.com/notifications/unsubscribe-auth/AZZGCFMQKQSFT4RA5HI6UP3XPLXMXANCNFSM5SS44KQQ . You are receiving this because you commented.Message ID: @.***>

[gszigethy]

The multi-VLAN setup works as of pfSense CE 2.7.0 using the udpbroadcastrelay package.

Once you've installed the package, go to Services / UDP Broadcast Relay.

1. Add instance button on the bottom right.
2. Check Enable this instance.
3. Description: Gree or something you'll recognize later.
4. Network interfaces: pick at least two, the one where Home Assistant is and the other where the aircos are.
5. Spoof source: keep original.
6. Instance id: 1 (or anything that is still available for you).
7. Destination port: 7000
8. IP address: empty.
9. Save.
10. Enable the UDP broadcast relay service on the top.

Go to firewall rules and create a new rule. Action: pass interface: the ones the aircos use address family: ipv4 proto: UDP source: the ip address of the airco (or the alias if multiple aircos - in this case you need to create an alias with the airco IPs). source port: 7000 destination: your home asisstant ip dest port: any description: gree AC broadcast Save, reload the rules.

In home assistant reload gree integration or restart HA.

I have 6 ACs, they started to work immediately.

[CIURI86]

The strange thing is that even if you have an HA network adapter in the same subnet the UDP broadcast leaves from the one with default GW set. In my situation the problem was that I had some shelly devices that where offline (blow up a while ago) and the discovery failed on those and seems affecting also the GREE plugin.

In my case I had only one AC offline and I deleted everything , even reset the WIFI adapter on the AC and re-enrolled the device in the cloud. The discovery was not detecting the former unavailable device at all only worked after I deleted the Shelly's that were offline. Strange situation but this is my case. This was happening only for one device out of 4.

[RonGroen]

greeclimate works find with HA 2023.1.7 and greeclimate 1.3.0 It does not run (1.4.1) with HA 2023.6.1 or HA 2023.7.3 editing the core files is too complex. How to solve this? It broadcasts the {"t":"scan"} message, but is does not find any devices (while HA 2023.1.7 and greeclimate 1.3.0 finds it)

Problem solved, UFW blocked it. sudo ufw allow 7000 ## did not work sudo ufw allow 7000/udf ## did not work sudo ufw allow out 7000/udp ## did not work sudo ufw disable ## did, but is not a very nice solution Any suggestions?

[hellcry37]

Can anyone take this and fix it please? For me the unavailable issue happens at random times or when I restart home assistant but not on every restart.

[mfriik]

Hi Everyone, I think most cases for these issue are hardware related(I might be wrong because of personal experience ;) ). I spent ridiculous amount of time trying to fix this on software and networking level. I tried setting up my own fake gree server, but in the end it was faulty wifi module that for some reason kept disconnecting from my IOT wifi. I bought a new module on aliexpress connected it to wifi through app and the local control works stably now since 1 month ago. No unavailable status and/or downtime. Just a friendly advice to save you some time if you think you tried everything check the hardware :)

[hellcry37]

For me the weird issue is happening sometimes when I restart Home Assistant, integration devices come as unavailable. I have 2 Gree AC units both brand new, 1 month old so I doubt is the HW.

I should mention after restart when this happens, I do an integration reload, they load and work as intended.

[Buster14]

Hi Everyone, I think most cases for these issue are hardware related(I might be wrong because of personal experience ;) ). I spent ridiculous amount of time trying to fix this on software and networking level. I tried setting up my own fake gree server, but in the end it was faulty wifi module that for some reason kept disconnecting from my IOT wifi. I bought a new module on aliexpress connected it to wifi through app and the local control works stably now since 1 month ago. No unavailable status and/or downtime. Just a friendly advice to save you some time if you think you tried everything check the hardware :)

Hi Mrfriik, are you referring to wifi AP or wifi module on gree aircon? Im thinking of getting gree since daikin is too expensive and unlike gree it doesnt come with wifi module.(although i have 2 daikins with wifi module and the connection is stable to HA)

[hellcry37]

gree works good, there is ocazional dc but they are short and nothing to worry about, gree is a good choice.

[mfriik]

Hi Everyone, I think most cases for these issue are hardware related(I might be wrong because of personal experience ;) ). I spent ridiculous amount of time trying to fix this on software and networking level. I tried setting up my own fake gree server, but in the end it was faulty wifi module that for some reason kept disconnecting from my IOT wifi. I bought a new module on aliexpress connected it to wifi through app and the local control works stably now since 1 month ago. No unavailable status and/or downtime. Just a friendly advice to save you some time if you think you tried everything check the hardware :)

Hi Mrfriik, are you referring to wifi AP or wifi module on gree aircon? Im thinking of getting gree since daikin is too expensive and unlike gree it doesnt come with wifi module.(although i have 2 daikins with wifi module and the connection is stable to HA)

My issues was with the module directly connected on the AC Unit, I needed to replace the WiFi Module on the Split unit inside the house as it was disconnecting every 15-60 min and most of the time it couldn't connect back to my home WiFi. But experiences may vary.

[MichalBury]

Hello,

is there some Software solution for this?

I have the same problem. I have eight AC from Sinclair. All of them were discovered without problem. Seven from them work without any problem, one gets "Timeout" randomly 1-30 minutes. Tried the same AC with NODERED and also see Connection Time-outs.

2023-11-07 07:03:01.185 WARNING (MainThread) [homeassistant.components.gree.bridge] Timeout send state update to: gree-c687b637 (Device: c687b637 @ 192.168.16.225:7000 (mac: 502cc687b637)) 2023-11-07 07:04:31.569 WARNING (MainThread) [homeassistant.components.gree.bridge] Timeout send state update to: gree-c687b637 (Device: c687b637 @ 192.168.16.225:7000 (mac: 502cc687b637)) 2023-11-07 07:08:19.708 WARNING (MainThread) [homeassistant.components.gree.bridge] Device is unavailable: gree-c687b637 (Device: c687b637 @ 192.168.16.225:7000 (mac: 502cc687b637)) 2023-11-07 07:08:19.708 ERROR (MainThread) [homeassistant.components.gree.bridge] Error fetching gree-c687b637 data: Device gree-c687b637 is unavailable 2023-11-07 07:12:29.708 WARNING (MainThread) [homeassistant.components.gree.bridge] Device is unavailable: gree-c687b637 (Device: c687b637 @ 192.168.16.225:7000 (mac: 502cc687b637)) 2023-11-07 07:12:29.708 ERROR (MainThread) [homeassistant.components.gree.bridge] Error fetching gree-c687b637 data: Device gree-c687b637 is unavailable 2023-11-07 07:14:39.708 WARNING (MainThread) [homeassistant.components.gree.bridge] Device is unavailable: gree-c687b637 (Device: c687b637 @ 192.168.16.225:7000 (mac: 502cc687b637)) 2023-11-07 07:14:39.708 ERROR (MainThread) [homeassistant.components.gree.bridge] Error fetching gree-c687b637 data: Device gree-c687b637 is unavailable 2023-11-07 07:25:49.709 WARNING (MainThread) [homeassistant.components.gree.bridge] Device is unavailable: gree-c687b637 (Device: c687b637 @ 192.168.16.225:7000 (mac: 502cc687b637)) 2023-11-07 07:25:49.709 ERROR (MainThread) [homeassistant.components.gree.bridge] Error fetching gree-c687b637 data: Device gree-c687b637 is unavailable 2023-11-07 07:27:59.708 WARNING (MainThread) [homeassistant.components.gree.bridge] Device is unavailable: gree-c687b637 (Device: c687b637 @ 192.168.16.225:7000 (mac: 502cc687b637)) 2023-11-07 07:27:59.708 ERROR (MainThread) [homeassistant.components.gree.bridge] Error fetching gree-c687b637 data: Device gree-c687b637 is unavailable 2023-11-07 07:36:09.708 WARNING (MainThread) [homeassistant.components.gree.bridge] Device is unavailable: gree-c687b637 (Device: c687b637 @ 192.168.16.225:7000 (mac: 502cc687b637)) 2023-11-07 07:36:09.708 ERROR (MainThread) [homeassistant.components.gree.bridge] Error fetching gree-c687b637 data: Device gree-c687b637 is unavailable 2023-11-07 07:48:19.709 WARNING (MainThread) [homeassistant.components.gree.bridge] Device is unavailable: gree-c687b637 (Device: c687b637 @ 192.168.16.225:7000 (mac: 502cc687b637)) 2023-11-07 07:48:19.709 ERROR (MainThread) [homeassistant.components.gree.bridge] Error fetching gree-c687b637 data: Device gree-c687b637 is unavailable 2023-11-07 07:48:23.530 WARNING (MainThread) [homeassistant.components.gree.bridge] Timeout send state update to: gree-c687b637 (Device: c687b637 @ 192.168.16.225:7000 (mac: 502cc687b637)) 2023-11-07 07:48:26.232 WARNING (MainThread) [homeassistant.components.gree.bridge] Timeout send state update to: gree-c687b637 (Device: c687b637 @ 192.168.16.225:7000 (mac: 502cc687b637)) 2023-11-07 07:48:27.843 WARNING (MainThread) [homeassistant.components.gree.bridge] Timeout send state update to: gree-c687b637 (Device: c687b637 @ 192.168.16.225:7000 (mac: 502cc687b637)) 2023-11-07 07:48:59.802 ERROR (MainThread) [homeassistant.components.ipp.coordinator] Error fetching ipp data: Invalid response from API: Error occurred while communicating with IPP server. 2023-11-07 07:54:29.708 WARNING (MainThread) [homeassistant.components.gree.bridge] Device is unavailable: gree-c687b637 (Device: c687b637 @ 192.168.16.225:7000 (mac: 502cc687b637)) 2023-11-07 07:54:29.708 ERROR (MainThread) [homeassistant.components.gree.bridge] Error fetching gree-c687b637 data: Device gree-c687b637 is unavailable 2023-11-07 08:03:39.707 WARNING (MainThread) [homeassistant.components.gree.bridge] Device is unavailable: gree-c687b637 (Device: c687b637 @ 192.168.16.225:7000 (mac: 502cc687b637)) 2023-11-07 08:03:39.707 ERROR (MainThread) [homeassistant.components.gree.bridge] Error fetching gree-c687b637 data: Device gree-c687b637 is unavailable 2023-11-07 08:14:59.708 WARNING (MainThread) [homeassistant.components.gree.bridge] Device is unavailable: gree-c687b637 (Device: c687b637 @ 192.168.16.225:7000 (mac: 502cc687b637)) 2023-11-07 08:14:59.708 ERROR (MainThread) [homeassistant.components.gree.bridge] Error fetching gree-c687b637 data: Device gree-c687b637 is unavailable

[defaultsecurity]

For me the weird issue is happening sometimes when I restart Home Assistant, integration devices come as unavailable. I have 2 Gree AC units both brand new, 1 month old so I doubt is the HW.

I should mention after restart when this happens, I do an integration reload, they load and work as intended.

Mine stay unavailable after restart for 6 hours or even more. Integration reload does not help. There should be an option for direct IP connect in addition to default broadcast packet method.