¶ Integration Note
| Manufacturer | Gree Electric Appliances — including rebrands: Tosot, Cooper & Hunter, Trane (ductless), Innova, Tadiran, Sinclair, Heiwa, Proklima, Lessar, Wilfa |
|---|---|
| Model | Any Gree Smart air conditioner or heat pump that works in the Gree+ app (also sold as EWPE Smart) |
| Driver Name | MagicCubeClimatePro / MagicCubeClimatePro-Dark |
| Driver Version | 26.09.22.00 |
| ELAN Platform Value | gree_cloud (cloud) | gree (local) |
| Magic Cube Integration | Gree Climate Cloud (HACS) v1.5.0 | Gree Climate (built-in) |
| Document Revision | Oct 9, 2026 |
| Core Min / Max Tested | 8.8.xx |
¶ Overview
Gree air conditioners can reach Magic Cube two different ways. Which one you need is decided by the AC's Wi-Fi module firmware, not by preference. Read this section before you install anything — picking the wrong path is the single most common cause of "Gree won't find my units".
¶ Which path do I need?
Local — gree | Cloud — gree_cloud | |
|---|---|---|
| Transport | UDP port 7000 on the LAN | Gree cloud MQTT over the internet |
| Works when | Module firmware still supports the local protocol | Always, as long as the unit works in Gree+ |
| Internet required | No | Yes |
| Response time | Fast | Up to 60 s (cloud poll interval) |
| ELAN Platform field | gree | gree_cloud |
Rule of thumb: try the local Gree integration first. If it finds every unit, either path works. If it misses even one unit, put the whole site on gree_cloud — local control uses a single port with no fallback, so a unit that does not answer it cannot be rescued by a different local driver or custom component.
¶ Supported Features
- Two-way control and feedback for every Gree unit in the Gree+ account
- Auto-discovery of all units — no per-unit IP address or MAC entry
- Cool, Heat, Dry, Fan Only and Auto modes
- Target temperature with correct °F / °C handling
- Fan speed, including medium-low and medium-high where the unit reports them
- Option switches: Panel Light, Quiet, Fresh Air, X-Fan, Health Mode
- Energy and compressor sensors where the unit reports them
- Gree WHIO hot water heat pumps (water heater entity)
- Mix and match with any other Magic Cube climate platform in the same ELAN driver
¶ Prerequisites
- Every AC already added to a single Gree+ account and reachable in the app
- The Gree+ account e-mail / username and password
- The correct cloud region — this must match the region the account was created in, or login fails with no useful error
- Magic Cube with internet access and HACS installed
¶ Cloud regions
Australia · China Mainland · East South Asia · Europe · India · Latin American · Middle East · North American · Russia · South American
¶ Part 1 — Install in Magic Cube
The cloud integration is distributed through HACS so it receives update notifications. Install it as a custom repository.
davo22/homeassistant-gree-cloud Type: Integration → Add.¶ Part 2 — Configure in ELAN
Add the Magic Cube Climate Pro communication device as usual, then set the platform fields as shown.
8123Other from the dropdown. Other Platform: type gree_cloud — lower case, with the underscore.
gree_cloud for the cloud integration and gree for the local one. Do not enter a brand name such as "Gree", "GREE" or "Tosot" — the driver will not match anything. If your platform is not listed, contact support@innovo.net before entering any value.
¶ Field reference
| Field | Value |
|---|---|
| Type | Ethernet |
| IP Address | Magic Cube IP address |
| Port | 8123 |
| Platform | Other |
| Other Platform | gree_cloud |
| Setpoint Upper / Lower Limit | Off, unless the site requires clamping |
| Setpoint Timeout (Sec) | 3 |
| Disable UI Update | Unchecked |
¶ Part 3 — Verification
Confirm all three layers before leaving site:
- Magic Cube — one climate entity per AC, each showing a sensible room temperature and setpoint, none showing
unavailable. - ELAN — every zone present on the Climate page with current and target temperature.
- Round trip — change a setpoint in ELAN, confirm it lands at the wall controller; change it at the wall, confirm ELAN follows within 60 seconds.
¶ Troubleshooting
¶ "No devices found on the network" when adding the local Gree integration
First confirm the Magic Cube is on the same subnet as the air conditioners — local Gree discovery is a broadcast and will not cross subnets or VLANs, so a routed or mis-masked network finds nothing at all.
If the network is correct and the units are still not found, the firmware has dropped the local protocol. Use gree_cloud. Removing and re-adding the local integration will not help, and neither will a HACS alternative, because they all use the same single port.
¶ Only some units are found
Normal on a mixed site. Older units answer locally, newer replacements do not. Do not run local for some and cloud for others — put the whole site on gree_cloud so there is one source of truth and no duplicate zones.
¶ Units ping fine but never appear
Expected behaviour, not a network fault. The module answers ICMP from its TCP/IP stack while the Gree application listener is off. Ping and ARP prove only that the unit has an address — they say nothing about whether it will accept control. Use gree_cloud.
¶ Zones drop in and out / go unavailable
Gree modules handle effectively one control session at a time. Check for a second controller on the LAN — most often a phone running Gree+ or EWPE Smart, which broadcasts discovery packets to 255.255.255.255:7000 and re-binds the units out from under Magic Cube. Close the app, and make sure only one integration is polling.
¶ Temperatures read in the 100s (for example 181° or 185°)
Seen on the local gree integration at sites where the units are set to Fahrenheit. The entity starts with a Celsius default and only switches to Fahrenheit once the device's TemUn flag arrives in a poll. Until then the °F value is treated as °C and converted to °F a second time:
- 85 °F target → read as 85 °C → displayed as 185 °F
- 83 °F room → read as 83 °C → displayed as 181 °F
It appears on the first reading after a restart or after a unit recovers from unavailable, and normally corrects itself on the next successful poll. If that unit then stops polling, the wrong value sticks and is never flagged — the zone is not marked unavailable, it simply holds a confident, wrong reading. The cloud integration is not affected. This is another reason not to leave the local integration installed alongside the cloud one.
¶ Login fails when adding Gree Climate Cloud
Almost always the wrong region. Confirm which region the Gree+ account was created in and retry. Also confirm the account can actually see the units in the app — the integration sees exactly what Gree+ sees.
¶ Known Limitations
- Cloud path requires internet. If the site loses WAN, Gree zones stop responding. Local control is unaffected by WAN loss but is unavailable on newer firmware.
- Up to 60 seconds of feedback lag on the cloud path for changes made outside ELAN.
- One controller at a time. Leaving Gree+ open on a phone on the same LAN can destabilise local control.
- Gree does not expose a model string, so zones are identified by the name set in Gree+. Name the units meaningfully in the app before installing — those names flow straight through to ELAN.
¶ Support
When contacting support@innovo.net, include the Gree+ cloud region, whether every unit is visible and controllable in the Gree+ app, which units are missing in Magic Cube, and whether the Magic Cube shares a subnet with the air conditioners.