Total Connect Comfort (Honeywell) Issues

Third party integrations
1

Starting around 430am ET this morning, the Honeywell Total Connect Comfort integration stopped working, and a reload generates a “failed setup” error. I wonder if it’s a certificate error - I saw a forum post from 2020 that cited certificate errors between “mytotalconncectcomfort.com” (no error) and “www.mytotalconnectcomfort.com” (integration uses this but it generates a certificate error). That may be the case again, perhaps the integration can be modified to try both variants? My logs:

Blockquote
ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: Hostname mismatch, certificate is not valid for ‘www.mytotalconnectcomfort.com’. (_ssl.c:1032)

Oddly enough, on the integration home help page, it links to “mytotalconnectcomfort.com/portal” which does not generate a certificate error.

1 Like
2

Just an FYI mine integration is also down with the same certificate error.

3

Same here unfortunately.

4

Yes, it seems to be a certificate error. See this GitHub issue:

Seems it started around 0430 EST for most of us.

2 Likes
5

I’m having the issue as well. Similar to THIS CASE 5 years ago, it does work in my browser without ssl error if I omit the www from the address, can we make HA direct to the URL without the www?

Also, last year a different Honeywell service seemed to have the same issue as discussed HERE, and it seems there was a fix provided by @zxdavb

6

Awesome, fix is already provided & coming in 2025.11 (beta).

Looking at the PR here Bump AIOSomecomfort to 0.0.35 by mkmer · Pull Request #155265 · home-assistant/core · GitHub
… I think we can patch locally by updating

"requirements": ["AIOSomecomfort==0.0.35"]
in /usr/src/homeassistant/homeassistant/components/honeywell/manifest.json

and

# homeassistant.components.honeywell
AIOSomecomfort==0.0.35

(was 0.0.33)
in /usr/src/homeassistant/requirements_all.txt
& restarting

7

I can confirm that the patch described above by @cboehnke does indeed work. A nice workaround until 2025.11 comes out.

1 Like
8

There’s also a fix for those using HAOS (e.g., no direct access to the /usr directory.)

It’s described in the GitHub issue. Basically,

  • download this zip file,
  • extract the directory called aiosomecomfort and
  • copy it to your “config” directory.

That’s the directory which the Samba Share add-on connects to, which contains configuration.yaml and such. Or you could use the file editor add-on to create and populate the aiosomecomfort directory and load the four files into it.

Restart HA and it should pick up this “new” version. Just remember to delete it after you’ve updated to the HA version which includes the fix.

2 Likes
9

Mine is back on-line without the fix. Just saying in case you prefer to wait for 2025.11…

1 Like