Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

pyoverkiz.enums.gateway] Unsupported value 126 has been returned for <enum 'GatewayType'> #133283

Closed
TomGeske opened this issue Dec 15, 2024 · 6 comments · Fixed by #133458 or #133471
Closed
Assignees

Comments

@TomGeske
Copy link

The problem

Unable to add / install Overkiz for my Somfy TaHoma Box.

Selected Server: Somfy (Europe)
API Type: Local API (tried Cloud API, same issue)
Entered my Host + Credentials.

Error message in UI while activating integration: "Failed to connect"

Logs are attached below.

What version of Home Assistant Core has the issue?

core-2024.12.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

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?

2024-12-15 15:25:32.673 WARNING (MainThread) [pyoverkiz.enums.gateway] Unsupported value 126 has been returned for <enum 'GatewayType'>
2024-12-15 15:25:32.673 ERROR (MainThread) [homeassistant.components.overkiz] Unknown error
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/overkiz/config_flow.py", line 148, in async_step_cloud
    await self.async_validate_input(user_input)
  File "/usr/src/homeassistant/homeassistant/components/overkiz/config_flow.py", line 79, in async_validate_input
    await self.async_set_unique_id(gateway_id)
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2685, in async_set_unique_id
    raise data_entry_flow.AbortFlow("already_in_progress")
homeassistant.data_entry_flow.AbortFlow: Flow aborted: already_in_progress

Additional information

No response

@home-assistant
Copy link

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
Copy link
Contributor

iMicknl commented Dec 15, 2024

This warning ([pyoverkiz.enums.gateway] Unsupported value 126 has been returned for <enum 'GatewayType'>) is actually unrelated. However, we should add this specific type to our library. Where did you buy your TaHoma Switch (which country / region?)

Regarding the other issue, can you try to reboot Home Assistant and try the Cloud API again? The Cloud API should work.

@iMicknl iMicknl mentioned this issue Dec 17, 2024
19 tasks
@TomGeske
Copy link
Author

I bought it in Switzerland / Europe.

The "unkown error" is unrelated?

@iMicknl
Copy link
Contributor

iMicknl commented Dec 17, 2024

Yes, that is unrelated to the warning. I have seen more reports of this error in the past, but we haven't been able to reproduce this yet.

Often after a reboot / HA upgrade, the ConfigFlow error is gone... I am still figuring out the exact steps to reproduce this issue, so I can work on a fix.

@TomGeske
Copy link
Author

Same behavior even after HA reboot. Any additional steps you can suggest for troubleshooting?

@iMicknl
Copy link
Contributor

iMicknl commented Dec 18, 2024

@TomGeske I figured out the issue, will try to add the fix to HA for an upcoming release!

# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
2 participants