-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Comments
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 |
No but I will buy a cheap one if it can help.
I will order it today.
Thanks
Le mar. 22 nov. 2022, 3 h 44 a.m., danieledwardgeorgehitchcock <
***@***.***> a écrit :
… 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
—
Reply to this email directly, view it on GitHub
<#15124 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AXKJDQCFOQA65LO2KIDMYS3WJSBYFANCNFSM6AAAAAASHAWZE4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
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 |
@marc3k18 have you received the hub yet? I have the same valve and problem. |
Not yet!
Le lun. 28 nov. 2022, 3 h 48 a.m., Bjørnar Ness ***@***.***>
a écrit :
… @marc3k18 <https://github.com/marc3k18> have you received the hub yet? I
have the same valve and problem.
—
Reply to this email directly, view it on GitHub
<#15124 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AXKJDQBHB5XVZRSKK4CTJIDWKRWVVANCNFSM6AAAAAASHAWZE4>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
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 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 |
@LittleBlackDuck did you write any integration for this yet? |
@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. |
I should get my tuya zigbee device soon to provide the DP.
Hope that will help.
Le jeu. 15 déc. 2022, 2 h 45 p.m., LittleBlackDuck ***@***.***>
a écrit :
… @bjne <https://github.com/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.
—
Reply to this email directly, view it on GitHub
<#15124 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AXKJDQD4WK3KWAIOS3UCKNTWNNYNNANCNFSM6AAAAAASHAWZE4>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@marc3k18 Hi, the datapoints I posted above were all the DP the controller was exposing within Tuya. Did I miss something? |
@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.. |
This would be great to get working. |
@marc3k18 did you receive your device? |
Is this a DOA request? |
Upvote, I have 2 of these devices I'm waiting eagerly for z2m to support. |
Yes I received it. I will try to add it this week.
Le ven. 6 janv. 2023, 5 h 39 a.m., Bjørnar Ness ***@***.***>
a écrit :
… @marc3k18 <https://github.com/marc3k18> did you receive your device?
—
Reply to this email directly, view it on GitHub
<#15124 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AXKJDQDC2YBL6Z6ELACIKDLWQ7Y5BANCNFSM6AAAAAASHAWZE4>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
+1 from me |
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:
|
Working: Not Working: 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)
|
@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 |
i have what i belive to be a rebrand of the same valve There may or may not be differences, i've had some success with this:
...still very much a work in progress... If anyone experienced could chip in, it would be greatly appreciated! |
@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? |
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; |
|
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. Feel free to make any changes to the code we pasted. |
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) |
@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! |
Great! |
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. |
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. |
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've switched today to the development branch(i'm on docker), connected my valves and nothing is working. These are the logs when any of the valves currently announces itself:
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! |
|
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:
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 ;) |
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 |
Hi @Koenkk, I also have a yellow/green Rain Seer device.
I am not sure that this converter has sucessfully been pushed to dev branch. |
@Clem- this has been integrated to dev, your device will be supported in the z2m 1 May release. |
Hi, @DarioKTS |
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
The text was updated successfully, but these errors were encountered: