Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[New device support]: Tuya Water Valve (Tuya FJKZ005C-Y) #15124

Closed
marc3k18 opened this issue Nov 21, 2022 · 37 comments
Closed

[New device support]: Tuya Water Valve (Tuya FJKZ005C-Y) #15124

marc3k18 opened this issue Nov 21, 2022 · 37 comments
Labels
new device support New device support request

Comments

@marc3k18
Copy link

Link

https://developer.tuya.com/en/docs/iot/Zigbee-Water-valve-controller-access-standard?id=Kbahvojbqzvgl

Database entry

{"id":36,"type":"EndDevice","ieeeAddr":"0xa4c138afef85b372","nwkAddr":33813,"manufId":4417,"manufName":"_TZ3210_0jxeoadc","powerSource":"Battery","modelId":"TS0049","epList":[1],"endpoints":{"1":{"profId":260,"epId":1,"devId":0,"inClusterList":[61184,0],"outClusterList":[25,10],"clusters":{"genBasic":{"attributes":{"modelId":"TS0049","manufacturerName":"_TZ3210_0jxeoadc","powerSource":3,"zclVersion":3,"appVersion":69,"stackVersion":0,"hwVersion":1,"dateCode":""}}},"binds":[],"configuredReportings":[],"meta":{}}},"appVersion":69,"stackVersion":0,"hwVersion":1,"dateCode":"","zclVersion":3,"interviewCompleted":true,"meta":{},"lastSeen":1669061163974,"defaultSendRequestWhen":"immediate"}

Comments

Device join but not supported

https://www.aliexpress.com/item/1005004661809489.html?spm=a2g0o.order_list.0.0.523f1802feGJLg

I'm new to Zigbee2Mqtt but can provide any detail that can help!

Thanks

External converter

No response

Supported color modes

No response

Color temperature range

No response

@marc3k18 marc3k18 added the new device support New device support request label Nov 21, 2022
@danieledwardgeorgehitchcock
Copy link
Contributor

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 Points (a deviation away from the standard Zigbee protocol) in order to see what data / control is available for the device

@marc3k18
Copy link
Author

marc3k18 commented Nov 22, 2022 via email

@danieledwardgeorgehitchcock
Copy link
Contributor

danieledwardgeorgehitchcock commented Nov 22, 2022

Here's 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

@bjne
Copy link

bjne commented Nov 28, 2022

@marc3k18 have you received the hub yet? I have the same valve and problem.

@marc3k18
Copy link
Author

marc3k18 commented Nov 29, 2022 via email

@LittleBlackDuck
Copy link

LittleBlackDuck commented Dec 10, 2022

Hi,

Not wanting to hijack this thread or anything, but I've also got the same Tuya-compatible Irrigation controller (RainSeer Green+Yellow = ZigBee) and the appropriate Tuya ZigBee gateway.

As per OPs post, it identifies in ZigBee2MQTT as "Model TS0049" and "Manufacturer ID 4417"

Here's the datapoints I found for this unit:

Fault 26
Switch 101
Mode 102
Rain Sensor 103
Automatic Execution Status 104
Countdown 105
Loop Timing 106
Automatic Mode Distinction 107
Effective Time Period 108
Model 109
Log Report 110
Irrigation Timer 111
Flow Reset 112
Temp Current 113
Humidity Value 114
Battery State 115
MaxTemp Set 116
MiniTemp set 117
MaxHum Set 118
MiniHum Set 119
Charge State 120
Water Once 121
Flowrate Total 122
Water Supply Pressure 123
Flow Rate Instant Value 124
Flow Calibration 125

Hope this can help. I'd love to get this working directly with ZigBee2MQTT... beyond providing you this requested info I don't know what to do next.

FWIW the units themselves are very well built and heavy/ sturdy construction, and would make irrigation with ZigBee a very easy solution. In the past I used a Zwave 8-zone controller that was such a pain to setup and use (including the need to run control cables from the main box to each valve in the garden etc).

Ducky

@bjne
Copy link

bjne commented Dec 15, 2022

@LittleBlackDuck did you write any integration for this yet?

@LittleBlackDuck
Copy link

@bjne No I have not, sorry, that is beyond my knowledge. Many months ago I saw someone had written an integration for a similar type device; when I went back to see if I could modify it with the values I posted above, I found they had since deleted their posts/info.

I hope someone else on here may be able to help us.

@marc3k18
Copy link
Author

marc3k18 commented Dec 15, 2022 via email

@LittleBlackDuck
Copy link

@marc3k18 Hi, the datapoints I posted above were all the DP the controller was exposing within Tuya. Did I miss something?

@bjne
Copy link

bjne commented Dec 16, 2022

@danieledwardgeorgehitchcock So I manage to get the state of the switch back, datapoint 102, but I am unable to set it. I have read through the guides I have found, but not extremely helpful..

