Tuya soil temp/moisture sensor (TZE200_myd45weu) moisture reading stalls

Xiaomi, Ikea TRÅDFRI, Philips Hue and more.

Moderator: leecollings

Post Reply
petervz
Posts: 13
Joined: Monday 08 March 2021 15:07
Target OS: Raspberry Pi / ODroid
Domoticz version: 2023.2
Location: The Netherlands
Contact:

Tuya soil temp/moisture sensor (TZE200_myd45weu) moisture reading stalls

Post by petervz »

Hi All,

Last weeks I struggled a bit to get a Tuya soil temp and moisture sensor to work, but with the help of the deconz forum we finally managed to get it working, now the thing is, yesterday the sensor was finally added to Domoticz (using the deconz-domoticz plugin). and shows up as two sensors in Domoticz. The temperature sensors works as expected, gets updated frequently and is changing values now and then, the soil sensor is something else:

Yesterday when added it first reported 200CB *very dry* which was correct as the sensor was just lying around on my desk. After putting it in soil which was quite wet it started at 0CB (very wet) and then seemed to stabalize at 6cb (still very wet). then after the rain of yesterday evening it went to 0cb again, which is quite understandable. Though at the moment it still is displaying 0cb, which in theoretically is possible, but according to domoticz the "last seen at" says 05:31 this morning, and last record in the "log" of the sensor is at 6:30. When looking at devices I also see the last seen of 05:31....
Now comes the strange part, if I look at the json that's being reported in the deconz plugin in Domoticz it shows me that the last-seen and last-updated retrieved from the sensor(s) is just a few minutes ago, which is still 10000 (translated to 0cb, so okay there), though is not being processed by domoticz anymore......

Am I seeing something what's not here, or does this sound familiar to someone?
As said: the temp sensor part is being updated as expected and only the moisture part is reporting in a strange way.
petervz
Posts: 13
Joined: Monday 08 March 2021 15:07
Target OS: Raspberry Pi / ODroid
Domoticz version: 2023.2
Location: The Netherlands
Contact:

Re: Tuya soil temp/moisture sensor (TZE200_myd45weu) moisture reading stalls

Post by petervz »

Small update: this morning at 5:53 an update from the sensor was received (a little over 24 hours after the last update) again 0 (100% wet), and no updates since....
Thorgal789
Posts: 815
Joined: Wednesday 15 August 2018 14:38
Target OS: -
Domoticz version:
Contact:

Re: Tuya soil temp/moisture sensor (TZE200_myd45weu) moisture reading stalls

Post by Thorgal789 »

Hello.
Your probrem is you have not enought values ?
The raw value from API (visible on custom page or phoscon/help/API Information/sensors) is variable or you only have 0 or 10000 ?

(To check if the problem come from the convertion deconz>domoticz or direclty from bad value from deconz)
petervz
Posts: 13
Joined: Monday 08 March 2021 15:07
Target OS: Raspberry Pi / ODroid
Domoticz version: 2023.2
Location: The Netherlands
Contact:

Re: Tuya soil temp/moisture sensor (TZE200_myd45weu) moisture reading stalls

Post by petervz »

Thorgal,

As can be seen in the API call I just did on the sensor:

{
"config": {
"battery": 90,
"offset": 0,
"on": true,
"reachable": true
},
"etag": "72dd15c52f807ba0e8c34f7a3f4e7dd4",
"lastannounced": "2023-07-05T00:02:24Z",
"lastseen": "2023-07-06T17:55Z",
"manufacturername": "_TZE200_myd45weu",
"modelid": "TS0601",
"name": "Moisture 20",
"state": {
"lastupdated": "2023-07-06T17:55:57.759",
"lowbattery": false,
"moisture": 10000
},
"swversion": "1.0.8",
"type": "ZHAMoisture",
"uniqueid": "a4:c1:38:58:c4:64:32:ad-01-0408"
}

The result is new (lastupdated is not from long ago).
I understood Domoticz only updates values once in 24 hours when the value itself doesn't change, which is in line with the fact that this morning again (this time around 6:00) 1 update was done in domoticz...

Though, as it is dry for almost all day now, I would expect the 100% (10000) of wetness to have at least dropped a few % (100's of points)

When the sensor was just added to domoticz/deconz it went from 0 (in dry air) to 10000 (in wet soil), then dropped to 9700 and back to 10000 again after rain, so I looked like working at that moment, though as said, I actually expected him to drop again now....

Edit 6-7-2023 21:15: After removing the batteries and plugging them in again, the device triggered an update, as it went from 200cb (0 value) at start directly to 0cb (10000) in the next domoticz reading. So the device does something, though not what I would expect.
Thorgal789
Posts: 815
Joined: Wednesday 15 August 2018 14:38
Target OS: -
Domoticz version:
Contact:

Re: Tuya soil temp/moisture sensor (TZE200_myd45weu) moisture reading stalls

Post by Thorgal789 »

Yep, values are too "extrem". I have see some negative return for this device, but some others can use it normaly.
Need to check if the problem is from deconz or the device.

If I remember you have access to the GUI ?
petervz
Posts: 13
Joined: Monday 08 March 2021 15:07
Target OS: Raspberry Pi / ODroid
Domoticz version: 2023.2
Location: The Netherlands
Contact:

Re: Tuya soil temp/moisture sensor (TZE200_myd45weu) moisture reading stalls

Post by petervz »

Nope, I don't, I'm using the headless raspbian image, I can create the debug logging using the CLI params as needed.
Though if it would really make a big difference, I could (temporary) put my stick into a pi400 and install the GUI enabled version of deconz on that. Then I would be able to use the GUI, so if that would make sense...
Thorgal789
Posts: 815
Joined: Wednesday 15 August 2018 14:38
Target OS: -
Domoticz version:
Contact:

Re: Tuya soil temp/moisture sensor (TZE200_myd45weu) moisture reading stalls

Post by Thorgal789 »

I m asking for another sample on the github https://github.com/dresden-elektronik/d ... ssues/6731
But I don't think the device is talkative enought to see debug output "in live".

You can make a try with a water bottle.
Just enable logs with flag "info" (--dbg-info=1 on cli), you will see some logs like this one

Code: Select all

"TY_DATA_REORT: seq %u, dpid: 0x0003, type: 0x%02X, length: %u, val: %d\n"
It will be raw zigbee value from the device, without interpretation, so will be possible to see if we have more values.
petervz
Posts: 13
Joined: Monday 08 March 2021 15:07
Target OS: Raspberry Pi / ODroid
Domoticz version: 2023.2
Location: The Netherlands
Contact:

Re: Tuya soil temp/moisture sensor (TZE200_myd45weu) moisture reading stalls

Post by petervz »

I'll give it a try and will come back to you with the results.
petervz
Posts: 13
Joined: Monday 08 March 2021 15:07
Target OS: Raspberry Pi / ODroid
Domoticz version: 2023.2
Location: The Netherlands
Contact:

Re: Tuya soil temp/moisture sensor (TZE200_myd45weu) moisture reading stalls

Post by petervz »

Thorgal,

Just did some testing and it was quite interesting.
I started on Domoticz with the everlasting 0cb (superwet).
I went to grab the device for some testing and almost right after grabbing the device from the soil domoticz went straight to 200cb (dry as a desert).
So that sudden change as picked up and reported.

I then started deconz in debug mode and here are the results of the dutch jury ;)
Spoiler: show
09:17:14:993 HTTP Server listen on address 0.0.0.0, port: 80, root: /usr/share/deCONZ/webapp/
09:17:15:084 /home/pi/.local/share/dresden-elektronik/deCONZ/config.ini exists and is writeable
09:17:15:084 /home/pi/.local/share/dresden-elektronik/deCONZ/zll.db exists and is writeable
09:17:15:303 dev /dev/ttyAMA0
09:17:15:304 ZCLDB init file /home/pi/.local/share/dresden-elektronik/deCONZ/zcldb.txt
09:17:15:639 DDF enabled for Silver, Gold status
09:17:16:395 parent process -bash
09:17:16:395 gw run mode: normal
09:17:16:395 GW sd-card image version file does not exist: /home/pi/.local/share/dresden-elektronik/deCONZ/gw-version
09:17:16:395 sd-card cid: 744a60555344553120ffffffff01216d
09:17:16:397 DB sqlite version 3.27.2
09:17:16:399 DB PRAGMA page_count: 63
09:17:16:399 DB PRAGMA page_size: 4096
09:17:16:399 DB PRAGMA freelist_count: 3
09:17:16:399 DB file size 258048 bytes, free pages 3
09:17:16:399 DB PRAGMA user_version: 9
09:17:16:399 DB cleanup
09:17:16:400 DB create temporary views
09:17:16:436 DB skip loading sensor Temperature 19 19, handled by DDF Tuya Soil Sensor
09:17:16:437 DB skip loading sensor Moisture 20 20, handled by DDF Tuya Soil Sensor
09:17:16:438 DB skip loading sensor Nachthok 15, handled by DDF Temperature and humidity sensor
09:17:16:439 DB skip loading sensor Humidity 16 16, handled by DDF Temperature and humidity sensor
09:17:16:441 DB skip loading sensor Multi Sensor 6, handled by DDF SNZB-02 multisensor
09:17:16:442 DB skip loading sensor Multi Sensor 7, handled by DDF SNZB-02 multisensor
09:17:16:444 DB skip loading sensor Humidity 17 17, handled by DDF Temperature Humidity Sensor TS0601
09:17:16:445 DB skip loading sensor Temperature 18 18, handled by DDF Temperature Humidity Sensor TS0601
09:17:16:446 DB skip loading sensor Multi Sensor schuur 8, handled by DDF SNZB-02 multisensor
09:17:16:448 DB skip loading sensor Multi Sensor schuur 9, handled by DDF SNZB-02 multisensor
09:17:16:449 DB skip loading sensor Battery 12 12, handled by DDF TS0101
09:17:16:451 DB skip loading sensor Tuinkasje 10, handled by DDF SNZB-02 multisensor
09:17:16:452 DB skip loading sensor Tuinkasje 11, handled by DDF SNZB-02 multisensor
09:17:16:636 [INFO] - Setting environment variable 'TZ=:/etc/localtime'...
09:17:16:637 Started websocket server on 0.0.0.0, port: 8088
09:17:16:641 [INFO] - Found file containing button maps. Parsing data...
09:17:16:672 [INFO] - Button maps loaded.
09:17:16:674 found node plugin: libde_rest_plugin.so - REST API Plugin
09:17:16:675 found node plugin: libde_signal_plugin.so - Signal Monitor Plugin
09:17:16:697 found node plugin: libstd_otau_plugin.so - STD OTAU Plugin
09:17:17:042 LightNode 1: Configuration tool 1 added
09:17:17:077 LightNode 10: Eettafel added
09:17:17:085 skip legacy loading 04:cd:15:ff:fe:6a:72:20-01 / TRADFRI bulb E27 WW 806lm
09:17:17:087 skip legacy loading 04:cd:15:ff:fe:6a:72:20-01 / TRADFRI bulb E27 WW 806lm
09:17:17:089 skip legacy loading 04:cd:15:ff:fe:6a:72:20-01 / TRADFRI bulb E27 WW 806lm
09:17:17:091 skip legacy loading bc:33:ac:ff:fe:98:11:0e-01 / TRADFRI bulb E27 WW 806lm
09:17:17:094 skip legacy loading bc:33:ac:ff:fe:98:11:0e-01 / TRADFRI bulb E27 WW 806lm
09:17:17:095 skip legacy loading bc:33:ac:ff:fe:98:11:0e-01 / TRADFRI bulb E27 WW 806lm
09:17:17:098 skip legacy loading bc:33:ac:ff:fe:8f:80:29-01 / TRADFRI bulb GU10 WW 400lm
09:17:17:100 skip legacy loading bc:33:ac:ff:fe:8f:80:29-01 / TRADFRI bulb GU10 WW 400lm
09:17:17:102 skip legacy loading bc:33:ac:ff:fe:8f:80:29-01 / TRADFRI bulb GU10 WW 400lm
09:17:17:105 LightNode 13: Slaapkamer added
09:17:17:109 LightNode 16: Buiten oprit added
09:17:17:114 skip legacy loading bc:33:ac:ff:fe:19:aa:14-01 / TRADFRI bulb E27 WW 806lm
09:17:17:116 skip legacy loading bc:33:ac:ff:fe:19:aa:14-01 / TRADFRI bulb E27 WW 806lm
09:17:17:118 skip legacy loading bc:33:ac:ff:fe:19:aa:14-01 / TRADFRI bulb E27 WW 806lm
09:17:17:119 SensorNode 2 set node 0x60a423fffecef08d
09:17:17:127 skip legacy loading bc:33:ac:ff:fe:a0:0c:a8-01 / TRADFRI bulb E27 WW 806lm
09:17:17:129 skip legacy loading bc:33:ac:ff:fe:a0:0c:a8-01 / TRADFRI bulb E27 WW 806lm
09:17:17:131 skip legacy loading bc:33:ac:ff:fe:a0:0c:a8-01 / TRADFRI bulb E27 WW 806lm
09:17:17:134 LightNode 8: Gang voor added
09:17:17:139 skip legacy loading bc:33:ac:ff:fe:be:64:ea-01 / TRADFRI bulb E27 WW 806lm
09:17:17:141 skip legacy loading bc:33:ac:ff:fe:be:64:ea-01 / TRADFRI bulb E27 WW 806lm
09:17:17:143 skip legacy loading bc:33:ac:ff:fe:be:64:ea-01 / TRADFRI bulb E27 WW 806lm
09:17:17:148 skip legacy loading bc:33:ac:ff:fe:d3:70:cb-01 / TRADFRI bulb E27 WW 806lm
09:17:17:150 skip legacy loading bc:33:ac:ff:fe:d3:70:cb-01 / TRADFRI bulb E27 WW 806lm
09:17:17:152 skip legacy loading bc:33:ac:ff:fe:d3:70:cb-01 / TRADFRI bulb E27 WW 806lm
09:17:17:153 DB SELECT manufacturername FROM nodes WHERE mac LIKE 'b4:e3:f9:ff:fe:f4:e3:68%' COLLATE NOCASE: SONOFF
09:17:17:155 LightNode 22: Lader boot added
09:17:17:249 DB SELECT manufacturername FROM nodes WHERE mac LIKE 'b4:e3:f9:ff:fe:f4:e3:68%' COLLATE NOCASE: SONOFF
09:17:17:249 DB SELECT manufacturername FROM nodes WHERE mac LIKE 'b4:e3:f9:ff:fe:f4:e3:68%' COLLATE NOCASE: SONOFF
09:17:17:252 skip legacy loading bc:33:ac:ff:fe:99:c5:f1-01 / TRADFRI bulb GU10 WW 400lm
09:17:17:254 skip legacy loading bc:33:ac:ff:fe:99:c5:f1-01 / TRADFRI bulb GU10 WW 400lm
09:17:17:256 skip legacy loading bc:33:ac:ff:fe:99:c5:f1-01 / TRADFRI bulb GU10 WW 400lm
09:17:17:259 SensorNode 4 set node 0x60a423fffef28f01
09:17:17:264 skip legacy loading bc:33:ac:ff:fe:7c:10:aa-01 / TRADFRI control outlet
09:17:17:266 skip legacy loading bc:33:ac:ff:fe:7c:10:aa-01 / TRADFRI control outlet
09:17:17:268 skip legacy loading bc:33:ac:ff:fe:7c:10:aa-01 / TRADFRI control outlet
09:17:17:269 SensorNode 5 set node 0x60a423fffece969f
09:17:17:275 LightNode 3: Gang trap added
09:17:17:283 DB SELECT manufacturername FROM nodes WHERE mac LIKE '90:35:ea:ff:fe:eb:8e:25%' COLLATE NOCASE: _TZ3210_eymunffl
09:17:17:289 skip legacy loading 90:35:ea:ff:fe:eb:8e:25-01 / TS0101
09:17:17:290 DB SELECT manufacturername FROM nodes WHERE mac LIKE '90:35:ea:ff:fe:eb:8e:25%' COLLATE NOCASE: _TZ3210_eymunffl
09:17:17:295 skip legacy loading 90:35:ea:ff:fe:eb:8e:25-01 / TS0101
09:17:17:298 skip legacy loading bc:33:ac:ff:fe:a0:49:d7-01 / TRADFRI bulb GU10 WW 400lm
09:17:17:300 skip legacy loading bc:33:ac:ff:fe:a0:49:d7-01 / TRADFRI bulb GU10 WW 400lm
09:17:17:302 skip legacy loading bc:33:ac:ff:fe:a0:49:d7-01 / TRADFRI bulb GU10 WW 400lm
09:17:17:303 SensorNode 3 set node 0xbc33acfffe17650b
09:17:17:310 LightNode 20: Kippenhok added
09:17:17:315 LightNode 15: Schuur added
09:17:17:320 LightNode 17: Buiten Woonkamer added
09:17:17:415 DEV no DDF for 0xBC33ACFFFE17650B, modelId: TRADFRI on/off switch
09:17:17:416 DEV create on-the-fly DDF for 0xBC33ACFFFE17650B
09:17:17:447 dlg action: Read binding table
09:17:17:480 DEV found DDF for 0x60A423FFFECEF08D, path:
09:17:17:508 New websocket 127.0.0.1:48784 (state: 3)
09:17:17:509 DEV no DDF for 0x60A423FFFECE969F, modelId: TRADFRI motion sensor
09:17:17:509 DEV create on-the-fly DDF for 0x60A423FFFECE969F
09:17:17:511 DEV found DDF for 0x60A423FFFEF28F01, path:
09:17:17:512 DEV no DDF for 0xEC1BBDFFFE7B7CEC, modelId: TRADFRI bulb E27 WW clear 250lm
09:17:17:512 DEV create on-the-fly DDF for 0xEC1BBDFFFE7B7CEC
09:17:17:518 DEV found DDF for 0x04CD15FFFE6A7220, path: /usr/share/deCONZ/devices/ikea/tradfri_bulb_e27_ww_806lm.json
09:17:17:522 DEV found DDF for 0xBC33ACFFFE98110E, path: /usr/share/deCONZ/devices/ikea/tradfri_bulb_e27_ww_806lm.json
09:17:17:528 DEV found DDF for 0xBC33ACFFFE8F8029, path: /usr/share/deCONZ/devices/ikea/tradfri_bulb_gu10_ww_400lm.json
09:17:17:529 DEV found DDF for 0xBC33ACFFFE16AFB8, path:
09:17:17:530 DEV found DDF for 0xBC33ACFFFE977DE3, path:
09:17:17:534 DEV found DDF for 0xBC33ACFFFE19AA14, path: /usr/share/deCONZ/devices/ikea/tradfri_bulb_e27_ww_806lm.json
09:17:17:543 DEV found DDF for 0xA4C13858C46432AD, path: /usr/share/deCONZ/devices/tuya/_TZE200_myd45weu_soil_sensor.json
09:17:17:548 DEV found DDF for 0xBC33ACFFFEA00CA8, path: /usr/share/deCONZ/devices/ikea/tradfri_bulb_e27_ww_806lm.json
09:17:17:550 DEV found DDF for 0xEC1BBDFFFE7B7DDA, path:
09:17:17:555 DEV found DDF for 0xBC33ACFFFEBE64EA, path: /usr/share/deCONZ/devices/ikea/tradfri_bulb_e27_ww_806lm.json
09:17:17:564 DEV found DDF for 0xA4C138A77CB4DAD7, path: /usr/share/deCONZ/devices/tuya/_TZ3000_TS0201_temp_hum_sensor.json
09:17:17:569 DEV found DDF for 0xBC33ACFFFED370CB, path: /usr/share/deCONZ/devices/ikea/tradfri_bulb_e27_ww_806lm.json
09:17:17:570 DEV no DDF for 0xB4E3F9FFFEF4E368, modelId: 01MINIZB
09:17:17:571 DEV create on-the-fly DDF for 0xB4E3F9FFFEF4E368
09:17:17:576 DEV found DDF for 0xBC33ACFFFE99C5F1, path: /usr/share/deCONZ/devices/ikea/tradfri_bulb_gu10_ww_400lm.json
09:17:17:585 DEV found DDF for 0x00124B0023A500D7, path: /usr/share/deCONZ/devices/sonoff/snzb-02-multisensor.json
09:17:17:589 DEV found DDF for 0xBC33ACFFFE7C10AA, path: /usr/share/deCONZ/devices/ikea/tradfri_control_outlet.json
09:17:17:591 DEV found DDF for 0xCCCCCCFFFEEDABCD, path:
09:17:17:599 DEV found DDF for 0xA4C138089017FF39, path: /usr/share/deCONZ/devices/tuya/_TZE200_TS0601_humidity_temp.json
09:17:17:607 DEV found DDF for 0x00124B0025104B7F, path: /usr/share/deCONZ/devices/sonoff/snzb-02-multisensor.json
09:17:17:616 DEV found DDF for 0x9035EAFFFEEB8E25, path: /usr/share/deCONZ/devices/woox/woox_r7060_ts0101.json
09:17:17:621 DEV found DDF for 0xBC33ACFFFEA049D7, path: /usr/share/deCONZ/devices/ikea/tradfri_bulb_gu10_ww_400lm.json
09:17:17:630 DEV found DDF for 0x00124B002510D929, path: /usr/share/deCONZ/devices/sonoff/snzb-02-multisensor.json
09:17:17:631 DEV no DDF for 0x540F57FFFE1F25F6, modelId: ROB_200-006-0
09:17:17:631 DEV create on-the-fly DDF for 0x540F57FFFE1F25F6
09:17:17:633 DEV found DDF for 0xBC33ACFFFE8C0170, path:
09:17:17:634 DEV found DDF for 0xBC33ACFFFE978477, path:
09:17:18:388 dev /dev/ttyAMA0
09:17:18:574 Skip idle timer callback, too early: elapsed 930 msec
09:17:20:146 Device firmware version 0x26780700 ConBee II
09:17:20:148 unlocked max nodes: 512
09:17:20:162 Device protocol version: 0x010E
09:17:20:318 Current channel 15
09:17:20:401 CTRL ANT_CTRL 0x03
09:17:20:421 CTRL ZDP_RESPONSE handler 0x0001
09:17:20:607 ZCL attribute report 0xEC1BBDFFFE7B7CEC for cluster: 0x0008, ep: 0x01, frame control: 0x08, mfcode: 0x0000
09:17:20:624 ZCL attribute report 0x00124B0023A500D7 for cluster: 0x0402, ep: 0x01, frame control: 0x18, mfcode: 0x0000
09:17:21:893 GW update firmware found: /usr/share/deCONZ/firmware/deCONZ_ConBeeII_0x26720700.bin.GCF
09:17:21:894 GW firmware version is up to date: 0x26780700
09:17:22:091 Announced to internet https://phoscon.de/discover
09:17:22:092 discovery server date: Tue, 11 Jul 2023 07:17:22 GMT
09:17:22:093 local time seems to be ok
09:17:25:042 DEV Tick.Init: booted after 8000 seconds
09:17:44:717 Bind response success for 0xbc33acfffe16afb8 ep: 0x01 cluster: 0x0000
09:17:44:950 ZCL configure reporting rsp seq: 165 0xBC33ACFFFE16AFB8 for ep: 0x01 cluster: 0x0000 attr: 0x4000 status: 0x00
09:17:45:048 Bind response success for 0xbc33acfffe16afb8 ep: 0x01 cluster: 0x0006
09:17:45:127 ZCL configure reporting rsp seq: 167 0xBC33ACFFFE16AFB8 for ep: 0x01 cluster: 0x0006 attr: 0x0000 status: 0x00
09:17:45:305 Bind response success for 0xbc33acfffe16afb8 ep: 0x01 cluster: 0x0008
09:17:45:307 skip configure report for cluster: 0x0008 attr: 0x0000 of node 0xBC33ACFFFE16AFB8 (wait reading or unsupported)
09:17:45:414 ZCL attribute report 0xEC1BBDFFFE7B7DDA for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000
09:17:47:046 ZCL attribute report 0x00124B0023A500D7 for cluster: 0x0402, ep: 0x01, frame control: 0x18, mfcode: 0x0000
09:17:47:196 ZCL attribute report 0x00124B0023A500D7 for cluster: 0x0405, ep: 0x01, frame control: 0x18, mfcode: 0x0000
09:17:47:654 TY_DATA_REPORT: seq 5, dpid: 0x05, type: 0x02, length: 4, val: 21
09:17:47:655 TY_DATA_REPORT: seq 5, dpid: 0x05, type: 0x02, length: 4, val: 21
09:17:47:657 TY_DATA_REPORT: seq 5, dpid: 0x05, type: 0x02, length: 4, val: 21
09:17:47:687 TY_DATA_REPORT: seq 5, dpid: 0x05, type: 0x02, length: 4, val: 21
09:17:47:688 TY_DATA_REPORT: seq 5, dpid: 0x05, type: 0x02, length: 4, val: 21
09:17:47:689 TY_DATA_REPORT: seq 5, dpid: 0x05, type: 0x02, length: 4, val: 21
09:17:47:892 TY_DATA_REPORT: seq 6, dpid: 0x03, type: 0x02, length: 4, val: 100
09:17:47:893 TY_DATA_REPORT: seq 6, dpid: 0x03, type: 0x02, length: 4, val: 100
09:17:47:893 TY_DATA_REPORT: seq 6, dpid: 0x03, type: 0x02, length: 4, val: 100
09:17:47:894 TY_DATA_REPORT: seq 6, dpid: 0x03, type: 0x02, length: 4, val: 100
09:17:47:895 TY_DATA_REPORT: seq 6, dpid: 0x03, type: 0x02, length: 4, val: 100
09:17:47:896 TY_DATA_REPORT: seq 6, dpid: 0x03, type: 0x02, length: 4, val: 100
09:17:48:081 0xBC33ACFFFE978477 error APSDE-DATA.confirm: 0xE9 on task
09:17:48:203 TY_DATA_REPORT: seq 7, dpid: 0x0F, type: 0x02, length: 4, val: 90
09:17:48:204 TY_DATA_REPORT: seq 7, dpid: 0x0F, type: 0x02, length: 4, val: 90
09:17:48:205 TY_DATA_REPORT: seq 7, dpid: 0x0F, type: 0x02, length: 4, val: 90
09:17:48:206 TY_DATA_REPORT: seq 7, dpid: 0x0F, type: 0x02, length: 4, val: 90
09:17:48:207 TY_DATA_REPORT: seq 7, dpid: 0x0F, type: 0x02, length: 4, val: 90
09:17:48:207 TY_DATA_REPORT: seq 7, dpid: 0x0F, type: 0x02, length: 4, val: 90
09:17:48:367 TY_DATA_REPORT: seq 8, dpid: 0x0E, type: 0x04, length: 1, val: 2
09:17:48:368 TY_DATA_REPORT: seq 8, dpid: 0x0E, type: 0x04, length: 1, val: 2
09:17:48:369 TY_DATA_REPORT: seq 8, dpid: 0x0E, type: 0x04, length: 1, val: 2
09:17:48:370 TY_DATA_REPORT: seq 8, dpid: 0x0E, type: 0x04, length: 1, val: 2
09:17:48:371 TY_DATA_REPORT: seq 8, dpid: 0x0E, type: 0x04, length: 1, val: 2
09:17:48:372 TY_DATA_REPORT: seq 8, dpid: 0x0E, type: 0x04, length: 1, val: 2
09:17:48:898 ZCL attribute report 0x00124B0025104B7F for cluster: 0x0405, ep: 0x01, frame control: 0x18, mfcode: 0x0000
09:17:49:573 binding for cluster 0x0006 of 0xEC1BBDFFFE7B7DDA exists (verified by reporting)
09:17:49:576 skip configure report for cluster: 0x0006 attr: 0x0000 of node 0xEC1BBDFFFE7B7DDA (seems to be active)
09:18:00:132 Bind response success for 0xccccccfffeedabcd ep: 0x01 cluster: 0x0000
09:18:00:190 ZCL configure reporting rsp seq: 211 0xCCCCCCFFFEEDABCD for ep: 0x01 cluster: 0x0000 attr: 0x4000 status: 0x00
09:18:02:141 Bind response success for 0xccccccfffeedabcd ep: 0x01 cluster: 0x0006
09:18:02:199 ZCL configure reporting rsp seq: 214 0xCCCCCCFFFEEDABCD for ep: 0x01 cluster: 0x0006 attr: 0x0000 status: 0x00
09:18:02:278 Bind response success for 0xbc33acfffe16afb8 ep: 0x01 cluster: 0x0000
09:18:03:278 Bind response success for 0xccccccfffeedabcd ep: 0x01 cluster: 0x0008
09:18:03:280 skip configure report for cluster: 0x0008 attr: 0x0000 of node 0xCCCCCCFFFEEDABCD (wait reading or unsupported)
09:18:03:324 Bind response success for 0xbc33acfffe16afb8 ep: 0x01 cluster: 0x0006
09:18:03:325 skip configure report for cluster: 0x0006 attr: 0x0000 of node 0xBC33ACFFFE16AFB8 (seems to be active)
09:18:06:535 Bind response success for 0xbc33acfffe8c0170 ep: 0x01 cluster: 0x0000
09:18:06:625 ZCL configure reporting rsp seq: 226 0xBC33ACFFFE8C0170 for ep: 0x01 cluster: 0x0000 attr: 0x4000 status: 0x00
09:18:07:079 ZCL attribute report 0x00124B0023A500D7 for cluster: 0x0402, ep: 0x01, frame control: 0x18, mfcode: 0x0000
09:18:18:569 ZCL attribute report 0xEC1BBDFFFE7B7DDA for cluster: 0x0008, ep: 0x01, frame control: 0x08, mfcode: 0x0000
09:18:21:647 Bind response success for 0xbc33acfffe8c0170 ep: 0x01 cluster: 0x0006
09:18:21:839 ZCL configure reporting rsp seq: 1 0xBC33ACFFFE8C0170 for ep: 0x01 cluster: 0x0006 attr: 0x0000 status: 0x00
09:18:21:947 Bind response success for 0xccccccfffeedabcd ep: 0x01 cluster: 0x0000
09:18:25:193 Bind response success for 0xbc33acfffe8c0170 ep: 0x01 cluster: 0x0008
09:18:25:195 skip configure report for cluster: 0x0008 attr: 0x0000 of node 0xBC33ACFFFE8C0170 (wait reading or unsupported)
09:18:25:283 Bind response success for 0xccccccfffeedabcd ep: 0x01 cluster: 0x0006
09:18:25:284 skip configure report for cluster: 0x0006 attr: 0x0000 of node 0xCCCCCCFFFEEDABCD (seems to be active)
09:18:29:813 TY_DATA_REPORT: seq 9, dpid: 0x05, type: 0x02, length: 4, val: 21
09:18:29:814 TY_DATA_REPORT: seq 9, dpid: 0x05, type: 0x02, length: 4, val: 21
09:18:29:815 TY_DATA_REPORT: seq 9, dpid: 0x05, type: 0x02, length: 4, val: 21
09:18:29:816 TY_DATA_REPORT: seq 9, dpid: 0x05, type: 0x02, length: 4, val: 21
09:18:29:817 TY_DATA_REPORT: seq 9, dpid: 0x05, type: 0x02, length: 4, val: 21
09:18:29:817 TY_DATA_REPORT: seq 9, dpid: 0x05, type: 0x02, length: 4, val: 21
09:18:29:957 TY_DATA_REPORT: seq 10, dpid: 0x03, type: 0x02, length: 4, val: 0
09:18:29:957 TY_DATA_REPORT: seq 10, dpid: 0x03, type: 0x02, length: 4, val: 0
09:18:29:958 TY_DATA_REPORT: seq 10, dpid: 0x03, type: 0x02, length: 4, val: 0
09:18:29:959 TY_DATA_REPORT: seq 10, dpid: 0x03, type: 0x02, length: 4, val: 0
09:18:29:959 TY_DATA_REPORT: seq 10, dpid: 0x03, type: 0x02, length: 4, val: 0
09:18:29:960 TY_DATA_REPORT: seq 10, dpid: 0x03, type: 0x02, length: 4, val: 0
09:18:30:351 Bind response success for 0xbc33acfffe8c0170 ep: 0x01 cluster: 0x0000
09:18:31:286 TY_DATA_REPORT: seq 11, dpid: 0x0F, type: 0x02, length: 4, val: 90
09:18:31:287 TY_DATA_REPORT: seq 11, dpid: 0x0F, type: 0x02, length: 4, val: 90
09:18:31:288 TY_DATA_REPORT: seq 11, dpid: 0x0F, type: 0x02, length: 4, val: 90
09:18:31:289 TY_DATA_REPORT: seq 11, dpid: 0x0F, type: 0x02, length: 4, val: 90
09:18:31:289 TY_DATA_REPORT: seq 11, dpid: 0x0F, type: 0x02, length: 4, val: 90
09:18:31:290 TY_DATA_REPORT: seq 11, dpid: 0x0F, type: 0x02, length: 4, val: 90
09:18:31:849 TY_DATA_REPORT: seq 11, dpid: 0x0F, type: 0x02, length: 4, val: 90
09:18:31:850 TY_DATA_REPORT: seq 11, dpid: 0x0F, type: 0x02, length: 4, val: 90
09:18:31:850 TY_DATA_REPORT: seq 11, dpid: 0x0F, type: 0x02, length: 4, val: 90
09:18:31:852 TY_DATA_REPORT: seq 11, dpid: 0x0F, type: 0x02, length: 4, val: 90
09:18:31:853 TY_DATA_REPORT: seq 11, dpid: 0x0F, type: 0x02, length: 4, val: 90
09:18:31:854 TY_DATA_REPORT: seq 11, dpid: 0x0F, type: 0x02, length: 4, val: 90
09:18:31:986 TY_DATA_REPORT: seq 12, dpid: 0x0E, type: 0x04, length: 1, val: 2
09:18:31:987 TY_DATA_REPORT: seq 12, dpid: 0x0E, type: 0x04, length: 1, val: 2
09:18:31:988 TY_DATA_REPORT: seq 12, dpid: 0x0E, type: 0x04, length: 1, val: 2
09:18:31:989 TY_DATA_REPORT: seq 12, dpid: 0x0E, type: 0x04, length: 1, val: 2
09:18:31:990 TY_DATA_REPORT: seq 12, dpid: 0x0E, type: 0x04, length: 1, val: 2
09:18:31:990 TY_DATA_REPORT: seq 12, dpid: 0x0E, type: 0x04, length: 1, val: 2
09:18:40:574 binding for cluster 0x0008 of 0xEC1BBDFFFE7B7CEC exists (verified by reporting)
09:18:40:576 skip configure report for cluster: 0x0008 attr: 0x0000 of node 0xEC1BBDFFFE7B7CEC (seems to be active)
09:18:45:658 Bind response success for 0xbc33acfffe8c0170 ep: 0x01 cluster: 0x0006
09:18:45:661 skip configure report for cluster: 0x0006 attr: 0x0000 of node 0xBC33ACFFFE8C0170 (seems to be active)
09:18:45:829 ZCL attribute report 0x540F57FFFE1F25F6 for cluster: 0x0006, ep: 0x01, frame control: 0x18, mfcode: 0x0000
09:18:45:838 ZCL attribute report 0x540F57FFFE1F25F6 for cluster: 0x0008, ep: 0x01, frame control: 0x18, mfcode: 0x0000
09:18:47:663 Bind response success for 0xbc33acfffe977de3 ep: 0x01 cluster: 0x0000
09:18:47:744 ZCL configure reporting rsp seq: 37 0xBC33ACFFFE977DE3 for ep: 0x01 cluster: 0x0000 attr: 0x4000 status: 0x00
09:18:47:914 Bind response success for 0xbc33acfffe977de3 ep: 0x01 cluster: 0x0006
09:18:48:034 ZCL configure reporting rsp seq: 38 0xBC33ACFFFE977DE3 for ep: 0x01 cluster: 0x0006 attr: 0x0000 status: 0x00
09:18:48:125 Bind response success for 0xbc33acfffe977de3 ep: 0x01 cluster: 0x0008
09:18:48:127 skip configure report for cluster: 0x0008 attr: 0x0000 of node 0xBC33ACFFFE977DE3 (wait reading or unsupported)
09:18:51:319 TY_DATA_REPORT: seq 13, dpid: 0x05, type: 0x02, length: 4, val: 21
09:18:51:320 TY_DATA_REPORT: seq 13, dpid: 0x05, type: 0x02, length: 4, val: 21
09:18:51:321 TY_DATA_REPORT: seq 13, dpid: 0x05, type: 0x02, length: 4, val: 21
09:18:51:323 TY_DATA_REPORT: seq 13, dpid: 0x05, type: 0x02, length: 4, val: 21
09:18:51:324 TY_DATA_REPORT: seq 13, dpid: 0x05, type: 0x02, length: 4, val: 21
09:18:51:324 TY_DATA_REPORT: seq 13, dpid: 0x05, type: 0x02, length: 4, val: 21
09:18:51:862 TY_DATA_REPORT: seq 13, dpid: 0x05, type: 0x02, length: 4, val: 21
09:18:51:863 TY_DATA_REPORT: seq 13, dpid: 0x05, type: 0x02, length: 4, val: 21
09:18:51:864 TY_DATA_REPORT: seq 13, dpid: 0x05, type: 0x02, length: 4, val: 21
09:18:51:865 TY_DATA_REPORT: seq 13, dpid: 0x05, type: 0x02, length: 4, val: 21
09:18:51:866 TY_DATA_REPORT: seq 13, dpid: 0x05, type: 0x02, length: 4, val: 21
09:18:51:867 TY_DATA_REPORT: seq 13, dpid: 0x05, type: 0x02, length: 4, val: 21
09:18:52:018 TY_DATA_REPORT: seq 14, dpid: 0x03, type: 0x02, length: 4, val: 97
09:18:52:019 TY_DATA_REPORT: seq 14, dpid: 0x03, type: 0x02, length: 4, val: 97
09:18:52:020 TY_DATA_REPORT: seq 14, dpid: 0x03, type: 0x02, length: 4, val: 97
09:18:52:021 TY_DATA_REPORT: seq 14, dpid: 0x03, type: 0x02, length: 4, val: 97
09:18:52:022 TY_DATA_REPORT: seq 14, dpid: 0x03, type: 0x02, length: 4, val: 97
09:18:52:023 TY_DATA_REPORT: seq 14, dpid: 0x03, type: 0x02, length: 4, val: 97
09:18:52:627 TY_DATA_REPORT: seq 14, dpid: 0x03, type: 0x02, length: 4, val: 97
09:18:52:628 TY_DATA_REPORT: seq 14, dpid: 0x03, type: 0x02, length: 4, val: 97
09:18:52:628 TY_DATA_REPORT: seq 14, dpid: 0x03, type: 0x02, length: 4, val: 97
09:18:52:629 TY_DATA_REPORT: seq 14, dpid: 0x03, type: 0x02, length: 4, val: 97
09:18:52:630 TY_DATA_REPORT: seq 14, dpid: 0x03, type: 0x02, length: 4, val: 97
09:18:52:631 TY_DATA_REPORT: seq 14, dpid: 0x03, type: 0x02, length: 4, val: 97
09:18:53:185 ZCL attribute report 0xBC33ACFFFE7C10AA for cluster: 0x0008, ep: 0x01, frame control: 0x08, mfcode: 0x0000
09:18:53:239 TY_DATA_REPORT: seq 15, dpid: 0x0F, type: 0x02, length: 4, val: 90
09:18:53:241 TY_DATA_REPORT: seq 15, dpid: 0x0F, type: 0x02, length: 4, val: 90
09:18:53:241 TY_DATA_REPORT: seq 15, dpid: 0x0F, type: 0x02, length: 4, val: 90
09:18:53:243 TY_DATA_REPORT: seq 15, dpid: 0x0F, type: 0x02, length: 4, val: 90
09:18:53:244 TY_DATA_REPORT: seq 15, dpid: 0x0F, type: 0x02, length: 4, val: 90
09:18:53:244 TY_DATA_REPORT: seq 15, dpid: 0x0F, type: 0x02, length: 4, val: 90
09:18:54:599 DeviceAnnce of SensorNode: 0xA4C13858C46432AD [1]
09:18:54:600 DeviceAnnce of SensorNode: 0xA4C13858C46432AD [1]
09:18:54:907 Bind response success for 0xb4e3f9fffef4e368 ep: 0x01 cluster: 0x0006
09:18:56:587 ZCL configure reporting rsp seq: 45 0xB4E3F9FFFEF4E368 for ep: 0x01 cluster: 0x0006 attr: 0x0000 status: 0x00
09:18:57:572 binding for cluster 0x0006 of 0x540F57FFFE1F25F6 exists (verified by reporting)
09:18:57:574 skip configure report for cluster: 0x0006 attr: 0x0000 of node 0x540F57FFFE1F25F6 (seems to be active)
09:18:57:576 binding for cluster 0x0008 of 0x540F57FFFE1F25F6 exists (verified by reporting)
09:18:57:578 skip configure report for cluster: 0x0008 attr: 0x0000 of node 0x540F57FFFE1F25F6 (seems to be active)
09:19:06:549 ZCL attribute report 0xEC1BBDFFFE7B7CEC for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000
09:19:07:649 Bind response success for 0xbc33acfffe978477 ep: 0x01 cluster: 0x0000
09:19:07:715 ZCL configure reporting rsp seq: 55 0xBC33ACFFFE978477 for ep: 0x01 cluster: 0x0000 attr: 0x4000 status: 0x00
09:19:07:855 Bind response success for 0xbc33acfffe977de3 ep: 0x01 cluster: 0x0000
09:19:08:301 Bind response success for 0xbc33acfffe978477 ep: 0x01 cluster: 0x0000
09:19:09:344 Bind response success for 0xbc33acfffe977de3 ep: 0x01 cluster: 0x0006
09:19:09:346 skip configure report for cluster: 0x0006 attr: 0x0000 of node 0xBC33ACFFFE977DE3 (seems to be active)
09:19:10:448 Bind response success for 0xbc33acfffe978477 ep: 0x01 cluster: 0x0006
09:19:10:527 ZCL configure reporting rsp seq: 57 0xBC33ACFFFE978477 for ep: 0x01 cluster: 0x0006 attr: 0x0000 status: 0x00
09:19:10:584 Bind response success for 0xbc33acfffe978477 ep: 0x01 cluster: 0x0008
09:19:10:586 skip configure report for cluster: 0x0008 attr: 0x0000 of node 0xBC33ACFFFE978477 (wait reading or unsupported)
09:19:15:694 Bind response success for 0xb4e3f9fffef4e368 ep: 0x01 cluster: 0x0006
09:19:15:695 skip configure report for cluster: 0x0006 attr: 0x0000 of node 0xB4E3F9FFFEF4E368 (seems to be active)
09:19:23:636 skip configure report for cluster: 0x0006 attr: 0x0000 of node 0xBC33ACFFFE978477 (seems to be active)
09:19:24:152 0x04cd15fffe6a7220 found group 0xFFF0
09:19:24:919 0xbc33acfffe98110e found group 0xFFF0
09:19:24:920 0xbc33acfffe98110e found group 0x0001
09:19:25:712 0xbc33acfffe8f8029 found group 0xFFF0
09:19:26:383 0xbc33acfffe19aa14 found group 0xFFF0
09:19:26:384 0xbc33acfffe19aa14 found group 0x0009
09:19:27:128 0xbc33acfffea00ca8 found group 0xFFF0
09:19:27:913 0xbc33acfffebe64ea found group 0xFFF0
09:19:27:914 0xbc33acfffebe64ea found group 0x0002
09:19:27:942 remove binding from 0x540F57FFFE1F25F6 cluster 0x2000 due non existing cluster
09:19:28:663 0xbc33acfffed370cb found group 0xFFF0
09:19:28:664 0xbc33acfffed370cb found group 0x0005
09:19:29:265 Unbind response failed with status 0x88 for 0x540f57fffe1f25f6 ep: 0x01 cluster: 0x2000
09:19:29:489 0xbc33acfffe99c5f1 found group 0xFFF0
09:19:30:126 0xbc33acfffe7c10aa found group 0xFFF0
09:19:30:126 0xbc33acfffe7c10aa found group 0x0003
09:19:31:703 0xbc33acfffea049d7 found group 0xFFF0
09:19:31:703 0xbc33acfffea049d7 found group 0x0003
09:19:32:362 0xec1bbdfffe7b7cec found group 0xFFF0
09:19:33:123 0xbc33acfffe16afb8 found group 0xFFF0
09:19:33:124 0xbc33acfffe16afb8 found group 0x0001
09:19:33:872 0xbc33acfffe977de3 found group 0xFFF0
09:19:33:873 0xbc33acfffe977de3 found group 0x0009
09:19:34:662 0xec1bbdfffe7b7dda found group 0xFFF0
09:19:34:663 0xec1bbdfffe7b7dda found group 0x0002
09:19:35:405 0xb4e3f9fffef4e368 found group 0xFFF0
09:19:35:871 0x9035eafffeeb8e25 found group 0xFFF0
09:19:35:872 0x9035eafffeeb8e25 found group 0x0009
09:19:35:946 ZCL attribute report 0xB4E3F9FFFEF4E368 for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000
09:19:36:131 0xccccccfffeedabcd found group 0xFFF0
09:19:36:132 0xccccccfffeedabcd found group 0x0002
09:19:36:952 0x540f57fffe1f25f6 found group 0xFFF0
09:19:37:709 0xbc33acfffe8c0170 found group 0xFFF0
09:19:37:710 0xbc33acfffe8c0170 found group 0x0009
09:19:38:413 0xbc33acfffe978477 found group 0xFFF0
09:19:38:414 0xbc33acfffe978477 found group 0x0009
09:19:54:176 DeviceAnnce of SensorNode: 0xA4C13858C46432AD [1]
09:19:54:177 DeviceAnnce of SensorNode: 0xA4C13858C46432AD [1]
09:19:54:923 ZCL attribute report 0xEC1BBDFFFE7B7CEC for cluster: 0x0008, ep: 0x01, frame control: 0x08, mfcode: 0x0000
09:19:56:707 remove binding from 0x540F57FFFE1F25F6 cluster 0x2000 due non existing cluster
09:19:56:807 Unbind response failed with status 0x88 for 0x540f57fffe1f25f6 ep: 0x01 cluster: 0x2000
09:19:59:329 ZCL attribute report 0xA4C13858C46432AD for cluster: 0x0000, ep: 0x01, frame control: 0x08, mfcode: 0x0000
09:20:04:648 ZCL attribute report 0xA4C13858C46432AD for cluster: 0x0000, ep: 0x01, frame control: 0x08, mfcode: 0x0000
09:20:16:611 ZCL attribute report 0xBC33ACFFFEA049D7 for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000
09:20:18:690 ZCL attribute report 0xBC33ACFFFE8F8029 for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000
09:20:20:361 ZCL attribute report 0xBC33ACFFFE99C5F1 for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000
09:20:22:314 ZCL attribute report 0xBC33ACFFFE99C5F1 for cluster: 0x0008, ep: 0x01, frame control: 0x08, mfcode: 0x0000
09:20:25:394 ZCL attribute report 0x04CD15FFFE6A7220 for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000
09:20:36:551 TY_DATA_REPORT: seq 21, dpid: 0x05, type: 0x02, length: 4, val: 22
09:20:36:553 TY_DATA_REPORT: seq 21, dpid: 0x05, type: 0x02, length: 4, val: 22
09:20:36:554 TY_DATA_REPORT: seq 21, dpid: 0x05, type: 0x02, length: 4, val: 22
09:20:36:556 TY_DATA_REPORT: seq 21, dpid: 0x05, type: 0x02, length: 4, val: 22
09:20:36:557 TY_DATA_REPORT: seq 21, dpid: 0x05, type: 0x02, length: 4, val: 22
09:20:36:558 TY_DATA_REPORT: seq 21, dpid: 0x05, type: 0x02, length: 4, val: 22
09:20:36:673 TY_DATA_REPORT: seq 22, dpid: 0x03, type: 0x02, length: 4, val: 0
09:20:36:674 TY_DATA_REPORT: seq 22, dpid: 0x03, type: 0x02, length: 4, val: 0
09:20:36:675 TY_DATA_REPORT: seq 22, dpid: 0x03, type: 0x02, length: 4, val: 0
09:20:36:676 TY_DATA_REPORT: seq 22, dpid: 0x03, type: 0x02, length: 4, val: 0
09:20:36:677 TY_DATA_REPORT: seq 22, dpid: 0x03, type: 0x02, length: 4, val: 0
09:20:36:678 TY_DATA_REPORT: seq 22, dpid: 0x03, type: 0x02, length: 4, val: 0
09:20:36:799 TY_DATA_REPORT: seq 23, dpid: 0x0F, type: 0x02, length: 4, val: 90
09:20:36:800 TY_DATA_REPORT: seq 23, dpid: 0x0F, type: 0x02, length: 4, val: 90
09:20:36:801 TY_DATA_REPORT: seq 23, dpid: 0x0F, type: 0x02, length: 4, val: 90
09:20:36:803 TY_DATA_REPORT: seq 23, dpid: 0x0F, type: 0x02, length: 4, val: 90
09:20:36:804 TY_DATA_REPORT: seq 23, dpid: 0x0F, type: 0x02, length: 4, val: 90
09:20:36:804 TY_DATA_REPORT: seq 23, dpid: 0x0F, type: 0x02, length: 4, val: 90
09:20:36:924 TY_DATA_REPORT: seq 24, dpid: 0x0E, type: 0x04, length: 1, val: 2
09:20:36:925 TY_DATA_REPORT: seq 24, dpid: 0x0E, type: 0x04, length: 1, val: 2
09:20:36:926 TY_DATA_REPORT: seq 24, dpid: 0x0E, type: 0x04, length: 1, val: 2
09:20:36:927 TY_DATA_REPORT: seq 24, dpid: 0x0E, type: 0x04, length: 1, val: 2
09:20:36:929 TY_DATA_REPORT: seq 24, dpid: 0x0E, type: 0x04, length: 1, val: 2
09:20:36:929 TY_DATA_REPORT: seq 24, dpid: 0x0E, type: 0x04, length: 1, val: 2
09:20:45:354 ZCL attribute report 0xEC1BBDFFFE7B7DDA for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000
09:21:18:571 ZCL attribute report 0xEC1BBDFFFE7B7DDA for cluster: 0x0008, ep: 0x01, frame control: 0x08, mfcode: 0x0000
09:21:18:657 TY_DATA_REPORT: seq 25, dpid: 0x05, type: 0x02, length: 4, val: 22
09:21:18:658 TY_DATA_REPORT: seq 25, dpid: 0x05, type: 0x02, length: 4, val: 22
09:21:18:659 TY_DATA_REPORT: seq 25, dpid: 0x05, type: 0x02, length: 4, val: 22
09:21:18:660 TY_DATA_REPORT: seq 25, dpid: 0x05, type: 0x02, length: 4, val: 22
09:21:18:660 TY_DATA_REPORT: seq 25, dpid: 0x05, type: 0x02, length: 4, val: 22
09:21:18:660 TY_DATA_REPORT: seq 25, dpid: 0x05, type: 0x02, length: 4, val: 22
09:21:18:781 TY_DATA_REPORT: seq 26, dpid: 0x03, type: 0x02, length: 4, val: 72
09:21:18:781 TY_DATA_REPORT: seq 26, dpid: 0x03, type: 0x02, length: 4, val: 72
09:21:18:782 TY_DATA_REPORT: seq 26, dpid: 0x03, type: 0x02, length: 4, val: 72
09:21:18:782 TY_DATA_REPORT: seq 26, dpid: 0x03, type: 0x02, length: 4, val: 72
09:21:18:783 TY_DATA_REPORT: seq 26, dpid: 0x03, type: 0x02, length: 4, val: 72
09:21:18:784 TY_DATA_REPORT: seq 26, dpid: 0x03, type: 0x02, length: 4, val: 72
09:21:18:913 TY_DATA_REPORT: seq 27, dpid: 0x0F, type: 0x02, length: 4, val: 90
09:21:18:913 TY_DATA_REPORT: seq 27, dpid: 0x0F, type: 0x02, length: 4, val: 90
09:21:18:914 TY_DATA_REPORT: seq 27, dpid: 0x0F, type: 0x02, length: 4, val: 90
09:21:18:915 TY_DATA_REPORT: seq 27, dpid: 0x0F, type: 0x02, length: 4, val: 90
09:21:18:915 TY_DATA_REPORT: seq 27, dpid: 0x0F, type: 0x02, length: 4, val: 90
09:21:18:916 TY_DATA_REPORT: seq 27, dpid: 0x0F, type: 0x02, length: 4, val: 90
09:21:19:037 TY_DATA_REPORT: seq 28, dpid: 0x0E, type: 0x04, length: 1, val: 2
09:21:19:038 TY_DATA_REPORT: seq 28, dpid: 0x0E, type: 0x04, length: 1, val: 2
09:21:19:039 TY_DATA_REPORT: seq 28, dpid: 0x0E, type: 0x04, length: 1, val: 2
09:21:19:039 TY_DATA_REPORT: seq 28, dpid: 0x0E, type: 0x04, length: 1, val: 2
09:21:19:040 TY_DATA_REPORT: seq 28, dpid: 0x0E, type: 0x04, length: 1, val: 2
09:21:19:040 TY_DATA_REPORT: seq 28, dpid: 0x0E, type: 0x04, length: 1, val: 2
09:21:22:081 GW firmware version is up to date: 0x26780700
09:21:23:633 ZCL attribute report 0xB4E3F9FFFEF4E368 for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000
09:21:40:172 TY_DATA_REPORT: seq 1398, dpid: 0x01, type: 0x02, length: 4, val: 223
09:21:40:173 TY_DATA_REPORT: seq 1398, dpid: 0x01, type: 0x02, length: 4, val: 223
09:21:40:174 TY_DATA_REPORT: seq 1398, dpid: 0x01, type: 0x02, length: 4, val: 223
09:21:40:176 TY_DATA_REPORT: seq 1398, dpid: 0x01, type: 0x02, length: 4, val: 223
09:21:40:389 TY_DATA_REPORT: seq 1399, dpid: 0x02, type: 0x02, length: 4, val: 60
09:21:40:390 TY_DATA_REPORT: seq 1399, dpid: 0x02, type: 0x02, length: 4, val: 60
09:21:40:483 TY_DATA_REPORT: seq 1399, dpid: 0x02, type: 0x02, length: 4, val: 60
09:21:40:484 TY_DATA_REPORT: seq 1399, dpid: 0x02, type: 0x02, length: 4, val: 60
09:21:40:679 TY_DATA_REPORT: seq 1400, dpid: 0x03, type: 0x04, length: 1, val: 2
09:21:40:680 TY_DATA_REPORT: seq 1400, dpid: 0x03, type: 0x04, length: 1, val: 2
09:21:40:681 TY_DATA_REPORT: seq 1400, dpid: 0x03, type: 0x04, length: 1, val: 2
09:21:40:682 TY_DATA_REPORT: seq 1400, dpid: 0x03, type: 0x04, length: 1, val: 2
09:21:40:838 TY_DATA_REPORT: seq 1401, dpid: 0x09, type: 0x04, length: 1, val: 0
09:21:40:839 TY_DATA_REPORT: seq 1401, dpid: 0x09, type: 0x04, length: 1, val: 0
09:21:40:840 TY_DATA_REPORT: seq 1401, dpid: 0x09, type: 0x04, length: 1, val: 0
09:21:40:841 TY_DATA_REPORT: seq 1401, dpid: 0x09, type: 0x04, length: 1, val: 0
09:21:42:258 ZCL attribute report 0x04CD15FFFE6A7220 for cluster: 0x0008, ep: 0x01, frame control: 0x08, mfcode: 0x0000
09:21:42:494 ZCL attribute report 0xBC33ACFFFEA049D7 for cluster: 0x0008, ep: 0x01, frame control: 0x08, mfcode: 0x0000
09:21:42:588 ZCL attribute report 0xBC33ACFFFE8F8029 for cluster: 0x0008, ep: 0x01, frame control: 0x08, mfcode: 0x0000
09:22:06:611 ZCL attribute report 0xEC1BBDFFFE7B7CEC for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000
09:22:54:874 ZCL attribute report 0xEC1BBDFFFE7B7CEC for cluster: 0x0008, ep: 0x01, frame control: 0x08, mfcode: 0x0000
09:23:04:033 [INFO] - Button 1002 - TRADFRI motion sensor, broadcast to: 0x0007, endpoint: 0x01, cluster: ONOFF (0x0006), action: On with timed off, payload: 0008070000, zclSeq: 86
09:23:04:171 delay sending request 212 dt 0 ms to 0xBC33ACFFFEBE64EA, ep: 0x01 cluster: 0x0008 onAir: 1
09:23:04:244 0xBC33ACFFFEBE64EA force poll (2)
09:23:04:263 ZCL attribute report 0xBC33ACFFFEBE64EA for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000
09:23:04:337 ZCL attribute report 0xBC33ACFFFEBE64EA for cluster: 0x0008, ep: 0x01, frame control: 0x08, mfcode: 0x0000
09:23:04:364 0xBC33ACFFFEBE64EA force poll (2)
09:23:04:571 Set sensor check interval to 100 milliseconds
09:23:09:256 ZCL attribute report 0xBC33ACFFFEBE64EA for cluster: 0x0008, ep: 0x01, frame control: 0x08, mfcode: 0x0000
09:23:10:182 [INFO] - Button 1002 - TRADFRI motion sensor, broadcast to: 0x0008, endpoint: 0x01, cluster: ONOFF (0x0006), action: On with timed off, payload: 0008070000, zclSeq: 94
09:23:23:033 TY_DATA_REPORT: seq 29, dpid: 0x05, type: 0x02, length: 4, val: 22
09:23:23:035 TY_DATA_REPORT: seq 29, dpid: 0x05, type: 0x02, length: 4, val: 22
09:23:23:036 TY_DATA_REPORT: seq 29, dpid: 0x05, type: 0x02, length: 4, val: 22
09:23:23:037 TY_DATA_REPORT: seq 29, dpid: 0x05, type: 0x02, length: 4, val: 22
09:23:23:038 TY_DATA_REPORT: seq 29, dpid: 0x05, type: 0x02, length: 4, val: 22
09:23:23:039 TY_DATA_REPORT: seq 29, dpid: 0x05, type: 0x02, length: 4, val: 22
09:23:23:113 TY_DATA_REPORT: seq 30, dpid: 0x03, type: 0x02, length: 4, val: 0
09:23:23:114 TY_DATA_REPORT: seq 30, dpid: 0x03, type: 0x02, length: 4, val: 0
09:23:23:115 TY_DATA_REPORT: seq 30, dpid: 0x03, type: 0x02, length: 4, val: 0
09:23:23:116 TY_DATA_REPORT: seq 30, dpid: 0x03, type: 0x02, length: 4, val: 0
09:23:23:117 TY_DATA_REPORT: seq 30, dpid: 0x03, type: 0x02, length: 4, val: 0
09:23:23:118 TY_DATA_REPORT: seq 30, dpid: 0x03, type: 0x02, length: 4, val: 0
09:23:23:793 TY_DATA_REPORT: seq 31, dpid: 0x0F, type: 0x02, length: 4, val: 90
09:23:23:794 TY_DATA_REPORT: seq 31, dpid: 0x0F, type: 0x02, length: 4, val: 90
09:23:23:795 TY_DATA_REPORT: seq 31, dpid: 0x0F, type: 0x02, length: 4, val: 90
09:23:23:796 TY_DATA_REPORT: seq 31, dpid: 0x0F, type: 0x02, length: 4, val: 90
09:23:23:797 TY_DATA_REPORT: seq 31, dpid: 0x0F, type: 0x02, length: 4, val: 90
09:23:23:798 TY_DATA_REPORT: seq 31, dpid: 0x0F, type: 0x02, length: 4, val: 90
09:23:24:469 TY_DATA_REPORT: seq 32, dpid: 0x0E, type: 0x04, length: 1, val: 2
09:23:24:471 TY_DATA_REPORT: seq 32, dpid: 0x0E, type: 0x04, length: 1, val: 2
09:23:24:472 TY_DATA_REPORT: seq 32, dpid: 0x0E, type: 0x04, length: 1, val: 2
09:23:24:473 TY_DATA_REPORT: seq 32, dpid
I started this test at 200cb (sensor value in deconz/json 0)

I dipped the sensor into water, which was picked up almost instant, logged to deconz info and changed in Domoticz to 0cb again.
After that picked it out of the water again and again, almost instant it went up to 200cb.
After that I put it back into the water, this time it wasn't picked up instantly, though after short pressing the button it did report it back to 6cb this time (I saw that before, so for some reason it thinks it's 97% wet.
Then again, picked it out and put it into a cactus standing by here which I put a little water in it for testing purposes and it reported 56cb, so it actually seems to be picking up correct numbers up as well then....

I restarted deconz as service, and brought the sensor back to my garden. It now went directly from 200 (dry) to 0 again (after putting it in the soil) and that's where it's at now.....

For some reason it almost looks like it is able to pick up big movements in moisture without any issue, though smaller changes (caused by a dry day after rain for instance) aren't picked up at all (even after a whole dry day it is just reporting 0cb every day (after it's 24 hour reporting interval).
And just in case: the device is closer to my stick at it's oficial position then the test position and I have multiple 220v power lights in that area as well, so signalling shouldn't be a problem here.
Thorgal789
Posts: 815
Joined: Wednesday 15 August 2018 14:38
Target OS: -
Domoticz version:
Contact:

Re: Tuya soil temp/moisture sensor (TZE200_myd45weu) moisture reading stalls

