Tuya TS0601_TZE204_umh2xkoc thermostat unsupported

[kris-ramius]

Hi!

This is my first post on Git, so please be patient ;)

I'm trying to add a floor heating thermostat to my HA via z2m but this is the result

I have found this discussion relating to the same model
#21826

Based on that I have created new converter

const exposes = require('zigbee-herdsman-converters/lib/exposes');
const tuya = require('zigbee-herdsman-converters/lib/tuya');
const e = exposes.presets;
const ea = exposes.access;

const definition = {
    fingerprint: tuya.fingerprint('TS0601', ['_TZE204_umh2xkoc']),
    model: 'TS0601_floor_thermostat',
    vendor: 'TuYa',
    description: 'Zigbee thermostat for electric floors',
    fromZigbee: [tuya.fz.datapoints],
    toZigbee: [tuya.tz.datapoints],
    onEvent: tuya.onEventSetTime, // Add this if you are getting no converter for 'commandMcuSyncTime'
    configure: tuya.configureMagicPacket,
    exposes: [
        e.climate()
            .withSystemMode(['off', 'heat'], ea.STATE_SET)
            .withPreset(['manual', 'auto'])
            .withRunningState(['idle', 'heat'], ea.STATE)
            .withSetpoint('current_heating_setpoint', 5, 35, 0.5, ea.STATE_SET)
            .withLocalTemperature(ea.STATE).withDescription('Floor temperature')
            .withLocalTemperatureCalibration(-9, 9, 0.1, ea.STATE_SET).withDescription('Calibration floor temperature sensor'),
        e.deadzone_temperature().withValueMin(0).withValueMax(5).withValueStep(1).withDescription('Floor temperature'),
        e.child_lock(),
        ...tuya.exposes.scheduleAllDays(ea.STATE_SET, 'HH:MM/C HH:MM/C HH:MM/C HH:MM/C'),
    ],
    meta: {
        tuyaDatapoints: [
            [1, 'system_mode', tuya.valueConverterBasic.lookup({'heat': true, 'off': false})],
            [2, 'preset', tuya.valueConverter.tv02Preset()],
            [16, 'current_heating_setpoint', tuya.valueConverter.divideBy10],
            [24, 'device_temperature', tuya.valueConverter.divideBy10],
            [27, 'local_temperature_calibration', tuya.valueConverter.localTempCalibration2],
            [36, 'running_state', tuya.valueConverterBasic.lookup({'heat': tuya.enum(0), 'idle': tuya.enum(1)})],
            [40, 'child_lock', tuya.valueConverter.lockUnlock],
            [102, 'local_temperature', tuya.valueConverter.divideBy10],
            [103, 'deadzone_temperature', tuya.valueConverter.raw],
            [110, 'schedule_monday', tuya.valueConverter.thermostatScheduleDayMultiDP],
            [109, 'schedule_tuesday', tuya.valueConverter.thermostatScheduleDayMultiDP],
            [108, 'schedule_wednesday', tuya.valueConverter.thermostatScheduleDayMultiDP],
            [107, 'schedule_thursday', tuya.valueConverter.thermostatScheduleDayMultiDP],
            [106, 'schedule_friday', tuya.valueConverter.thermostatScheduleDayMultiDP],
            [105, 'schedule_saturday', tuya.valueConverter.thermostatScheduleDayMultiDP],
            [101, 'schedule_sunday', tuya.valueConverter.thermostatScheduleDayMultiDP],
        ],
    },
    whiteLabel: [{vendor: 'ELECTSMART', model: 'EST-120Z'}],
};
module.exports = definition;

And I added it in the Studio Code Server

After several resets of the z2m, HA and thermostat itself there are no effects.

If anyone of you could tell me what am I doing wrong, I would be really grateful :)

Thanks!

PS: thermostat works properly, just doesn't connect to HA

[andrei-lazarov]

Hi. Check the log when Z2M starts (Not in Z2M UI), to see if the converter lodas. HA -> Apps (Add-ons) -> Z2M -> Log:

[2026-03-06 20:41:36] info: z2m: Loaded external converter 'test.js'.

I tried the code and it loads fine for me.
Try to save it from Z2M UI: Settings -> Dev console -> External converters

[kris-ramius]

Hi Andrei and thanks for the advise!
I can't find any message like yours in the log.
I have added the converter through the UI and it shows in the Studio Code Server, but still thermostat's status hasn't changed.

I remembered one thing. Few weeks back when I started battling this, I was able to make the z2m recognize the thermostat based on my converter. But when I tried to add datapoints it all crashed. Would it be possible, that z2m still "remembers" that old definition? Maybe I need to delete it in some config file to get a clean start?

[kris-ramius]

Ok there's progress. I added to z2m configuration.yaml following:
external_converters:

• termostat_2.js

Now it is recognized by z2m and I can turn it on. But everyting else is complete mess. I guess now I need to work with datapoints to make it work properly