No sorry… This error means that your Home Assistant cannot connect to your Somfy Hub. Very hard to debug. Do you still face this?
You could try to add the IP address of your hub in the local integration, instead of the hostname.
Somfy finally fixed the issue ((self-signed) SSL cert uses the wrong common name · Issue #5 · Somfy-Developer/Somfy-TaHoma-Developer-Mode · GitHub) where they issued the wrong certificate. Soon the local API (alpha version) in HA will verify the certificate as well.
Not sure what is worse, that it takes Somfy 1.5 years to fix such a bug, or that my PR is already open since May 2022…
We are getting closer! Still a minor issue in the diagnostics generation, but at least full test coverage now. Looking for testers of the latest version. You will need to first remove your config entry and add it again, since there are breaking changes.
- SSL verify is now in place! This will only work if you connect to your Somfy hub via the hostname (e.g. gateway-1234-1234-1234.local). You can enable or disable this when you set up your entry.
- Simplified code
just updated to latest pull, after removing hub, and re-adding, all working.
1 Like
Thanks for the tip. I’m using now my fixed ip address hopefully it will improve the connection.
I have update the local api integration and everything still works!
But when it finally is in the core then it will remember all settings? Now I have to rename every cover, add some hidden sensors, etc?
When it is in core, there won’t be breaking changes, however the first time you will need to remove your cloud entry and create a new local entry as not both are supported.
Okay nice!
New version again! Now it should be better in retrying in the background, before it drops a cannot connect error. Let’s see if this is more stable for you all.
Had a very old version of this integration that worked for months, then it didn’t after a home assistant update. Now I have updated the ‘PR custom component’ integration and trying to set it up again but I can’t seem to log in using my somfy email address and password.
Tried with SSL toggle on and off.
The certificate from my Tahoma box also seems to be invalid.
try a second HA restart, I have had this before, sometimes the cache is not fully cleared on a HA restart.
also try going to OverKIZ integration and downloading the diag file, check that it is indeed up to date
"overkiz": {
"version": "2023.11.8-T122642Z",
"requirements": [
"pyoverkiz==1.13.0"
]
},
2 Likes
Not sure what goes wrong here, but you could check if it is fixed after a reboot. If it is a certificate error, it should show a different error. This is the error when it cannot connect to the server.
In the details you should see multiple hostnames if you have the latest update and after a restart of your hub. The main certificate is still for the wrong hostname, but the right hostname is part of the new certificate. The certificate is ‘invalid’ for Chrome because they don’t have the Overkiz root certificate in their store, we do include this in the integration.
1 Like
Restarted the whole container, still the same issue.
I then tried setting up the cloud API instead of local API to be able to view the diag file. That one worked immediately and I can now confirm that I have the latest overkiz version ( “version”: “2023.11.8-T122642Z”)
Maybe it has to do with the .local part of the host.
In my previous integration I also had to remove that to make it work.
Seems like it’s no longer possible due to the verify SSL option.
Probably has something to do with running in Synology as a container or something with my specific Somfy device because it also shows up without the .local in network scanning tools.
1 Like
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