danieledwardgeorgehitchcock

Try this: ```javascript const exposes = require('zigbee-herdsman-converters/lib/exposes'); const fz = require('zigbee-herdsman-converters/converters/fromZigbee'); const tz = require('zigbee-herdsman-converters/converters/toZigbee'); const reporting = require('zigbee-herdsman-converters/lib/reporting'); const extend = require('zigbee-herdsman-converters/lib/extend'); const e = exposes.presets; const ea =...

Just tweaked the code in the above converter. Could you give that a whirl?

Ok, I feel that the above is good progress - I'm coding this blind using some existing converters as templates so, there may be a few things that need some...

Ok, It's good that the states are updating correctly so I'd still say we are moving in the right direction! I stripped a lot of the converters out as I...

Yes, I knew that this wouldn't change much but just wanted to try a few things first. Try this one: ```javascript const exposes = require('zigbee-herdsman-converters/lib/exposes'); const fz = require('zigbee-herdsman-converters/converters/fromZigbee'); const...

Ok, Based on all of the above, this should hopefully give you everything in a working state: ```javascript const exposes = require('zigbee-herdsman-converters/lib/exposes'); const fz = require('zigbee-herdsman-converters/converters/fromZigbee'); const tz = require('zigbee-herdsman-converters/converters/toZigbee');...

This should be fixed in the `Dev` branch of Z2M and will be available in the release at the start of next month

It looks like this is coming from the device itself and is therefore not a Z2M issue

I don't suppose you have a TuYa Zigbee Gateway at hand? As this is a new TuYa device type to Zigbee2MQTT, we need to find out the TuYa device Data...

[Here's](https://www.zigbee2mqtt.io/advanced/support-new-devices/03_find_tuya_data_points.html) an article that will help you when you receive it (always good to keep it in the drawer anyway. Happy to help you through it when you start investigating