Unable to connect to the device. Please check the network connection and try again.

[mbulles]

I am unable to connect to my Gree ACs via HA using this integration.

I am using Gree Multi Inverter / Lomo [ info from the Gree App];
Model 1001
Firmware 3.75
Modelversion v19.4
The ACs do work via the Gree App without any issues.

The AC's have worked in the past but I have moved them into a different VLAN.
I am able from the HA Terminal window on the HA box the ping the ACs.
There is no Firewall currently deployed between the VLANS or any other restrictions.

I was able to pull the necessary information

✅ Login Successful!
User ID: 1399XXX
Token: 8776aXXXXXXXXXX

🏡 Homes Found:

🏠 Thuis (Home ID: 130XXXX)

• Devices:
  • Name: Airco XXX
    MAC: f491XXXXXXXX
    Key: Qr8Tu1WxXXXXXXXX

However when either automatically or manually trying to add the device it is not found and the error is shown.
"Unable to connect to the device. Please check the network connection and try again." will appear.

Is the Encryption key considered the "Key" value?
Is the UID value considered the "User ID" value"?
Just to make sure I have the right field mapping.

Further help is appreciated.
Thanks.

[p-monteiro]

Key is the Encryption key; UID is not the User ID and is probably 0.

Can you enable debug logging on the integration page, try adding the device or triggering the error, and then post the full log here?

[p-monteiro]

@ChillingSilence I believe this is the same problem as yours. Check #406

@mbulles did this integration ever worked for your unit?

[mbulles]

Hi, as mentioned it did in the past when everything was in the flat network not separated by vlans. I will try do a tcpdump first on the HA host and enable debug logging. Otherwise I'll move 1 unit back into my default vlan [1] to see if that makes any difference. Thanks for all the replies so far. Op wo 18 mrt 2026, 23:32 schreef Pedro Monteiro ***@***.***>:

…

*p-monteiro* left a comment (RobHofmann/HomeAssistant-GreeClimateComponent#422) <#422 (comment)> @ChillingSilence <https://github.com/ChillingSilence> I believe this is the same problem as yours. @mbulles <https://github.com/mbulles> did this integration ever worked for your unit? — Reply to this email directly, view it on GitHub <#422 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AMWJRMCIIYXVPAQXXSHOLND4RMPZFAVCNFSM6AAAAACWU3IYJGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DAOBVHE4DOMZYHA> . You are receiving this because you were mentioned.Message ID: <RobHofmann/HomeAssistant-GreeClimateComponent/issues/422/4085987388@ github.com>

[ChillingSilence]

Looks like it @p-monteiro !
You mentioned:

It's performing the normal {"t":"scan"} broadcast. What is the device sending back after those?
src: 192.168.22.120 dst: 192.168.22.86

There was no response sadly. It seems .86 was the mobile device, but there was nothing returned from the AC on .120.
I'm not entirely sure what to do next 🤷‍♂️

[ChillingSilence]

My device is similar to @mbulles :

Firmware update: V3.10
Model ID: 10001
Model Version: V19.4

[p-monteiro]

Check if there are packets being sent to the device at all when you change any option in the Gree app.

[p-monteiro]

Ok, unfortunately, it seems like you are out of luck for now: see this

[ChillingSilence]

It seems you're right @p-monteiro , that's a shame but also thanks heaps for investigating!

[mbulles]

Hi, I even noticed that after upgrading to the latest Gree Firmware 3.75 I am no longer able to register the AC using the Gree App client on Android or iOS. It always runs stuck at 69%.
Does anyone else experience the same, as with a previous version FW, can't remember the exact version it did work, even on a different vlan.
I took a pcap during the registration between the mobile AC Gree client 192.168,1.32 and the Gree Cloud Server 63.183.151.51
PCAP is attached and compressed with ZIP.

greedump.zip