Sadly, no. I was mainly wondering if you or someone else had encountered something similar and had a quick fix. Otherwise, I guess I will find a way be starting from scratch with converting them back to Zigbee.
I have the exact same issue. Did you find any fix? Thankfully I didn’t update all my sensors at once
I wonder which sensors on which firmware version…
For me I didn’t have to reinsert batterie nor wakeup the sensor, it was quick smooth update for me frankly, naturally I got sensors close to Homey.
I tried just pressing «update» in Homey app (no re-inserting of batteries after pressing update). Update started, but same error. Eventually after re-inserting the batteries (after the update failed) the sensor started working again.
The update process itself is performed by Homey itself, so can’t advise here anything except of use a healthy battery, keep the sensor near Homey, start the update, then remove and reinsert the battery to wake it. Do not remove the device from Homey beforehand.
You may want to check also if given sensor has healthy nodes in Homey Developer Tools
Btw which error exactly you are getting ?
Can you share with me the debug log please, this bug is strange
Thanks for the app, smoothly working and easy to use!
Beside the already supported devices I’m using Qingping CGD1 Alarm Clock (cgllc.clock.dove). Would you consider to add this devices from the Xiaomi ecosystem?
-
Model:
cgllc.clock.dove -
Product Name: Qingping Bluetooth Alarm Clock (CGD1)
-
Protocol: Standard Xiaomi MiBeacon v4/v5 (encrypted with Bindkey)
-
Capabilities: Temperature, Humidity, Battery
It uses the exact same encryption parsing as LYWSD02MMC.
Hi @hori , I don’t have good experience with requests from users that are not active member of the the community, but let me try and contact you via DM on required inputs. Let’s see if that will work 
1.2.46
1. 8. 2026 - Added Test support for Qingping CGD1 alarm clocks
1.2.44
27. 7. 2026 - Fix LYWSD03MMC firmware migration routing
(in case of failures, first repair the device (REPAIR not pairing again)
Please note, there is always certain risk of bricking your device so if you are not comfortable with loosing your sensor, don’t update the firmare.
I have issues with 2 LYWSDCGQ/01ZM (BLE), they have worked for months up until 3 days ago. I have deleted them but now I can’t add them back. It only gets timed out after 30000ms
Solved it… had to restart the entire Homey and they were able to be added again.
Could be related to Homey version actually …
Hi there, apologise if this has been answered, but I’ve gone through the whole threads and forum and unable to find a solution for it. I have the Xiaomi smart temperature and humidity monitor 3, as well as Xiaomi Smart Home Hub 2, but even using the app above I am unable to connect any of the monitors. Would anyone would be able to suggest what the issues may be? Thank you again!
If that’s BHR9041GL, that’s not supported
Hi @Sharkys,
I seem to have a reproducible BLE issue with LYWSD03MMC ATC sensors and the current Xiaomi Miija app.
I have 4 × LYWSD03MMC sensors with ATC custom BLE firmware. All four were working normally, but recently all of them stopped updating at the same time.
Current behaviour:
- Restarting the Xiaomi Miija app immediately updates the sensor values.
- After the restart, the values stop updating again after a short time.
- Restarting / power-cycling the Homey Pro does not solve it permanently.
- I removed and paired one sensor again as LYWSD03MMC ATC (BLE) — pairing succeeds, but the same issue remains.
- I also checked the sensor with the ATC1441 Telink Flasher.
- Advertising type is set to Custom / ATC1441, Celsius, and I tested a 10-second advertising interval.
- The settings were saved to flash.
- After restarting the Miija app, Homey receives a new temperature/humidity value, but then stops receiving subsequent updates again.
- The sensor itself is definitely alive: I can discover and connect to it directly from Chrome/macOS over BLE.
This makes me suspect that the BLE advertisement listener/subscription in the Homey app stops working after initialization.
I noticed that version 1.2.42 introduced BLE advertisement subscriptions. Could this be related?
Have you seen this with the current app version, or is there a test version / workaround I could try without converting the sensors to Zigbee?
I would prefer to keep them on BLE because of the lower power consumption.
I can provide a diagnostic report if needed
Check if you can still see the devices also in the Dev interface, I guess they will be not visible and after Homey restart it will start working… Athom is currently investigating this issue as it’s reported by other integrations as well. If they devices reports back after Homey restart, I can’t help with that and you need to wait for new firmware. If they are still not reporting even after restart, try to submit diagnostic log from the Xiaomi app - eg. after 10mins since restart.
But does it helps? Anyway maybe submit the diagnostic log ideally shortly after you see sensors are not sending updates anymore
