Update OTA files for Xiaomi QBKG30LM, QBKG31LM, QBKG32LM, ZNLDP13LM, TDL01LM and RTCZCGQ11LM
#425
Conversation
…P13LM`, `TDL01LM` and `RTCZCGQ11LM`
|
Thanks! |
|
for the RTCZCGQ11LM : |
I think this can only be understood experimentally, because it’s not clear what Aqara means by this and how it will affect the operation of the device 🤷 |
|
I have 3 presence sensors RTCZCGQ11LM and after updating one of them with the new firmware, I find it very unstable and it will stop detecting my presence after some time. Unplugging it from the USB power and re-plugging it fixes it for a little while and presence detection starts working again, before it breaks later on again. Affected sensor details: Other sensors, not yet updated: Kitchen Bedroom The bedroom sensor shows the same firmware build date as the already upgraded Living sensor, yet I see the option to update the Bedroom sensor. Has anyone else experienced issues, following the firmware upgrade of their presence sensor? |
I confirm. I've 5 FP1's for about a year. Everithing was stable. Updated 3 of 5 sensors to v.58. Got unstable presence detection, "blinking" leave events and bad senisitivity. After power shutdown today, all sensors with version 58 didn't rejoined the network. "54" are working well. Strongly unrecommend to update sensors. |
|
Thank you for sharing, hope you'll be able to fix it, maybe you can force a downgrade ? |
|
Try to repair FP1 after updating the firmware and if this does not help, then I can suggest trying to roll back the firmware version to 20220524105221_OTA_lumi.motion.ac01_0.0.0_0054_20220509_EB279B_modded_to_v99.ota.zip |
|
@Otnow I tried downgrading the firmware back to 54 using the above modded file, but I get the following in the logs: My index.json has the following, with the firmware file available locally next to configuration.yaml: [
{
"url": "20220524105221_OTA_lumi.motion.ac01_0.0.0_0054_20220509_EB279B_modded_to_v99.ota",
"force": true
}
]I also tried forcing the original 54 firmware, using force: true, but I get the following error: Re-pairing the sensor unfortunately also doesn't work. I am not sure what else I can try, other than waiting for an updated firmware that hopefully fixes this issue. |
|
@vivobg, I think the result will be the same, but you can also try this modified firmware (only the version number in the header has been changed to 59): 20220524105221_OTA_lumi.motion.ac01_0.0.0_0054_20220509_EB279B_modded_to_v59.ota.zip |
|
Still got the same issues report. seem can't downgrade |
|
It's a pity, then all that remains is to wait for the release of a new firmware version. In general, it is strange that it was not possible to downgrade the firmware version, because this method worked on several other Aqara devices. I hope that this is an isolated case and Aqara has not started prohibiting downgrading in new versions of the firmware of its devices, otherwise it will be completely sad. |
|
Created a PR to return the previous version of firmware |
|
Hi, I have not been able to downgrade to version 54. I have tried unplug devices and also re-pairing them but in all cases I end up with the following message: |
|
If you have another Zigbee coordinator/"dongle", you could try to do the downgrade with ZHA. If you want to do the downgrade with ZHA, there are some extra config options you need to set for now. |
|
I believe I'm having the same issue many have reported here. After updating the firmware the devices will get stuck in an "away" state after a few days. I need to unplug/replug the device to get it back to normal until it happens again a few days later. As one upside, it did seem like the detection it had was more solid in my bedroom for when I was sleeping. From the above conversation it seems like downgrading is not possible? |
Otnow has made new PR to revert the previous fw OTA. let wait for new release |
With the dev version, no OTA was shown. |
Like @dedors I want to test this v58 firmware on my own but we cant. This is what the log shows me: Is there any easy way to install v58 If a user really want to do this? |
Some strange error in the log. What version of z2m is this? |
|
Anyone actually managed to downgrade? FP1 was working fine and became pretty much unusable since the update to 58 on my end. It will clear the presence even when I'm in the room and it's really annoying. |
|
I haven't tried since it doesn't sound possible from the above conversations, so I've sadly just resorted to connecting them to smart plugs that cycle every so often :/ |
|
yeah, it's impossible right now, so annoy with v58. Need to buy another sonoff to cover the presence_event status change frequently of Fp1. If any one have the way to downgrade, that's really a savior |
|
I couldn't downgrade my firmware either, and I think I bricked my FP1 as it no longer wants to pair with z2m. |
|
Any possibility to downgrade the version from v58 back to v54? Two of myFP1s with v58 are totally unusable after upgrading to 2.0.0 (Not very sure if it is related with 2.0.0). |
|
I have the same issue. After updating the firmware version to 58 (I don't know how it happened), the sensor started switching to "leave" status even when there is motion. I tried rolling back to firmware version 54 by specifying a local file for the OTA update, but for some reason, Zigbee2MQTT still looks for the file in the repository and throws an error saying that the version is newer than in the repository. What should I do? Wait for an official firmware update? That might not happen. Taking a shower with a light show isn't really an ideal option. |
|
Unfortunately I don't think anyone has figured out how to downgrade the firmware. My FP1 has been a nice paper weight since the upgrade. :/ |
|
Does anyone have contacts at Aqara to ask them to roll back the changes and release a version with number 59 or higher? UPD: I wrote to support@aqara.com. |
QBKG30LM:
QBKG31LM:
QBKG32LM:
ZNLDP13LM:
TDL01LM:
RTCZCGQ11LM: