MOES TRV HY368 TS0601 : wrong reporting of current temperature (2 degrees)

SebLz commented 2 years ago

Describe the bug

Multiple MOES HY368 TRV report wrong "current temperature values" of 2 degrees. Sometimes it updates to the right value, sometimes to 2. Similar to this closed issue: https://github.com/dresden-elektronik/deconz-rest-plugin/issues/5384 ?

Steps to reproduce the behavior

Expected behavior

Display same temperature values as on the TRV device

Screenshots

Environment

Host system: Odroid C4
Running method: Home Assistant deCONZ Add-on
Firmware version: 26660700
deCONZ version: 2.12.06 / 19/08/2021
Device: ConBee II
Do you use an USB extension cable: yes
Is there any other USB or serial devices connected to the host system: no

deCONZ Logs

Additional context

REST API:

{
    "config": {
        "heatsetpoint": 2000,
        "locked": false,
        "mode": "auto",
        "offset": 0,
        "on": true,
        "preset": "manual",
        "reachable": true,
        "schedule": {
            "W124": [
                {
                    "heatsetpoint": 20,
                    "localtime": "T06:00"
                },
                {
                    "heatsetpoint": 15,
                    "localtime": "T08:00"
                },
                {
                    "heatsetpoint": 15,
                    "localtime": "T11:30"
                },
                {
                    "heatsetpoint": 15,
                    "localtime": "T12:30"
                },
                {
                    "heatsetpoint": 20,
                    "localtime": "T17:30"
                },
                {
                    "heatsetpoint": 15,
                    "localtime": "T22:00"
                }
            ],
            "W3": [
                {
                    "heatsetpoint": 20,
                    "localtime": "T134:00"
                },
                {
                    "heatsetpoint": 15,
                    "localtime": "T08:00"
                },
                {
                    "heatsetpoint": 15,
                    "localtime": "T11:30"
                },
                {
                    "heatsetpoint": 15,
                    "localtime": "T12:30"
                },
                {
                    "heatsetpoint": 20,
                    "localtime": "T17:30"
                },
                {
                    "heatsetpoint": 15,
                    "localtime": "T22:00"
                }
            ]
        },
        "schedule_on": false,
        "setvalve": false,
        "windowopen_set": false
    },
    "ep": 1,
    "etag": "0fe205de324967817d4ae8b739e9ca30",
    "lastannounced": "2021-10-18T20:11:43Z",
    "lastseen": "2021-10-18T20:11Z",
    "manufacturername": "_TZE200_ckud7u2l",
    "modelid": "TS0601",
    "name": "Radiateur chambre à coucher",
    "state": {
        "lastupdated": "2021-10-18T20:13:12.031",
        "lowbattery": false,
        "on": true,
        "temperature": 200,
        "valve": 85
    },
    "type": "ZHAThermostat",
    "uniqueid": "5c:02:72:ff:fe:8e:f7:e9-01-0201"
}

TheNON75 commented 2 years ago

Hi @SebLz When did you upgrade to this version? Directly after upgrading, I have experienced the same but from 15-30 minutes to few hours later all 6 TRVs have fixed itself and sending the correct temperature values. I am using the latest stable and latest firmware

Mimiix commented 2 years ago

@Smanar

Smanar commented 2 years ago

There is probably a new command that overwrite the temperature one. The temperature is 0x02 0x03 for this device.

Can you check using log with "info" line starting by "Tuya debug 4" and "Tuya debug 5" ?

It's all requests send by the device to the coordinator. If I m right you will have one with 0x02 0x18 or 0x02 0x6B.

I can't guess what can be the "2" value, min temperature value ?

SebLz commented 2 years ago

There is probably a new command that overwrite the temperature one. The temperature is 0x02 0x03 for this device.

Can you check using log with "info" line starting by "Tuya debug 4" and "Tuya debug 5" ?

It's all requests send by the device to the coordinator. If I m right you will have one with 0x02 0x18 or 0x02 0x6B.

I can't guess what can be the "2" value, min temperature value ?

Hello @Smanar, I'm not sure if this is providing enough info but here is a log sample I've captured after changing the temperature on the device to trigger some exchanges between the node and the coordinator.

21:10:01:910 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 04156a04000100
21:10:01:911 Tuya debug 5 : Status: 4 Transid: 21 Dp: 1130 (0x04,0x6A) Fn: 0 Data 365072220160
21:10:01:912 APS-DATA.request id: 96, addrmode: 0x02, addr: 0x741f, profile: 0x0104, cluster: 0xEF00, ep: 0x01 -> 0x01 queue: 0 len: 5 tx.options 0x04
21:10:02:018 APS-DATA.confirm id: 96, status: 0x00 SUCCESS
21:10:02:019 APS-DATA.confirm request id: 96 -> erase from queue
21:10:02:026 APS-DATA.indication srcAddr: 0x741f, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0xEF00, lqi: 255, rssi: -55
21:10:02:027 APS-DATA.request id: 96 erase from queue
21:10:02:028 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 04166b02000400000014
21:10:02:029 Tuya debug 5 : Status: 4 Transid: 22 Dp: 619 (0x02,0x6B) Fn: 0 Data 365072220180
21:10:02:029 APS-DATA.request id: 98, addrmode: 0x02, addr: 0x741f, profile: 0x0104, cluster: 0xEF00, ep: 0x01 -> 0x01 queue: 0 len: 5 tx.options 0x04
21:10:02:140 APS-DATA.confirm id: 98, status: 0x00 SUCCESS
21:10:02:141 APS-DATA.confirm request id: 98 -> erase from queue
21:10:02:145 aps request id: 98 finished, erase from queue
21:10:02:155 APS-DATA.indication srcAddr: 0x741f, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0xEF00, lqi: 255, rssi: -54
21:10:02:157 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 04176c0200040000000f
21:10:02:157 Tuya debug 5 : Status: 4 Transid: 23 Dp: 620 (0x02,0x6C) Fn: 0 Data 365072220175
21:10:02:158 APS-DATA.request id: 101, addrmode: 0x02, addr: 0x741f, profile: 0x0104, cluster: 0xEF00, ep: 0x01 -> 0x01 queue: 0 len: 5 tx.options 0x04
21:10:02:278 APS-DATA.confirm id: 101, status: 0x00 SUCCESS
21:10:02:280 APS-DATA.confirm request id: 101 -> erase from queue
21:10:02:285 APS-DATA.indication srcAddr: 0x741f, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0xEF00, lqi: 255, rssi: -54
21:10:02:287 APS-DATA.request id: 101 erase from queue
21:10:02:288 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 04186d02000400000005
21:10:02:289 Tuya debug 5 : Status: 4 Transid: 24 Dp: 621 (0x02,0x6D) Fn: 0 Data 365072220165
21:10:02:290 APS-DATA.request id: 103, addrmode: 0x02, addr: 0x741f, profile: 0x0104, cluster: 0xEF00, ep: 0x01 -> 0x01 queue: 0 len: 5 tx.options 0x04
21:10:02:381 APS-DATA.confirm id: 103, status: 0x00 SUCCESS
21:10:02:382 APS-DATA.confirm request id: 103 -> erase from queue
21:10:02:385 aps request id: 103 finished, erase from queue
21:10:02:390 APS-DATA.indication srcAddr: 0x741f, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0xEF00, lqi: 255, rssi: -54
21:10:02:391 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 04196e01000100
21:10:02:392 Tuya debug 5 : Status: 4 Transid: 25 Dp: 366 (0x01,0x6E) Fn: 0 Data 365072220160
21:10:02:393 APS-DATA.request id: 106, addrmode: 0x02, addr: 0x741f, profile: 0x0104, cluster: 0xEF00, ep: 0x01 -> 0x01 queue: 0 len: 5 tx.options 0x04
21:10:02:508 APS-DATA.confirm id: 106, status: 0x00 SUCCESS
21:10:02:509 APS-DATA.confirm request id: 106 -> erase from queue
21:10:02:513 APS-DATA.indication srcAddr: 0x741f, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0xEF00, lqi: 255, rssi: -54
21:10:02:514 APS-DATA.request id: 106 erase from queue
21:10:02:515 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 041a6f04000100
21:10:02:516 Tuya debug 5 : Status: 4 Transid: 26 Dp: 1135 (0x04,0x6F) Fn: 0 Data 365072220160
21:10:02:516 APS-DATA.request id: 108, addrmode: 0x02, addr: 0x741f, profile: 0x0104, cluster: 0xEF00, ep: 0x01 -> 0x01 queue: 0 len: 5 tx.options 0x04
21:10:02:631 APS-DATA.confirm id: 108, status: 0x00 SUCCESS
21:10:02:632 APS-DATA.confirm request id: 108 -> erase from queue
21:10:02:637 APS-DATA.indication srcAddr: 0x741f, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0xEF00, lqi: 255, rssi: -54
21:10:02:638 APS-DATA.request id: 108 erase from queue
21:10:02:639 Tuya : Schedule command
21:10:02:639 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 041b7000001206001408000f0b1e0f0c1e0f111e1416000f
21:10:02:640 Tuya debug 5 : Status: 4 Transid: 27 Dp: 112 (0x00,0x70) Fn: 0 Data 365072220160
21:10:02:640 Tuya : Schedule data error
21:10:02:641 APS-DATA.request id: 111, addrmode: 0x02, addr: 0x741f, profile: 0x0104, cluster: 0xEF00, ep: 0x01 -> 0x01 queue: 0 len: 5 tx.options 0x04
21:10:02:746 APS-DATA.confirm id: 111, status: 0x00 SUCCESS
21:10:02:746 APS-DATA.confirm request id: 111 -> erase from queue
21:10:02:761 APS-DATA.indication srcAddr: 0x741f, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0xEF00, lqi: 255, rssi: -54
21:10:02:762 APS-DATA.request id: 111 erase from queue
21:10:02:762 Tuya : Schedule command
21:10:02:763 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 041c7100001206001408000f0b1e0f0c1e0f111e1416000f
21:10:02:764 Tuya debug 5 : Status: 4 Transid: 28 Dp: 113 (0x00,0x71) Fn: 0 Data 365072220160
21:10:02:764 Tuya : Schedule data error
21:10:02:765 APS-DATA.request id: 113, addrmode: 0x02, addr: 0x741f, profile: 0x0104, cluster: 0xEF00, ep: 0x01 -> 0x01 queue: 0 len: 5 tx.options 0x04
21:10:02:868 APS-DATA.confirm id: 113, status: 0x00 SUCCESS
21:10:02:869 APS-DATA.confirm request id: 113 -> erase from queue
21:10:02:874 APS-DATA.indication srcAddr: 0x741f, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0xEF00, lqi: 255, rssi: -54
21:10:02:875 APS-DATA.request id: 113 erase from queue
21:10:02:876 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 041d720200040000000f
21:10:02:877 Tuya debug 5 : Status: 4 Transid: 29 Dp: 626 (0x02,0x72) Fn: 0 Data 365072220175
21:10:02:877 APS-DATA.request id: 116, addrmode: 0x02, addr: 0x741f, profile: 0x0104, cluster: 0xEF00, ep: 0x01 -> 0x01 queue: 0 len: 5 tx.options 0x04
21:10:02:990 APS-DATA.confirm id: 116, status: 0x00 SUCCESS
21:10:02:991 APS-DATA.confirm request id: 116 -> erase from queue
21:10:02:997 APS-DATA.indication srcAddr: 0x741f, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0xEF00, lqi: 255, rssi: -54
21:10:03:001 APS-DATA.request id: 116 erase from queue
21:10:03:002 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 041e7301000100
21:10:03:003 Tuya debug 5 : Status: 4 Transid: 30 Dp: 371 (0x01,0x73) Fn: 0 Data 365072220160
21:10:03:004 APS-DATA.request id: 118, addrmode: 0x02, addr: 0x741f, profile: 0x0104, cluster: 0xEF00, ep: 0x01 -> 0x01 queue: 0 len: 5 tx.options 0x04
21:10:03:107 APS-DATA.confirm id: 118, status: 0x00 SUCCESS
21:10:03:108 APS-DATA.confirm request id: 118 -> erase from queue
21:10:03:116 APS-DATA.indication srcAddr: 0x741f, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0xEF00, lqi: 255, rssi: -55
21:10:03:117 APS-DATA.request id: 118 erase from queue
21:10:03:118 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 041f7401000100
21:10:03:119 Tuya debug 5 : Status: 4 Transid: 31 Dp: 372 (0x01,0x74) Fn: 0 Data 365072220160
21:10:03:119 APS-DATA.request id: 121, addrmode: 0x02, addr: 0x741f, profile: 0x0104, cluster: 0xEF00, ep: 0x01 -> 0x01 queue: 0 len: 5 tx.options 0x04
21:10:03:227 APS-DATA.confirm id: 121, status: 0x00 SUCCESS
21:10:03:228 APS-DATA.confirm request id: 121 -> erase from queue
21:10:03:251 APS-DATA.indication srcAddr: 0x741f, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0xEF00, lqi: 255, rssi: -54
21:10:03:252 APS-DATA.request id: 121 erase from queue
21:10:03:253 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 04207502000400000004
21:10:03:254 Tuya debug 5 : Status: 4 Transid: 32 Dp: 629 (0x02,0x75) Fn: 0 Data 365072220164
21:10:03:254 APS-DATA.request id: 123, addrmode: 0x02, addr: 0x741f, profile: 0x0104, cluster: 0xEF00, ep: 0x01 -> 0x01 queue: 0 len: 5 tx.options 0x04
21:10:03:348 APS-DATA.confirm id: 123, status: 0x00 SUCCESS
21:10:03:350 APS-DATA.confirm request id: 123 -> erase from queue
21:10:03:426 aps request id: 123 finished, erase from queue
21:10:04:657 APS-DATA.request id: 130, addrmode: 0x03, addr: 0x588e81fffed395cc, profile: 0x0104, cluster: 0x0006, ep: 0x01 -> 0x01 queue: 0 len: 5 tx.options 0x00
21:10:04:670 APS-DATA.confirm id: 130, status: 0x00 SUCCESS
21:10:04:671 APS-DATA.confirm request id: 130 -> erase from queue
21:10:04:705 aps request id: 130 finished, erase from queue
21:10:04:754 APS-DATA.indication srcAddr: 0xfa84, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0006, lqi: 255, rssi:

