Is this the right place to report this: COPY AND PASTE THIS ROW TO THE DEVELOPER: fingerprint model:“3320-L”, manufacturer:“CentraLite”, profileId:“0104”, endpointId:“01”, inClusters:“0000,0001,0003,0020,0402,0500,0B05”, outClusters:“0019”
Let me know if you get any breakthroughs I can add it to the driver on HE forum
Erratic. I can read an set Setpoint, mode and few others features. I want add presence “a la Markus”, but something is wrong. Some messages have still unknonkn meaning. Tomorrow I’ll share my discoveries.
Do you know how to set manually min and max temperatures? I scrambled them and now the max temperature is 22!
Its in the instructions do you gave them?
May be it’s me, but I cannot understand how to. in the sheet that kind of options are signed by Symbol A1, A2,… I cannot see that symbol in the UI (should I?). when I enter set mode there are two numbers (30 and 00) rapidly flipping each other, but I cannot change them… 🤷
The setting on the device is shown on the top right, its only the number is shows
Press to wake
Long press
Press + until SET is shown
Short press
Then short press to cycle thought settings
Then + or - to adjust
The short press
I tried exactly that sequence, as stated in the sheet.
What is wrong ? 
I made a video I cannot upload…
EDIT I inserted the video in github
I made a code patch work
In the header of code there are the known errors and unknown received messages
The error is due to a temptative to integrate presence code by @markus.It is not working and I coud not understand why.
I could not go any further in these two days… after all I’m not a groovy coder :-), but I’ll go on
hubitat-zigbee-trv-moes/zigbee_trs.groovy at main · brunialti/hubitat-zigbee-trv-moes (github.com)
Looking at video it timed out, once set is lit, short press the home button
Have you confirmed battery working?
Your code looks a lot cleaner than mine!
I cannot trap the battery message.
I must check if it correctly bind the battery cluster. But I have not much of information about how the device report (I do’nt even know if the device support battery report).
I had not time nor sniffer by now.
I’ll go on anyway…
What does binding do?
You need to declare/subscribe all clusters your drive is interested to. If the device is enabled to them, will send messages of those clusters to all the subscriptors.
Similar mechanism for cluster attributes
this might be battery, id noted it down a few days ago to look into but it has changed now
// 6702 - [68, 13, 103, 2, 0, 4, 0, 0, 0, 35] ?3.5 volt?
//6702 - [44, 103, 103, 2, 0, 4, 0, 0, 0, 30]
I’m confused.
If I’m not wrong in the standard ZCL the power cluster should be 0001.
The AttribId should be 0020 (volts) e 0021 (%).
Your numbers are decimal or hex?
their decimal out of the EF00 cluster , but its a willed guess
Tuya doesn’t use any standard
OK. That is my problem. I have not a map for the eF00 commands. 
That data could be volts.
I need to invest more time than I did to get out of this driver 
Thank you Mark
Team work.
The less battery reporting the only issue i have is temperature reporting frequency is intermittent and how to call a refresh of temperature
This in python is what I used initially
I might be wrong on battery, I swaped the batteries for a used set but still came back at 30, don’t know how used they were but ill keep an eye
@markus with your tuya work have you managed to be able to send a refresh command to any devices? If so could you post some snippets, the driver is doing 95% of what I need but it doesn’t report temperature very often