Somfy TaHoma Switch | Blinds and Windows | Version 1.00

Introduction

This driver has been designed to provide two-way control of the Somfy TaHoma Switch and associated windows and blinds. Ensure that the TaHoma Switch is connected to the same network as the RTI processor and is accessible through its app interface. Please make sure the device is correctly set up and working independently before integration with this driver.

Driver Features

High-level overview of the driver’s features.

• Communication through HTTP to one or multiple Somfy TaHoma Switches.

• Blind and Window monitoring and adjustment.

If you would like help with any other Home Control Device that connects to a Somfy TaHoma Switch, contact us at https://support.janustechnology.co.uk and we’ll be happy to help develop support for a new device.

Version History

Version 1.00 – 26 June 2026

• initial release

System Requirements & Prerequisites

RTI System Requirements

• Integration Designer: Apex ID 10.8

• XP FW: 25.1.27 or later.

Driver Configuration

Gateways

• Number of Gateways: The number of Somfy TaHoma Switches that are being connected to the driver. This must be at least 1, or the gateways will not configure properly.

Gateway Information (one sections per gateway)

• IP: The IP address of the TaHoma Switch that the driver is connecting to.

• Token: The api token used to connect to the TaHoma Switch. This can be generated by going to the TaHoma by Somfy app, selecting ‘Account’, then ‘Configuration of the installation’, then selecting ‘Access the parameters’ for the correct TaHoma Switch. Find the ‘PIN’ field and tap it 7 times to activate Developer Mode and press ‘Accept’. Then select ‘Developer Mode’ then ‘Generate a token’. Copy this token into the RTI Configuration to allow communication between the driver and the TaHoma switch.

• Gateway Name: The friendly name of the gateway used by the installer to differentiate between gateways.

Friendly Names (one section per gateway)

Once these names are set, the driver will generate the appropriate system functions, variables, tags, and Integration Designer sources for each device that you can add from the driver to the source list to assist in auto-programming.

Opening Times (one section per gateway)

Apex Actions

• Discover Devices: This is the method by which windows and blinds are discovered. This must be pressed after entering the gateway information in order to add the associated devices to Integration Designer and the driver.

Driver Functions

Send Command

Sends a POST command directly to a TaHoma switch via an HTTP request. This allows for direct command to a device if desired.

Parameters:

• Endpoint – The endpoint for the HTTP request being sent to the TaHoma Switch.

• Body – The body of the HTTP request being sent to the TaHoma Switch.

• Gateway – The TaHoma Switch which the driver is sending the command to.

For each Window or Blind, there are the following functions:

Set Position:

Set the position of a window or blind, ranging from 0 (fully closed) to 100 (fully open).

Parameters:

• Position – The desired position for the window or blind.

Open:

Fully open the window or blind.

The Set position and Open commands may be blocked by the Switch due to local weather conditions, in which case the window will not open beyond 2%.

Close:

Fully close the window or blind.

Stop:

Stop any movement of a window or blind and freeze it in its current position.

Driver Variables

For each Gateway, there is the following variable.

Connection Status

Indicates whether the gateway is currently connected.

• Type: Boolean

For each Window or Blind, there are the following variables

Target Position

Reports the user set target position of the Window or Blind from 0 (fully closed) to 100 (fully open). If the blind or window is not executing a command and has not been sent a command, then this will be the same as the Position In Motion variable. This is the most appropriate variable to use for slider values.

• Type: integer

Position In Motion

Reports the current position of the Window or Blind from 0 (fully closed) to 100 (fully open), including updating with a predicted position while the blind or window is in motion.

• Type: integer

Instance Id

The friendly name of the Window or Blind.

• Type: string

Tags

This driver uses the following non-standard tags. For default tags, reference the master tag list.

Gateway Connected (V)

• Variable usage: Current connection status of a gateway.

Level In Motion (V)

• Variable usage: The current position of the blind or window, which updates as the device is in motion.

Level (F/V)

• Function usage: Sets the target position of the device and executes a command to move the device to the desired position.

• Variable usage: The target position of the device. This is set to the user desired level and then not updated until movement is complete or stopped.

Open (F)

• Function usage: Fully opens the device, setting the position to 100.

Closed (F)

• Function usage: Fully closes the device, setting the position to 0.

Stop (F)

• Function usage: Stops any currently executing movement commands.

Instance ID (V)

Troubleshooting

If the driver cannot control the unit confirm the following:

• The TaHoma system is online and can be controlled using the TaHoma Switch for Somfy App.

• The correct IP address and token are defined in the RTI driver properties for the units control interface.

System Testing

Integration Designer: 11.2

XP Processor Model: XP-3

XP Processor Firmware: 25.9.24

Device Model(s): Somfy TaHoma Switch

Support Contact

If you encounter any issues with the driver, please contact us at https://support.janustechnology.co.uk, and we will be happy to assist however needed.

Disclaimer of liability

The company shall not be liable for any issues, damages, or costs that may arise from the use of our driver software. While we strive to ensure that all versions of our driver are backward compatible, we cannot guarantee that this will always be the case. Users are advised to thoroughly test the driver in their specific environments and configurations before deployment to ensure compatibility and proper functionality. The company makes every effort to provide a reliable and functional product, but the driver is provided “as is” without warranties of any kind, either express or implied. The user assumes full responsibility for any loss, damage, or disruption caused using our driver, including, but not limited to, hardware malfunctions, data loss, or system failures. By using our driver, you acknowledge that you have read and understood this disclaimer, and you agree to release and hold harmless the company from all liabilities associated with its use.