SmartThings Community

Honeywell EvoHome support coming?


If you want access to the beta thread, just email UK support. They’ll give you access.

(codersaur) #103

Right, I’ve given up waiting for the official Evohome app to be released and have decided to release my own unofficial version.

I’ve created a new thread for it here: [RELEASE] Honeywell Evohome Integration


(Joe) #104

SmartThings is happy to say that we’ve released our Honeywell evohome integration via the Marketplace in the SmartThings app! We apologise for the lengthy wait for this integration. This was due to OAuth stability issues that would cause occasional disconnects, forcing a manual re-authorisation. Honeywell has recently made improvements to their API to correct for this. Please contact SmartThings support if you notice any issues with the Honeywell evohome integration

(Adam Mills) #105

That’s awesome news!

(Arnoud) #106

I can confirm that I had no problems whatsoever to connect my Honeywell Round Connected thermostat to SmartThings, so it is not only the EvoHome but also the cheaper Round Connected thermostat that works!

(Iain) #107

@Joe-UK I have the official app installed and see my 4 zones, how do I assign those Honeywell zones to Smarthings rooms?

thanks, Iain.

(John) #108

Do you mean this?

Its a pity you need the RFG100 with the round thermostat as wifi is now built into the normal evohome controller, the price difference isn’t that big anymore.

(Joel) #109

So for someone in the market to get a smart thermostat would you guys recommend this one?

(codersaur) #110

That depends on your requirements. The key advantage of the Honeywell Evohome system is that is supports multiple heating zones and individual radiator valves. When I looked at Nest, Tado, Hive etc, they only supported one heating zone, which is a major flaw in my opinion, as most of your energy savings will come from being able to control rooms independently and avoid heating the rooms you don’t use at particular times. The disadvantage of Honeywell Evohome is that is more expensive as you have to buy all the valves.

(Arnoud) #111

I would guess most European homes are fitted with manual or thermostatic radiator valves, and therefore equipped with a single thermostat in the house.

If you have a single thermostat setup and do not want the expense of changing all your valves with intelligent ones, the simple Honeywell Round Connect might be a good option to consider.

No, you won´t get the maximum savings from this setup, but the initial expense is not horrible either.

(Aaron S) #112

Hi Everyone,

I sincerely apologize for the inconvenience. We released integrations for a handful of Honeywell thermostats in North America today. The UK Honeywell evohome release was incidentally included. We are going to pull it while we put on some finishing touches, but know we are hard at work and it is coming soon.


(Iain) #113

@Aaron Will the version I installed last night still work?
A pain if not as I deleted all the setup from the alternative to install this.

(Aaron S) #114

Clarification: existing installs should continue to operate. However, support will be extremely limited as this was a premature release.

(Joel) #115

thank you. so essentially I could go either way. I’m pretty keen to use keen smart vents. Which would remove the need for zones, but then I may get into trouble with shutting of too many vents and cause issues with my central ducted gas/air cond.

BUT i can set it so only one or two are closed - as my house isn’t that big.

(Jeffrey) #116

Played around a bit with this new integration this evening. Works mostly correct for two of my thermostats but I can’t add the third one. It has a bit less capabilities then the others and it seems it’s looking for capabilties this one doesn’t have and throws a java error.
java.lang.NullPointerException: Cannot get property ‘allowedModes’ on null object @ line 491

Bummer was hoping to move away from the community written version.

Also noticed the resume schedule doesn’t seem to want to cancel my holds - it just seems to do nothing. Will have to look into that later

**released I totally put this in the wrong post as I am a US user.

@Aaron any chance you want to chat about what I am seeing and see if I am stuck with the one thermostat?



Admittedly I haven’t checked out the ‘released’ version yet - but if it’s anything like the Beta version - it’s pretty useless compared to @zcapr17 version.

(Paul Ockenden) #118

What he said!


(Jeffrey) #119

I shouldn’t have replied here as I am using TCC and not a EvoHome so I assume there are some differences in that.

For me the ST version did everything I would need plus a few things that don’t work on the TCC community app but none of this has anything to do with you guys :slight_smile:
Sorry for hijacking!

(Arnoud) #120

Because I am now using an unsupported version (that seems to do what I want so far), would I need to do anything to keep it working after the ‘real’ version is released? Is it known when that will be?

(Aaron S) #121

In all honesty, I am not sure… it is going to depend on how much dev work is needed and if any changes occur with the APIs (ie. I cannot guarantee that the C2C integration will not break between now and an official release).

I will give notice if I hear of any changes that could affect existing integrations, although with active work in process, I am not in a position to make any promises. I do not have one in my unit (heck - I wish I even had a thermostat to control?!), so you may find out before me.

Personal note: I was eyeing some connected radiator valves myself until I realized one of the two valves is cemented shut and the other is pretty much non-functional. I think I need a new apartment to test thermostats :grinning: