Issues with new Tuya Temperature & Humidity sensor _TZE284_vvmbj46n

[latez]

Device is being reported as unsupported. I've attempted to add it using a hackey custom external converter

`const fz = require('zigbee-herdsman-converters/converters/fromZigbee');
const tz = require('zigbee-herdsman-converters/converters/toZigbee');
const exposes = require('zigbee-herdsman-converters/lib/exposes');
const reporting = require('zigbee-herdsman-converters/lib/reporting');
const extend = require('zigbee-herdsman-converters/lib/extend');
const ota = require('zigbee-herdsman-converters/lib/ota');
const tuya = require('zigbee-herdsman-converters/lib/tuya');
const utils = require('zigbee-herdsman-converters/lib/utils');
const globalStore = require('zigbee-herdsman-converters/lib/store');
const e = exposes.presets;
const ea = exposes.access;
const legacy = require('zigbee-herdsman-converters/lib/legacy');

const definition = {
zigbeeModel: ['TS0601'],
model: 'TS0601',
vendor: '_TZE284_vvmbj46n',
description: 'Temperature & humidity sensor with clock - xpl',
fromZigbee: [legacy.fromZigbee.nous_lcd_temperature_humidity_sensor, fz.ignore_tuya_set_time],
toZigbee: [legacy.toZigbee.nous_lcd_temperature_humidity_sensor],
onEvent: tuya.onEventSetLocalTime,
configure: async (device, coordinatorEndpoint, logger) => {
const endpoint = device.getEndpoint(1);
await reporting.bind(endpoint, coordinatorEndpoint, ['genBasic']);
},
exposes: [
e.temperature(), e.humidity(), e.battery(),
e.numeric('temperature_report_interval', ea.STATE_SET).withUnit('min').withValueMin(1).withValueMax(120)
.withValueStep(1)
.withDescription('Temperature Report interval'),
e.numeric('humidity_report_interval', ea.STATE_SET).withUnit('min').withValueMin(1).withValueMax(120)
.withValueStep(1)
.withDescription('Humidity Report interval'),
e.enum('temperature_unit_convert', ea.STATE_SET, ['celsius', 'fahrenheit']).withDescription(
'Current display unit'),
e.enum('temperature_alarm', ea.STATE, ['canceled', 'lower_alarm', 'upper_alarm'])
.withDescription('Temperature alarm status'),
e.numeric('max_temperature', ea.STATE_SET).withUnit('°C').withValueMin(-20).withValueMax(60)
.withDescription('Alarm temperature max'),
e.numeric('min_temperature', ea.STATE_SET).withUnit('°C').withValueMin(-20).withValueMax(60)
.withDescription('Alarm temperature min'),
e.enum('humidity_alarm', ea.STATE, ['canceled', 'lower_alarm', 'upper_alarm'])
.withDescription('Humidity alarm status'),
e.numeric('max_humidity', ea.STATE_SET).withUnit('%').withValueMin(0).withValueMax(100)
.withDescription('Alarm humidity max'),
e.numeric('min_humidity', ea.STATE_SET).withUnit('%').withValueMin(0).withValueMax(100)
.withDescription('Alarm humidity min'),
],
};

module.exports = definition;
`

This has been met with little to no success.

Info 2025-01-28 00:13:21z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"interview_successful","meta":{"description":"Temperature & humidity sensor with clock","friendly_name":"0xa4c138730decf8b0","model":"TS0601","supported":true,"vendor":"_TZE284_vvmbj46n"},"type":"pairing"}'
Info 2025-01-28 00:13:21z2m:mqtt: MQTT publish: topic 'homeassistant/sensor/0xa4c138730decf8b0/linkquality/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state"}],"device":{"identifiers":["zigbee2mqtt_0xa4c138730decf8b0"],"manufacturer":"_TZE284_vvmbj46n","model":"Temperature & humidity sensor with clock (TS0601)","name":"0xa4c138730decf8b0","via_device":"zigbee2mqtt_bridge_0x187a3efffe99f9c0"},"enabled_by_default":false,"entity_category":"diagnostic","icon":"mdi:signal","json_attributes_topic":"zigbee2mqtt/0xa4c138730decf8b0","name":"Linkquality","object_id":"0xa4c138730decf8b0_linkquality","origin":{"name":"Zigbee2MQTT","sw":"1.39.0","url":"https://www.zigbee2mqtt.io"},"state_class":"measurement","state_topic":"zigbee2mqtt/0xa4c138730decf8b0","unique_id":"0xa4c138730decf8b0_linkquality_zigbee2mqtt","unit_of_measurement":"lqi","value_template":"{{ value_json.linkquality }}"}'
Info 2025-01-28 00:13:21z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"definition":{"description":"Temperature & humidity sensor with clock","exposes":[{"access":1,"category":"diagnostic","description":"Link quality (signal strength)","label":"Linkquality","name":"linkquality","property":"linkquality","type":"numeric","unit":"lqi","value_max":255,"value_min":0}],"model":"TS0601","options":[],"supports_ota":false,"vendor":"_TZE284_vvmbj46n"},"friendly_name":"0xa4c138730decf8b0","ieee_address":"0xa4c138730decf8b0","status":"successful","supported":true},"type":"device_interview"}'
Info 2025-01-28 00:13:21z2m:mqtt: MQTT publish: topic 'homeassistant/sensor/0xa4c138730decf8b0/last_seen/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state"}],"device":{"identifiers":["zigbee2mqtt_0xa4c138730decf8b0"],"manufacturer":"_TZE284_vvmbj46n","model":"Temperature & humidity sensor with clock (TS0601)","name":"0xa4c138730decf8b0","via_device":"zigbee2mqtt_bridge_0x187a3efffe99f9c0"},"device_class":"timestamp","enabled_by_default":false,"entity_category":"diagnostic","icon":"mdi:clock","json_attributes_topic":"zigbee2mqtt/0xa4c138730decf8b0","name":"Last seen","object_id":"0xa4c138730decf8b0_last_seen","origin":{"name":"Zigbee2MQTT","sw":"1.39.0","url":"https://www.zigbee2mqtt.io"},"state_topic":"zigbee2mqtt/0xa4c138730decf8b0","unique_id":"0xa4c138730decf8b0_last_seen_zigbee2mqtt","value_template":"{{

Link to device - https://www.aliexpress.us/item/3256805815064396.html?spm=a2g0o.order_list.order_list_main.17.6b851802FpS1ZO&gatewayAdapt=glo2usa

It appears to be the same as previous similar devices though a bit smaller.

[Koenkk]

Could you try to:

• Stop Z2M
• Open data/database.db with a text editor and change all occurrences of _TZE284_vvmbj46n to _TZE200_vvmbj46n
• Start Z2M and see if the device now works

[latez]

Just did that, they must have changed some items on this 'new' hardware - while it did get identified now the values are missing.

[latez]

Looks like everything started working with time, cheers!!

[Koenkk]

Added! You can change back the manufacturer name after updating.

Changes will be available in the dev branch in a few hours from now and in the next release which is every 1st of the month.