TS0201_TZ3210_ncw88jfq

[kszaboa]

Hi pvxx,

any chance for a FW for this tuya zigbee thermometer?
It can be connected to ZHA but does not update values unless you connect it first to a tuya hub. Then it updates every 5 min. Same procedure on every battery change :(

FW in SmartLife 2.0.3, in ZHA 0x00000083

[pvvx]

I ordered, I'll see when it's delivered.

[juha63]

I found some informations here: https://www.elektroda.com/rtvforum/topic4042463.html

[pvvx]

I found some informations here: https://www.elektroda.com/rtvforum/topic4042463.html

This is about the WiFi version.

[pvvx]

https://pvvx.github.io/LKTMZL02/

The AHT20 sensor is terrible:

Comparison with STHV3 (LYWSD03MMC B1.4). Both are in the same cardboard box to eliminate convection...

[kszaboa]

mine is not shown as LKTMZL02 in HA but it written on the board

[pvvx]

LKTMZL02-z is a ZigbeeTLc firmware.
1286-0202-10993607-TH03Zz_v0123.zigbee - firmware for transferring Tuya to ZigbeeTlc

[kszaboa]

mine is not so bad, TS0201_TZ3000_fllyghyj (orange) vs TS0201_TZ3210_ncw88jfq (blue)
the new one shows even higher humidity levels, but the difference is only 1-1,5%

[pvvx]

TS0201_TZ3000 usually has a CHT8305 sensor. Humidity readings are usually 10% too low.
In the CHT8305, when the battery voltage decreases below 2.5 V, there is a strong drop in the readings. Instead of +25C, it can give -20C.

[stonie08]

What's the status on this sensor? Should it work with ZigbeeTLc? I have this exact sensor with the same firmware version 0x00000083. The sensor is set to Zigbee by default. Which firmware version are we supposed to flash in which order?

I just barely recovered from a bricked sensor and don't know where I might have gone wrong. I get a bit confused by the documentation and the sheer number of files there are. So outline what I did and maybe to leave some pointers for others who might stumble upon this post:
The page for the sensor links at the bottom to the pvvx/ATC_MiThermometer repo that seems to be for the BLE variant of the sensor and also holds the LKTMZL02_v50. This seems to be the wrong one in my case?

The ZigbeeTLc repo has the bin folder that holds the 1141-021f-01243001-LKTMZL02Z.zigbee and the 1141-d3a3-01993001-LKTMZL02z_v0124.zigbee but also the LKTMZL02Z_v0124.bin. The two former are explained a bit in the readme but the last one isn't. What is that one for?

Based on the readme in that bin folder I went with the 1141-d3a3-01993001-LKTMZL02z_v0124.zigbee which seems to be for that initial flash?

Getting ZHA to do it was another challenge because there were a number of ways to do this in the issues. In the end based on the documentation I added the following to my configuration.yaml, created a /homeassistant/zigbee_ota folder and put the 1141-d3a3-01993001-LKTMZL02z_v0124.zigbee file in the folder:

zha:
  zigpy_config:
    ota:
      extra_providers:
        - type: advanced  # !!! Please read the message below before enabling OTA updates from raw OTA files !!!
          warning: "I understand I can *destroy* my devices by enabling OTA updates from files. Some OTA updates can be mistakenly applied to the wrong device, breaking it. I am consciously using this at my own risk."
          path: ./zigbee_ota

After doing some more trickery to get ZHA to realize there's an update available I started the update. It ran to 100% but then stopped and the sensor wouldn't respond anymore. I waited a bit longer, but the display wasn't updating anymore, so I removed the battery but the display stayed off.
I then tried to get to flash any firmware with the USBCOMFlashTx tool and luckily the "Original FullFlash.bin" restored my device. It should be noted that if one's USB2serial device doesn't have an RTS pin connecting the three others is enough.

[pvvx]

also the LKTMZL02Z_v0124.bin. The two former are explained a bit in the readme but the last one isn't. What is that one for?

For flashing with a programmer or for creating a *.zigbee OTA file by adding a header. With *.bin or *.zigbee it is possible to make BLE OTA in TelinkMiFlasher.html

[pvvx]

I waited a bit longer, but the display wasn't updating anymore, so I removed the battery but the display stayed off.

After a while, you need to put the battery back in.
(And it is unknown - perhaps ZHA gave the command to turn off the device after the firmware was completed. And since there may be matches with the configuration written in the Flash, the device turned off, showing a blank screen.)
It takes time for the internal capacitor in this device to discharge.
The device software is using too little battery power in "off" mode. To reset the settings, remove the battery, wait, and then insert the battery.
It also has a reset button... The old settings written by the original version in Flash are not suitable.
For these reasons, after reflashing the device cannot be restored to the old settings in the ZigBee network.
A new registration is required.
If a Zigbee OTA update adds a new feature or you update the firmware to a different type, you always need to remove the device from the Zigbee list and register it again. Otherwise, only incorrect operation of the device and the program servicing Zigbee is possible.

These are general rules for all Zigbee devices.
And this is not a school for learning how to use Zigbee devices.

[pvvx]

Where is everyone rushing to?

The files for LKTMZL02Z_v0124 are signed - v0.1.2.4 beta2.
This means that this version has not yet been tested for all options and may freeze, etc. You should not use beta versions without the ability to restore via a programmer.

Testing all new versions for all functions requires hundreds of hours of work. It takes me a long time to do it alone.

The beta version may change after some time. But you won't be able to do Zigbee OTA, since the number is the same.
You'll need to do a forced update via Zigbee OTA. And that's not available in ZHA.
You will have to create a new header for the *.zigbee file, replacing the version number with a higher one.

[stonie08]

For flashing with a programmer or for creating a *.zigbee OTA file by adding a header. With *.bin or *.zigbee it is possible to make BLE OTA in TelinkMiFlasher.html

Okay I see. Now I flashed this one with a programmer and it indeed worked. Nice! Thank you

After a while, you need to put the battery back in.

Poorly phrased on my part. Of course I put the battery back in, the display on the device stayed off. It also didn't react to the reset button. Pressing/holding the reset button also didn't cause any reaction of the LED. So it definitely seemed like it was bricked.

You should not use beta versions without the ability to restore via a programmer.

Hardly a way to avoid because the latest release is 1.2.2 and doesn't yet have a firmware for this sensor. I wanted to test how well it works with the custom firmware before buying more of them and because the original fw one has some issues with the humidity in ZHA.

But you won't be able to do Zigbee OTA, since the number is the same.

I guess I can just update with a programmer once again.

[pvvx]

Hardly a way to avoid because the latest release is 1.2.2

Before LKTMZL02Z_V0124 there was a tested version of ZL02_V0123.
The current LKTMZL02Z_V0124 (beta2) has already been tested for the main errors in LKTMZL02.

https://github.com/pvvx/ZigbeeTLc/blob/master/bin/index0124.json

And only now LKTMZL02Z_v0124.bin is added to enable flashing in TelinkMiFlasher.html with BLE OTA.