Post by Thorgal789 »

Supposing you haven't 20 tuya device (haven't checked if logs are from the same one)

Code: Select all

09:17:47:892 TY_DATA_REPORT: seq 6, dpid: 0x03, type: 0x02, length: 4, val: 100
09:18:29:957 TY_DATA_REPORT: seq 10, dpid: 0x03, type: 0x02, length: 4, val: 0
09:18:52:018 TY_DATA_REPORT: seq 14, dpid: 0x03, type: 0x02, length: 4, val: 97
09:21:18:781 TY_DATA_REPORT: seq 26, dpid: 0x03, type: 0x02, length: 4, val: 72
And no more value (the dutch jury have spoken), so 0, 100 , 72 and 97 %, converted to domoticz value : 200 , 0 , 56 and 6 %.

So exaclty the value you have see, and the device haven't send more.

IDK what to say, tuya device haven't report/bind for tuya cluster, all is native, and this device don't have a setting to change the sensibility https://www.zigbee2mqtt.io/devices/TS0601_soil.html
petervz
Posts: 13
Joined: Monday 08 March 2021 15:07
Target OS: Raspberry Pi / ODroid
Domoticz version: 2023.2
Location: The Netherlands
Contact:

Re: Tuya soil temp/moisture sensor (TZE200_myd45weu) moisture reading stalls

Post by petervz »

So if I understand right, I'm stuck with a device that misbehaves in a way, although it is able to work as long as (as it seems now) the changes in value are super big (that probably will only be when given water from a situation when the device measures dry soil, but that will never happen in normal day life, right?

I'll see if I can test it for a longer time at my test location of yesterday, to see if it picks up smaller variation in there, which would puzzle me, but on the other hand, why not....

BY the way, I do own a couple of Tuya (based) devices, but they were not part of the test window ;-)
petervz
Posts: 13
Joined: Monday 08 March 2021 15:07
Target OS: Raspberry Pi / ODroid
Domoticz version: 2023.2
Location: The Netherlands
Contact:

Re: Tuya soil temp/moisture sensor (TZE200_myd45weu) moisture reading stalls

Post by petervz »

Before we dive any deeper into this.
I just did a testrun with the/a plant in my office, a cactus, which normally has quite dry soil.
It's the one that gave 56cb after a bunch of water.
Today I put in in the soil again and it gave me a much higher value (142), and after stabilizing a little below, I gave it another bit of water and again, it lowered till 82. So long story short, it seems just to be working here. What is the fact that causes multpile days of 0 (100% moisture) in a row then when it's outside......?

I have a theory: it might be the case that in the pot that I'm measuring, the moisture content is actually way above the content it classifies as 100% moisture, which causes it to report 0 for multiple days in a row, because the moisture saturation at the sensor depth is still > 100% measurement all the time. I will put it back and see what it does if all (automatic) hidrations are disabled for a few days and it really must get dryer (also at sensor depth).
Although I find it strange cause at the current weather (dry, sunny and windy) I would expect the level the change during the day, but let's see.
Thorgal789
Posts: 815
Joined: Wednesday 15 August 2018 14:38
Target OS: -
Domoticz version:
Contact:

Re: Tuya soil temp/moisture sensor (TZE200_myd45weu) moisture reading stalls

Post by Thorgal789 »

Here you have a graph for this device from a z2m user https://github.com/dresden-elektronik/d ... 1629844479
Ha have more values, but bouncing one.
petervz
Posts: 13
Joined: Monday 08 March 2021 15:07
Target OS: Raspberry Pi / ODroid
Domoticz version: 2023.2
Location: The Netherlands
Contact:

Re: Tuya soil temp/moisture sensor (TZE200_myd45weu) moisture reading stalls

Post by petervz »

Mine didn't even had that problem, this is mine from the last day, the first rampup is going from 0 to 200 when starting the test and as can be seen, after a shile I put it back into the outside soil again (an 0cb since), but the time doing the tests actually looks good.

Image

I'll keep you posted about the progress.
Last edited by petervz on Friday 14 July 2023 8:13, edited 1 time in total.
petervz
Posts: 13
Joined: Monday 08 March 2021 15:07
Target OS: Raspberry Pi / ODroid
Domoticz version: 2023.2
Location: The Netherlands
Contact:

Re: Tuya soil temp/moisture sensor (TZE200_myd45weu) moisture reading stalls

Post by petervz »

All (en Thorgal),

I'm so sorry for keeping you busy in this "problem", now I found out there is no problem at all.
After transferring the sensor to another pot, it started displaying values and as can be seen in the attached picture, it responds perfectly during the day and the drop in dryness, is also clearly visible as at 6:00 the irrigation kicked in.

