-
-
Notifications
You must be signed in to change notification settings - Fork 31.5k
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
Overkiz integration hangs on Flow aborted: already_in_progress
#127986
Comments
Hey there @iMicknl, @vlebourl, @tetienne, @nyroDev, @Tronix117, @alexfp14, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) overkiz documentation |
Similar issue - mine has been working fine for about a year using somfy local API (europe) and stopped working altogether about a week ago. my existing connection now gets an error "failed setup, will retry: failed to connect" |
@wisien you are not using the Overkiz integration... Please create a new issue. @silkit @GilDev can you still access your box in the browser? Go to your mdns address or ip address, and port 8443. e.g. gateway-xxxx-xxxx-xxxx.local:8443. Most likely after an update your box is not available anymore in local mode, and it needs a reboot or you need to reenable the developer mode. Regarding the |
@iMicknl Thanks for the reply. Indeed I cannot access it in my browser, though I had never tried before. A Cloud API configuration following a reboot of Home Assistant didn’t help either, still get that “already_in_progress” error. |
Odd - mine was rebooted the other day but didn't seem to change anything. However, i completely rebooted everything this morning; All Ubiquiti/Fiber/HA/UPS etc all shutdown and restarted. Wouldn't you know, it's come back online :-) I have re-checked my somfy account and developer mode is still activated but oddly i have tried to access the somfy box via both the mdns address & ip address, and port 8443 - but neither will let me connect. I don't know if I've ever been able to though as i have never attempted to directly log into it this way. Not bothered by this though as it's comes back online and is functioning. |
Thank you very much. I had the same problem and after a restart everything works again |
Any way to disable and enable back developer mode? Can’t seem to disable it from the Somfy’s web interface… |
Flow aborted: already_in_progress
No, only through support if I am not mistaken. |
Okay thanks. Cloud would be fine but still no way to get through that |
Bonjour, |
Résolu à l'instant. J'ai supprimé l'intégration Overkiz, puis l'ai recréé en passant directement par Cloud API. |
Also tried again yesterday, and the connection via the Cloud API worked, don't know what happened… |
The problem
Everything was working fine, for a few months using the Cloud API, then a few weeks using the Local API, and everything became unavailable. I removed the integration and now can’t get it t connect anymore.
If I try to use the Local API, I get a “Failed to connect error” with no logs. Using the mDNS or the IP address of the TaHoma V2, enabling or disabling the “Verify SSL certificate” checkbox is the same.
Using the Cloud API, I get an “Unexpected error”:
What version of Home Assistant Core has the issue?
core-2024.10.1
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?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: