Overkiz API and Somfy API

What is your Somfy Tahoma firmware version? And could you turn on debug mode and share your log. (preferably in a GitHub issue on ha-tahoma).

Did the official Somfy integration work before? I wonder if an update did break your environment, or if there is another reason.

fully my badā€¦I installed custom component thinking it was overloading the Somfy integration, ā€¦ basically i didnā€™t reconfigure ā€œSomfy Tahomaā€ custom integrationā€¦once done all worked fineā€¦ feel free to remove my previous post if you think itā€™s better for the thread.

1 Like

I also have Login issue on Tahomalink.com web sitte
If I login through https://www.somfy-connect.com/en/, I can access my Tahoma Box
If I login with my iPhone App, I can also access my Tahoma Box

Login issue happen only on Tahomalinkā€¦com or if I uninstall and reinstall the Tahoma Official Integration
Login Credential error message

Please add your context to this GitHub issue, Somfy Tahoma invalid auth Ā· Issue #420 Ā· iMicknl/ha-tahoma (github.com).

Hi just connected my PC used to connect to Tahomalink.com through a VPN instead of sirect connection and after than I can inform you that the Login on Tahomalink.com is working.
If I disconnect the VPN, then login issue ahappen again
I can now say thatā€™s this issue is in fact a Public IP Blacklisting done by Somfy !!!
I will try to set a VPN client on my HA Server (HASSOS) to connect to my VPN service (Wireshark)
I saw Wireguard VPN Add-on. I don"t know if thatā€™s what I have to use but I will investigate this during the weekend

Is someone has an idea how I could have VPN client avaialble on my HASSOS (actually under proxmox)

Thanks

If you stop hitting their server (so remove / disable the integration) this should be removed in the next days. I will see if we can prioritize the new ReAuth required functionality, that will stop hitting the server and prompt for a password.

Adding a VPN client to HA OS would be a hassle and I would just wait until you have access again :).

HI Mick,

looking for a way to guard the Garagedoor in the HA interface, because this is way too accident prone for my taste:

I was wondering if the locktimerstate attribute in


could be of any use in HA?

if not, would you know of an interface that can guard us from accidental opening? (I did create a custom button card which allows me a confirmation, but I dont think the default up/down buttons offer that too? Or the slider for that matter)

thanks for your continued support!

@Mariusthvdb the lock timer attribute cannot be used, this is an internal attribute from Somfy used when you have hardware locks (wind, rain etc.)

For the other question, that would be out of scope for this issue and I would just ask it on the forum / see if there are others with the same issue.

ok thanks for letting me know.
Do you have more info on the hardware locks? Does Somfy sell these? (I have been looking for a hardware lock on the garage door, electronically set, so it can serve as an extra guard for preventing forced entry, but open on the Somfy remote command to the garage doorā€¦)

I donā€™t know how exactly works these locks. But from a UI point of view, you can create a switch for each cover, and then create a template cover where the open and close command are guard by your switch: Template Cover - Home Assistant

Hello! I just bought the Tahoma box and the Somfy eolis wirefree io. Someone with the same that can verify the sensor can work with tahoma and home assistantā€¦?

Hi, if the sensor isnā€™t picked up by the official API, have a look at the Tahoma integration on HACS.

But I first need to add it in the Tahoma app I guess? Canā€™t find it in the io sensor product list there?

yes indeed, the TaHoma integration relies on the TaHoma box and whatā€™s controlled by it.

still on 2.4.8, thereā€™s one thing happening lately I canā€™t explain. Maybe its something at Tahoma, or itā€™s in the HA update to 2120.4.5/6, but this script:

  garage_lamellen_my:
    alias: Lamellen My
    mode: restart
    sequence:
      service: tahoma.set_cover_my_position
      entity_id:
        - cover.lamel_rechts
        - cover.lamel_links

which is executed each morning, suddenly needs an extra manual kick, because the cover.lamel_links remains in the closed position.

Could this be somehow explained by any of the updates? No Errors in the log (not set to debug, but errors would should show)

thanks for helping me here.

Ran into issues today with the Somy official api integration and just switched over to the ha-tahoma custom integration. So far itā€™s working great good job all :slight_smile:

Good evening,

Is it just me or the Somfy integration is down? It worked today but I get a certificate-related error on api.somfy.com now.

Caused by SSLError(SSLCertVerificationError(1, ā€˜[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1125)ā€™))); Retrying in background

Thanks!

Seeing the same here. No luck re-adding the integration unfortunately.

I donā€™t have issues with accessing https://api.somfy.com/api/v1, but it could be that they messed up their SSL certificateā€¦ Most likely this will be fixed tomorrow during work hours.

In the mean-time, you can always use ha-tahoma which uses a different API. However, I would expect them to fix this tomorrow.

1 Like

I had that same ssl error. So I ended up switching over the ha-tahoma which seems better ha