-
Notifications
You must be signed in to change notification settings - Fork 489
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
RTX ZVG1 smart water valve #5248
Comments
Ha yessss Koenkk/zigbee-herdsman-converters#2795 It seem it s the same valve than this one but with reporting not locked #4958 So the code is already done, give me some time to add your device. |
Ok so can you try this code ? You have the procedure here https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/Compiling-the-REST-plugin-for-device-specific-testing
It s realy experimental, I m not sure your device will react like the first one. This PR will
Still missing return, enable/disable the timer (I hope for enable by defaut), and some measured values. |
Great news. Sure i'll try it later, for now i can't install deconz-dev got 404 from http://phoscon.de/apt/deconz/ |
You can't use the package method ? Then just |
Im not sure if it possible to recompile plugin on home assistant, so i installed ubuntu but i stuck on apt-get update
EDITSorry i didn't check supported ubuntu versions i got installed 21.x |
Can be my fault, haven't see your device is not a router. Have updated the code
Then re-include the device, can need 2 inclusions, the first one will create a ZHAbattery entry. |
Ok it realy similar at #5238 A Tuya device that need the battery sensor to be reconised. Can you share the log during the inclusion ? with "info" and "info_l2" ? |
10:30:18:731 Daylight now: goldenHour2, status: 180, daylight: 0, dark: 0 |
when i press button 10:37:12:693 Tuya debug Request : Address 0xCC86ECFFFEA4FFF8, Endpoint 0x01, Command 0x01, Payload 002a0c04000101 |
Can you check your configuration ? https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/Network-lost-and-configuration-restore-does-not-help And the name is still something like 0xXXXX ? |
You have a setting issue (but not sure if it explain why we can't include it, as the sensor is included, just missing the "light" entry) |
changed to 0x0000000000000000 re added but still same result |
Ok so can you try with this version, it will have more debug
Then can you share again logs (with "info" and "info_l2") during the pairing procedure (just start the logging 5s before the inclusion) |
07:40:04:391 UPNP socket not bound, state: 0 |
It s realy strange, something make the code skip the addlight fonction ... Can you make another try ?
|
08:46:09:805 UPNP socket not bound, state: 0 |
You are using "add new light" in phoscon ? (even in my memory it don't change lot of thing) ? |
yes "add new light" thru web app to pair, because permit join always got me "send permit join, duration: 0" in debug no matter what i set. |
Yep, it s no more possible using the deconz application. I will ask to other devs, because there is something I don't understand ... |
Can you make this try
|
Swoops have perhaps an idea
But unfortunately the only one that appear is the conbee itself, I realy need the same logs but for the device. Swoops say to me it s perhaps because there is already a sensor, It's strange because it s the way I m using for tuya battery powered device, but can you make a try with deleting the device first.
|
sensor removed and added. 06:43:15:819 Websocket disconnected 192.168.131.131:53464, state: 0, close-code: 1001, reason: |
Ok so it seem, swoops was right, if the sensor is deleted it works again
Have updated the code to don't create the sensor battery for test
So now I think the fonction will be called on all inclusion (after having deleted the device again), but the problem is how the code will reconize it without the battery sensor .... But now, you can use the phoscon trick
The battery sensor will not block you. |
13:47:41:855 UPNP socket not bound, state: 0 |
If you have read the basic attribute on deconz, for tuya the API is able to retreive the value from the GUI, here the manufacture name. |
Need more informations.
|
Ok, so values are not updated on your capture, so I presume you have too the _TZE200_akjefhj5. And I don't think he have share his DDF, so need to re make one #5248 (comment) |
Thank you, thats it, I have too the _TZE200_akjefhj5. |
Try to follow the same step than him. Tell me where you are stucked. |
Hey, i gave up with deconz for ha. |
-------------> I'll take a moment to try this, thank you for your answers !
-------------> One more time, somebody tell me to use Zigbee2mqtt + Mosquitto en HA, I think this is a good solution, but I'll see this later, for the moment I just have time to add elements one by one. |
So, what's the situation with Deconz and SAS980SWT-7-Z01 at the moment? Is it working with HASS and is it possible to get water consumpiton and turn it on and off via UI? I am thinking of buying one, but only if it works in HA :) |
I ended up buying the device, but I cannot figure out how to add it with Phoscon app. I tried searching for new lights or switch, and then putting the valve in pairing mode but Phoscon didn't find anything. Usually when this happens, it's because the zigbee item you are trying to add (light bulb for example) is factory-paired with something and you need to reset it first. But I am not sure if this is the case with the valve, or with what it could be already paired. EDIT: I got it working now! I haven't been using Deconz too much other than seeing my mesh network etc, but I was able to figure out that DDF thing and did just what you did:
When I next time opened Phoscon, there was new light "On/Off output 35" but it was grey/unavailable. So I searched for new lights once again, and it became active. And now I could open and close the valve via Phoscon as well! In addition to that, it works via Home Assistant as well :) Thanks to this thread, otherwise I couldn't get it working. Now, if there was consumption data available etc, that would be even better! But I guess then it should be added as something else than light entity. |
Hello @GileanEU & Hello to everybody ,
Do you know what could be the origin of such anomaly? Thanks a lot, |
Hello drZlash, I am not sure why it is working one-way only, it is odd as you can see the light symbol changing when pushing the physical button on the valve so the connection itself works. The valve itself shows as "fairy lights" for me as well, but it also works other way round, meaning that if I switch it on/off from Home Assistant, the valve opens/closes. And if I push that physical button on the valve, my HA switch changes status accordingly. Have you tried to create a switch in Home Assistant for your valve? In my experience, Phoscon app can be buggy sometimes. So maybe it works when you try from HA. |
Hello @GileanEU , Maybe I should start from scratch. |
|
If you use the editor, there is an option in the menu "hot reload", that reload the DDF, but IDK if it delete the previous entry. If you haven't a REST client, you can check all API entries in phoscon / help / API Information |
Hello, |
And you have an error message too ? If I m right you have started a DDF for this device ? |
Hello, |
According to configuration "Bronze" can be ignored, if you want to be sure the DDF is used put "Gold" For the water consumption, we surely ned to use the tuya cluster, the use of DDF for tuya cluster is still WIP. |
Not sure why, but this valve seems to go offline either after HA boot and/or HA update. It happened to me few days ago, and I had to pair it again (I saw it still in Phoscon but couldn't use it) by searching new lights. After that, it became active. But today I updated to HA OS version 8.0. and HA Core version 2022.5.5. And after that I noticed that my valve switch was grey again, AND this time the whole light entity for this valve was disappeared from Phoscon! I still saw it via Deconz, but even I tried couple of times searching for new lights and put my valve in pairing mode, it didn't find my "fairy light" again. Very frustrating! |
Hi, |
I m not able to find the DDF again ^^, you have a link ? I can probably add measurement, because we can read tuya cluster with DDF now, but I can't write them yet, so I don't think the timer possible, what feature are you searching ? |
I dont see the DDF too.. |
Your device use the same DDF than this one #6143 Try this DDF
|
Thanks a lot ! |
It seems that there is two different versions of this device. I've bought two of them without the consumption function and they have a different
|
According to https://www.zigbee2mqtt.io/devices/ZVG1.html, it seems that there are additional values related to the internal timer such as Is there a way to update that using the API and some POST ? EDIT: seems that as an example, |
If you want to add it on official DDF you can make like that in the DDF
For the moment we can read all value on tuya cluster, but not possible to write all value we want. |
Device
Product name: Tuya smart garden valve
Manufacturer: RTX
Model identifier: ZVG1
Device type :
link to zigbee2mqtt maybe it will help RTX ZVG1
Screenshots
Node info
![node info](https://user-images.githubusercontent.com/5422049/130857350-c958327f-1c71-485f-957d-a2f25b802093.png)
Basic
Basic cluster
![basic cluster info](https://user-images.githubusercontent.com/5422049/130857092-7bca8781-5ea5-4710-83c7-601ba9e44511.png)
Groups
Groups cluster info
![Groups cluster info](https://user-images.githubusercontent.com/5422049/130857391-a6dba41e-a8eb-4a6c-8fb5-bdc061c216d1.png)
Scenes
Scenes cluster info
![Scenes cluster info](https://user-images.githubusercontent.com/5422049/130857428-49810082-b2c1-4b3a-a1fd-bc8b45ed905e.png)
Other
Tuya specyfic Cluster cluster info
![Tuya specyfic Cluster cluster info](https://user-images.githubusercontent.com/5422049/130857478-dc6f3e88-7941-4a06-8871-91f5c90fd6aa.png)
OTAU cluster info
![OTAU cluster info](https://user-images.githubusercontent.com/5422049/130857520-afa23f64-de66-41f3-b210-e8572b17d092.png)
Time cluster info
![Time cluster info](https://user-images.githubusercontent.com/5422049/130857553-b10faabb-999c-4443-b149-78b734820e32.png)
The text was updated successfully, but these errors were encountered: