Unsupported devices: product 1734 (cooling not exposed) + 1505-1510 (THZONE) on Atlantic ducted heat pump

[pfhtz]

Hello, and thank you for this integration — it works very well on 5 of my 6 zones.
I have an Atlantic ducted (gainable) heat pump with 6 zones, managed by a HUB SHOGUN - PRT sans fil. Seven devices are reported as Unknown product, and one of them loses a real hardware capability as a result.
Integration version: 1.4
Home Assistant Core: 2026.8.2
Home Assistant OS: 18.2
Main problem — product 1734: cooling capability not exposed
One zone (ROOM_5, my "Chambre 2") is detected as Unknown product (1734) and exposed as heating only, although the hardware does support cooling.
Affected zone:

climate.unknown_product_1734_chauffage
hvac_modes:    [off, heat]
preset_modes:  [basic, prog, override]
min_temp: 16.0 / max_temp: 30.0

A correctly detected zone on the same installation (ROOM_4, detected as air_conditioner):

climate.air_conditioner_chambre_3_climatisation
hvac_modes:    [off, auto, cool, heat, fan_only, dry]
preset_modes:  [none, activity, eco, boost, basic, prog, override]
fan_modes:     [low, medium, high, auto, quiet]
swing_modes:   [up, middle_up, middle_down, down, on]

Evidence that product 1734 does support cooling
The integration already creates, for this very device, entities that only make sense on a cooling-capable zone:

1. A cooling setpoint number:

number.unknown_product_1734_temperature_consigne_cool = 24.0

2. A full weekly schedule for zone 2 (cooling) alongside zone 1 (heating):

sensor.unknown_product_1734_prog_01_lun_z1 = "06:00  20°C / 22:00  19°C"   <- heating setpoints
sensor.unknown_product_1734_prog_02_mar_z1 = "06:00  20°C / 22:00  19°C"
... (z1: mon->sun)

sensor.unknown_product_1734_prog_08_lun_z2 = "07:00  29°C / 21:00  24°C"   <- cooling setpoints
sensor.unknown_product_1734_prog_09_mar_z2 = "07:00  29°C / 21:00  24°C"
sensor.unknown_product_1734_prog_10_mer_z2 = "07:00  29°C / 21:00  24°C"
sensor.unknown_product_1734_prog_11_jeu_z2 = "07:00  29°C / 21:00  24°C"
sensor.unknown_product_1734_prog_12_ven_z2 = "07:00  29°C / 21:00  24°C"
sensor.unknown_product_1734_prog_13_sam_z2 = "07:00  29°C / 21:00  24°C"
sensor.unknown_product_1734_prog_14_dim_z2 = "07:00  29°C / 21:00  24°C"

The z2 schedule is byte-for-byte identical to the one on my correctly-detected cooling zones.
3. The climate entity is named Chauffage (heating) instead of Climatisation, which suggests the model falls back to a heating-only profile.
Raw capabilities exposed by product 1734 (71 entities)
Named entities:

temperature_consigne, temperature_consigne_cool, temperature_absence,
temperature_maximale, temperature_minimale, duree_delegation_z1,
duree_delegation_restante_z1, temperature_thermostat_z1,
mode_eco, mode_prog, flamme, zone_1, chauffage

Unnamed capability IDs:

17, 73, 157, 162, 163, 166, 171, 217, 218, 294, 295, 296, 303, 306, 350, 358,
100000, 100002, 100004, 100013, 100021, 100022, 100023, 100024, 100260, 100261,
100301, 100450, 102004, 102005, 102006, 102020, 102021, 102022, 102023, 102024,
102025, 102026, 103026, 103150

Secondary — the six THZONE devices are also unknown
All six zone thermostats are unrecognised, with consecutive product IDs:
Device Product ID Entities
THZONE_0 1505 4
THZONE_1 1506 4
THZONE_2 1507 4
THZONE_3 1508 4
THZONE_4 1509 2
THZONE_5 1510 2
They expose Cozytouch (binary_sensor) and Capability_100014 / Capability_100044 / Capability_218 sensors. The consecutive numbering suggests a single family that could be mapped in one go.
The HUB SHOGUN - PRT sans fil itself is also reported as unknown_product_1681.
Note
The integration does not implement a diagnostics dump, so I could not attach one — I hope the data above is enough. I'm very happy to run any test, dump any endpoint or try a patched branch if that helps.
Thanks a lot for your work!

Pierre

[mathieuletyrant]

Hello Pierre,

Thanks for the detailed report, it made the problem easy to find.

Product 1734 was actually mapped upstream back in February, but it never made it into a release. 1.4 is from December 2025, so you're on the latest version available and still missing the fix. Nothing you did wrong.

I maintain a fork where that fix is released, plus a few others: https://github.com/mathieuletyrant/cozytouch-hacs

It uses the same cozytouch domain, so remove the other one first. Your config entries are kept.

That should get Chambre 2 recognised as an air conditioner, with cooling, fan and swing like your other zones. It'll also put names on 7 of your 40 unnamed capabilities, mostly the air circulation ones plus the error code and wifi.

Your HUB SHOGUN and the six THZONE are still unmapped though, and that's where I could use your help.

I added a diagnostics dump so you don't have to retype anything this time. Settings, Devices & Services, Atlantic Cozytouch, then the three dots on a device entry and Download diagnostics. Each entry only holds the capabilities of the device it drives, so one file per zone would help. Ideally Chambre 2, one THZONE and the hub. Credentials and address are stripped automatically but have a look before posting.

Fair warning, I'm on holiday and haven't tested the diagnostics on real hardware, only against another user's capture. Tell me if it misbehaves.

With those files I should be able to map the THZONE family and your hub properly.

[pfhtz]

Hi Mathieu,
really sorry i didn t see your messages :/
I tried to do with your explications but nothing changed...
Could be possible to speak together directly by email or whatsapp to try to find solutions?
thank you for your help :)

[pfhtz]

I tried to download diagnostics for the problem room or try to go to system > repair but nothing appear...