192.168.178.0/24 is the default IP range for Fritzbox routers. So probably not a guest network
Homey and ac are in same subnet, no client isolation.
It did work but I was so stupid to update firmware on the ac with the ewpe smart app (app still works)
Verzonden vanaf Outlook voor Android
@aivus Sinclair S-THERM heat pump with an EWPE Smart Wi-Fi wired controller. Homey Gree 1.2.0 discovers the device at 192.168.22.57, but it remains unavailable and returns no temperature or device name. EWPE Smart works correctly. Diagnostic report: a6d7f957-4db0-467d-a69a-befdc918f9b9
Exactly same problem here. After updating Wi-Fi module to 2.12 in Gree Airy, devices became unavailable in Homey, but still works in Gree official app.
@Fred_Schaap @keke @ozi1024 please ensure you are on v1.2.1 and send diagnostic report.
@Fac3 Usually ACs should be discovered by default. By adding the ACs by IPs you are just forcing the app to create a device with hardcoded IP. It helps bypass issues with discovery, when the Homey and ACs are in different IP subnetworks, but in case app cannot communicate with AC it will not help.
Try also send diagnostic report, I’ll take a look. Mention you nickname or describe the problem in the message
2all. Avoid firmware updates of WiFi module
Hi everyone,
I am experiencing the same issue with my Gree units and wanted to share my observations.
After updating to the official v2.12 (v2.12+) firmware, the connection to two of my Gree Smart One units completely dropped in Homey (showing offline/timeout status), while my third unit, which has not been updated, continues to work flawlessly and stably through Homey. (Also, a new feature appeared in the official Gree app on the updated units: the ability to turn the device beep sound on or off).
While researching online, I came across the following technical explanation that perfectly describes the issue:
The Gree firmware 2.12 (v2.12+) software update refreshes the operation of the air conditioners’ built-in Wi-Fi module. This version improves the security and stability of the cloud connection, but it closes the local UDP port (port 7000), causing smart home systems (like Home Assistant) to lose local connectivity with the air conditioner. The update has no effect on the mechanical cooling or heating performance of the AC.
Similar issues have been reported in other smart home communities (such as Home Assistant) following the latest Gree updates.
Does anyone have any ideas, or is there any workaround / alternative method expected from the developers to restore local communication or introduce cloud API support?
@aivus Thanks for response, report id is ea35e66a-fed2-4904-9a5b-9fbdab479fb4
Halo @aivus ,
any news ?
@aivus Hi. Hoping you can help. Trying to connect to my Wilfa Chill 12 Connected, but can only add the device by entering the ip manually. Shows as not available.
Report id: ea9f7e58-11a7-489a-b2a5-9212ef42f1a0
My Gree GUD100PHS1/A-S U-Match (commercial/VRF, behind an XE7A-24/HC wired zone controller) never worked with this app — showed unavailable, same symptom others here have reported for similar commercial-class units.
Turns out these units don’t use the consumer Gree+ cloud MQTT broker (mqtt-eu.gree.com:1984) at all — which is what this app, and every open-source Gree library I found, assumes. After reverse-engineering the real GREE+ app’s own traffic:
- It calls an endpoint that’s in no reference implementation:
POST /App/QueryOnline(same regional host as login, e.g.eugrih.gree.comfor Europe), passing the device MAC(s). Returns, per device:{ "svr": "eu05.as.gree.com:16385", "isSSL": false } - That host:port isn’t an MQTT broker — it’s a bare TCP socket, one request at a time: open, write one newline-terminated JSON line, read one back, close. No subscribe, no session.
- The JSON envelope (
pack/i/cid/uid/tcid/t) is identical to the consumer MQTT message shape, andpackuses the same AES encryption (CipherV1/CipherV2). Only the transport differs — login, ciphers, property codes all carry straight over.
One more thing specific to this hardware class: it can show up twice in the device list under the same key — one MAC ending in 00, one not. Only the 00 one responds to commands.
Built a driver against this and it’s been running solidly. @aivus — happy to share the discovery + raw-socket transport code if you want proper commercial/VRF support in the official app, rather than everyone with this hardware having to DIY it. Let me know.
Hope this helps whoever else is stuck on a commercial unit. With thanks to my friend Claude 
Hello, my Gree AC can be added manually with IP 192.168.1.38, but afterwards it stays offline / “No response”.
GREE+ app works normally.
AC firmware: V1.38
Homey Gree app: 1.2.1
Homey and AC are on the same network.
Power cycling the AC did not help.
Diagnostic code: d27fe1bd-c93c-4030-8591-25b974ac2970
Please report your issue in the app topic:
Its the issue most of us face here. Gree changed the way it communicates with their own App. If you look into my post, this contains the end points you need. But they are not worked into the driver by @aivus (yet)
