3.2 KiB
title, description, ha_category, ha_iot_class, ha_release, ha_config_flow, ha_codeowners, ha_domain
title | description | ha_category | ha_iot_class | ha_release | ha_config_flow | ha_codeowners | ha_domain | ||
---|---|---|---|---|---|---|---|---|---|
Somfy | Instructions on how to set up the Somfy hub within Home Assistant. |
|
Cloud Polling | 0.95 | true |
|
somfy |
The Somfy integration will allow users to integrate their Somfy devices into Home Assistant using the official API, unlike the Tahoma integration.
Installation
Somfy is leveraging the new account linking service. This means that to set up Somfy, you only need to go to the integrations page and click on add new integration.
Installation with own developer account
It is possible to create your own developer account and configure Somfy via that.
Setting up developer account
- Visit https://developer.somfy.com.
- Log in using your Somfy credentials.
- Open the My Apps menu.
- Add a new App:
- App Name: Home Assistant
- Callback URL:
<YOUR_HOME_ASSISTANT_URL>/auth/external/callback
- Description: Home Assistant instance
- Product: Somfy Open API
- Once Home Assistant restarted, go to Configuration>Integrations.
- Select the Somfy integration.
Configuration
# Example configuration.yaml entry
somfy:
client_id: CONSUMER_KEY
client_secret: CONSUMER_SECRET
{% configuration %} client_id: description: Your Somfy consumer key. required: true type: string client_secret: description: Your Somfy consumer secret. required: true type: string optimistic: description: Set optimistic mode. required: false default: false type: boolean {% endconfiguration %}
optimistic mode should only be used when the integration is not able to gain information on whether a cover is open or closed (e.g., RTS devices). It will attempt to track the status within Home Assistant. This mode should only be used if Home Assistant is the only way you operate the blind. If you also use the physical remote control or the Somfy app, Home Assistant will become out of sync.
Potential duplicate with the Tahoma integration
If you use the Tahoma integration, you will have to exclude the covers added by this one. Otherwise, they will be added twice.
# Example configuration.yaml entry
tahoma:
username: YOUR_USERNAME
password: YOUR_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",
]