LIDL PARKSIDE Smart Watering Timer PSBZS A1

[ojcalvo]

Hello, this smart watering dont refresh its state and dont work well.
Thanks

Device

Product name: PARKSIDE Smart Watering Timer PSBZS A1
Manufacturer: _TZE200_htnnfasr
Model identifier: TS0601.
Device type :
Other: Smart watering timer

Screenshots

Other clusters that are not mentioned above

[ottelo9]

Do you mean this one?
https://www.lidl.de/de/parkside-smarter-bewaesserungscomputer-zigbee-smart-home/p375570

[stefangries]

I'm having issues with the device, too. It does pair via Phoscon, but switching it manually is neither reported in the UI, nor does controlling the device via the UI work.

Yes, it's the linked device from the LIDL Online Shop.

[ojcalvo]

Yes, is exactly like this. In phoscon It's integrated likea light, but dont refresh the state and dont show any sensor of battery level, etc.
Thanks.

[stefangries]

As some screenshots are hard to read, I added some in higher resolution:

Btw, for me, these buttons are working:

BUT, clicking the light button in phoscon isn't doing anything:

When controlling the device via deconz, however, phoscon is able to show the correct state of the device (on/off).

When controlling it via the Home Assistant integration, it's a little bit different. You can switch the device on/off correctly, but the switch in Home Assistant stays at the old state. When switching it via deconz, the correct state is indicated in Home Assistant.

So for me, it seems like deconz/phoscan has problems reading the current state of the device.

[Smanar]

Hello, can you show the device JSON pls ?

[stefangries]

Can you give me a hint, where to find it? I couldn't find the information, where to get the JSON here.

[flausen]

I am not able to find the parkside watercomputer via phoscon. Any hints?

[ojcalvo]

I am not able to find the parkside watercomputer via phoscon. Any hints?

It shows like a light in phoscon.

[stefangries]

Hello, can you show the device JSON pls ?

Is it this, what you are asking for?

{
   "etag":"9e8cc3af3dd044b93eafa4d7c1cafe6f",
   "hascolor":false,
   "lastannounced":null,
   "lastseen":"2021-06-01T17:16Z",
   "manufacturername":"_TZE200_htnnfasr",
   "modelid":"TS0601",
   "name":"On/Off light 14",
   "state":{
      "alert":"none",
      "on":false,
      "reachable":true
   },
   "swversion":null,
   "type":"On/Off light",
   "uniqueid":"84:71:27:ff:fe:d3:4a:81-01"
}

By the way, when I turn on the device, whether via Deconz or manually via button, it automatically turns off after 60 seconds. Is this also the case for you?

[SmartHomeForDummies]

The auto-off timer is the best thing about this device! 😁 unfortunately you can’t change the timer yet. I hope the device support comes very soon. 😀 I have 3 devices in use. And with this price and the auto-off function, there are sure to be even more!

[flausen]

By now I am able to open the waterflow, but the switch turns off immediately, so that I can’t Stop the waterflow using a device. Only manual at the parkside computer

[Smanar]

@stefangries yes exactly, thx.

For thoses one that can act on the device using deconz, but not working using phoscon (or API)

You have the procedure here https://github.com/dresden-elektronik/deconz-rest-plugin#install-deconz-development-package-optional-linux-only (but need a linux machine with full OS)
So for you, after having installed deconz :

sudo apt install deconz-dev
git clone --branch watering https://github.com/Smanar/deconz-rest-plugin.git
cd deconz-rest-plugin
qmake && make -j2
sudo cp ../libde_rest_plugin.so /usr/share/deCONZ/plugins

Still need to check for timer.

[Smanar]

Ok, so for the timer, nothing about this device on other project, so you need to search ^^. On the description they say the device can work with philips HUE gateway, so I don't think they use the tuya cluster (good new)

With the GUI :
Take a look on cluster 0x0006 (on/off), on attribute 0x4002 "off wait time".
Can try too the command "on with timed off"

This device can just use the "ontime" param
curl -H 'Content-Type: application/json' -X PUT -d '{"on": true, "ontime": 600}' http://192.168.1....

[stefangries]

So this should just turn the device on for 90 seconds, right?

It does turn on, but goes off after 60 seconds.

Btw, this device is very new, offical release was yesterday. I was not successful in pairing it with the hue bridge.

[ottelo9]

I ordered, too. I‘m hoping that deconz will include this new device :)

[Smanar]

Just by curiosity, someone can take a look in logs for line starting by

Tuya debug ....................

[stefangries]

I didn't find any, Here are the logs, filtered with the device id:

[Smanar]

And neither if using the device manualy ?

[stefangries]

Regardless of whether I switched the device via deconz or manually, I could not find "tuya" in the log. I use the Home Assistant addon, and have set all debug flags to 1.

[Smanar]

Ok, so we are blocked for the moment.
No tuya request.

Have you tried too with the "off wait time" in the deconz GUI ?

Someone have tried to compile the new code to check if the device is working in the API with it ?

[stefangries]

Ok, so we are blocked for the moment.
No tuya request.

Just to make sure: which debug level should be enabled to see the tuya request?

Have you tried too with the "off wait time" in the deconz GUI ?

You mean this?

Didn't changed anything.

Attributes are read only:

Someone have tried to compile the new code to check if the device is working in the API with it ?

No, I'm only running the docker container and don't have a full linux machine, sorry :-/

[SmartHomeForDummies]

The off timer starts from the new one, if On is sent again. My workaround For a watering duration of 5 min (295s), the sequence is repeated 5 times (on, wait 59s)

[Smanar]

To have tuya log you just need the flag "info", so you was fine

You mean this?

Yep, but with changing the 0 value (yeah I know, not logic, but tuya is magic ...)

No, I'm only running the docker container and don't have a full linux machine, sorry :-/

It s possible too with docker #4841 (comment)

[stefangries]

Yep, but with changing the 0 value (yeah I know, not logic, but tuya is magic ...)

Now I tried this command, which instantly turns on the device. But it turns off automatically after 60s, too.

It s possible too with docker #4841 (comment)

Building containers is quite a stressing task for my NUC J4005 :-D
Do I have to use tuya_trv_12 branch as well?
I was able to build it, but currently having trouble to pair the device.

[stefangries]

Now I was able to pair it. Here are some debug outputs (filtered for "tuya"):

21:49:03:602 Tuya debug 1 : Time sync request
21:49:03:605 Send Tuya command 0x24, data: 000060b7fccf60b7fccf
21:49:32:532 Send Tuya request: Dp_type: 0x01, Dp_identifier 0x68, data: 01
21:49:35:178 Send Tuya request: Dp_type: 0x01, Dp_identifier 0x68, data: 00

When trying to toggle in phoscon:

The server replies:
[{"error":{"address":"/lights/1/state","description":"parameter, transitiontime, not available","type":6}}]

[Smanar]

Have just updated the code for the "transitiontime" error.

But for the tuya log it s strange, this command is send when using "alert" in the request ....

[ottelo9]

I have the device in my hands now, too. Do the same that described from @stefangries . It shows in phoscon and deconz (I use the Home Assistant Addon on my Rpi3B). The state is not updated in HA but I can switch it on/off. The device switch always off after 60s.

[ottelo9]

To avoid the 60s auto off timer I use two scripts in Home Assistant as a workaround to switch on (for 1h) and switch off the valve. See the pics:

script turn on (send a switch on command every 50s)

script turn off device and script

[github-actions]

As there has not been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs.

[kopierschnitte]

Bump...

[github-actions]

As there has not been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs.

[kopierschnitte]

Bump

[github-actions]

As there has not been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs.

[github-actions]

As there has not been any response in 28 days, this issue will be closed. @ OP: If this issue is solved post what fixed it for you. If it is not solved, request to get this opened again.

[besiktas97]

Bumb, i’ve got the same device. Does anyone have got work it already with deconz?

[ChrisHae]

I have made an DDF for that device. But only On/Off works for now. Also reporting of On/Off status.
I would share it next week.

[MrSolo570]

This would be great

[ChrisHae]

Pull Request is online #6729
You can test the DDF by copying it into you (user/appData/local/) dresden-elektronik/deCONZ/devices folder
and pair the device again.

[Mimiix]

Also make sure to enable Bronze DDF's to be read.

[VentiloFred]

Pull Request is online #6729 You can test the DDF by copying it into you (user/appData/local/) dresden-elektronik/deCONZ/devices folder and pair the device again.

Good news, thanks for your job. Will it be included in future update? I'm not familiarized with DDF^^

[ChrisHae]

Yes, thx to @BabaIsYou and @sinus61 the DDF should be quite usabale now. The pull request is merged. It could be included already in the current deconz beta.

[magaHH]

Hi,
Great to see the progress made on this device. So I pulled the meter out of the dust to give it another try.
I updated and rebooted my raspberry with deconz-beta and paired the meter. It is still detected as a fairy light, still closes automatically after 60 seconds and doesn't report the updated status.

What did I miss or do wrong?

Thanks and regards
Mathias

[BabaIsYou]

Have you checked the presence of the DDF file (with .json extension) ?

[magaHH]

Yes. Both located at /usr/share/deCONZ/devices/tuya

_TZE200_htnnfasr_water_valve
_TZE200_htnnfasr_water_valve.json

[BabaIsYou]

Great. Could you first delete the one wlithout extension ? It will be deleted automatically in the next release but it’s just to be sure it doesn’t interfere here.

Then can you see the device in deconz-GUI and do you have access to DDF editor ?

[magaHH]

Sure I can delete the file without the extension. Shall I reboot and repair the meter?

I'm running the raspberry headless without a gui. I could install one if really needed.

[BabaIsYou]

Yes please, delete the file, delete the device, reboot and rejoin it.

Then using Phoscon, that will see the device as a fairy light in all case, could you get the json from all the sensors to see if the sensors are present and in which form they are …

[magaHH]

ok.

you mean the content of _TZE200_htnnfasr_water_valve.json? or the list of the other files located at /usr/share/deCONZ/devices/tuya ?

[BabaIsYou]

Sorry, not clear. Not the content of the DDF files but the way the API see the device and sensors in Phoscon for instance or Rest-Api.
Because you don’t have access to Deconz-gui we need to see results on API

[magaHH]

ahh ok.

I have two new device. One light and one Sensor.

{ "config": { "groups": [] }, "etag": "5ff649573bd20e2564e4dbe0ed166c0e", "hascolor": false, "lastannounced": null, "lastseen": "2023-03-31T11:56Z", "manufacturername": "_TZE200_htnnfasr", "modelid": "TS0601", "name": "On/Off output 2", "state": { "on": false, "reachable": true }, "swversion": null, "type": "On/Off output", "uniqueid": "84:71:27:ff:fe:1a:90:0b-01" }

{ "config": { "battery": 100, "duration": null, "locked": false, "on": true, "reachable": true }, "etag": "19dfa63bfdc7aa6990e47178cc4d868f", "lastannounced": null, "lastseen": "2023-03-31T11:57Z", "manufacturername": "_TZE200_htnnfasr", "modelid": "TS0601", "name": "OpenClose 14", "state": { "lastupdated": "none", "seconds_remaining": 0 }, "type": "ZHAOpenClose", "uniqueid": "84:71:27:ff:fe:1a:90:0b-01-0500" }

[magaHH]

any idea?

[BabaIsYou]

any idea?

About what ? The device seems to be picked up by the DDF now. Have you tried to change the duration attribute as it's explain in the referenced PR #6729 (comment) ?