Another one 6 minutes later:

21:16:55:017 APS-DATA.request id: 242 erase from queue
21:16:55:018 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 04546d0200040000002d
21:16:55:019 Tuya debug 5 : Status: 4 Transid: 84 Dp: 621 (0x02,0x6D) Fn: 0 Data 365072220205
21:16:55:019 APS-DATA.request id: 244, addrmode: 0x02, addr: 0x741f, profile: 0x0104, cluster: 0xEF00, ep: 0x01 -> 0x01 queue: 0 len: 5 tx.options 0x04
21:16:55:126 APS-DATA.confirm id: 244, status: 0x00 SUCCESS
21:16:55:127 APS-DATA.confirm request id: 244 -> erase from queue
21:16:55:142 APS-DATA.indication srcAddr: 0x741f, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0xEF00, lqi: 255, rssi: -54
21:16:55:143 APS-DATA.request id: 244 erase from queue
21:16:55:144 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 04556e01000100
21:16:55:144 Tuya debug 5 : Status: 4 Transid: 85 Dp: 366 (0x01,0x6E) Fn: 0 Data 365072220160
21:16:55:145 APS-DATA.request id: 249, addrmode: 0x02, addr: 0x741f, profile: 0x0104, cluster: 0xEF00, ep: 0x01 -> 0x01 queue: 0 len: 5 tx.options 0x04
21:16:55:157 APS-DATA.request id: 246, addrmode: 0x03, addr: 0x588e81fffed397b2, profile: 0x0104, cluster: 0x0B04, ep: 0x01 -> 0x01 queue: 1 len: 9 tx.options 0x00
21:16:55:171 APS-DATA.confirm id: 246, status: 0x00 SUCCESS
21:16:55:172 APS-DATA.confirm request id: 246 -> erase from queue
21:16:55:185 aps request id: 246 finished, erase from queue
21:16:55:243 APS-DATA.indication srcAddr: 0x477d, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0B04, lqi: 255, rssi: -54
21:16:55:244 ZCL got data for node=0x477D, cl=0x0B04, at=0x0505, status=0x00, type=0x21
21:16:55:245 ZCL got data for node=0x477D, cl=0x0B04, at=0x0508, status=0x00, type=0x21
21:16:55:246 ZCL got data for node=0x477D, cl=0x0B04, at=0x050B, status=0x00, type=0x29
21:16:55:249 APS-DATA.confirm id: 249, status: 0x00 SUCCESS
21:16:55:250 APS-DATA.confirm request id: 249 -> erase from queue
21:16:55:265 aps request id: 249 finished, erase from queue
21:16:55:269 APS-DATA.indication srcAddr: 0x741f, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0xEF00, lqi: 255, rssi: -54
21:16:55:270 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 04566f04000100
21:16:55:271 Tuya debug 5 : Status: 4 Transid: 86 Dp: 1135 (0x04,0x6F) Fn: 0 Data 365072220160
21:16:55:272 APS-DATA.request id: 252, addrmode: 0x02, addr: 0x741f, profile: 0x0104, cluster: 0xEF00, ep: 0x01 -> 0x01 queue: 0 len: 5 tx.options 0x04
21:16:55:369 APS-DATA.confirm id: 252, status: 0x00 SUCCESS
21:16:55:370 APS-DATA.confirm request id: 252 -> erase from queue
21:16:55:383 APS-DATA.indication srcAddr: 0x741f, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0xEF00, lqi: 255, rssi: -54
21:16:55:384 APS-DATA.request id: 252 erase from queue
21:16:55:385 Tuya : Schedule command
21:16:55:386 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 04577000001206001408000f0b1e0f0c1e0f111e1416000f
21:16:55:387 Tuya debug 5 : Status: 4 Transid: 87 Dp: 112 (0x00,0x70) Fn: 0 Data 365072220160
21:16:55:387 Tuya : Schedule data error
21:16:55:388 APS-DATA.request id: 255, addrmode: 0x02, addr: 0x741f, profile: 0x0104, cluster: 0xEF00, ep: 0x01 -> 0x01 queue: 0 len: 5 tx.options 0x04
21:16:55:490 APS-DATA.confirm id: 255, status: 0x00 SUCCESS
21:16:55:491 APS-DATA.confirm request id: 255 -> erase from queue
21:16:55:502 APS-DATA.indication srcAddr: 0x741f, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0xEF00, lqi: 255, rssi: -54
21:16:55:503 APS-DATA.request id: 255 erase from queue
21:16:55:504 Tuya : Schedule command
21:16:55:505 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 04587100001206001408000f0b1e0f0c1e0f111e1416000f
21:16:55:505 Tuya debug 5 : Status: 4 Transid: 88 Dp: 113 (0x00,0x71) Fn: 0 Data 365072220160
21:16:55:506 Tuya : Schedule data error
21:16:55:507 APS-DATA.request id: 1, addrmode: 0x02, addr: 0x741f, profile: 0x0104, cluster: 0xEF00, ep: 0x01 -> 0x01 queue: 0 len: 5 tx.options 0x04
21:16:55:612 APS-DATA.confirm id: 1, status: 0x00 SUCCESS
21:16:55:613 APS-DATA.confirm request id: 1 -> erase from queue
21:16:55:625 APS-DATA.indication srcAddr: 0x741f, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0xEF00, lqi: 255, rssi: -54
21:16:55:626 APS-DATA.request id: 1 erase from queue
21:16:55:627 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0459720200040000000f
21:16:55:627 Tuya debug 5 : Status: 4 Transid: 89 Dp: 626 (0x02,0x72) Fn: 0 Data 365072220175
21:16:55:628 APS-DATA.request id: 4, addrmode: 0x02, addr: 0x741f, profile: 0x0104, cluster: 0xEF00, ep: 0x01 -> 0x01 queue: 0 len: 5 tx.options 0x04
21:16:55:734 APS-DATA.confirm id: 4, status: 0x00 SUCCESS
21:16:55:735 APS-DATA.confirm request id: 4 -> erase from queue
21:16:55:745 aps request id: 4 finished, erase from queue
21:16:55:748 APS-DATA.indication srcAddr: 0x741f, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0xEF00, lqi: 255, rssi: -54
21:16:55:750 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 045a7301000100
21:16:55:751 Tuya debug 5 : Status: 4 Transid: 90 Dp: 371 (0x01,0x73) Fn: 0 Data 365072220160
21:16:55:751 APS-DATA.request id: 6, addrmode: 0x02, addr: 0x741f, profile: 0x0104, cluster: 0xEF00, ep: 0x01 -> 0x01 queue: 0 len: 5 tx.options 0x04
21:16:55:851 APS-DATA.confirm id: 6, status: 0x00 SUCCESS
21:16:55:852 APS-DATA.confirm request id: 6 -> erase from queue
21:16:55:878 APS-DATA.indication srcAddr: 0x741f, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0xEF00, lqi: 255, rssi: -54
21:16:55:879 APS-DATA.request id: 6 erase from queue
21:16:55:880 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 045b7401000100
21:16:55:880 Tuya debug 5 : Status: 4 Transid: 91 Dp: 372 (0x01,0x74) Fn: 0 Data 365072220160
21:16:55:881 APS-DATA.request id: 9, addrmode: 0x02, addr: 0x741f, profile: 0x0104, cluster: 0xEF00, ep: 0x01 -> 0x01 queue: 0 len: 5 tx.options 0x04
21:16:55:977 APS-DATA.confirm id: 9, status: 0x00 SUCCESS
21:16:55:978 APS-DATA.confirm request id: 9 -> erase from queue
21:16:55:986 aps request id: 9 finished, erase from queue
21:16:55:996 APS-DATA.indication srcAddr: 0x741f, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0xEF00, lqi: 255, rssi: -54
21:16:55:997 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 045c7502000400000004
21:16:55:998 Tuya debug 5 : Status: 4 Transid: 92 Dp: 629 (0x02,0x75) Fn: 0 Data 365072220164
21:16:55:999 APS-DATA.request id: 11, addrmode: 0x02, addr: 0x741f, profile: 0x0104, cluster: 0xEF00, ep: 0x01 -> 0x01 queue: 0 len: 5 tx.options 0x04
21:16:56:058 APS-DATA.request id: 12, addrmode: 0x03, addr: 0x588e81fffed395cc, profile: 0x0104, cluster: 0x0B04, ep: 0x01 -> 0x01 queue: 1 len: 9 tx.options 0x00
21:16:56:079 APS-DATA.confirm id: 12, status: 0x00 SUCCESS
21:16:56:080 APS-DATA.confirm request id: 12 -> erase from queue
21:16:56:123 APS-DATA.confirm id: 11, status: 0x00 SUCCESS
21:16:56:124 APS-DATA.confirm request id: 11 -> erase from queue
21:16:56:129 APS-DATA.indication srcAddr: 0xfa84, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0B04, lqi: 255, rssi: -54
21:16:56:130 APS-DATA.request id: 11 erase from queue
21:16:56:131 APS-DATA.request id: 12 erase from queue
21:16:56:131 ZCL got data for node=0xFA84, cl=0x0B04, at=0x0505, status=0x00, type=0x21
21:16:56:132 ZCL got data for node=0xFA84, cl=0x0B04, at=0x0508, status=0x00, type=0x21
21:16:56:133 ZCL got data for node=0xFA84, cl=0x0B04, at=0x050B, status=0x00, type=0x29
21:16:57:157 APS-DATA.request id: 19, addrmode: 0x03, addr: 0xccccccfffeee4c77, profile: 0x0104, cluster: 0x0300, ep: 0x01 -> 0x01 queue: 0 len: 13 tx.options 0x00
21:16:57:172 APS-DATA.confirm id: 19, status: 0x00 SUCCESS
21:16:57:173 APS-DATA.confirm request id: 19 -> erase from queue
21:16:57:186 aps request id: 19 finished, erase from queue
21:16:57:190 APS-DATA.indication srcAddr: 0x028f, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0300, lqi: 255, rssi: -54

There is indeed a line with "Tuya debug 5" and "0x02,0x6B" : 21:10:02:029 Tuya debug 5 : Status: 4 Transid: 22 Dp: 619 (0x02,0x6B) Fn: 0 Data 365072220180

I notice there are also multiple "Schedule data error", for example: 21:10:02:640 Tuya : Schedule data error

I'm not sure what the value "2" represents... The default min temperature value is 5 so I doubt it's that.

If more logs are needed or anything else I'm happy to provide all needed info (it seems log output is circular and I'm not too sure how to capture a longer period of time)

EDIT: here is another (probably more useful) log sample with all dbg_* disabled except dbg_info:

22:00:12:495 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 05876602000400000005
22:00:12:496 Tuya debug 5 : Status: 5 Transid: 135 Dp: 614 (0x02,0x66) Fn: 0 Data 545460846597
22:00:12:569 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 05886702000400000023
22:00:12:570 Tuya debug 5 : Status: 5 Transid: 136 Dp: 615 (0x02,0x67) Fn: 0 Data 35
22:00:12:690 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 058902020004000000e1
22:00:12:691 Tuya debug 5 : Status: 5 Transid: 137 Dp: 514 (0x02,0x02) Fn: 0 Data 225
22:00:12:808 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 058a03020004000000be
22:00:12:809 Tuya debug 5 : Status: 5 Transid: 138 Dp: 515 (0x02,0x03) Fn: 0 Data 545460846782
22:00:12:935 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 058b03020004000000be
22:00:12:936 Tuya debug 5 : Status: 5 Transid: 139 Dp: 515 (0x02,0x03) Fn: 0 Data 190
22:00:13:056 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 058c0404000102
22:00:13:058 Tuya debug 5 : Status: 5 Transid: 140 Dp: 1028 (0x04,0x04) Fn: 0 Data 2
22:00:13:174 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 058d0404000102
22:00:13:175 Tuya debug 5 : Status: 5 Transid: 141 Dp: 1028 (0x04,0x04) Fn: 0 Data 545460846594
22:00:13:297 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 058e0701000100
22:00:13:298 Tuya debug 5 : Status: 5 Transid: 142 Dp: 263 (0x01,0x07) Fn: 0 Data 0
22:00:13:418 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 058f0d05000100
22:00:13:419 Tuya debug 5 : Status: 5 Transid: 143 Dp: 1293 (0x05,0x0D) Fn: 0 Data 0
22:00:13:543 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 05902c02000400000000
22:00:13:544 Tuya debug 5 : Status: 5 Transid: 144 Dp: 556 (0x02,0x2C) Fn: 0 Data 0
22:00:13:663 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 05916800000300050a
22:00:13:664 Tuya debug 5 : Status: 5 Transid: 145 Dp: 104 (0x00,0x68) Fn: 0 Data 545460847882
22:00:13:786 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0592690200040000012c
22:00:13:787 Tuya debug 5 : Status: 5 Transid: 146 Dp: 617 (0x02,0x69) Fn: 0 Data 300
22:00:13:936 Bind response success for 0x680ae2fffe4148ad ep: 0x01 cluster: 0x0000
22:00:13:974 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 05936a04000100
22:00:13:975 Tuya debug 5 : Status: 5 Transid: 147 Dp: 1130 (0x04,0x6A) Fn: 0 Data 545460846592
22:00:14:045 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 05946b02000400000014
22:00:14:046 Tuya debug 5 : Status: 5 Transid: 148 Dp: 619 (0x02,0x6B) Fn: 0 Data 545460846612
22:00:14:165 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 05956c0200040000000f
22:00:14:165 Tuya debug 5 : Status: 5 Transid: 149 Dp: 620 (0x02,0x6C) Fn: 0 Data 545460846607
22:00:14:293 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 05966d0200040000005a
22:00:14:294 Tuya debug 5 : Status: 5 Transid: 150 Dp: 621 (0x02,0x6D) Fn: 0 Data 90
22:00:14:413 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 05976e01000100
22:00:14:414 Tuya debug 5 : Status: 5 Transid: 151 Dp: 366 (0x01,0x6E) Fn: 0 Data 545460846592
22:00:14:532 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 05986f04000100
22:00:14:533 Tuya debug 5 : Status: 5 Transid: 152 Dp: 1135 (0x04,0x6F) Fn: 0 Data 0
22:00:14:655 Tuya : Schedule command
22:00:14:656 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 05997000001206001408000f0b1e0f0c1e0f111e1416000f
22:00:14:656 Tuya debug 5 : Status: 5 Transid: 153 Dp: 112 (0x00,0x70) Fn: 0 Data 0
22:00:14:657 Tuya : Schedule data error
22:00:14:783 Tuya : Schedule command
22:00:14:784 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 059a7100001206001408000f0b1e0f0c1e0f111e1416000f
22:00:14:784 Tuya debug 5 : Status: 5 Transid: 154 Dp: 113 (0x00,0x71) Fn: 0 Data 545460846592
22:00:14:785 Tuya : Schedule data error
22:00:14:897 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 059b720200040000000f
22:00:14:898 Tuya debug 5 : Status: 5 Transid: 155 Dp: 626 (0x02,0x72) Fn: 0 Data 15
22:00:15:024 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 059c7301000100
22:00:15:025 Tuya debug 5 : Status: 5 Transid: 156 Dp: 371 (0x01,0x73) Fn: 0 Data 0
22:00:15:137 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 059d7401000100
22:00:15:138 Tuya debug 5 : Status: 5 Transid: 157 Dp: 372 (0x01,0x74) Fn: 0 Data 545460846592
22:00:15:260 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 059e7502000400000004
22:00:15:261 Tuya debug 5 : Status: 5 Transid: 158 Dp: 629 (0x02,0x75) Fn: 0 Data 545460846596
22:00:15:911 Bind response success for 0x680ae2fffe4148ad ep: 0x01 cluster: 0x0006
22:00:15:912 skip configure report for cluster: 0x0006 attr: 0x0000 of node 0x680AE2FFFE4148AD (seems to be active)
22:00:19:436 Bind response success for 0x588e81fffed395cc ep: 0x01 cluster: 0x0006

22:01:57:387 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 06116602000400000005
22:01:57:388 Tuya debug 5 : Status: 6 Transid: 17 Dp: 614 (0x02,0x66) Fn: 0 Data 5
22:01:57:509 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 06126702000400000023
22:01:57:510 Tuya debug 5 : Status: 6 Transid: 18 Dp: 615 (0x02,0x67) Fn: 0 Data 35
22:01:57:633 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 06130202000400000078
22:01:57:634 Tuya debug 5 : Status: 6 Transid: 19 Dp: 514 (0x02,0x02) Fn: 0 Data 545460846712
22:01:57:756 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 06140404000102
22:01:57:757 Tuya debug 5 : Status: 6 Transid: 20 Dp: 1028 (0x04,0x04) Fn: 0 Data 2
22:01:57:876 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 06150404000102
22:01:57:877 Tuya debug 5 : Status: 6 Transid: 21 Dp: 1028 (0x04,0x04) Fn: 0 Data 2
22:01:57:997 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 06160701000100
22:01:57:998 Tuya debug 5 : Status: 6 Transid: 22 Dp: 263 (0x01,0x07) Fn: 0 Data 545460846592
22:01:58:124 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 06170d05000100
22:01:58:125 Tuya debug 5 : Status: 6 Transid: 23 Dp: 1293 (0x05,0x0D) Fn: 0 Data 0
22:01:58:241 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 06182c02000400000000
22:01:58:242 Tuya debug 5 : Status: 6 Transid: 24 Dp: 556 (0x02,0x2C) Fn: 0 Data 0
22:01:58:363 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 06196800000300050a
22:01:58:364 Tuya debug 5 : Status: 6 Transid: 25 Dp: 104 (0x00,0x68) Fn: 0 Data 545460847882
22:01:58:484 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 061a690200040000012c
22:01:58:485 Tuya debug 5 : Status: 6 Transid: 26 Dp: 617 (0x02,0x69) Fn: 0 Data 300
22:01:58:600 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 061b6a04000100
22:01:58:601 Tuya debug 5 : Status: 6 Transid: 27 Dp: 1130 (0x04,0x6A) Fn: 0 Data 0
22:01:58:724 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 061c6b02000400000014
22:01:58:725 Tuya debug 5 : Status: 6 Transid: 28 Dp: 619 (0x02,0x6B) Fn: 0 Data 20
22:01:58:845 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 061d6c0200040000000f
22:01:58:846 Tuya debug 5 : Status: 6 Transid: 29 Dp: 620 (0x02,0x6C) Fn: 0 Data 545460846607
22:01:58:982 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 061e6d0200040000000f
22:01:58:983 Tuya debug 5 : Status: 6 Transid: 30 Dp: 621 (0x02,0x6D) Fn: 0 Data 15
22:01:59:094 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 061f6e01000100
22:01:59:095 Tuya debug 5 : Status: 6 Transid: 31 Dp: 366 (0x01,0x6E) Fn: 0 Data 0
22:01:59:216 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 06206f04000100
22:01:59:217 Tuya debug 5 : Status: 6 Transid: 32 Dp: 1135 (0x04,0x6F) Fn: 0 Data 0
22:01:59:345 Tuya : Schedule command
22:01:59:346 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 06217000001206001408000f0b1e0f0c1e0f111e1416000f
22:01:59:346 Tuya debug 5 : Status: 6 Transid: 33 Dp: 112 (0x00,0x70) Fn: 0 Data 0
22:01:59:346 Tuya : Schedule data error
22:01:59:466 Tuya : Schedule command
22:01:59:467 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 06227100001206001408000f0b1e0f0c1e0f111e1416000f
22:01:59:467 Tuya debug 5 : Status: 6 Transid: 34 Dp: 113 (0x00,0x71) Fn: 0 Data 545460846592
22:01:59:468 Tuya : Schedule data error
22:01:59:586 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0623720200040000000f
22:01:59:587 Tuya debug 5 : Status: 6 Transid: 35 Dp: 626 (0x02,0x72) Fn: 0 Data 15
22:01:59:702 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 06247301000100
22:01:59:702 Tuya debug 5 : Status: 6 Transid: 36 Dp: 371 (0x01,0x73) Fn: 0 Data 0
22:01:59:824 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 06257401000100
22:01:59:825 Tuya debug 5 : Status: 6 Transid: 37 Dp: 372 (0x01,0x74) Fn: 0 Data 545460846592
22:01:59:945 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 06267502000400000004
22:01:59:946 Tuya debug 5 : Status: 6 Transid: 38 Dp: 629 (0x02,0x75) Fn: 0 Data 4
22:02:07:489 Bind response success for 0x680ae2fffe771ec7 ep: 0x01 cluster: 0x0000
22:02:11:367 Device TTL 1865 s flags: 0x7

SebLz commented 2 years ago

Hi @SebLz When did you upgrade to this version? Directly after upgrading, I have experienced the same but from 15-30 minutes to few hours later all 6 TRVs have fixed itself and sending the correct temperature values. I am using the latest stable and latest firmware

Hello @TheNON75 To be honest I hadn't used my TRVs since last winter, so it's only now that I want to use them again that I notice the issue. Mine haven't fixed themselves after a few hours / days. When you say you're using latest firware, do you mean latest firware for the TRV device ? I've come across these firmwares https://github.com/Koenkk/zigbee-OTA/tree/master/images/Tuya but I'm not sure if those are compatible with my device and if flashing them with deconz would work.

TheNON75 commented 2 years ago

When you say you're using latest firware, do you mean latest firware for the TRV device ?

No, I meant about the conbee ii (I have a raspbee ii with the latest firmware).

Smanar commented 2 years ago

It's from a recent device. Yours use the command 0x02 0x6B for temperature comfort, but another one use the same for the local temperature (tuya multi sensor)

Are you able to compile the code to test code modifcation ?

You have the procedure here https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/Compiling-the-REST-plugin-for-device-specific-testing So for you, after having installed deconz :

sudo apt install deconz-dev
git clone --branch tuya_fix_2 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

SebLz commented 2 years ago

After quite some struggles, I've managed to build your version in a new container on my odroidc4 and imported my deconz config (config.ini, zll.db and zlcdb.txt) in it. Then I did some rest calls to capture the values (the test container is not connected to homeassistant). I have not noticed wrong temperatures anymore, so it seems your fix works, thanks @Smanar ! Here is the log with the new version compiled from your branch:

23:07:28:094 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0ac802020004000000a0,
23:07:28:095 Tuya debug 5 : Status: 10 Transid: 200 Dp: 514 (0x02,0x02) Fn: 0 Data 160,
23:07:28:166 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0ac902020004000000a5,
23:07:28:167 Tuya debug 5 : Status: 10 Transid: 201 Dp: 514 (0x02,0x02) Fn: 0 Data 165,
23:07:28:286 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0aca03020004000000cd,
23:07:28:287 Tuya debug 5 : Status: 10 Transid: 202 Dp: 515 (0x02,0x03) Fn: 0 Data 205,
23:07:28:405 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0acb03020004000000cd,
23:07:28:406 Tuya debug 5 : Status: 10 Transid: 203 Dp: 515 (0x02,0x03) Fn: 0 Data 205,
23:07:28:530 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0acc02020004000000aa,
23:07:28:531 Tuya debug 5 : Status: 10 Transid: 204 Dp: 514 (0x02,0x02) Fn: 0 Data 170,
23:07:28:650 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0acd03020004000000cd,
23:07:28:651 Tuya debug 5 : Status: 10 Transid: 205 Dp: 515 (0x02,0x03) Fn: 0 Data 205,
23:07:28:770 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0ace03020004000000cd,
23:07:28:771 Tuya debug 5 : Status: 10 Transid: 206 Dp: 515 (0x02,0x03) Fn: 0 Data 205,
23:07:28:890 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0acf02020004000000af,
23:07:28:891 Tuya debug 5 : Status: 10 Transid: 207 Dp: 514 (0x02,0x02) Fn: 0 Data 175,
23:07:29:012 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0ad003020004000000cd,
23:07:29:013 Tuya debug 5 : Status: 10 Transid: 208 Dp: 515 (0x02,0x03) Fn: 0 Data 205,
23:07:29:135 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0ad103020004000000cd,
23:07:29:136 Tuya debug 5 : Status: 10 Transid: 209 Dp: 515 (0x02,0x03) Fn: 0 Data 205,
23:07:29:253 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0ad202020004000000b4,
23:07:29:254 Tuya debug 5 : Status: 10 Transid: 210 Dp: 514 (0x02,0x02) Fn: 0 Data 180,
23:07:29:376 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0ad303020004000000cd,
23:07:29:377 Tuya debug 5 : Status: 10 Transid: 211 Dp: 515 (0x02,0x03) Fn: 0 Data 205,
23:07:29:497 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0ad403020004000000cd,
23:07:29:498 Tuya debug 5 : Status: 10 Transid: 212 Dp: 515 (0x02,0x03) Fn: 0 Data 205,
23:07:29:620 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0ad502020004000000b9,
23:07:29:621 Tuya debug 5 : Status: 10 Transid: 213 Dp: 514 (0x02,0x02) Fn: 0 Data 185,
23:07:29:739 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0ad603020004000000cd,
23:07:29:740 Tuya debug 5 : Status: 10 Transid: 214 Dp: 515 (0x02,0x03) Fn: 0 Data 205,
23:07:29:862 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0ad703020004000000cd,
23:07:29:863 Tuya debug 5 : Status: 10 Transid: 215 Dp: 515 (0x02,0x03) Fn: 0 Data 205,
23:07:29:982 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0ad802020004000000be,
23:07:29:983 Tuya debug 5 : Status: 10 Transid: 216 Dp: 514 (0x02,0x02) Fn: 0 Data 190,
23:07:30:105 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0ad903020004000000cd,
23:07:30:106 Tuya debug 5 : Status: 10 Transid: 217 Dp: 515 (0x02,0x03) Fn: 0 Data 205,
23:07:30:227 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0ada03020004000000cd,
23:07:30:228 Tuya debug 5 : Status: 10 Transid: 218 Dp: 515 (0x02,0x03) Fn: 0 Data 205,
23:07:30:350 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0adb02020004000000c3,
23:07:30:351 Tuya debug 5 : Status: 10 Transid: 219 Dp: 514 (0x02,0x02) Fn: 0 Data 195,
23:07:30:472 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0adc03020004000000cd,
23:07:30:473 Tuya debug 5 : Status: 10 Transid: 220 Dp: 515 (0x02,0x03) Fn: 0 Data 205,
23:07:30:592 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0add03020004000000cd,
23:07:30:593 Tuya debug 5 : Status: 10 Transid: 221 Dp: 515 (0x02,0x03) Fn: 0 Data 205,
23:07:30:715 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0ade0404000102,
23:07:30:716 Tuya debug 5 : Status: 10 Transid: 222 Dp: 1028 (0x04,0x04) Fn: 0 Data 2,
23:07:30:835 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0adf02020004000000c8,
23:07:30:836 Tuya debug 5 : Status: 10 Transid: 223 Dp: 514 (0x02,0x02) Fn: 0 Data 200,
23:07:30:960 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0ae003020004000000cd,
23:07:30:961 Tuya debug 5 : Status: 10 Transid: 224 Dp: 515 (0x02,0x03) Fn: 0 Data 205,
23:07:31:082 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0ae103020004000000cd,
23:07:31:083 Tuya debug 5 : Status: 10 Transid: 225 Dp: 515 (0x02,0x03) Fn: 0 Data 205,
23:07:31:206 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0ae202020004000000cd,
23:07:31:206 Tuya debug 5 : Status: 10 Transid: 226 Dp: 514 (0x02,0x02) Fn: 0 Data 205,
23:07:31:322 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0ae303020004000000cd,
23:07:31:323 Tuya debug 5 : Status: 10 Transid: 227 Dp: 515 (0x02,0x03) Fn: 0 Data 205,
23:07:31:444 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0ae403020004000000cd,
23:07:31:444 Tuya debug 5 : Status: 10 Transid: 228 Dp: 515 (0x02,0x03) Fn: 0 Data 205,
23:07:31:563 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0ae502020004000000d2,
23:07:31:564 Tuya debug 5 : Status: 10 Transid: 229 Dp: 514 (0x02,0x02) Fn: 0 Data 210,
23:07:31:687 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0ae603020004000000cd,
23:07:31:688 Tuya debug 5 : Status: 10 Transid: 230 Dp: 515 (0x02,0x03) Fn: 0 Data 205,
23:07:31:807 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0ae703020004000000cd,
23:07:31:808 Tuya debug 5 : Status: 10 Transid: 231 Dp: 515 (0x02,0x03) Fn: 0 Data 205,
23:07:31:927 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0ae80404000102,
23:07:31:928 Tuya debug 5 : Status: 10 Transid: 232 Dp: 1028 (0x04,0x04) Fn: 0 Data 2,
23:07:32:049 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0ae902020004000000d7,
23:07:32:049 Tuya debug 5 : Status: 10 Transid: 233 Dp: 514 (0x02,0x02) Fn: 0 Data 215,
23:07:32:172 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0aea02020004000000dc,
23:07:32:172 Tuya debug 5 : Status: 10 Transid: 234 Dp: 514 (0x02,0x02) Fn: 0 Data 220,
23:07:32:295 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0aeb03020004000000cd,
23:07:32:295 Tuya debug 5 : Status: 10 Transid: 235 Dp: 515 (0x02,0x03) Fn: 0 Data 205,
23:07:32:411 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0aec03020004000000cd,
23:07:32:411 Tuya debug 5 : Status: 10 Transid: 236 Dp: 515 (0x02,0x03) Fn: 0 Data 205,
23:07:32:535 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0aed02020004000000e1,
23:07:32:535 Tuya debug 5 : Status: 10 Transid: 237 Dp: 514 (0x02,0x02) Fn: 0 Data 225,
23:07:32:651 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0aee03020004000000cd,
23:07:32:651 Tuya debug 5 : Status: 10 Transid: 238 Dp: 515 (0x02,0x03) Fn: 0 Data 205,
23:07:32:772 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0aef03020004000000cd,
23:07:32:772 Tuya debug 5 : Status: 10 Transid: 239 Dp: 515 (0x02,0x03) Fn: 0 Data 205,
23:07:32:892 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0af002020004000000e6,
23:07:32:892 Tuya debug 5 : Status: 10 Transid: 240 Dp: 514 (0x02,0x02) Fn: 0 Data 230,
23:07:33:007 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0af103020004000000cd,
23:07:33:007 Tuya debug 5 : Status: 10 Transid: 241 Dp: 515 (0x02,0x03) Fn: 0 Data 205,
23:07:33:131 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0af203020004000000cd,
23:07:33:131 Tuya debug 5 : Status: 10 Transid: 242 Dp: 515 (0x02,0x03) Fn: 0 Data 205,
23:07:33:247 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0af302020004000000eb,
23:07:33:248 Tuya debug 5 : Status: 10 Transid: 243 Dp: 514 (0x02,0x02) Fn: 0 Data 235,
23:07:33:375 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0af403020004000000cd,
23:07:33:376 Tuya debug 5 : Status: 10 Transid: 244 Dp: 515 (0x02,0x03) Fn: 0 Data 205,
23:07:33:496 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0af503020004000000cd,
23:07:33:497 Tuya debug 5 : Status: 10 Transid: 245 Dp: 515 (0x02,0x03) Fn: 0 Data 205,
23:07:33:608 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0af60404000102,
23:07:33:608 Tuya debug 5 : Status: 10 Transid: 246 Dp: 1028 (0x04,0x04) Fn: 0 Data 2,
23:07:33:730 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0af70404000102,
23:07:33:731 Tuya debug 5 : Status: 10 Transid: 247 Dp: 1028 (0x04,0x04) Fn: 0 Data 2,
23:07:42:364 Device TTL 1672 s flags: 0x7,
23:07:45:574 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0af96602000400000005,
23:07:45:575 Tuya debug 5 : Status: 10 Transid: 249 Dp: 614 (0x02,0x66) Fn: 0 Data 5,
23:07:45:643 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0afa6702000400000023,
23:07:45:644 Tuya debug 5 : Status: 10 Transid: 250 Dp: 615 (0x02,0x67) Fn: 0 Data 35,
23:07:45:763 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0afb02020004000000eb,
23:07:45:764 Tuya debug 5 : Status: 10 Transid: 251 Dp: 514 (0x02,0x02) Fn: 0 Data 235,
23:07:45:887 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0afc0404000102,
23:07:45:888 Tuya debug 5 : Status: 10 Transid: 252 Dp: 1028 (0x04,0x04) Fn: 0 Data 2,
23:07:46:014 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0afd0404000102,
23:07:46:015 Tuya debug 5 : Status: 10 Transid: 253 Dp: 1028 (0x04,0x04) Fn: 0 Data 2,
23:07:46:133 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0afe0701000100,
23:07:46:134 Tuya debug 5 : Status: 10 Transid: 254 Dp: 263 (0x01,0x07) Fn: 0 Data 0,
23:07:46:257 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0aff0d05000100,
23:07:46:258 Tuya debug 5 : Status: 10 Transid: 255 Dp: 1293 (0x05,0x0D) Fn: 0 Data 0,
23:07:46:375 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0b002c02000400000000,
23:07:46:376 Tuya debug 5 : Status: 11 Transid: 0 Dp: 556 (0x02,0x2C) Fn: 0 Data 0,
23:07:46:493 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0b016800000300050a,
23:07:46:494 Tuya debug 5 : Status: 11 Transid: 1 Dp: 104 (0x00,0x68) Fn: 0 Data 1290,
23:07:46:617 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0b02690200040000012c,
23:07:46:618 Tuya debug 5 : Status: 11 Transid: 2 Dp: 617 (0x02,0x69) Fn: 0 Data 300,
23:07:46:745 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0b036a04000100,
23:07:46:746 Tuya debug 5 : Status: 11 Transid: 3 Dp: 1130 (0x04,0x6A) Fn: 0 Data 0,
23:07:46:860 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0b046b02000400000014,
23:07:46:861 Tuya debug 5 : Status: 11 Transid: 4 Dp: 619 (0x02,0x6B) Fn: 0 Data 20,
23:07:46:982 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0b056c0200040000000f,
23:07:46:983 Tuya debug 5 : Status: 11 Transid: 5 Dp: 620 (0x02,0x6C) Fn: 0 Data 15,
23:07:47:105 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0b066d02000400000055,
23:07:47:106 Tuya debug 5 : Status: 11 Transid: 6 Dp: 621 (0x02,0x6D) Fn: 0 Data 85,
23:07:47:224 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0b076e01000100,
23:07:47:225 Tuya debug 5 : Status: 11 Transid: 7 Dp: 366 (0x01,0x6E) Fn: 0 Data 0,
23:07:47:347 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0b086f04000100,
23:07:47:348 Tuya debug 5 : Status: 11 Transid: 8 Dp: 1135 (0x04,0x6F) Fn: 0 Data 0,
23:07:47:474 Tuya : Schedule command,
23:07:47:475 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0b097000001206001408000f0b1e0f0c1e0f111e1496000f,
23:07:47:475 Tuya debug 5 : Status: 11 Transid: 9 Dp: 112 (0x00,0x70) Fn: 0 Data 0,
23:07:47:591 Tuya : Schedule command,
23:07:47:592 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0b0a7100001206001408000f0b1e0f0c1e0f111e1416000f,
23:07:47:592 Tuya debug 5 : Status: 11 Transid: 10 Dp: 113 (0x00,0x71) Fn: 0 Data 0,
23:07:47:715 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0b0b720200040000000f,
23:07:47:716 Tuya debug 5 : Status: 11 Transid: 11 Dp: 626 (0x02,0x72) Fn: 0 Data 15,
23:07:47:834 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0b0c7301000100,
23:07:47:835 Tuya debug 5 : Status: 11 Transid: 12 Dp: 371 (0x01,0x73) Fn: 0 Data 0,
23:07:47:962 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0b0d7401000100,
23:07:47:963 Tuya debug 5 : Status: 11 Transid: 13 Dp: 372 (0x01,0x74) Fn: 0 Data 0,
23:07:48:084 Tuya debug 4 : Address 0x5C0272FFFE8EF7E9 Payload 0b0e7502000400000004,
23:07:48:085 Tuya debug 5 : Status: 11 Transid: 14 Dp: 629 (0x02,0x75) Fn: 0 Data 4,
23:07:48:360 GW firmware version is up to date: 0x26660700,
23:07:52:690 Tuya debug 1 : Time sync request,
23:07:52:692 Send Tuya command 0x24, data: 029e6171d6a86171f2c8,
23:07:54:703 ZCL attribute report 0x842E14FFFE139AEF for cluster: 0x0702, ep: 0x01, frame control: 0x08, mfcode: 0x0000 ,

In case it would help someone, this is what I did to build the docker on arm64:

1) Run these commands

git clone https://github.com/franciscogouveia/docker-deconz-rest-plugin-test.git
cd docker-deconz-rest-plugin-test
docker pull marthoc/deconz

2) Modify the franciscogouveia's Dockerfile like this (I had to change arch to arm64, use debian 9 instead of 10 (otherwise it wouldn't find deconz packets) and add qtdeclarative5-dev :

ARG PLUGIN_REPOSITORY=https://github.com/dresden-elektronik/deconz-rest-plugin.git
ARG PLUGIN_GIT_COMMIT=master

FROM debian:9-slim as compile-plugin

ENV DEBIAN_FRONTEND="noninteractive"
ENV TERM="xterm"

RUN apt-get update && apt-get install -y git qt5-default libqt5websockets5-dev libqt5serialport5-dev qtdeclarative5-dev sqlite3 libcap2-bin lsof curl libsqlite3-dev libssl-dev g++ make gnupg2

RUN curl -L http://phoscon.de/apt/deconz.pub.key | apt-key add -
RUN sh -c "echo 'deb [arch=arm64] http://phoscon.de/apt/deconz \
            stretch-beta main' > \
            /etc/apt/sources.list.d/deconz.list"
RUN apt-get update && apt-get install -y deconz deconz-dev

ARG PLUGIN_REPOSITORY
ARG PLUGIN_GIT_COMMIT

# Get code from repository and compile
RUN git clone --branch $PLUGIN_GIT_COMMIT $PLUGIN_REPOSITORY && cd deconz-rest-plugin && qmake && make -j2

FROM marthoc/deconz:latest AS final-image

COPY --from=compile-plugin /libde_rest_plugin.so /usr/share/deCONZ/plugins/libde_rest_plugin.so

3) Build the image:

docker build -t deconz-test-device --build-arg PLUGIN_REPOSITORY=https://github.com/Smanar/deconz-rest-plugin.git --build-arg PLUGIN_GIT_COMMIT=tuya_fix_2 .

4) Run docker image (notice the cggroup parameters to avoid permission errors)

docker run -d \
    --name=deconz \
    -p 8765:8765 \
    -p 4443:4443 \
    -p 5999:5999 \
    --restart=always \
    --device=/dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_**** \
    --device-cgroup-rule='c 166:* rmw' \
    --device-cgroup-rule='c 188:* rmw' \
    -e DECONZ_WEB_PORT=8765 \
    -e DECONZ_WS_PORT=4443 \
    -e DECONZ_VNC_MODE=1 \
    -e DECONZ_VNC_PORT=5999 \
    deconz-test-device

Smanar commented 2 years ago

Nice thx, was a little uncertain because I have modified too the schedule and thoses modification can crash deconz if I m wrong.

Making the PR.

fi-sch commented 2 years ago

I am experiencing the same issue. Unfortunately, I will need to wait for next stable to test the fix, since I'm usiany deCONZ as Home Assistant add-on.

SebLz commented 2 years ago

@Smanar : since I'm running on this branch, the bug seems to have reappeared (or maybe it has never been completely fixed... in the tests I made before I could only use the REST API, now it's running 24/7 and connected to HA and I notice that after a while the 2 degrees appears again).

Smanar commented 2 years ago

The branch only update the "mode", if you speak about this PR https://github.com/dresden-elektronik/deconz-rest-plugin/pull/5471

The PR was validated 5 days ago, so can you try with the last code from official github or wait for the version v2.13.3

Edit: I m stupid, it was normal, the branc on your previous link was created before the PR from this issue was validated, so it's n't inside. I have updated the branch for the "auto" issue, you can update and recompile.

SebLz commented 2 years ago

Tested it for 2 days, no more 2 degrees issue, thanks 👍

dresden-elektronik / deconz-rest-plugin