Overkiz API and Somfy API

martinst · October 8, 2021, 6:19pm

Okay it is strange that there is no stop functionallity.

What about discrete mode?

Is that possible? (So the slow speed)

tetienne · October 8, 2021, 7:15pm

I haven’t such covers. I don’t know. But I think it’s not supported.

imick · October 9, 2021, 11:17am

I would say this is not supported, since this is not supported in HomeKit. In my case, unfortunately they don’t support my light and pergola cover, thus HomeKit is rather useless for me.

However, for some users this could be great solution!

Robi07 · October 9, 2021, 7:11pm

Hello. My first post and a complete HA beginner but I was able to set-up within 5 minutes my RTS covers (connected to Tahoma Switch) with your Overkiz API. Many thanks! My question: the “My position” on the RTS covers is also working through your integration (triggered through scenes performed in the Tahoma App) but I’ve also some old RTS receivers (PF versions, approx. 20 years old) that does no offer the My Position function at all. Is it possible to perform a time-based script (e.g. close for 30 seconds and than open for 1 second) and if so, can you share a code-template? Or do i need to buy newer RTS (or IO) receivers to perform a My position?

martinst · October 9, 2021, 7:51pm

Okay that is bad news for me….

tetienne · October 11, 2021, 9:23am

HA component must only expose features implemented by a device.
In your case, you can create a script to open or close your cover, wait and then stop.

Robi07 · October 11, 2021, 4:19pm

Many thanks Tetienne! I’m almost there. The following script works - but I realized that the actions are performed in parallel and not consequently. I therefore included a trigger of “58” to allow enough time from fully open to close with the disadvantage that it takes 58s for the upward command when the cover is nearly closed…do you see a more elegant way than the following

storen_wohnzimmer_angewinkelt:
  alias: Storen Links Wohnzimmer angewinkelt
  sequence:
  - device_id: 47a065a2bb4bf8b1c95638b96ea64622
    domain: cover
    entity_id: cover.storen_links_wohnzimmer
    type: close
  - wait_for_trigger:
    - platform: device
      device_id: 47a065a2bb4bf8b1c95638b96ea64622
      domain: cover
      entity_id: cover.storen_links_wohnzimmer
      type: closed
    timeout: '58'
  - device_id: 47a065a2bb4bf8b1c95638b96ea64622
    domain: cover
    entity_id: cover.storen_links_wohnzimmer
    type: open
  - wait_template: ''
    continue_on_timeout: true
    timeout: '1'
  - device_id: 47a065a2bb4bf8b1c95638b96ea64622
    domain: cover
    entity_id: cover.storen_links_wohnzimmer
    type: stop
  mode: single

tetienne · October 12, 2021, 8:20am

I don’t like the automation using device.

I would image more something like:

alias: Close and Stop
sequence:
  - service: cover.open_cover
    target:
      entity_id: cover.storen_links_wohnzimmer
  - delay:
      hours: 0
      minutes: 0
      seconds: 5
      milliseconds: 0
  - service: cover.stop_cover
    target:
      entity_id: cover.storen_links_wohnzimmer
mode: single

martinst · October 12, 2021, 3:04pm

Are there no possibilities to change this behaviour?

You could not reconnect automatically? The problems of banned i have never had before.

Today it occurred another time, while i get push notifications that some automations are running while the covers could not controlled.

Your suggestion about the check if reauthenticate is necessary i still not have found

Robi07 · October 12, 2021, 3:47pm

Many thanks! Simple and works.

With various tests I have found that automations with RTS blinds does not turn out to be reliable. If I send the close command ahead of your script including a wait of 58 seconds to allow full closure, then the whole sequence (close/wait/open/wait/stop) works in 6 out of 10 cases. In the other cases the blinds usually remain closed. Must be related to the RTS technology. RTS really only seems to be suitable for simple commands like close, open and my position(if available).

If have also some Shelly’s 2.5 with other covers. Extended script with closing/wait ahead of your script works reliable. No errors so far.

NicoLeOca · October 12, 2021, 7:41pm

Hi!
I have a Somfy box Tahoma V1.
The status of my various devices are really slow to be updated into HA, sometimes up to 1h.
Is it due to the cloud API, or it is a limitation of this hardware?
Thanks
NicoLeOca

imick · October 12, 2021, 10:30pm

It should be 30 seconds maximum, or when you hard refresh all states by opening tahomalink.com (in case of devices like the Pedestrian Gate).

Could you open an issue on GitHub with your debug log, so we can investigate?

NicoLeOca · October 13, 2021, 7:33pm

Hi @imick
For instance, when I open (or close) my garage door, the state is long to be updated automatically. But it is updated, as soon as I opened the Somfy app.
My understanding of this phenomenum is that the state of the garage door is not updated back into the Somfy box very often; but when I open the Somfy app, the somfy box asks the garage door for its state.
Would that make sense?

tetienne · October 13, 2021, 8:15pm

That’s a known issue. Please see https://github.com/iMicknl/ha-tahoma/issues/167

MichaelT · October 14, 2021, 7:24am

Hi,

I am using the Overkiz (by Somfy) - Home Assistant integration to link my Tahoma Switch. This works great, except every week I am logged out of the integration.

My covers (both RTS and IO) aren’t available anymore in HA and I get a warning that one of my integrations needs reconfiguration. In the integrations UI I see Overkiz (by Somfy) needs attention. In the HA log is read “Authentication failed while fetching device events data: Bad credentials”.

As soon as I re-enter my credentials I first get a message “aborted” but then all is working again, at least for a while until I am logged out again.

Anyone else bumped into this issue? And any ideas on how to fix this? It’s becoming quite annoying

imick · October 14, 2021, 10:34am

Also a known issue, have a look at At least one of your integrations requires reconfiguration to continue functioning. · Issue #599 · iMicknl/ha-tahoma (github.com).

We are looking into this, however the main issue is that Somfy is throwing these BadCredentials errors when your credentials have changed, but also randomly when they encounter issues apparently.

The last days we have seen quite some reports from users, which is not related to an integration update, but related to the Somfy behavior…

mcm57 · October 14, 2021, 11:32am

I managed to control my SOMFY IO shutters connected to a TAHOMA SWITCH 2 days ago using Overkiz integration. (I did not manage to use the integrated somfy integration as either a quota error - when using cloud access - or an oauth2 error when using private developer api codes occured).

Today the integration was offline because of issue #599:

After reconfiguration the shutters work again BUT *.rssi_level entities and sensor.homekit_setup_code are offline.

Any idea how to reenable the homekit_setup_code sensor? (I’ve noted the code issued - but I do not know when it will probabl change so I would feel better if it can be read)

Thanks
McM

imick · October 14, 2021, 11:34am

This will work after a reboot, we will fix this issue soon.

Tracking issue: Config entry has already been setup · Issue #560 · iMicknl/ha-tahoma (github.com)

mcm57 · October 14, 2021, 11:38am

Thanks for the fast reply

NicoLeOca · October 14, 2021, 6:27pm

thank you @tetienne
I hope it gets fixed soon as I see it important to have reliable info in home automation