Delta Dore Tydom

English | Français

This is a custom component for Home Assistant.

The Delta Dore Tydom integration allows you to monitor and control your Delta Dore Tydom smart home gateway.

The integration works in local or cloud mode, depending on its configuration. The Delta Dore gateway can be detected using DHCP discovery.

Contents

• Feature highlights
• Tested hardware
• Requirements
• Installation
• Configuration
• Troubleshooting
• Capturing data for unsupported devices
• TYXAL+ remote management
• Known limitations
• Security
• Contributing

This integration sets up the following platforms.

Platform	Description
alarm_control_panel	Controls a TYXAL alarm.
binary_sensor	Reports binary states and diagnostics.
button	Exposes stateless controls such as gate, garage door and alarm actions.
climate	Controls heating, cooling and ventilation.
cover	Controls shutters, blinds and awnings.
event	Reports physical remote-control and wall-switch button presses.
light	Controls lights and dimmers.
lock	Controls a lock.
number	Controls writable numeric settings exposed by a device.
scene	Activates TYDOM scenes.
select	Controls writable enumerated settings exposed by a device.
sensor	Reports measurements and device information.
switch	Controls binary outputs, plugs and TYDOM moments.
update	Installs supported TYDOM firmware updates.
weather	Reports weather information.

Feature highlights

• Receive live state changes published by the gateway and use the configured refresh interval to reconcile data which is not pushed automatically.
• Expose genuine TYDOM light, plug, shutter and awning groups as native Home Assistant entities, including the corresponding gateway-provided total groups when present.
• Combine the TWC_UP, TWC_DOWN and TWC_STOP scenarios generated by Tywell into one native cover, using feedback from its configured shutter targets when available.
• Keep Tywell wall-controller sensors, area-backed climate control and companion weather or shutter controls attached to the same physical device across the different endpoint layouts advertised by TYDOM.
• Expose alarm modes and zones, event history and acknowledgement, supported remote maintenance operations, and native automation events from compatible wall switches and remote controls.

Tested hardware

The integration is capability-driven: compatible devices are discovered from the usage types and metadata advertised by TYDOM rather than from a fixed model allowlist. The following hardware and configurations have been tested by contributors; this is not an exhaustive compatibility list.

Category	Confirmed hardware or configuration	Home Assistant support
Alarm and safety	TYXAL+, CS8000, CSX40 and DFR TYXAL+ smoke detectors	Alarm control, zone modes, diagnostics, smoke state, event history, acknowledgement and supported remote product/zone management.
Climate and heating	Tybox 5101 with Typass ATL, Tywell Control, Tywell 2050, TYXIA 1137, Calybox and RF 6600 FP	Area-backed climate control, temperatures, heating and cooling setpoints, operating modes, humidity, battery and capability-driven heating or pilot-wire commands where advertised.
Energy monitoring	TYWATT 1000, TYWATT 2000 and TYWATT 5400 with EMIC	Power, current and energy measurements, including heating and domestic hot water channels where advertised.
Gates and garage doors	TYXIA 4620 dry-contact receivers	Stateless toggle buttons matching the receiver's open/stop/close pulse sequence, without claiming unavailable position feedback.
Lighting and switching	TYXIA 4910 fixed-output and TYXIA 4940 dimming receivers configured under TYDOM's Others usage, TYXIA 6610, Delta Dore Easy Plug and compatible X3D equipment	Lights, brightness, switches and plugs according to the capabilities reported by the endpoint.
Openings and covers	TYMOOV and Well'com roller shutters, BSO installations, Profalux MOT-C1Z06F and MOT-C1Z10F Zigbee shutters, TYXIA 5731 awnings, K-Line DVI openings and K-Line POD doors	Native covers with up, down, stop and position control where advertised; awning commands and positions are translated into Home Assistant open/close semantics; opening/contact state is exposed when feedback is supplied.
Physical controls	TYXIA 2600 wall switches, TYXIA 1410 remote controls and TL 2000 Tyxal+ remote controls	Native Home Assistant button events for automations, with battery diagnostics where supplied.
Sensors	Tysense Sun and Tysense Thermo/SE 2000	Solar irradiance in W/m², outdoor temperature and associated diagnostics where supplied.
Groups and automation	Gateway-provided light, plug, shutter and awning groups; TYDOM scenes and moments; Tywell shutter scenarios	Native grouped lights, switches and covers, scene activation, moment switches and one combined Tywell shutter cover.
Ventilation	Naviclim Atlantic 875311	Climate control, operating modes and supported fan speeds.

Devices not listed above may still work fully or expose a useful subset of their attributes. Please include sanitised debug data when reporting an untested device so support can be extended without hard-coding one installation.

Requirements

• Home Assistant 2024.7.0 or newer.
• HACS 2.0.1 or newer when installing or updating through HACS.
• Network access from Home Assistant to the local TYDOM gateway or to mediation.tydom.com, according to the configured host.

Installation

The preferred way to install the Delta Dore Tydom integration is through HACS.

Add the integration from Home Assistant's Settings > Devices & services page.

Manual installation

1. Open the Home Assistant configuration directory containing configuration.yaml.
2. Create the custom_components directory if it does not already exist.
3. Inside custom_components, create a directory named deltadore_tydom.
4. Download all files from this repository's custom_components/deltadore_tydom directory.
5. Place the downloaded files in the new custom_components/deltadore_tydom directory.
6. Restart Home Assistant.
7. Open Settings > Devices & services, select Add Integration, and search for Delta Dore Tydom.

Upgrading

For a HACS installation, install the update offered by HACS. Releases include a generated deltadore_tydom.zip archive containing a consistent integration version.

For a manual installation, replace the complete custom_components/deltadore_tydom directory with the files from one release, then restart Home Assistant. Do not combine individual files from different releases or test branches.

Configuration

Configuration is performed through the Home Assistant user interface.

Connection modes

The selected configuration mode determines how the TYDOM gateway password is obtained. The host determines whether the connection itself is local or uses Delta Dore's mediation service.

Mode	Credentials	Connection
Cloud	Enter the Delta Dore account email address and password. The integration retrieves the matching gateway password automatically.	Use the gateway hostname or IP address for a local connection, or mediation.tydom.com for a cloud connection.
Manual	Enter the TYDOM gateway password directly. A Delta Dore account is not required during setup.	Normally the local gateway hostname or IP address; any compatible explicitly configured host is accepted.

Configuration fields

Field	Required	Description
Host	Yes	Local TYDOM hostname or IP address, or mediation.tydom.com for a cloud connection.
MAC address	Yes	The gateway MAC address as 12 hexadecimal characters without separators.
Delta Dore email and password	Cloud mode	Credentials for the Delta Dore account containing the gateway. These are used to retrieve its gateway password.
TYDOM password	Manual mode	The gateway password, which is different from the ordinary Delta Dore account password.
Refresh interval	Yes	Periodic refresh interval from 1 to 1,440 minutes; the default is 30 minutes. Push events remain active between refreshes.
Home, Away and Night zones	No	Comma-separated TYXAL zone IDs from 0 to 8, for example 1,2,4. Each field defines the zones armed by that Home Assistant alarm mode.
Alarm PIN	No	Required when using Home Assistant to change the alarm mode; not required for read-only alarm state.

After setup, open the integration's Configure menu to change the refresh interval, alarm zones or PIN.

Troubleshooting

Enable debug logging

Open Settings > Devices & services, select Delta Dore Tydom, open the three-dot menu and select Enable debug logging. Reproduce the problem, then use the same menu to disable debug logging and download the resulting log.

To capture startup behaviour, add the following to configuration.yaml and restart Home Assistant:

logger:
  default: info
  logs:
    custom_components.deltadore_tydom: debug

Authentication and communication errors

Error	Meaning	Checks
Authentication error	The supplied or retrieved credentials were rejected.	In Cloud mode, verify the Delta Dore email address, account password and gateway MAC. In Manual mode, verify that the TYDOM gateway password—not the Delta Dore account password—was entered.
Communication error	Home Assistant could not reach the configured host or complete the connection.	Verify the hostname or IP address, local network access, DNS, gateway power and, when using cloud access, connectivity to mediation.tydom.com.

TYWATT readings do not appear immediately

TYWATT 1000, TYWATT 2000 and TYWATT 5400/EMIC energy data may not all appear immediately after setup or restart. The integration requests registered TYWATT energy data once at startup and then follows the configured refresh interval, which is 30 minutes by default. The gateway or measuring equipment may also return a new value only when its own counter is updated.

To request an additional reading without waiting for the next scheduled poll, open the corresponding TYWATT device and press Refresh energy data. Allow Home Assistant additional time to create long-term statistics before expecting a newly eligible sensor to appear in the Energy dashboard.

Remove obsolete devices

Open Settings > Devices & services > Delta Dore Tydom > Devices, open the obsolete device's menu and select Remove device. This removes its Home Assistant device-registry entry; it does not delete anything from the TYDOM gateway or official application. A device may be discovered again if the gateway still advertises it.

After an entity type changes or a technical placeholder is filtered out, its old registry entry may first appear as Unavailable or No longer provided. Verify that the genuine replacement device is present and working before using Remove device. Filtered placeholders, such as empty Profalux Produit X endpoints, will not be recreated while they remain empty.

Capturing data for unsupported devices

The repository includes a read-only capture tool for documenting devices and protocol behaviour that the integration does not yet support:

python3 tools/capture_tydom_data.py \
  --host 192.168.1.100 \
  --mac AABBCCDDEEFF \
  --password '<Tydom gateway password>' \
  --duration 120

The tool requests the current configuration, device, area, scenario, group and moment resources, including /devices/meta, /devices/cmeta, /devices/data, /areas/meta, /areas/cmeta and /areas/data. It then continues listening for events while the equipment is operated physically or from the Tydom app.

Each run produces:

• raw_messages.txt, containing timestamped and replayable WebSocket frames;
• parsed_messages.json, containing normalised URIs, methods or response statuses, and decoded payloads.

Passwords, tokens, authorisation headers and email addresses are redacted before the files are written. Device identifiers, names, topology and state values are retained because they are needed for protocol analysis, so captures must still be reviewed before being shared publicly.

For a useful device capture, perform one clearly identifiable action, wait about ten seconds, perform the reverse action, and record both timestamps. The capture records responses and events published by the gateway; it cannot necessarily reveal the exact outbound request sent by another client such as the official mobile application.

See the complete capture guide for local and remote connection examples, output analysis, parser validation and security guidance. The separate endpoint discovery guide describes how to probe available API resources and HTTP methods.

TYXAL+ remote management

The alarm control panel provides services for the TYXAL+ functions that are useful in Home Assistant:

• deltadore_tydom.get_events returns alarm history and can filter it to alarm, activation/deactivation or unacknowledged events;
• deltadore_tydom.acknowledge_events acknowledges pending alarm events;
• deltadore_tydom.get_alarm_products lists configured products and zones;
• deltadore_tydom.enter_alarm_maintenance unlocks remote configuration and puts a disarmed CS8000 into maintenance mode;
• deltadore_tydom.get_alarm_product_configuration reads a product's active state and zone assignment;
• deltadore_tydom.configure_alarm_product enables or disables a product and can assign it to another zone;
• deltadore_tydom.rename_alarm_zone changes a zone's custom name, or clears its label when supplied with an empty name;
• deltadore_tydom.exit_alarm_maintenance returns the CS8000 to its normal disarmed state and locks remote configuration again.

Use the first service to obtain the product and zone IDs required by the other services. Product configuration requires the CS8000 to be disarmed and the TYXAL installer code supplied in each service call. Enter maintenance before reading or changing product configuration, and always exit maintenance when finished. The installer code is used only for the request and is redacted from logs. Product deletion, access codes, telephone settings and siren configuration are not exposed.

The TYXAL alarm device also provides an Acknowledge events button for convenient dashboard use without requiring a service call or automation.

Known limitations

• TYXIA 4620 gate and garage receivers provide an impulse command but no position or direction feedback. Home Assistant therefore exposes a stateless toggle button and cannot determine whether the next pulse will open, stop or close the motor.
• The native Tywell shutter cover replays the TWC_UP, TWC_DOWN and TWC_STOP scenarios created by TYDOM. Its shutter membership must therefore be configured in the official application, and aggregate position is only available when all configured targets provide suitable feedback.
• Battery-powered and radio devices report according to their own schedule. Refreshing or polling the gateway cannot force a sleeping device to transmit a newer value.
• An exact model name is displayed only when TYDOM provides reliable product or tutorial metadata. Other compatible devices retain a generic Delta Dore model name rather than being guessed from broad capabilities.
• The capture tool records messages returned or published by the gateway. It cannot always reveal the exact outbound request sent by the official mobile application.
• TYXAL remote management exposes the safe, confirmed operations documented above. Product deletion, access codes, telephone settings and siren configuration are not supported.

Security

Do not report suspected vulnerabilities in a public issue. Read the security policy and use the private reporting process described there.

Contributing

If you would like to contribute, please read the contribution guidelines.

---