I CANT CONNECT TO GREE CLIVA ON HOME ASSISTANT

[FloreaIonut]

The integration see the ac gree, but he cant finish setup.
I have all upgrade .
On my phone all works very good, but on home assistant nothink.

[SkilledITAUS]

What version is the Firmware on the Aircon? I am having the same issue with firmware version 3.10

[RobHofmann]

Unfortunately timeout errors is something we can't fix. Closing this issue due to duplicates.

[SkilledITAUS]

Rob, what would cause the time out error occurring?
The device is on the network and working fine but this error comes up. It also only appears to be happening with some newer versions for the WiFi Card

[RobHofmann]

Honestly, a lot. This is what makes this the most difficult issue.

Amongst others:

• Network connectivity problems: Socket timeouts or failure to reach the device over the local network, often due to firewall blocks, WiFi instability, or IP changes.
• Device power or reset needed: Unplugging and replugging the AC unit resolves communication glitches, forcing a fresh connection.
• Incorrect encryption key: Key mismatch if the Gree app was used first for remote control, requiring key extraction or reset.
• Firmware incompatibility: Recent device firmware updates that alter protocol support for sensors like outside temperature.
• Internet access interference: Device attempting cloud connections, causing instability if blocked; ensure local-only comms.
• Home Assistant version mismatch: Component not fully compatible with latest HA releases, leading to sensor errors during setup.
• Apparently theres "cloud only" gree devices which don't work with local communication at all (https://github.com/roldengarm/homeassistant-gree-cloud)
• Some devices do have port 7000 open but dont accept any commands (Gree (tosot) app 1.24.1.13 +fw v1.43 +remote wired XE7A-24 controller #392 (comment)).

I can keep going, but the thing is: Posting this error says nothing. The only valuable thing here would be someone that has this error actually debugging the issue locally on his side. Until that happens, I can't do anything with the waterfall of these types of issues that are being created.

[iofo1311-ai]

Thanks, that makes sense.

I agree that the timeout by itself is too generic to be actionable. What seems relevant in my case is that I have three very similar Toyotomi/Gree units in the same network and environment, and only the larger GTN/GTG-24CMW fails, while the two GTN/GTG-09CMW units work fine with local communication.

The main difference I found in the cloud data is:

failing unit: ver: V3.2.M, hid: ''
working units: ver: V3.4.M, hid: '362001065279+U-WB05RT13V1.28.bin'

So my current suspicion is that this is not just a generic network timeout, but a model / Wi-Fi module / firmware-specific difference, or possibly a cloud-only / partially local-only variant.

I’m happy to help debug this locally. If useful, I can provide:

full debug logs from the integration
packet captures from Home Assistant to the unit on port 7000
side-by-side data from a working 09CMW and the failing 24CMW
confirmation of power-cycle / re-pair / key re-extraction tests

If you tell me exactly what data would be most useful, I can collect it.

[RobHofmann]

I understand your point of view, but even if I would have all that information it would be still impossible for me to debug & test a potential solution.

The only reasonable path I see here is that someone actually modifies the current code until it works on his/her device and then creates a Pull Request to this repository with that working version (while maintaining backwards compatibility with the current situation).