Image

Thanks for you time!

Some advice for anyone looking for these kind of problems, probably the sensor is quite sensitive for moisture, so expect him to stay at 100% (or 0cb in Domoticz) for a long time, when it's wet, ony one measurement (displaying 0) per 24 hours in normal in that case.
Thorgal789
Posts: 815
Joined: Wednesday 15 August 2018 14:38
Target OS: -
Domoticz version:
Contact:

Re: Tuya soil temp/moisture sensor (TZE200_myd45weu) moisture reading stalls

Post by Thorgal789 »

Perhaps the moisture in ground don't work like humidity in air. There is probably a physical reaction with water in earth when you just put the water.
petervz
Posts: 13
Joined: Monday 08 March 2021 15:07
Target OS: Raspberry Pi / ODroid
Domoticz version: 2023.2
Location: The Netherlands
Contact:

Re: Tuya soil temp/moisture sensor (TZE200_myd45weu) moisture reading stalls

Post by petervz »

I have no clue how it works exactly, but now I am monitoring another pot, levels are being updated regularly and today I even managed to build a simple LUA script that monitors the cb values to start and stop irrigating and because of the now correct working, it really works like a charm.
Using these moisture sensors has a learning curve, but I expect it to be a steep one, so probably I'll manage to keep the plants in top condition without spending to much water.... Now we only need a dedicated sensor for every plant / tree :-P
Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest