Honeywell EVO Home integration fails

Third party integrations
1

EVOHome wont connect today, have they broken SSL?
Their own app works fine still.

I don’t see any way to ignore SSL or anything with this integration, anybody got any tips / clues?

2024-12-12 09:18:48.849 ERROR (MainThread) [homeassistant.components.evohome.helpers] Failed to authenticate with the vendor's server. Check your username and password. NB: Some special password characters that work correctly via the website will not work via the web API. Message is: Cannot connect to host tccna.honeywell.com:443 ssl:True [SSLCertVerificationError: (1, "[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: Hostname mismatch, certificate is not valid for 'tccna.honeywell.com'. (_ssl.c:1020)")]
2024-12-12 09:18:48.853 ERROR (MainThread) [homeassistant.setup] Setup failed for 'evohome': Integration failed to initialize.
2

yeah, same problem here. The SSL certificate for the evohome api endpoint no longer includes tccna.honeywell.com, it only covers: *.resideo.com domains

It’s possible this is a mistake and they’ll fix it, but I suppose it’s possible they’ve changed the API endpoint and the HA integration should be updated?

My actual honeywell evohome controller seems to still be working fine, reporting updated temperatures that I can see with the app (which is also working fine). I don’t think my evohome controller updates it’s firmware, so it must be using a different api endpoint (or doesn’t validate SSL certificates - which is very interesting :slight_smile:

John.

3

I’m having the same issue. It seemed to start after a planned maintenance on Resideo’s side was finished.

4

Same issue with my setup - just noticed it.

5

yep me too.

6

Yep, same issue

7

Well, they certainly did a boo-boo with the certificate(s) on their service. I wonder, if we can (like some other stuff) tell the app to just ignore faulty ssl certificates and just continue? Or people should point out where the hostname is to find in the code, so we can manually for now change it to the resideo.com option. (Which works if you make a proper api call).

8

Same issue here.

9

Solution is here: ssl cert for tccna.honeywell.com is only valid for tccna.resideo.com · Issue #32 · zxdavb/evohome-async · GitHub
Tested and approved

2 Likes
10

same issue here. It started for me last night. Evohome app works fine. After restarting HA and updating it also my HUE bridge doesnt work any more in HA. Not sure if they are correlated.

11

Same here…

12

Same issue :frowning:

13

Same problem :cold_face:

14

Same issue :thinking:

15

As I am having the same issue, I have tried to report it on https://www.resideo.com/us/en/support/. I am from Europe, and unfortunately they have refused to open ticket as they only support US and Canada. Please anyone here from US or Canada, report the problem on the above site (via the chat) … as customer service person could not understand that the problem is on their side, not on my end…

1 Like
16

Try here instead : KCS UK

I just submitted my complaint there without problem.

17

I posted it on the Europe site at the end
I still ask US or Canada members to open a case on the US site now as there are live agents on chat now

18

I have this too! Should we submit a Home Assistant issue too? Copying @zxdavb too in case you’re not aware. EDIT: sorry @zxdavb I see there’s already a solution above that you’re working on

19

Same here! :cold_face: :cold_face: :cold_face:

20

I have got a fix into the next version of HA - should be dropped tomorrow sometime.

5 Likes