Maybe I am not understanding correctly, but I was under the impression that this bugfix:
opened 01:39AM - 19 May 26 UTC
closed 11:16AM - 19 May 26 UTC
integration: lyric
### The problem
The `lyric` integration is failing with the error below:
```te… xt
Failed setup, will retry: Cannot connect to host api.honeywell.com:443 ssl:True [SSLCertVerificationError: (1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate has expired (_ssl.c:1081)')]
```
By checking the URL: `https://api.honeywell.com/` we can confirm the certificate has expired:
<img width="521" height="571" alt="Image" src="https://github.com/user-attachments/assets/b6a2b473-d56b-4883-9875-074cce54595e" />
I know this is an issue on their end, but maybe we could have an option to not check the certificate? It's not safe and I hate the option and other options are always welcome.
Or if companies actually took care of their certificates. 🤦
### What version of Home Assistant Core has the issue?
core-2026.5.2
### What type of installation are you running?
Home Assistant OS
### Integration causing the issue
Honeywell Lyric
### Link to integration documentation on our website
https://www.home-assistant.io/integrations/lyric/
### Anything in the logs that might be useful for us?
```txt
Failed setup, will retry: Cannot connect to host api.honeywell.com:443 ssl:True [SSLCertVerificationError: (1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate has expired (_ssl.c:1081)')]
```
### Additional information
The `Residio` apps is still working, but not sure if they also use the same endpoint.
Was supposed to fix this issue:
After the update to 2026.5.3 my Lyric integration is still reporting the SSL error. Do I manually need to change the URL?
1 Like
I would suggest restarting everything and rebooting the host to eliminate caching issues.
avdgaag
May 20, 2026, 9:06pm
4
avdgaag
May 20, 2026, 9:09pm
5
The problem must be fixed by Honeywell, because the certificate is expired:
You must have not read the fix in the Git issue. Honeywell changed the API URL.
In any event. This is resolved in the 2026.5.4 release.
I have upgraded to 2026.5.4 and now I have "Bad Request" error. I have disabled/enabled the integration and rebooted and have the same problem.
