Overkiz API and Somfy API

ben23fr · April 23, 2021, 1:33am

I also had this ssl issue, so I tried to unistall an reinstall the integration… Somfy is not anymore in the integration list, but it tell me I can’t add it because it’s already installed and I can install only one…
And not a word in the log.

ColinRobbins · April 23, 2021, 6:29am

After a long period of reliable operation, I am seeing this same issue today in HA, so cannot control my blinds from HA.

I also have the blinds directly integrated in Google Home (so I can still open the blinds as a backup if HA does it work), and this is working fine.

The HA error suggests the issue is with the Certificate chain, and not being able to verify the root certificate. I wonder if Somfy have a new certificate, but are not suppling the chain.
Any ideas how we can intercept and view the certificate in HA to take a look at what’s going on, or get details logs from the SSL verification code?

tetienne · April 23, 2021, 6:50am

Nothing complicated here

Like last year they didn’t renew their certificate. I will contact them.

See SSL Server Test: api.somfy.com (Powered by Qualys SSL Labs)

tetienne · April 23, 2021, 7:02am

Can you retry reloading the integration, the certificate is well updated:

Wed, 20 Apr 2022 23:59:59 UTC (expires in 11 months and 28 days)

etique57 · April 23, 2021, 7:17am

Hello Etienne,

I still get the same error (just rebooted). Should I delete/reinstall the integration?

Logger: homeassistant.config_entries
Source: config_entries.py:265
First occurred: 9:15:35 AM (1 occurrences)
Last logged: 9:15:35 AM

Config entry ‘Home Assistant Cloud’ for somfy integration not ready yet: HTTPSConnectionPool(host=‘api.somfy.com’, port=443): Max retries exceeded with url: /api/v1/site (Caused by SSLError(SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1125)’))); Retrying in background

tetienne · April 23, 2021, 7:35am

You can try, but on my side the devices are not retrieved anymore

Edit: same thing on their website: Somfy Open API Developer Portal | GetSiteByID

nmz · April 23, 2021, 7:49am

It looks like they installed a new certificate, but forgot to add the required intermediate certificate to the configuration.
We’re missing the certificate for “C = US, O = DigiCert Inc, CN = RapidSSL TLS DV RSA Mixed SHA256 2020 CA-1”.
It’s available here: http://cacerts.digicert.com/RapidSSLTLSDVRSAMixedSHA2562020CA-1.crt

ha_irish · April 23, 2021, 10:24am

Thanks so much for posting this. SSL has always escaped me lol. How did you get the missing intermediate cert ? More so how did you figure that was the problem ?

Also are you saying if we install the intermediate cert on our HA boxes that the somy integration will work again ? Wonder how you would go about doing that in a docker install of HA without the extra need of mapping the ssl dir to a volume mapping

nmz · April 23, 2021, 11:24am

The URL was embedded in the certificate metadata:

$ echo | openssl s_client -connect api.somfy.com:443 2> /dev/null | openssl x509 -noout -text 2> /dev/null | grep CA\ Issuers
                 CA Issuers - URI:http://cacerts.digicert.com/RapidSSLTLSDVRSAMixedSHA2562020CA-1.crt

The openssl s_client command also pointed me to the problem initially.
It seems the issue has been resolved by somfy on the servers side now.
The intermediate cert is present in the chain, and the errors no longer appear in the homeassistant log file.

delboydell · April 23, 2021, 11:33am

mine stopped working last night , but I clicked on update within the entity and they came back up. I had tried this earlier today and also last night but it didnt work then.

etique57 · April 23, 2021, 11:40am

I confirm it’s back online now.

Boris · April 23, 2021, 11:58am

Same here!
Issue Deens resolved

ha_irish · April 23, 2021, 12:42pm

Thanks for the details ! @nmz

ColinRobbins · April 23, 2021, 5:24pm

Thank you, it’s started to work now.

ColinRobbins · April 24, 2021, 11:46am

Hi,
@tetienne is there a way we could change the behaviour on API error?
It seems to me, that HA has a set of devices configured, and working.
A Somfy error occurs, and the devices disappear.
Is there a way we could configure the integration to keep the cached devices until a positive response from Somfy. Then when theybmess the certificates up (or other frequent API error), it should all keep working.
I’m happy to help with the coding effort, if we agree an approach.

tetienne · April 24, 2021, 12:00pm

About SSL issues, even if you cached the devices you won’t be able to send any commands or retrieve any states.

For other kind of errors, I have indeed to enhance the behavior. Within the Core issues someone already suggested an idea of fix.
You have to know I already cache the device list.

I will have a look if I find some free time.

Link to the issue: Somfy integration problem · Issue #44783 · home-assistant/core · GitHub

ColinRobbins · April 24, 2021, 3:39pm

Thank you - your efforts on this integration are very much appreciated.
Let me know if I can help, e.g., testing etc.
Colin.

etique57 · May 27, 2021, 4:54am

Hello,

With the official API I now have an error 500 since yesterday.

Am I the only one?

Thanks!

tetienne · May 27, 2021, 7:02am

Can you please provide the error you have?

martinst · May 27, 2021, 10:44am

Today I saw that Somfy has renamed there ios App to Somfy Tahoma Classic. There is a new box the Somfy Tahoma Switch.

Does anybody know (maybe someone has already this box) if this box has local support instead of only cloud support? (I don’t think so but maybe there are miracles )