Local API cannot connect certificate verify failed ('Could not contact DNS servers') in HA >2024.12.0 in Overkiz

[pretorian83]

The problem

After the update to 2024.12.0 overkiz is displaying the following error:
... Failed to connect.

What version of Home Assistant Core has the issue?

core-2024.12.0

What was the last working version of Home Assistant Core?

core-2024.11.3

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Overkiz

Link to integration documentation on our website

https://www.home-assistant.io/integrations/overkiz/

Diagnostics information

home-assistant_overkiz_2024-12-05T00-22-58.121Z.log

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant]

Hey there @iMicknl, @vlebourl, @tetienne, @nyroDev, @Tronix117, @alexfp14, mind taking a look at this issue as it has been labeled with an integration (overkiz) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of overkiz can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign overkiz Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

overkiz documentation
overkiz source
_{^{(message by IssueLinks)}}

[jkosharek]

Getting the same error after updating to core-2024.12.0. Was connected to Somfy TaHoma Switch using the local API.

[lrixford]

Somfy just upgraded their app to consolidate the Somfy and TaHoma North America apps. Seems API changes might have been made.

Somfy Upgrade Notice

The HA integration failed after upgrade.

EDIT - For people that did the Somfy migration, this broke cloud integration and authentication (to get the Local API token) on Somfy end it seems.

See Issue

Somfy-Developer/Somfy-TaHoma-Developer-Mode#151

[ColinRobbins]

A roll back to 2024.11.2 works, so don't think it is a Somfy API issue.

[ColinRobbins]

@ColinRobbins if you turn on debug mode and try to configure the integration, you should see a warning. At least in the UI. Have you tried connecting with an without SSL verification? And can you access the ip/mens + port 8443 of your gateway in your browser?

With 2024.12.0 I get the following debug log on a HA restart.

2024-12-04 22:18:20.096 DEBUG (MainThread) [homeassistant.components.overkiz] ZeroConf discovery detected gateway ****-****-7195 on gateway-0403-5459-7195.local. (_kizbox._tcp.local.)

I've not tried with the browser - the fact reverting to 2024.11.2 works, suggests the gateway is fine.

Reconfiguring is not easy, as the integration is stuck in the initialisation state, so the configure, disable and delete buttons are not available. (They only appear when the integration fails to start - this integration does not seem to fail - rather hits an endless loop of retries).
So I think I would need to downgrade to 2024.11.2, delete, update to 2024.12.0 and reconfigure.
Thats too much to do on my live system, so later today I'll dust off my development version and progress under there to get more logs.

[calamarain]

Somfy just upgraded their app to consolidate the Somfy and TaHoma North America apps. Seems API changes might have been made.

Somfy Upgrade Notice

The HA integration failed after upgrade.

My Somfy hub/gateway is blocked from accessing the internet, it cannot have updated its API.

[raffoul]

Somfy just upgraded their app to consolidate the Somfy and TaHoma North America apps. Seems API changes might have been made.

Somfy Upgrade Notice

The HA integration failed after upgrade.

I don't live in the US and have the same issue only in 2024.12 (ok after rollback to 2024.11.3).

[avdb35]

Same issue here. Tried to generate a new API. there is a connection failure in the SOMFY link in my account. Maybe the problem is bij SOMFY

[ricoroci]

Same issue here.
Rollback worked just fine.

[ColinRobbins]

OK, here's a debug log from my development environment, using 2024.12.0...

Local API. verify SSL ticked...

2024-12-05 08:00:16.537 DEBUG (MainThread) [homeassistant.components.overkiz] ZeroConf discovery detected gateway ****-****-7195 on gateway-0403-5459-7195.local. (_kizbox._tcp.local.)
2024-12-05 08:00:16.537 DEBUG (MainThread) [homeassistant.components.overkiz] ZeroConf discovery detected gateway ****-****-7195 on gateway-0403-5459-7195.local. (_kizboxdev._tcp.local.)
2024-12-05 08:00:48.760 DEBUG (MainThread) [homeassistant.components.overkiz] Cannot connect to host gateway-xxxx-xxxx-xxxx.local:8443 ssl:<ssl.SSLContext object at 0x72bf701617d0> [Could not contact DNS servers]

DNS on the machine is working fine (e.g,. I can get to github to send this message)

Local API, SSL unticked...

2024-12-05 08:04:02.411 DEBUG (MainThread) [homeassistant.components.overkiz] ZeroConf discovery detected gateway ****-****-7195 on gateway-0403-5459-7195.local. (_kizboxdev._tcp.local.)
2024-12-05 08:04:44.215 DEBUG (MainThread) [homeassistant.components.overkiz] Cannot connect to host gateway-xxxx-xxxx-xxxx.local:8443 ssl:False [Could not contact DNS servers]

I.e., the same.

Cloud API Works fine.

[ColinRobbins]

Using Local_API, if I replace gateway-xxxx-xxxx-xxxx.local:8443 with the IP address & port, I get further.
The GUI reports Cannot connect to host, certificate verify failed. and the logs show

2024-12-05 08:09:25.302 DEBUG (MainThread) [homeassistant.components.overkiz] Cannot connect to host 192.168.10.187:8443 ssl:True [SSLCertVerificationError: (1, "[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: IP address mismatch, certificate is not valid for '192.168.xx.xx'. (_ssl.c:1000)")]

if I turn SSL verify off, and use the IP address its back up and running.

So this issue is the new code cannot DNS resolve gateway-xxxx-xxxx-xxxx.local.

[ColinRobbins]

So the workaound to get something working with 2024.12 the steps are...

1. BEFORE you upgrade - delete the integration.
2. If you have have already updated, I think you need to back off to 2024.11, as you cannot delete the integration in a perpetual retry state.
3. Upgrade to 2024.12
4. Re-add the integration, but do not use the auto-filled network address, replace it with the IP address
5. uncheck the SSL verify box.

Hopefully someone can figure out the name resolution issue, and we an revert to using SSL.