It’s great the Somfy API is now working. Replacing the Tahoma component with the Somfy component means I don’t have the Tahoma component constantly spamming requests to tahomalink.com. It was making about 10x more requests than anything else on my network.
One downside I’ve noticed is I’ve lost the ability to set the “My” position on my blinds. With the Tahoma component, calling the cover.stop_cover service would be the same as pressing my/stop on the remote, which matched the Tahoma iOS app:
I’ve noticed the same, the tahomalink requests also always top my pi-hole permitted domains.
Somfy gives me this:
hass[20794]: 2019-09-27 20:00:48 WARNING (MainThread) [homeassistant.components.somfy] Cannot update devices
Hi there,
Somfy integration is now working for me :).
One last question : is there any way to get the automations (scenarios) from Tahoma ?
Hello,
Yes. My configuration Tahoma with api Somfy or without api Somfy. The scenes work well
https://www.home-assistant.io/components/tahoma/
##avec API##
username: !secret login
password: !secret mdp
exclude: ['rts:RollerShutterRTSComponent','rts:CurtainRTSComponent','rts:BlindRTSComponent','rts:VenetianBlindRTSComponent','rts:DualCurtainRTSComponent','rts:ExteriorVenetianBlindRTSComponent','io:ExteriorVenetianBlindIOComponent','io:RollerShutterUnoIOComponent','io:RollerShutterWithLowSpeedManagementIOComponent','io:RollerShutterVeluxIOComponent','io:RollerShutterGenericIOComponent','io:WindowOpenerVeluxIOComponent','io:VerticalExteriorAwningIOComponent','io:HorizontalAwningIOComponent','BridgeHUEComponent','HueLampHUEComponent','PodComponent','internal:TSKAlarmComponent','internal:PodV2Component','myfox:SomfyProtectSecurityCameraController','myfox:LightController','myfox:SomfyProtectAlarmController']
##sans API##
#username: !secret login
#password: !secret mdp
#exclude: [BridgeHUEComponent','HueLampHUEComponent','PodComponent','internal:TSKAlarmComponent','internal:PodV2Component','myfox:SomfyProtectSecurityCameraController','myfox:LightController','myfox:SomfyProtectAlarmController']
Hi, about the My button, there is nothing I can do on my side. Somfy does not expose anything about it.
Hey,
I just noticed that the position slider is working the other way then I expect.
This blind is actually closed and I would expect the slider on the other side. Is there a chance to change this? And would it also be possible to add this slider directly in the entitiy card using an input_number?
Hello,
I did like that to have both. I think we can do better but it works well.
entities:
- entity: cover.volet_cuisine
- entity: cover.volet_cuisine
full_row: true
type: 'custom:slider-entity-row'
show_header_toggle: false
title: Cuisine
type: entities
You will have to see with the creator of this slider to see how configure it. For HA, 0 means closed and 100 fully opened. If I reverse the values, the arrow won’t show the current state.
Ok, understood. Then I will try to add the sliders and have to remember that 0 means close, if I write an automation.
I don’t understand : I’m using the somfy component, and the tahoma :
somfy:
client_id: ....
client_secret: .....
tahoma:
username: [email protected]
password: "......"
exclude: ['rts:RollerShutterRTSComponent','rts:CurtainRTSComponent','rts:BlindRTSComponent','rts:VenetianBlindRTSComponent','rts:DualCurtainRTSComponent','rts:ExteriorVenetianBlindRTSComponent','io:ExteriorVenetianBlindIOComponent','io:RollerShutterUnoIOComponent','io:RollerShutterWithLowSpeedManagementIOComponent','io:RollerShutterVeluxIOComponent','io:RollerShutterGenericIOComponent','io:WindowOpenerVeluxIOComponent','io:VerticalExteriorAwningIOComponent','io:HorizontalAwningIOComponent','BridgeHUEComponent','HueLampHUEComponent','PodComponent','internal:TSKAlarmComponent','internal:PodV2Component','myfox:SomfyProtectSecurityCameraController','myfox:LightController','myfox:SomfyProtectAlarmController']
I can see my Somfy devices, but no scene from Tahoma :(.
All I have in my logs are :
2019-10-01 23:01:33 WARNING (SyncWorker_10) [homeassistant.components.tahoma] Unsupported type rtd:AlarmRTDComponent for Tahoma device Alarme
2019-10-01 23:01:33 WARNING (SyncWorker_10) [homeassistant.components.tahoma] Unsupported type rts:HorizontalAwningRTSComponent for Tahoma device Store
2019-10-01 23:01:33 WARNING (SyncWorker_10) [homeassistant.components.tahoma] Unsupported type rts:OnOffRTSComponent for Tahoma device Prise sam
2019-10-01 23:01:33 WARNING (SyncWorker_10) [homeassistant.components.tahoma] Unsupported type rts:OnOffRTSComponent for Tahoma device Prise Salon
weird I have nothing else in my configuration.
In development tools / service / scene_turn_on / you have nothing in the list
Attention this does not appear in somfy integration
I wan’t looking at the right place :). I have indeed my scene ! Thanks !
Is this confirmed ?
I called Somfy Oz and thats what I was told. I havent seen or heard otherwise. I have since then returned my Connexoon box to Somfy and am using Rfxcom to control my blinds. Its cheaper and works flawlessly.
Somfy have confirmed to me they have no plans to add the “My” option to the API.
Since this is essentially 1/3 of what my blinds can do, I guess I’ll have to move back to the Tahoma component.
If you have RTS motors, that’s definitely a good (better) solution. If you have IO, that won’t work though.
Are there any ways to get the Somfy Protect status with the Tahoma component ?
This thread is related to the official somfy api.
There is good news about the Somfy API component. Paulus want to use it as a proof of concept for a future HA enhancement 
The idea is to avoid end-user to create their own application on the Somfy developer portal and so ease the installation of the component. An application will be host directly by the HA cloud 
You can see more here:https://github.com/tetienne/somfy-open-api/issues/19
Can I ask are you using the Connexoon or the Tahoma box for ths? Thinking of getting these blinds myself and was going to get the Tahoma as it seems to be better supported by HA and other Smart home platforms.