@cloudbr34k84
Copy link

This would be great to get working.

@bjne
Copy link

bjne commented Jan 6, 2023

@marc3k18 did you receive your device?

@LittleBlackDuck
Copy link

Is this a DOA request?

@Adam-Langley
Copy link

Upvote, I have 2 of these devices I'm waiting eagerly for z2m to support.

@marc3k18
Copy link
Author

marc3k18 commented Jan 15, 2023 via email

@toogooda
Copy link

Upvote, I have 2 of these devices I'm waiting eagerly for z2m to support.

+1 from me

@toogooda
Copy link

OK slowly making some progress I have it recognised and reporting off/on correctly but will take me some time as I am new to this:

So far here is my js code:

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 e = exposes.presets;
const ea = exposes.access;
const tuya = require('zigbee-herdsman-converters/lib/tuya');

const definition = {
    // Since a lot of TuYa devices use the same modelID, but use different datapoints
    // it's necessary to provide a fingerprint instead of a zigbeeModel
    fingerprint: [
        {
            // The model ID from: Device with modelID 'TS0601' is not supported
            // You may need to add \u0000 at the end of the name in some cases
            modelID: 'TS0049',
            // The manufacturer name from: Device with modelID 'TS0601' is not supported.
            manufacturerName: '_TZ3210_0jxeoadc',
        },
    ],
    model: 'Rain Seer',
    vendor: 'TuYa Compatable',
    description: 'Zigbee Hose Controller',
    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.switch(),
        // Here you should put all functionality that your device exposes
    ],
    meta: {
        // All datapoints go in here
        tuyaDatapoints: [
            [101, 'state', tuya.valueConverter.onOff] // <- mapped the datapoint
        ],
    },
};

module.exports = definition;

@toogooda
Copy link

Working:
Manual button updates Z2M state
Battery%

Not Working:
switch on from Z2M
most other datapoints

very slow process as I don't know how to see raw data before it is converted and have to assume datapoint list above is correct (I don't have a tuya router)

image


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 utils = require('zigbee-herdsman-converters/lib/utils');
const e = exposes.presets;
const ea = exposes.access;
const tuya = require('zigbee-herdsman-converters/lib/tuya');

const definition = {
    // Since a lot of TuYa devices use the same modelID, but use different datapoints
    // it's necessary to provide a fingerprint instead of a zigbeeModel
    fingerprint: [
        {
            // The model ID from: Device with modelID 'TS0601' is not supported
            // You may need to add \u0000 at the end of the name in some cases
            modelID: 'TS0049',
            // The manufacturer name from: Device with modelID 'TS0601' is not supported.
            manufacturerName: '_TZ3210_0jxeoadc',
        },
    ],
    model: 'Rain Seer',
    vendor: 'TuYa Compatable',
    description: 'Zigbee Hose Controller',
    fromZigbee: [tuya.fz.datapoints],
    toZigbee: [tuya.tz.datapoints, tz.tuya_switch_state],
    onEvent: tuya.onEventSetTime, // Add this if you are getting no converter for 'commandMcuSyncTime'
    configure: tuya.configureMagicPacket,
    exposes: [e.switch() , e.battery(), tuya.exposes.batteryState(),e.temperature()
        // Here you should put all functionality that your device exposes
    ],
    meta: {
        // All datapoints go in here
        tuyaDatapoints: [
            [101, 'state', tuya.valueConverter.onOff], // <- mapped the datapoint
            [120, 'battery_state', tuya.valueConverter.batteryState],
            [115, 'battery', tuya.valueConverter.raw],
            [113,'temperature', tuya.valueConverter.raw]

        ],
    },
};

module.exports = definition;

@toogooda
Copy link

@danieledwardgeorgehitchcock I have been fumbling through using the tutorial etc and using the datapoints listed above, but only getting limited success I can see the state change for the switch but not change it remotely. You offered help above any chance you could give me some pointers from here?

Thank you in advance for your help

@DarioKTS
Copy link

DarioKTS commented Feb 7, 2023

i have what i belive to be a rebrand of the same valve
image
recognised as 'TS0049', manufacturer '_TZ3000_hwnphliv'
(FrankEver model FK-WT03W)

There may or may not be differences, i've had some success with this:

const fz = {...require('zigbee-herdsman-converters/converters/fromZigbee'), legacy: require('zigbee-herdsman-converters/lib/legacy').fromZigbee};
const tz = require('zigbee-herdsman-converters/converters/toZigbee');
const tuya = require('zigbee-herdsman-converters/lib/tuya');
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 e = exposes.presets;
const ea = exposes.access;

