So the initial cannot connect error was right? It could not connect from your environment. If you cannot use the .local hostname, you cannot use the SSL verification indeed.
Can you check if it works if you don’t select the verify SSL checkbox?
Correct. I’ll have to look into why mdns (that’s what the .local part is right?) doesn’t seem to work with my setup, but disabling the SSL checkbox and using the host name without the ‘.local’ part doesn’t work.
There is indeed a bug now that it will always verify the SSL certificate, this is a bug in the underlying library. Will try to fix this in the coming days. 
1 Like
New version again, please test.
- Underlying library will retry first on connection errors, should make it more stable
- Disabling verify SSL now works. In case you want to use the IP address.
Hopefully we can get this PR in before the 27th of November, so it can be part of next release. Code should be feature complete now, and in a good shape for core.
2 Likes
Works great for me the latest version.
Thanks Mick, I can confirm that the latest version works for me.
Still not sure why I cannot connect with the .local host address, but configuring with gateway-xxxx-xxxx-xxxx:8443 and the SSL check disabled works fine.
1 Like
Great! And regarding your connection issue, I wouldn’t know either. But if you can’t connect / ping the .local address from your Synology, it is probably a networking / Docker configuration issue.
The IP address should work as well .
1 Like
Good news, local API support has just been merged to core. From next week’s beta, Overkiz local API will be part of Home Assistant! Thank you all for testing!
This topic should not be used after the release. From now on you can report any issues via GitHub and feature requests via the Overkiz topic.
7 Likes
Thanks that is really good news 
1 Like
very good news.
when will it be available for all of us ?
the monthly HA update is released on the 1st wednesday of the month so it should be in 6th Dec unless something is found to be an issue with it.
You can already test this via the beta channel, see Common tasks - Operating System - Home Assistant (home-assistant.io). The release is scheduled for next week Wednesday.
Would be great if people from this thread can try the beta out this week and verify if it works as it should!
1 Like
I would, but I never install the 1st release of the month, as there is always some issue or other, I always wait for the .1 or .2 update, and I don’t have a spare SBC to install HA dev channel sorry.
@imick Seems to be working. Missing some labels in the config though:
After setup it takes a while to get the devices in HA. After that the covers are working.
Edit: After a reboot the labels appeared.
1 Like
You’re not mentioned in the beta release notes yet? This is a major accomplishment imho! Thank you!
1 Like
I also find it bizarre that you weren’t mentioned in the release notes. I think quite a few people have Somfy products and this is indeed a huge improvement.
Especially since (and rightly so) people insist on local control, this should be mentioned.
1 Like
Don’t worry about the release notes, this has been discussed already and will be added to the final version. 
3 Likes
I tested local API in the HA dev channel and I want to change my config from cloud to local API as soon as the HA 2023.12 is released. Is it possible to reconfigure my existing cloud integration to local and keep my device IDs? I have some device groups and automations and don’t want to reconfigure them.
1 Like
Hi,
I tested local API integration. First of all, congratulations for your work, it’s really good work, almost everything works except the scenes. When I try to call them, nothing happens.
Can anyone else try running the scene and confirm that it doesn’t work?