Zigbee OTA to BLE firmware

[wta12]

How can I flash Zigbee device (ZY-ZTH02Pro/Tuya ZigBee LKTMZL02) with BLE firmware ? I have ZHA installed on HA

[pvvx]

https://github.com/pvvx/ATC_MiThermometer/tree/master/zigbee_ota#readme

[pvvx]

a. I got lktml02 flashed to BLE but both have same MAC address (not sure how MAC assigned but web flashtek doesn't have set MAC address option. It makes BTHOME capturing messages from both as one device. Is there anyway to modify MAC address of lktml02 with custom firmware ?

TelinkMiFlasher:

firmware is on official zigpy-ota repo

https://github.com/pvvx/ZigbeeTLc/tree/master/bin -> index_v0129.json

---

Zigbee firmware is identified by its "Zigbee Image Type" number.
BLE firmware is identified by its "HW ID" number.

A general list of all supported models can be found here: https://github.com/pvvx/pvvx.github.io/blob/master/README.md

[wta12]

This is what I am get with TelinkMiFlasher - the SetMAC is hidden with LKTMZL02. I Mac Settings are available with Xiaomi ones.

[wta12]

firmware is on official zigpy-ota repo

https://github.com/pvvx/ZigbeeTLc/tree/master/bin -> index_v0129.json

Log Z2M when asking for OTA updating - the override index was loaded correctly but it doesn't show option for zigbee - which exactly input I need to use ? There are 17 models there and no "manufacturerCode":4098,"imageType":515 available
[2025-10-03 01:32:02] debug: zhc:ota: [0xa4c138e50636e53b | TS0201] Got request '{"fieldControl":0,"manufacturerCode":4098,"imageType":515,"fileVersion":1493250049}' [2025-10-03 01:32:02] debug: zhc:ota: [0xa4c138e50636e53b | TS0201] Checking latest image availability, current: {"fieldControl":0,"manufacturerCode":4098,"imageType":515,"fileVersion":1493250049} [2025-10-03 01:32:02] debug: zhc:ota: [0xa4c138e50636e53b | TS0201] Getting image metadata... [2025-10-03 01:32:02] debug: zhc:ota: Downloaded main index [2025-10-03 01:32:02] debug: zhc:ota: Loading override index '/config/repos/ZigbeeTLc/bin/index_v0129_dev.json' [2025-10-03 01:32:02] debug: zhc:ota: [0xa4c138e50636e53b | TS0201] No latest image currently available, current: {"fieldControl":0,"manufacturerCode":4098,"imageType":515,"fileVersion":1493250049}' [2025-10-03 01:32:02] debug: zhc:ota: [0xa4c138e50636e53b | TS0201] Upgrade available: NO [2025-10-03 01:32:02] info: z2m: No update available for '0xa4c138e50636e53b'

[pvvx]

"manufacterCode":4098," -> 4098: 'Tuya'

"manufacturerCode":4098,"imageType":515,"fileVersion":1493250049 -> HEX: 1002-0203-59013001

Manufacturer Code	Image Type	File Version	Stack Version
1002	0203	5901	3001
0x1002 - Tuya	0x02 - TLSR825x, 0x03 - ?	App release 0.1, App build 59	Zigbee v3.0, Release 0.1

"Image Type" 0x0203 is the default for examples from Telink's Zigbee SDK - The manufacturer was too lazy to change the number.

To flash the firmware via ZigBee OTA, you need to use a header converter for the *.zigBee file. Simply change the file version number to a higher number.
Converters for internal *.zigBee file headers can be found inernet...

---

Tuya firmware numbers for different models may have the same identifiers.
It's possible to get a ZigBee thermometer with firmware that matches any identifier or manufacturer number.
Since Tuya doesn't release updates, and the devices are assembled by small companies...
And if there is a firmware update, Tuya Hub will install it using its IDs. Tuya does not support Zigbee 3.0 - they have their own standards.

It's impossible to answer your questions, as it's unclear what Zigbee OTA firmware you're looking for. And what firmware should replace it with?

PS: There is a MAC fix in TelinkMiFlasher v12.3, but I don't have a chance to test it right now....

[wta12]

• I can confirm the TelinkMiFlasher v12.3 works with MAC fix - just modified duplicated MAC with new version.
• Would it be possible to get Tuya IDs using Tuya hub ? had one in my closet. But wonder what I should do with Tuya IDs ?
• My ultimate goal is converting all cheap Tuya thermostat (mostly zigbee) into BLE custom firmware. Don't want to interact with Zigbee devices with current level of sdk/software stack - too immature. The problem is my bad (or Z2M's - dunno) on index config. Z2M will recognize the local custom firmware if manufacturer and image type codes are correct. It works for lktml02 Tuya2z but not with Tuya2Ble. The ZYTH02(P) doesn't work for either - Z2M stills reject updating - for example ZHTTH02(P)Tuya2Ble.json is acknowledged when checking for update but it returns "INVALID_IMAGE" when starting update. Will find header modification for .zigbee firmwave and test if it works better.