module.exports = {
    fingerprint: [{modelID: 'TS0049', manufacturerName: '_TZ3000_hwnphliv'}],
    model: 'FK-WT03W',
    vendor: 'Frankever',
    description: 'Smart irrigation valve',
    fromZigbee: [fz.battery, tuya.fz.power_on_behavior, tuya.fz.switch_type, fz.on_off, ],
    toZigbee: [tuya.tz.power_on_behavior, tuya.tz.switch_type, tz.on_off ],
    onEvent: tuya.onEventSetLocalTime,
    configure: tuya.configureMagicPacket,
    exposes: [ e.power_on_behavior(), tuya.exposes.switchType(), e.switch(), e.battery(), e.battery_voltage() ],
   meta: {
           configure: async (device, coordinatorEndpoint, logger) => {
            try {
                const endpoint = device.getEndpoint(1);
                await reporting.bind(endpoint, coordinatorEndpoint, ['genPowerCfg']);
            } catch (error) {/* Fails for some*/}
            },
        tuyaDatapoints: [
        ],
    },
};

image

...still very much a work in progress...

If anyone experienced could chip in, it would be greatly appreciated!
I've shared more details about the logs in this post: link

@toogooda
Copy link

@Koenkk please help, I have been trying for weeks all the data points above are correct but I just can't get this to work I can only display state not change it. Can you add anything to help?

@JoppyFurr
Copy link

Hi,

We've got the TS0049 TuYa valve and have got it working.

Here's the code, hopefully somebody is able to migrate it to where it needs to go:

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 e = exposes.presets;
const ea = exposes.access;
const tuya = require("zigbee-herdsman-converters/lib/tuya");

const TS0049_ValueConverter = {
    Switch:{
        to: async (value, meta) => {
            const entity = meta.device.endpoints[0];
            await tuya.sendDataPointBool(entity, 101, value.toUpperCase() === 'ON', 0x04);
        },
        from: (value) => {
            return {false: 'OFF', true: 'ON'}[value];
        },
    },
    IrrigationTimer:{
        to: async (value, meta) => {
            const entity = meta.device.endpoints[0];
            await tuya.sendDataPointValue(entity, 111, value, 0x04);
        },
        from: (value) => {
            return value;
        },
    },
}

const definition = {
    fingerprint: tuya.fingerprint('TS0049', ['_TZ3210_0jxeoadc']),
    model: 'TS0049',
    vendor: 'TuYa',
    description: 'Water Valve',
    fromZigbee: [tuya.fz.datapoints],
    toZigbee: [tuya.tz.datapoints],
    onEvent: tuya.onEventSetLocalTime,
    configure: tuya.configureMagicPacket,
    exposes: [
        tuya.exposes.errorStatus(),
        tuya.exposes.switch(),
        tuya.exposes.countdown().withValueMin(0).withValueMax(255).withUnit('minutes')
            .withDescription('Max on time in minutes'),
        tuya.exposes.batteryState(),
    ],
    meta: {
        tuyaDatapoints: [
            [26, 'error_status', tuya.valueConverter.raw],
            [101, 'state', TS0049_ValueConverter.Switch],
            [111, 'countdown', TS0049_ValueConverter.IrrigationTimer],
            [115, 'battery_state', tuya.valueConverter.batteryState],
        ],
    },
};
module.exports = definition;

@Koenkk
Copy link
Owner

Koenkk commented Feb 18, 2023

@JoppyFurr

  • can you explain why TS0049_ValueConverter. Switch is needed? Doesn't tuya.valueConverter.onOff work?
  • same for the IrrigationTimer, can you try with tuya.valueConverter.raw?

@JoppyFurr
Copy link

JoppyFurr commented Feb 18, 2023

Hi @Koenkk,

I'm not sure of all the details, as the experimentation was done by my partner who is not on GitHub.

However, the main point that they found was that the valve wouldn't work until the sendDataPoint...() function was called with cmd = 0x04 ("Send commands"). Possibly this could be made more human-readable using the string "sendData" instead of 0x04.

https://developer.tuya.com/en/docs/iot/tuya-zigbee-module-uart-communication-protocol?id=K9ear5khsqoty#title-18-Send%20commands%20(0x04)

https://github.com/Koenkk/zigbee-herdsman/blob/af07c9b6e0a4f88d72c496fbe5f230b7693bfcc2/src/zcl/definition/cluster.ts#L4295

Feel free to make any changes to the code we pasted.

Koenkk added a commit to Koenkk/zigbee-herdsman-converters that referenced this issue Feb 19, 2023
@Koenkk
Copy link
Owner

Koenkk commented Feb 19, 2023

Thanks, integrated the device, please let me know if it works!

