Update to your firmware from another custom firmware

[LeidenSpain]

First of all, thank you for your work.

Some time ago I updated a LYWSD03MMC using another firmware (z03mmc).

But now I have a second LYWSD03MMC sensor, and I was advised to use your firmware. And I actually like it better.

Now I want to migrate from that firmware.
The problem is that I'm not sure which file to use, since I see many.
https://github.com/pvvx/ATC_MiThermometer/tree/master/zigbee_ota

And to add to my confusion, I see you have two OTA-related applications:
https://pvvx.github.io/ATC_MiThermometer/ZigbeeTlcIdxOTA.html
https://pvvx.github.io/ATC_MiThermometer/TelinkOTA.html

I understand it's entirely due to my lack of knowledge, but what are the steps and the file needed to install your firmware?

My device is as follows:

Regards

[pvvx]

https://github.com/pvvx/ZigbeeTLc/tree/master/bin/devbis

[LeidenSpain]

First of all, thank you for your reply.

Is it too much to ask which of the files I should use? (I think it's db15-0203-79993001-Z03MMC_v01NN.zigbee)
And can this be done with one of your web applications, or do I have to use LocalOTA with zigbee2mqtt?

[pvvx]

Requires using Zigbee OTA ("LocalOTA with zigbee2mqtt").

[LeidenSpain]

Thank you so much for replying.

I'm sorry for asking so many questions, but sometimes we have too much information, too many websites, too many files... and in the end it's worse because you don't understand anything.

From here on out, I'll look into how to use Zigbee OTA.

[LeidenSpain]

Hello again,

I've updated using this guide (I'm leaving it here to help others).
https://smarthomescene.com/guides/how-to-setup-zigbee2mqtt-local-ota-index/

And I used the file db15-0203-79993001-Z03MMC_v0132.zigbee (as you instructed).
But I'm still using the devbis version.

From:

To:

What I want is to switch to your firmware (device LYWSD03MMC-z).

[landmaj]

I had the same "issue". Interview the device, it should fix it.

[LeidenSpain]

I had the same "issue". Interview the device, it should fix it.

In the end I ended up recovering the firmware from devbis (1141-020a-09993001-z03mmc_v1100.zigbee).

But I don't quite understand what's happening with the versions.
When I switch from DevBIS to ZigbeeTLC, it shows Application 7.9 build 153.
But in the one I converted from Xiaomi directly to ZigbeeTLc, it shows Application 0.1 build 50.

What information does it show you about firmware, model, Firmware ID and Firmware Version?

[landmaj]

I guess it's to be expected - converting from another firmware is not the same as converting from pvvx's BLE firmware, otherwise there wouldn't be a separate firmware file to flash.

I just converted 5 devices from atc1441/ATC_MiThermometer to this firmware using this file and encountered both issues you mentioned.

The first issue (z2m displaying old firmware ID (3001-1100) but new firmware version (Application: 7.9 build 153)) was solved by pressing "interview". After that I pressed "reconfigure", changed some settings (calibration, etc) and replaced batteries. Then I had the same thing as you in OTA tab - 5 devices converted from another firmware showed (Application: 7.9 build 153), 1 installed fresh from BLE firmware showed App: 0.1 build 51. After removing custom OTA index, restarting z2m, ticking checkboxes for those 5 devices in OTA tab and pressing "check selected" at the top, the firmware version changed to App: 0.1 build 51, same as fresh install.

Was it just stale data in z2m, updated after checking for OTA update again? Was reconfiguration needed or maybe the new firmware does something on boot? No idea, but in the end everything is correct.

[pvvx]

When updating the firmware to a new version or firmware with new features, you must:

1. Remove (delete) the device from the Z2M/ZHA.
2. It is recommended to reset the device. On the LYWSD03MMC, this can be done by shorting the "reset" and "GND" pins for more than 15 seconds.
3. Re-pair.
   This applies to any Zigbee device when updating the firmware to a new version with new features.

[LeidenSpain]

I guess it's to be expected - converting from another firmware is not the same as converting from pvvx's BLE firmware, otherwise there wouldn't be a separate firmware file to flash.

I just converted 5 devices from atc1441/ATC_MiThermometer to this firmware using this file and encountered both issues you mentioned.

The first issue (z2m displaying old firmware ID (3001-1100) but new firmware version (Application: 7.9 build 153)) was solved by pressing "interview". After that I pressed "reconfigure", changed some settings (calibration, etc) and replaced batteries. Then I had the same thing as you in OTA tab - 5 devices converted from another firmware showed (Application: 7.9 build 153), 1 installed fresh from BLE firmware showed App: 0.1 build 51. After removing custom OTA index, restarting z2m, ticking checkboxes for those 5 devices in OTA tab and pressing "check selected" at the top, the firmware version changed to App: 0.1 build 51, same as fresh install.

Was it just stale data in z2m, updated after checking for OTA update again? Was reconfiguration needed or maybe the new firmware does something on boot? No idea, but in the end everything is correct.

First of all, and although it might sound harsh, I'm glad the same thing happened to you. Now I know I'm not a disaster.

I'm going to follow all your steps and see if it works out for me this time.

[landmaj]

One thing I forgot - after flashing I pressed "permit join", waited until "last seen" changed to "just now" and then pressed "interview".

After successfully flashing first device, it showed new firmware version but "last seen" was increasing, up to 9 minutes and the device did not react when I tried to interview it. I guess it was not really part of the network after flashing? After pressing "permit join" it immediately connected, "last seen" changed to "just now" and everything worked. It was at that point that doing the interview updated firmware ID.

I did not have to remove any of the devices from z2m, reset them or anything.

[pvvx]

I did not have to remove any of the devices from z2m, reset them or anything.

Such actions do not always work correctly in Z2M or ZHA.

[landmaj]

Guess I'm lucky then, it worked for me 5 times in a row. :)

And thanks for the firmware! I bought a few LYWSD03MMC as spares for my existing ones without knowing the hardware was changed at some point. I found out when the display stopped working after flashing. This repo saved them from the trash bin.

[pvvx]

If you haven't removed the device from the network:

1. If the device does not accept the delete command (reset all network settings), then it will work with the old data from memory, which may not match the new firmware version, and there will be incomprehensible errors.
2. The Zigbee coordinator and Zigbee service program will retain old device information, as well as other data related to the device's functionality.

Even if the device has cleared all bindings to the previous network, the device's IEEE hasn't changed. The coordinator will reconnect the device without your command and with the old functionality data, since the device's IEEE hasn't been removed from its list.
There are many other problems if the device hasn't been completely removed from the network, including information in all routers, etc.
Something worked for you only because the ZigbeeTLc firmware checked for data from a different version during a restart and cleared it. However, if you update the firmware to other versions, those FW versions do not have checks to ensure that the data written to the flash memory about the current network and functions is relevant to the other version of the program.
However, data from the previous firmware version still remains in the rest of the network and in Z2M.

Ultimately, it is necessary that the data be reset and updated in the device itself, in the network itself (coordinator), and in the network maintenance program.