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!
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:
Once all that’s in place, the climate entity will show the relevant HVAC modes (Heat, Cool, Auto).
I have now joined you in the econext world, after some frantic button clicking to swap all dashboards to the new entities 
it’s working great so far @LeeNuss - thanks! I’ll update as I find out more 
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:
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
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
yes great idea that is definitely possible. I’ve just added this, just need to test it a bit more thoroughly. Will post some instructions on how to configure this once I’m confident it works well
@MrW I finally got around to finishing the virtual thermostat support, needed a bigger rewrite to work reliable. Tested this for several days now without any issues. I’ve just published a beta for it:
To install it re-run the bootstrap with --pre:
curl -fsSL https://raw.githubusercontent.com/LeeNuss/econext-gateway/main/deploy/bootstrap.sh | sudo bash -s -- --pre
Also bump the HA integration to v0.1.1 (update should show up automatically in Homeassistant).
Setup:
> to confirm on the panel. The HA “State” entity should switch to “Paired (addr XYZ)”.The virtual thermostat coexists fine with a real ecoSTER on a different circuit. If HA stops sending updates for more than 5 minutes the gateway falls back to a fixed value (default 19 C, configurable) so the heat pump never sees stale data.
If anyone tries this and runs into issues please open a GitHub issue on either repo so I can track them.
Thanks so much for making this excellent gateway code and HA integration @LeeNuss . It’s very well thought out and really effective. I run the gateway on a Raspberry Pi Zero 2.
The thermostat feature is interesting and I have tested it as working with my system. Do you think it is possible to use a virtual thermostat in place of the outdoor temp sensor in the heat pump? Mine has very inaccurate readings in the evening when the sun shines on the heat pump.
Unfortunately that’s not possible, as this comes directly from the controller and not the api. I had the same issue and installed a Grant Smart Outdoor Sensor on the north side, away from direct sunlight which sorted that issue.
I thought so. I’ll have to get the external sensor then.
A minor point, but remember to site it well away from the effects of cold air circulation from the evaporator. Even though my HP (a Samsung) is on an elevated platform, the OAT sensor - located inside the outdoor unit chassis - dips by up to 2degC whenever the HP starts, so distorts the weather compensator.
@LeeNuss What an absolutely fabulous integration this is.
I eventually got myself a Raspberry pi Zero 2W, followed your instructions & got it fairly painlessly set up. Loaded the Home Assistant integration & everything appeared. Thank you so much for your time & effort to get this to its current state.