Changes will be available in the dev branch in a few hours from now. (https://www.zigbee2mqtt.io/advanced/more/switch-to-dev-branch.html)

@failMode
Copy link

failMode commented Feb 20, 2023

@JoppyFurr I've tested your code in an external converter with the green and yellow Rain Seer model and it works fantastically. Thank you for taking the time to post!
Edit: and thanks Koenkk for all your hard work on this as well!

@Koenkk
Copy link
Owner

Koenkk commented Feb 20, 2023

Great!

@Koenkk Koenkk closed this as completed Feb 20, 2023
@LittleBlackDuck
Copy link

Hi, I'm confused. OP and others were in this thread for "modelId":"TS0049","manufacturerName":"_TZ3210_0jxeoadc" (The Green and Yellow "Rain Seer" unit).

Was this thread closed/completed for this specific manufacturer name, or for the other one that was mentioned later in the thread (manufacturerName: '_TZ3000_hwnphliv' the grey unit which is a different unit to what OP/others need working)???

Can you confirm "modelId":"TS0049","manufacturerName":"_TZ3210_0jxeoadc" is being added to the dev branch/native support? I'm running dev and just tried adding my unit to Z2M and it is still showing up as unsupported.

@failMode
Copy link

Can you confirm "modelId":"TS0049","manufacturerName":"_TZ3210_0jxeoadc" is being added to the dev branch/native support? I'm running dev and just tried adding my unit to Z2M and it is still showing up as unsupported.

Sorry for the confusion. I was only confirming that the code posted by JoppyFurr works with the green and yellow Rain Seer unit when dropped into an external converter. The code enables remote valve toggling and valve state reporting features. I'm not running the dev branch so I haven't tested whether the device is being picked up automatically.

@DarioKTS
Copy link

DarioKTS commented Feb 23, 2023

Hello @Koenkk , and thanks for the amazing work with Z2M.

You've closed this issue i had opened and pointed me to this issue.
I had already followed previously what the others with the RainSeer valve tried in this thread, but it wasn't working for me.

I've switched today to the development branch(i'm on docker), connected my valves and nothing is working.
it might well be a case of the fingerprint not being recongnised, or effectively it is a different valve, with differnt datapoints.

These are the logs when any of the valves currently announces itself:

Debug 2023-02-23 12:42:58Device '0xa4c13880480deba6' announced itself
Info 2023-02-23 12:42:58MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0xa4c13880480deba6","ieee_address":"0xa4c13880480deba6"},"type":"device_announce"}'
Info 2023-02-23 12:42:58MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"announce","meta":{"friendly_name":"0xa4c13880480deba6"},"type":"device_announced"}'
Debug 2023-02-23 12:43:02Received Zigbee message from '0xa4c13880480deba6', type 'attributeReport', cluster 'genOnOff', data '{"32768":0,"moesStartUpOnOff":0,"offWaitTime":0,"onOff":0,"onTime":0,"tuyaBacklightMode":1,"tuyaBacklightSwitch":0}' from endpoint 1 with groupID 0
Warning 2023-02-23 12:43:02Received message from unsupported device with Zigbee model 'TS0049' and manufacturer name '_TZ3000_hwnphliv'
Warning 2023-02-23 12:43:02Please see: https://www.zigbee2mqtt.io/advanced/support-new-devices/01_support_new_devices.html
Debug 2023-02-23 12:43:02Received Zigbee message from '0xa4c13880480deba6', type 'attributeReport', cluster 'manuSpecificTuya_3', data '{"powerOnBehavior":0,"switchType":0}' from endpoint 1 with groupID 0
Warning 2023-02-23 12:43:02Received message from unsupported device with Zigbee model 'TS0049' and manufacturer name '_TZ3000_hwnphliv'
Warning 2023-02-23 12:43:02Please see: https://www.zigbee2mqtt.io/advanced/support-new-devices/01_support_new_devices.html
Debug 2023-02-23 12:43:03Received Zigbee message from '0xa4c13880480deba6', type 'read', cluster 'genTime', data '["localTime"]' from endpoint 1 with groupID 0
Warning 2023-02-23 12:43:03Received message from unsupported device with Zigbee model 'TS0049' and manufacturer name '_TZ3000_hwnphliv'
Warning 2023-02-23 12:43:03Please see: https://www.zigbee2mqtt.io/advanced/support-new-devices/01_support_new_devices.html
Debug 2023-02-23 12:43:03Received Zigbee message from '0xa4c13880480deba6', type 'raw', cluster 'manuSpecificTuya_3', data '{"data":[8,109,10,64,208,72,2,16,0],"type":"Buffer"}' from endpoint 1 with groupID 0
Warning 2023-02-23 12:43:03Received message from unsupported device with Zigbee model 'TS0049' and manufacturer name '_TZ3000_hwnphliv'
Warning 2023-02-23 12:43:03Please see: https://www.zigbee2mqtt.io/advanced/support-new-devices/01_support_new_devices.html
Debug 2023-02-23 12:43:05Received Zigbee message from '0xa4c13880480deba6', type 'raw', cluster 'manuSpecificTuya_3', data '{"data":[8,110,10,64,208,72,3,17,0],"type":"Buffer"}' from endpoint 1 with groupID 0
Warning 2023-02-23 12:43:05Received message from unsupported device with Zigbee model 'TS0049' and manufacturer name '_TZ3000_hwnphliv'
Warning 2023-02-23 12:43:05Please see: https://www.zigbee2mqtt.io/advanced/support-new-devices/01_support_new_devices.html
Debug 2023-02-23 12:43:08Received Zigbee message from '0xa4c13880480deba6', type 'raw', cluster 'manuSpecificTuya_3', data '{"data":[8,111,10,64,208,72,3,10,0],"type":"Buffer"}' from endpoint 1 with groupID 0
Warning 2023-02-23 12:43:08Received message from unsupported device with Zigbee model 'TS0049' and manufacturer name '_TZ3000_hwnphliv'
Warning 2023-02-23 12:43:08Please see: https://www.zigbee2mqtt.io/advanced/support-new-devices/01_support_new_devices.html
Debug 2023-02-23 12:43:10Received Zigbee message from '0xa4c13880480deba6', type 'raw', cluster 'manuSpecificTuya_3', data '{"data":[8,112,10,64,208,72,3,12,2],"type":"Buffer"}' from endpoint 1 with groupID 0
Warning 2023-02-23 12:43:10Received message from unsupported device with Zigbee model 'TS0049' and manufacturer name '_TZ3000_hwnphliv'
Warning 2023-02-23 12:43:10Please see: https://www.zigbee2mqtt.io/advanced/support-new-devices/01_support_new_devices.html
Debug 2023-02-23 12:43:12Received Zigbee message from '0xa4c13880480deba6', type 'attributeReport', cluster 'genOnOff', data '{"onOff":0}' from endpoint 1 with groupID 0
Warning 2023-02-23 12:43:12Received message from unsupported device with Zigbee model 'TS0049' and manufacturer name '_TZ3000_hwnphliv'
Warning 2023-02-23 12:43:12Please see: https://www.zigbee2mqtt.io/advanced/support-new-devices/01_support_new_devices.html
Debug 2023-02-23 12:43:13Received Zigbee message from '0xa4c13880480deba6', type 'raw', cluster 'manuSpecificTuya_3', data '{"data":[8,114,10,64,208,72,2,16,0],"type":"Buffer"}' from endpoint 1 with groupID 0
Warning 2023-02-23 12:43:13Received message from unsupported device with Zigbee model 'TS0049' and manufacturer name '_TZ3000_hwnphliv'
Warning 2023-02-23 12:43:13Please see: https://www.zigbee2mqtt.io/advanced/support-new-devices/01_support_new_devices.html
Debug 2023-02-23 12:43:15Received Zigbee message from '0xa4c13880480deba6', type 'attributeReport', cluster 'genBasic', data '{"65506":55,"65508":1,"appVersion":72}' from endpoint 1 with groupID 0
Warning 2023-02-23 12:43:15Received message from unsupported device with Zigbee model 'TS0049' and manufacturer name '_TZ3000_hwnphliv'
Warning 2023-02-23 12:43:15Please see: https://www.zigbee2mqtt.io/advanced/support-new-devices/01_support_new_devices.html
Debug 2023-02-23 12:43:15Received Zigbee message from '0xa4c13880480deba6', type 'attributeReport', cluster 'genPowerCfg', data '{"batteryPercentageRemaining":200,"batteryVoltage":30}' from endpoint 1 with groupID 0
Warning 2023-02-23 12:43:15Received message from unsupported device with Zigbee model 'TS0049' and manufacturer name '_TZ3000_hwnphliv'
Warning 2023-02-23 12:43:15Please see: https://www.zigbee2mqtt.io/advanced/support-new-devices/01_support_new_devices.html
Debug 2023-02-23 12:44:34Received Zigbee message from '0xa4c13880480deba6', type 'attributeReport', cluster 'genBasic', data '{"65503":"\u0000\u0000\u0000\u0000\u0011"}' from endpoint 1 with groupID 0
Warning 2023-02-23 12:44:34Received message from unsupported device with Zigbee model 'TS0049' and manufacturer name '_TZ3000_hwnphliv'
Warning 2023-02-23 12:44:34Please see: https://www.zigbee2mqtt.io/advanced/support-new-devices/01_support_new_devices.html

For the time being i'm reinserting my noobish external converter to get at least basic funcionality back, will also try inserting the datapoints numbers i got from the tuya hub and see if i get anywhere.

PS!
I have also tried @JoppyFurr 's external converter, not working for me.

@Koenkk
Copy link
Owner

Koenkk commented Feb 23, 2023

Received message from unsupported device with Zigbee model -> the device is not recognized as supported which should be the case when running the latest dev. Please make sure you are running the latest dev version.

@DarioKTS
Copy link

DarioKTS commented Feb 23, 2023

you are absolutely right... sorry, my bad, made a mistake with some folders.. (-.-)

it behaves as with the external converter by JoppyFurr.. meaning i have no control over the valve.

here are the logs:

Debug 2023-02-23 22:24:16Device '0xa4c13880480deba6' announced itself
Info 2023-02-23 22:24:16MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0xa4c13880480deba6","ieee_address":"0xa4c13880480deba6"},"type":"device_announce"}'
Info 2023-02-23 22:24:16MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"announce","meta":{"friendly_name":"0xa4c13880480deba6"},"type":"device_announced"}'
Debug 2023-02-23 22:24:18Retrieving state of '0xa4c13880480deba6' after reconnect
Debug 2023-02-23 22:24:19Received Zigbee message from '0xa4c13880480deba6', type 'attributeReport', cluster 'genOnOff', data '{"32768":0,"moesStartUpOnOff":0,"offWaitTime":0,"onOff":0,"onTime":0,"tuyaBacklightMode":1,"tuyaBacklightSwitch":0}' from endpoint 1 with groupID 0
Debug 2023-02-23 22:24:19No converter available for 'TS0049' with cluster 'genOnOff' and type 'attributeReport' and data '{"32768":0,"moesStartUpOnOff":0,"offWaitTime":0,"onOff":0,"onTime":0,"tuyaBacklightMode":1,"tuyaBacklightSwitch":0}'
Debug 2023-02-23 22:24:22Received Zigbee message from '0xa4c13880480deba6', type 'attributeReport', cluster 'manuSpecificTuya_3', data '{"powerOnBehavior":0,"switchType":0}' from endpoint 1 with groupID 0
Debug 2023-02-23 22:24:22No converter available for 'TS0049' with cluster 'manuSpecificTuya_3' and type 'attributeReport' and data '{"powerOnBehavior":0,"switchType":0}'
Debug 2023-02-23 22:24:24Received Zigbee message from '0xa4c13880480deba6', type 'raw', cluster 'manuSpecificTuya_3', data '{"data":[8,186,10,64,208,72,2,16,0],"type":"Buffer"}' from endpoint 1 with groupID 0
Debug 2023-02-23 22:24:24No converter available for 'TS0049' with cluster 'manuSpecificTuya_3' and type 'raw' and data '{"data":[8,186,10,64,208,72,2,16,0],"type":"Buffer"}'
Debug 2023-02-23 22:24:27Received Zigbee message from '0xa4c13880480deba6', type 'raw', cluster 'manuSpecificTuya_3', data '{"data":[8,187,10,64,208,72,3,17,0],"type":"Buffer"}' from endpoint 1 with groupID 0
Debug 2023-02-23 22:24:27No converter available for 'TS0049' with cluster 'manuSpecificTuya_3' and type 'raw' and data '{"data":[8,187,10,64,208,72,3,17,0],"type":"Buffer"}'
Debug 2023-02-23 22:24:29Received Zigbee message from '0xa4c13880480deba6', type 'raw', cluster 'manuSpecificTuya_3', data '{"data":[8,188,10,64,208,72,3,10,0],"type":"Buffer"}' from endpoint 1 with groupID 0
Debug 2023-02-23 22:24:29No converter available for 'TS0049' with cluster 'manuSpecificTuya_3' and type 'raw' and data '{"data":[8,188,10,64,208,72,3,10,0],"type":"Buffer"}'
Debug 2023-02-23 22:24:31Received Zigbee message from '0xa4c13880480deba6', type 'raw', cluster 'manuSpecificTuya_3', data '{"data":[8,189,10,64,208,72,3,12,2],"type":"Buffer"}' from endpoint 1 with groupID 0
Debug 2023-02-23 22:24:31No converter available for 'TS0049' with cluster 'manuSpecificTuya_3' and type 'raw' and data '{"data":[8,189,10,64,208,72,3,12,2],"type":"Buffer"}'
Debug 2023-02-23 22:24:34Received Zigbee message from '0xa4c13880480deba6', type 'attributeReport', cluster 'genOnOff', data '{"onOff":0}' from endpoint 1 with groupID 0
Debug 2023-02-23 22:24:34No converter available for 'TS0049' with cluster 'genOnOff' and type 'attributeReport' and data '{"onOff":0}'
Debug 2023-02-23 22:24:36Received Zigbee message from '0xa4c13880480deba6', type 'read', cluster 'genTime', data '["localTime"]' from endpoint 1 with groupID 0
Debug 2023-02-23 22:24:39Received Zigbee message from '0xa4c13880480deba6', type 'attributeReport', cluster 'genBasic', data '{"65506":55,"65508":1,"appVersion":72}' from endpoint 1 with groupID 0
Debug 2023-02-23 22:24:41Received Zigbee message from '0xa4c13880480deba6', type 'attributeReport', cluster 'genPowerCfg', data '{"batteryPercentageRemaining":200,"batteryVoltage":30}' from endpoint 1 with groupID 0
Debug 2023-02-23 22:24:41No converter available for 'TS0049' with cluster 'genPowerCfg' and type 'attributeReport' and data '{"batteryPercentageRemaining":200,"batteryVoltage":30}'
Debug 2023-02-23 22:24:52Received Zigbee message from '0xa4c13880480deba6', type 'raw', cluster 'manuSpecificTuya_3', data '{"data":[8,194,10,64,208,72,2,16,0],"type":"Buffer"}' from endpoint 1 with groupID 0
Debug 2023-02-23 22:24:52No converter available for 'TS0049' with cluster 'manuSpecificTuya_3' and type 'raw' and data '{"data":[8,194,10,64,208,72,2,16,0],"type":"Buffer"}'
Debug 2023-02-23 22:24:57Received Zigbee message from '0xa4c13880480deba6', type 'attributeReport', cluster 'genBasic', data '{"65506":55,"65508":1,"appVersion":72}' from endpoint 1 with groupID 0
Debug 2023-02-23 22:24:57Received Zigbee message from '0xa4c13880480deba6', type 'attributeReport', cluster 'genPowerCfg', data '{"batteryPercentageRemaining":200,"batteryVoltage":30}' from endpoint 1 with groupID 0
Debug 2023-02-23 22:24:57No converter available for 'TS0049' with cluster 'genPowerCfg' and type 'attributeReport' and data '{"batteryPercentageRemaining":200,"batteryVoltage":30}'

On the other hand, i've made a few baby steps forward with my own converter (definitely not complete yet), but it doesn't feel right to clog up this thread with it.

awaiting instructions ;)

@Koenkk
Copy link
Owner

Koenkk commented Feb 25, 2023

Seems the devices uses a different API in your case. Reverse engineering (sniffing) with the TuYa bridge is needed to understand the behaviour: https://www.zigbee2mqtt.io/advanced/zigbee/04_sniff_zigbee_traffic.html

@Clem-
Copy link

Clem- commented Apr 25, 2023

Hi @Koenkk, I also have a yellow/green Rain Seer device.

  • On dev branch : Device '0xa4c138ff5693f643' with Zigbee model 'TS0049' and manufacturer name '_TZ3210_0jxeoadc' is NOT supported...

  • With @JoppyFurr external converter : working well.

I am not sure that this converter has sucessfully been pushed to dev branch.

@Koenkk
Copy link
Owner

Koenkk commented Apr 27, 2023

@Clem- this has been integrated to dev, your device will be supported in the z2m 1 May release.

@maximatchev
Copy link

you are absolutely right... sorry, my bad, made a mistake with some folders.. (-.-)

it behaves as with the external converter by JoppyFurr.. meaning i have no control over the valve.

here are the logs:

Debug 2023-02-23 22:24:16Device '0xa4c13880480deba6' announced itself
Info 2023-02-23 22:24:16MQTT publish: topic 'zigbee2mqtt/bridge/event', payload '{"data":{"friendly_name":"0xa4c13880480deba6","ieee_address":"0xa4c13880480deba6"},"type":"device_announce"}'
Info 2023-02-23 22:24:16MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"announce","meta":{"friendly_name":"0xa4c13880480deba6"},"type":"device_announced"}'
Debug 2023-02-23 22:24:18Retrieving state of '0xa4c13880480deba6' after reconnect
Debug 2023-02-23 22:24:19Received Zigbee message from '0xa4c13880480deba6', type 'attributeReport', cluster 'genOnOff', data '{"32768":0,"moesStartUpOnOff":0,"offWaitTime":0,"onOff":0,"onTime":0,"tuyaBacklightMode":1,"tuyaBacklightSwitch":0}' from endpoint 1 with groupID 0
Debug 2023-02-23 22:24:19No converter available for 'TS0049' with cluster 'genOnOff' and type 'attributeReport' and data '{"32768":0,"moesStartUpOnOff":0,"offWaitTime":0,"onOff":0,"onTime":0,"tuyaBacklightMode":1,"tuyaBacklightSwitch":0}'
Debug 2023-02-23 22:24:22Received Zigbee message from '0xa4c13880480deba6', type 'attributeReport', cluster 'manuSpecificTuya_3', data '{"powerOnBehavior":0,"switchType":0}' from endpoint 1 with groupID 0
Debug 2023-02-23 22:24:22No converter available for 'TS0049' with cluster 'manuSpecificTuya_3' and type 'attributeReport' and data '{"powerOnBehavior":0,"switchType":0}'
Debug 2023-02-23 22:24:24Received Zigbee message from '0xa4c13880480deba6', type 'raw', cluster 'manuSpecificTuya_3', data '{"data":[8,186,10,64,208,72,2,16,0],"type":"Buffer"}' from endpoint 1 with groupID 0
Debug 2023-02-23 22:24:24No converter available for 'TS0049' with cluster 'manuSpecificTuya_3' and type 'raw' and data '{"data":[8,186,10,64,208,72,2,16,0],"type":"Buffer"}'
Debug 2023-02-23 22:24:27Received Zigbee message from '0xa4c13880480deba6', type 'raw', cluster 'manuSpecificTuya_3', data '{"data":[8,187,10,64,208,72,3,17,0],"type":"Buffer"}' from endpoint 1 with groupID 0
Debug 2023-02-23 22:24:27No converter available for 'TS0049' with cluster 'manuSpecificTuya_3' and type 'raw' and data '{"data":[8,187,10,64,208,72,3,17,0],"type":"Buffer"}'
Debug 2023-02-23 22:24:29Received Zigbee message from '0xa4c13880480deba6', type 'raw', cluster 'manuSpecificTuya_3', data '{"data":[8,188,10,64,208,72,3,10,0],"type":"Buffer"}' from endpoint 1 with groupID 0
Debug 2023-02-23 22:24:29No converter available for 'TS0049' with cluster 'manuSpecificTuya_3' and type 'raw' and data '{"data":[8,188,10,64,208,72,3,10,0],"type":"Buffer"}'
Debug 2023-02-23 22:24:31Received Zigbee message from '0xa4c13880480deba6', type 'raw', cluster 'manuSpecificTuya_3', data '{"data":[8,189,10,64,208,72,3,12,2],"type":"Buffer"}' from endpoint 1 with groupID 0
Debug 2023-02-23 22:24:31No converter available for 'TS0049' with cluster 'manuSpecificTuya_3' and type 'raw' and data '{"data":[8,189,10,64,208,72,3,12,2],"type":"Buffer"}'
Debug 2023-02-23 22:24:34Received Zigbee message from '0xa4c13880480deba6', type 'attributeReport', cluster 'genOnOff', data '{"onOff":0}' from endpoint 1 with groupID 0
Debug 2023-02-23 22:24:34No converter available for 'TS0049' with cluster 'genOnOff' and type 'attributeReport' and data '{"onOff":0}'
Debug 2023-02-23 22:24:36Received Zigbee message from '0xa4c13880480deba6', type 'read', cluster 'genTime', data '["localTime"]' from endpoint 1 with groupID 0
Debug 2023-02-23 22:24:39Received Zigbee message from '0xa4c13880480deba6', type 'attributeReport', cluster 'genBasic', data '{"65506":55,"65508":1,"appVersion":72}' from endpoint 1 with groupID 0
Debug 2023-02-23 22:24:41Received Zigbee message from '0xa4c13880480deba6', type 'attributeReport', cluster 'genPowerCfg', data '{"batteryPercentageRemaining":200,"batteryVoltage":30}' from endpoint 1 with groupID 0
Debug 2023-02-23 22:24:41No converter available for 'TS0049' with cluster 'genPowerCfg' and type 'attributeReport' and data '{"batteryPercentageRemaining":200,"batteryVoltage":30}'
Debug 2023-02-23 22:24:52Received Zigbee message from '0xa4c13880480deba6', type 'raw', cluster 'manuSpecificTuya_3', data '{"data":[8,194,10,64,208,72,2,16,0],"type":"Buffer"}' from endpoint 1 with groupID 0
Debug 2023-02-23 22:24:52No converter available for 'TS0049' with cluster 'manuSpecificTuya_3' and type 'raw' and data '{"data":[8,194,10,64,208,72,2,16,0],"type":"Buffer"}'
Debug 2023-02-23 22:24:57Received Zigbee message from '0xa4c13880480deba6', type 'attributeReport', cluster 'genBasic', data '{"65506":55,"65508":1,"appVersion":72}' from endpoint 1 with groupID 0
Debug 2023-02-23 22:24:57Received Zigbee message from '0xa4c13880480deba6', type 'attributeReport', cluster 'genPowerCfg', data '{"batteryPercentageRemaining":200,"batteryVoltage":30}' from endpoint 1 with groupID 0
Debug 2023-02-23 22:24:57No converter available for 'TS0049' with cluster 'genPowerCfg' and type 'attributeReport' and data '{"batteryPercentageRemaining":200,"batteryVoltage":30}'

On the other hand, i've made a few baby steps forward with my own converter (definitely not complete yet), but it doesn't feel right to clog up this thread with it.

awaiting instructions ;)

Hi, @DarioKTS
I have the same problem ("manufacturerName": "_TZ3000_srldgdxz" is the only difference).
Have you got the solution?
Have you made your own converter?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new device support New device support request
Projects
None yet
Development

No branches or pull requests