Official Honeywell evohome/Round Thermostat integration (EU-only)

Apologies, wrong end of the stick again.

I had thought that your question was specific to Evohome, I am not trying to control the boiler directly, I’m trying to control the Evohome controller. I have the Honeywell Evohome Essentials Pack ATP926G3001 with an ATC928G3000 controller. I want to be able to change the zones on the controller, the modes displayed in my controller are: Economy, Away, Day Off, Custom and Off.

1 Like

I’ve yet to look into Evohome integration in more detail (just using the sensor info in a dashboard so far) but this is something I’d like to be able to do myself at some point. So interested to see how this goes.

What’s the current state of this? Considering buying into evohome and looking at how best to control it.

Still works perfectly :wink:

1 Like

Confused… OP refers to RF control on GH but that’s a couple years old and there’s also another thread for it… Not interested in the cloud integration, only RF. Is that what this thread is?!

RF is here:
Honeywell CH/DHW via RF - evohome, sundial, hometronics, chronotherm - Share your Projects! - Home Assistant Community (home-assistant.io)

1 Like

Got it, thanks.

I’ve been trying to use the workaround for multiple locations at the same time, (WORKAROUND: two locations at same time · Issue #10 · zxdavb/evohome_cc_deprecated · GitHub), but I can’t seem to get it working. Anybody got an idea what’s wrong?

I think this workaround doesn’t work anymore, or I’m making some other mistakes… Can someone help?

I copied the 6 files ( init.py, climate.py, const.py, manifest.json, services.yaml, water_heater.py ) from GitHub ‘core/homeassistant/components/evohome/’ directory (core/homeassistant/components/evohome at dev · home-assistant/core · GitHub) to my new ‘custom_components/evohome_1/’ directory

I’ve figured out this already:

  1. const.py stores the variables, I changed the first variable DOMAIN = “evohome” to DOMAIN = “evohome_1”
  2. manifest.json change variable “domain”: “evohome” to “domain”: “evohome_1”
  3. manifest.json must have a version number, so I added “version”: “1.0.0”

But when I change in the configuration.yaml the entry ‘evohome’ to ‘evohome_1’ home assistant refuses to restart because “homeassistant.exceptions.HomeAssistantError: The system cannot restart because the configuration is not valid: Integration error: evohome_1 - Integration ‘evohome_1’ not found.”

I like to make an automation/script with te value from the target temperature.

When the target_heat_temperature is above 20 for example

I’m pretty new to HA and i think i have to make a custom sensor to work with target_heat_temperature
I found the below data from climate.merel. How can i use that in an auotmation?
It looks like i have to use something like…
climate.merel.?setpoint_status.target_heat_temparture ?

Anyone who can point me in the right direction?

hvac_modes:
  - 'off'
  - heat
min_temp: 5
max_temp: 21.5
preset_modes:
  - none
  - temporary
  - permanent
current_temperature: 20.4
temperature: 20
preset_mode: temporary
status:
  setpoints:
    this_sp_from: '2021-11-15T09:00:00+01:00'
    this_sp_temp: 12
    next_sp_from: '2021-11-15T23:00:00+01:00'
    next_sp_temp: 12
  zone_id: '1234567'
  active_faults: []
  setpoint_status:
    target_heat_temperature: 20
    setpoint_mode: TemporaryOverride
    until: '2021-11-15T23:10:00+01:00'
  temperature_status:
    temperature: 20
    is_available: true
friendly_name: Merel
icon: mdi:radiator
supported_features: 17

Use temperature, instead of target_heat_temperature - IIRC, they are essentially the same thing.

         value_template: >-
           {{ state_attr('climate.merel', 'temperature') }}
1 Like

@zxdavb Thanks, was easier than I thought. :blush:

Hi all,

Ive been using the round thermostat (and this intergration) for a while now and it always worked great. But latetely im having the following issue:

I use the “AutoWithEco” mode a lot for automations (when i leave the house, or at night) and set it back to “Auto” when i want heating to resume. This used to work great: The target tempature would automatically be set to whats current minus 3 degrees, and back to the target when mode became “Auto” again. But lately when setting the mode back to idle the temparature stays the same (whatever target was - 3 degrees). It does clear the mode (i can verify that in the honeywell app as well), so it does seem the automation and action are being sent correctly.

My entire heating setup is broken because I tried to change my password…

Just venting frustrations here about evo home / honneywell customer service…

  • 11 evo home thermostat + system costed me more than more than €1500 (including changing some old radiator fittings)
  • The radiator thermostat can never work by design since the heat of the radiator throws off the the heat sensor…
  • So I installed 11 small zigbee sensors (way cheaper than evo thermostats and they give me humidity readings)
  • Manually setup climate entities (with input buttons triggering automations since at the time it woudn’t work with the evo service… hours of drama)
  • I have 3 tablets controls in the house that shows the house (see below) - you see the thermostats in the big red/blue circles.
  • They are now just “decorations” since 4 days because evo api doesn’t work for me.

Last friday, I changed my Total Connect Comfort password for security. It corrupted my account - I only get Oops, an unexpected error has occurred. Please try again later.

Venting:
Their customer service is close on the weekend. (Really??? wtf?) Franctically tried to delete app, reinstall, change password again and so on. Nothing works. I created a new account and that worked. But I can’t migrate my current setup to that new one without contacting them… GRRRRR Called Monday morning, “it will be solved in a couple of days”. WTF??? Do this NOW, while I’m on the phone! How can that be? Told “migrate my system to new account then”. Supposed to get an email in the next 10 mins. 3 hours later, nothing. Called again. Then tell them I already know they need mac adress screenshot etc - so they give me the email I need to send my request to. We are now Tuesday and still nothing… So either they only have one persone in europe doing support, or they have so many bugs their teams is overwhelmed. How bloody simple can this be.

If you read that far and was thinking of buying evo home… Have your due dilligence on their customer support…

Big tip that may - or may not- help you: the TCC website appears to ‘escape’ certain non alphanumeric characters in a way the the RESTful API does not. This will manifest as:

  • you can log onto the TCC website
  • the evohome integration says authentication failed & to check your password

The only solution is to not use that special character.

Second tip: Have a look at this custom control.

You can run it alongside the evohome integration. It allows HA to work with evohome, without using the internet API at all, just local RF.

It allows for sensor faking, so that any temperature sensor can appear to the evohome controller as a evohome-compatible sensor.

All you need is a RF<–> USB dongle, approx £25, that can run the evofw3 firmware, although these ones are best.

1 Like

Thanks a lot. In the meantime, they un-coupled my first account so I was able to reinstall - all works again. You scared me with the special characters as I had a ! in my password but it worked on my side.
I got very curious and interested in the trail you gave me but I fear I’m not technically skilled enough to figure it all out - I coudn’t find any easy (newbie) instructions to follow - I mean “Arduino” is a scary word for me :wink:

Not all special characters, only some.

The evohome_rf integration isn’t as hard as you might think - just ask others on that forum what their experience has been…

Good luck.

I am trying to make 2 simple automations for my wife using an ikea on off button. I only have one zone for the whole house.

The first is to set the heat to 23 degrees (on) and the second to 5 degress (off).

When i use the button i feels that the thermostat gets stuck and i have to manually change the temperature on the evohome thermostat in order to unstuck it. Usually pressing the on button sets the zone override to 23 degrees but it does not set it to off (5).

Here are both my automations. Am i doing something wrong?

(On)

service: evohome.set_zone_override
data:
entity_id: climate.house
setpoint: 23

(Off)

service: evohome.set_zone_override
data:
setpoint: 5
entity_id: climate.house

This is driving me crazy as it should be a simple automation. Btw both automations show as completed when tracing them.

Maybe that’s an overkill but this is how it works on my side.

1) In my configuration.yaml I have a template switch:

- platform: template
  switches:
   warmergardenroom:
      turn_on:
      - service: climate.set_temperature
        data:
          temperature: 20.5
        entity_id: climate.garden_room
      turn_off:
      - service: climate.set_temperature
        data:
          temperature: 15
        entity_id: climate.garden_room

And then for the ikea switch I use a simple automation to turn on/off the switch that was created (switch.warmergardenroom)

addition…
Ok, afdter researching a bit, I realised I am not using the evo home service but the climate one. And it works on my side. Maybe try

service: climate.set_temperature
data:
entity_id: climate.house
setpoint: 23

Thanks a lot i will look into it.

I have same issue. Did you figure it out? I changed the permissions of the custom component files? What else did you try?