Add Scenaries from Tahoma

Hello.
Before new core (2024.11.x), I used ‘‘Overkiz (by Somfy) - Custom component’’.
This custom Overkiz allowed me to use all components connected to my Tahoma v2 (Io , RTS and Zwave).
I understand Overkiz and HA to implement zwave directly in HA but…my Tahoma is configured with some zwave components and scenaries with it,
The custom Overkiz allow HA to use all scenes from Tahoma. So I know it’s possible.
Even if you don’t want to implement customs components connected to Tahoma, could you allow HA to use scene from Tahoma and implement it in overkiz ?
It’s not a custom or zwave protocol but an official function from Tahoma v2…so a official implementation for an official Overkiz…
Thanks in advance.

Scenarios created in the TaHoma app should be supported in Overkiz integration in core as well (cloud API only). What is not working for you?

Thanks for your return.
With the custom Overkiz, I had my zwave components from Tahoma.
To prevent a changement, I created some scenes with Tahoma to activate or deactivate my zwave components from HA.
With that, in HA, I was allowed to used this scene and operated my zwave without to have migrate all zwave to HA …but since the official Overkiz and new HA Core, I can’t see the scenes from Tahoma in HA.
I don’t want migrate all zwave components form Tahoma to HA because :
1 my wife likes to use Tahoma.
2 in case of problem with HA, I can continue to use Tahoma…
I keep HA for the automatisation.

What do you mean with ‘’‘cloud api’’ ?

How did you configure the Overkiz integration? Did you select “Local API” or “Cloud API”?

I don’t remenber…
How can i verify it ?

My firsts config lines :

‘{
“home_assistant”: {
“installation_type”: “Home Assistant OS”,
“version”: “2024.11.3”,
“dev”: false,
“hassio”: true,
“virtualenv”: false,
“python_version”: “3.12.4”,
“docker”: true,
“arch”: “x86_64”,
“timezone”: “Europe/Paris”,
“os_name”: “Linux”,
“os_version”: “6.6.54-haos”,
“supervisor”: “2024.11.4”,
“host_os”: “Home Assistant OS 13.2”,
“docker_version”: “27.2.0”,
“chassis”: “embedded”,
“run_as_root”: true
},’

If you download the diagnostics for the Overkiz integration, it will show ‘local’ or ‘cloud’ at the bottom of your diagnostics JSON.

You can also remove and re-add the integration and select Cloud API.

If you think about “iot_class”: “local_polling”…so it’s seems that it’s on local…
i can’t imagine that the problem could be solve with changement from local to cloud…
With the custom Overkiz all worked fine…
The system was reactive, all component was seen, and i could use scenaries from Tahoma…
Also, as soon as we have to change overkiz we have to remake all the configuration…have you got a solution to prevent that ? is they existing a solution yo save all overkiz configuration or to permit to the new overkiz to recover everything from the old ? i used the overkiz custom only during some weeks, because i have HA from September…and i had a lot of regrets when i was in obligation to change HA for new and to lost overkiz custom…if you arrive to remake custom for new HA, i think you will make many people happy…
Thanks in advance.

It is not about iot_class. Please share your diagnostics JSON and I can have a look.

And the Overkiz integration in core has many more features and updates compared to the old integration. Scenarios work in the same way in both integrations…

“api_type”: “local”

Thank you for your patience.
I know that the integrated overkiz it certainly better than previously official addon, but i can see that the ‘‘Overkiz (by Somfy) - Custom component’’ was better than official integrated.
Both are on local, but custom was most quik reactive than official, if we don’t care about the integrate ‘‘customs’’ like zigbee connected to tahoma for exemple, he accept also the scene from tahoma.
Today , when i change a mode on a heating by HA to tahoma, I can see (on another page) tahoma accept the command , the heating change his mode, but the information arrive to HA most of 45 second after the first command… With the '‘custom’ it was almost instantany.
This means that something is wrong with the official.
And i’m on local…i couldn’t image the delay if it cross in cloud…

Once again thank you for the work because it’s not ‘‘your’’ job…
Maybe you could take inspiration from your ‘‘custom’’.
One think again : today i changed HA core from 2024.11.3 to 2024.12.0 , the result was a total lost of all components… i returned to 11.3…

Thank you.

My json file :

Best is to report issues via GitHub.

You say ‘both are on local’, but the Local API is not supported in the custom integration, thus you can’t compare this. The delay and connection issues are known issues.

See: