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

[Marcel_St (Marcel Stangenberger)]

I’ll try that, thanks!

update, that worked instantly, thanks again!

[SIW1973 (Simon Williams)]

Hi there, firstly thanks for the great work ! I’m taking my first steps on a Smartthings to HA migration due to the ongoing work Samsung are doing on ensuring that my home automation will slowly start to collapse over time !

I’m learning a lot and having the usual ongoing Google search, try, smash head against brick wall and then repeat…again…and again…

I’ve set up Evohome Zone Boost Automations, which took a while to get the required 30 minute duration, rather than the default next set point. This involved using Duration and Minutes Data points.

I’ve now spent time trying to get the DHW to turn on and off, but I couldn’t get either water_heater.turn_on or water_heater.set_operation_mode to accept a Duration… water_heater.turn_on defaults to Permanent and water_heater.set_operation_mode defaults to the next setpoint.

I do know that the Evohome API can accept a Duration on the DHW in some shape or form as it’s possible on the existing Smartthings Integration by @andremain , who coincidentally has moved to HA so hopefully could advise on the Evohome API parameters !!

If you could look at this it would be great !

[sashaz]

To be able to show a room as being heated, which state should I look at? I want to change the room icon colour to show that the thermostat is on and giving heat.
I could just assume that the room temperature is lower than the set temperature but I think that is not the best solution.

[zxdavb (David Bonnes)]

There is no way to do this with the web-based (i.e. using the REST API) integration.

I did have something similar to you thinking - it was unsatisfactory and so was removed.

However, for the sake of a £35 dongle (cheaper if you make it yourself), you can get heat demand per zone:

• Honeywell CH/DHW via RF - evohome, sundial, hometronics, chronotherm

Beware - the heat demand per zone will tell you what teh zone wants - it wont tell you what the controller has decided to do about it (that is, optimisations) - although the above integration will also tell you if the boiler is receiving a call for heat.

[zxdavb (David Bonnes)]

@SIW1973

I do know that the Evohome API can accept a Duration on the DHW in some shape or form as it’s possible on

I am sorry, I do not have capacity fro this at the moment - almost all my spare time is working with the RF version (although I do have an outstanding evohome PR with two more waiting for it to be merged).

I would be willing to facilitate a PR to HA’s evohome integration, or to evohome-async.

The state-of-the-art is the RF integration (see above post) - it should do want you’re wanting, and more - for example:

• get schedules (set is a WIP), incl. DHW schedules
• change DHW setpoint

[sashaz]

Thank you I will check that out. It seems a bit over the top for what I want to do. I will see if I have any integration that can listen for that channel already (probably not).

[SIW1973 (Simon Williams)]

Thanks for this, I will look into the RF Integration as it could contain some of the parameters that I have asked @andremain over on the Smartthings side before he moved to Home Assistant, such as the % Demand setting that a zone is at e.g. Lounge - 80%.

With respect to PR I’m assuming that you mean Pull Request ? But coming for a Demand Management background you could also mean Product Request. Can you please clarify what you mean !

[zxdavb (David Bonnes)]

@SIW1973

such as the % Demand setting that a zone is at e.g. Lounge - 80%.

It does expose this date (you simply can’t get this via the web api).

@SIW1973

With respect to PR I’m assuming that you mean Pull Request ?

Yes: Pull Request.

[neutronwrangler (John Cooper)]

Sorry to drag this up to the present, but is there a more recent version? I’ve just installed the latest HA and 0.103.6 is not compatible

cheers
John Cooper

[Klagio]

Hi my installer wants to install Evohome (radiant heating), is it a good system? Does integrate well in HA

[zxdavb (David Bonnes)]

@neutronwrangler

Sorry to drag this up to the present, but is there a more recent version? I’ve just installed the latest HA and 0.103.6 is not compatible

I am sorry - the question just isn’t clear enough for me to have a stab at an answer.

[neutronwrangler (John Cooper)]

Sorry, I’m not sure how the threading works here, I thought I was replying to the topic:
[Workaround] Evohome multiple concurrent locations

[Workaround] Evohome multiple concurrent locations

Hi, I need to integrate 4 evohome locations into HA. Is there any chance to do it? I am aware that evohome component docs says that multiple locations at one time are not suported. Is there any plan for component improvement for multiple locations? If there is any serious issue with multiple locations at one time, is there any option how to switch between locations? Your help is very appreciated !

I have since found another reply:

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

I resolved it as follows. Not quite sure what exactly was the problem. I believe the directory structures get corrupted somehow. Go to the config directory and look for the hidden directory “.storage”. Delete any “Evohome_custom” entries. On a Mac you make these files visible by pressing “cmd shift .” Delete the directory for “Evohome_custom” in the “custom_components” directory and all the files in it, especially the pycache directory. Go to the GitHub location for the official Evohome compon…

and have it working, with evohome1 instead of evohome_custom

[zxdavb (David Bonnes)]

Then see this:

[Workaround] Evohome multiple concurrent locations

All: You can have multiple locations by creating a custom component out of the official evohome integration. You do that, broadly, by copying the components/evhome folder to (say) custom_components/evohome_cc (the new folder must have a different name). But note: every time you upgrade HA, there is the potential for the official integration to have been updated. Whenever that happens, you have to replace your old custom component with the latest version.

[scstraus]

I’m very happy with it.

[Dongilles (Giel Bruinen)]

Having problems with making automations with the evohome integration.
For some reason I do not find and entities when creating an automation.
But the climate entities are present.
Someone who can point me in the right direction?

[andremain]

Hello Simon. Welcome to the club!

While i did make the latest Evohome integration for Smartthings, i am really not a developer, I got a lot of help from Nayely. I hope you manage to achieve what you are looking for.

[davidtja]

Hi I set up a simple How water on for 30 mins schedule as a boost with a hot water off as the final part of the automation. Unfortunately the off sets as permanent rather than reverting to schedule. Can someone advise what command sets it back to the schedule (as set in the Evohome app)?
Thanks

[davidtja]

Anyone had similar, seems it sets it to away rather than off:

type or paste code herealias: "Water heater on for 15 minutes "
description: ""
trigger: []
condition: []
action:
  - service: water_heater.turn_on
    entity_id: water_heater.dhw_controller
    alias: Water Heater On
  - delay:
      hours: 0
      minutes: 1
      seconds: 0
      milliseconds: 0
  - service: water_heater.turn_off
    entity_id: water_heater.dhw_controller
mode: single

Any help appreciated

[dunner]

I’d also love to know the answer to this…

[davidtja]

I resolved my issue. Stupidly I had another automation that I used for testing turning it off. Check on the entity to see what automation are linked to it. Here’s what works for me.

alias: "Water heater on for 20 minutes "
description: ""
trigger: []
condition: []
action:
  - service: water_heater.turn_on
    entity_id: water_heater.dhw_controller
    alias: Water Heater On
  - delay:
      hours: 0
      minutes: 20
      seconds: 0
      milliseconds: 0
  - service: water_heater.turn_off
    entity_id: water_heater.dhw_controller
    enabled: true
  - service: water_heater.set_operation_mode
    data:
      operation_mode: auto
    target:
      entity_id: water_heater.dhw_controller
    enabled: true
mode: single