[pyoverkiz.enums.gateway] Unsupported value 122 has been returned for <enum 'GatewayType'>

[jirkahronik]

The problem

Today after HA restart the Overkiz integration didn't start and logs two different errors - one from the title, another about DNS.
I use Local API, it has worked well for the past 2 months since I set it up.

Following issues sound similar:

• Overkiz Unsupported value 128 has been returned for <enum 'GatewayType'> #116043
• Local API cannot connect certificate verify failed ('Could not contact DNS servers') in HA >2024.12.0 in Overkiz #132318

What version of Home Assistant Core has the issue?

2024.12.2

What was the last working version of Home Assistant Core?

No response

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

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

The following messages get logged with the debug logging enabled (gateway ID anonymised):

2024-12-11 20:59:30.254 DEBUG (MainThread) [homeassistant.components.overkiz] ZeroConf discovery detected gateway ****-****-6495 on gateway-xxxx-xxxx-6495.local. (_kizbox._tcp.local.)
2024-12-11 20:59:30.254 DEBUG (MainThread) [homeassistant.components.overkiz] ZeroConf discovery detected gateway ****-****-6495 on gateway-xxxx-xxxx-6495.local. (_kizboxdev._tcp.local.)
2024-12-11 21:19:00.951 WARNING (MainThread) [pyoverkiz.enums.gateway] Unsupported value 122 has been returned for <enum 'GatewayType'>
2024-12-11 21:19:01.334 DEBUG (MainThread) [homeassistant.components.overkiz] Cannot connect to host gateway-xxxx-xxxx-xxxx.local:8443 ssl:False [Connect call failed ('10.10.0.152', 8443)]
2024-12-11 21:22:28.579 DEBUG (MainThread) [homeassistant.components.overkiz] Cannot connect to host gateway-xxxx-xxxx-xxxx:8443 ssl:False [DNS server returned answer with no data]

### Additional information

The Tahoma switch had auto upgrade enabled so it may have upgraded its firmware. I have no way to check :(

[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)}}

[iMicknl]

Do you know which TaHoma Switch you have? Apparently your specific gateway type is a new one that we haven't seen before. I will add the details to our underlying library.

It is just a warning that won't influence the working of the integration. Your issue with the local API is due to #132318.

[jirkahronik]

Thanks for a quick response!

The only thing other than Tahoma Switch on the device is 5152601A - possibly the model number? Otherwise it looks just like https://www.somfy.com.au/products/1871147/tahoma-switch

I'll follow up in #132318 but I already had verify_ssl: false from my initial setup. Re-adding the integration with any setting (using switch s/n hostname or IP address) with or without ssl verification, local or cloud, always yields connection error.
The integration stopped working today. I'm connecting to somfy_oceania.

[iMicknl]

@jirkahronik would be good to discuss your connection issues in a new issue. I would start by using the Cloud API for now, due to known issues with the local API in latest HA.