COMPONENT INDEX / INSTALLABLE COMPONENT / v0.2.0
Awnings
Somfy RTS awnings through an ESPSomfy-RTS radio node (ESP32 + CC1101), with the awnings' wind sensor
01 / REQUIREMENTS
What it needs
- rts awning
- Brand:
- Somfy
- Protocol:
- Somfy RTS, 433 MHz
- Setup note:
- each awning is paired to the node as one more virtual remote; a Telis handset keeps working and the node follows it
- esp32 board
- Recommended:
- m5stack-atom-lite
- Quantity:
- 1
- Setup note:
- runs ESPSomfy-RTS firmware, not ESPHome, so it is not a Bluetooth proxy; a second board is needed for those
- radio transceiver
- Recommended:
- cc1101
- Setup note:
- the module's band has to match the awnings (433.42 MHz for Somfy RTS in Europe); wired to the board over SPI
- mqtt broker
- Setup note:
- the home provides it (Mosquitto, for example); the node and the frame bridge publish to it
Home Assistant integrations
mqttcorean MQTT broker (Mosquitto); the node publishes under its own root topic
espsomfy-rtsfirmwareflashed over USB, then Wi-Fi and the radio pins in its web page; pair each awning from its own virtual remote
02 / YOUR PROJECT
Add it to your home project
domosenso add [email protected]
# Fill in your home-specific inputs
domosenso render awnings
domosenso statusRun these through uv run --project <catalog checkout> domosenso from your separate home folder. Adding and rendering files does not deploy them.
03 / CONFIGURATION
Your inputs
| Input | Type | Configuration |
|---|---|---|
covers | list[{name, shade_id, entity_id?}] | Supply your value |
mqtt_root_topic | string | Default available |
wind_sensor | entity_id | Default available |
node_id | string | Supply your value |
node | {name?, model?, area?, url?} | Default available |
wind_name | string | Default available |
wind_off_delay | int | Default available |
wind_last_heard | {id, name} | Default available |
wind_silent_hours | int | Default available |
wind_check_time | HH:MM:SS | Default available |
retract_at_sunset | bool | Default available |
notify | action | Supply your value |
Before a live change
Field experience is limited to the maintainer’s installation. Review device compatibility for your home.
Configuration validation is not a guarantee of hardware compatibility. Review the component source and deployment plan; verify behavior after deployment.