Econext: Direct local control of Grant HP290 Econet replacement (Plum ecoMAX360i)

I can’t see to see an option in the HA integration to change the work mode of the Circuit e.g Day (comfort), Night (Eco), Auto or Boost. Do you think this is something that could be added? The ability to set the day/night schedule is already available via the HA schedule car.

I’ve also noticed a number of cooling options in the HA integration. I think I’m correct that the Grant HP290 heat pump doesn’t support cooling (yet?!). Or have you been able to get cooling to work?

I think the hardware supports it and it’s simply unable to be controlled by by the software!

1 Like

The work mode is already available in the integration - it’s exposed as preset modes on the climate entity for each circuit:
Comfort = Day mode
Eco = Night mode
Schedule = Auto
Boost isn’t supported by the HA integration yet - I’ll add that in.

afaik the grant 290 does support cooling! There are a few things that need to be in place though:

  • Cooling support needs to be enabled for the heatpump. Either in the HA integration or via the 0000 service menu → Main heat source → Cooling support
  • Circuit type must be set to either UFH or Fan Coil - radiator circuits don’t support cooling. (min cooling temp is 18C for UFH, ~7C for fan coil)
  • Cooling needs to be enabled per circuit - each circuit has its own cooling enable switch
  • Operating mode needs to be set to Summer, or set to Auto with the outdoor temp above the summer threshold

Once all that’s in place, the climate entity will show the relevant HVAC modes (Heat, Cool, Auto).

Ah it took me a while to find this, it’s under the thermostat option, nice!

That’s cool, I’ll give it a try when the weather warms up a bit! Although from my past experiments, using cooling with radiators is pointless

I have now joined you in the econext world, after some frantic button clicking to swap all dashboards to the new entities :smiley: it’s working great so far @LeeNuss - thanks! I’ll update as I find out more :slight_smile:

1 Like

I see this occasionally in my logs, just me or is it fairly common?

Mar 13 16:18:53 emonhp uvicorn[2288]: 2026-03-13 16:18:53 [WARNING] econext_gateway.serial.protocol: Invalid END marker 0x00, discarding BEGIN marker

Also I notice coil temperature replicates what it did in econet24 (makes sense, obviously!) in that it goes high when it should be low, like this:

image

It went from 0.3 to 6553.4, so I’m thinking - is this an unsigned 16-bit int divided by 10 and it wraps when it goes negative? If so, wondering if this should be something we fix with a HA template or fix in the gateway?

Logic I guess being:

raw = displayed * 10

if raw >= 32768:
    raw = raw - 65536

final = raw / 10

Something like?

that’s normal, just the occasional hiccup in the parser confusing some bus traffic for a frame start marker, then discards it after.

yes good spot! I’ll rework this and add to the next release :slight_smile:

I had a good thought this morning - I believe the internal remote thermostat (the white one) uses the same GAZ-MODEM3 protocol that econext now talks, so would it therefore be possible to emulate a thermostat? Reason I ask is because I have aqara temp sensors all over my house and I take a room-size (m3) based average, so e.g. the larger kitchen has more influence over the average than a small toilet.

If econext could be a “virtual thermostat” this would be fantastic, e.g. home assistant submits the temperaterure reading to it and it simply passes on to the controller. That way my “thermostat” temperature is a whole house one.

Looks like there’s a GM3 integration on HACS: GitHub - lachand/plum_ecomax: Integration for Plum Gaz Modem 3 protocol · GitHub

From what I can tell that’s for a device which does pure conversion to RS485