XiaomiGateway3
XiaomiGateway3 copied to clipboard
4 BLE sensors are unknown and unavailable (LYWSD03MMC)
All my device temperature and humidity sensors do not seem to work on BLE gatway. My gateway is ZNDMWG03LM and other device work well on it except BLE sensors. Hope you give some advice. Thanks.
What versions of Hass, Integration and Gateway do you have?
What versions of Hass, Integration and Gateway do you have?
Hass is core-2022.4.1 Integration is v2.0.9 Gateway is 1.54_0052
Have you seen your gateway firmware in supported list? https://github.com/AlexxIT/XiaomiGateway3#supported-firmwares
I share of the same problem. The BLE devices show on the MiHome app connected to the gateway. They are recognized by the integration, but their values are always unavailable. Updated firmware to 1.54_0052. Reinstalled the Integration multiple times.
Running HASS core-2022.4.7.
https://github.com/AlexxIT/XiaomiGateway3#supported-firmwares :
"these firmwares are not supported yet: v1.5.4_0XXX"
Ended up misstyping mine.
Im actually runninhg 1.5.0.xxx
The problem still presists.
同1.5.0_0102
温湿度计传感器,显示不可用
@AlexxIT
Same problems... My BLE temperature sensors not send any data... I use the recommended firmware (1.5.0_0102)
Hass core-2022.6.5 Integration is v2.1.0 Gateway is 1.5.0_0102
Zigbee device (two gang relay switch) works well.
In mi home app, temp. sensors work normally.
Здраствуйте, аналогичная проблема с датчиками LYWSD03MMC Прошивка шлюза 1.5.0_0102 HAOS 2022.6.6 Интеграция 2.1.0 Датчик движения Qingping CGPR1 работает хорошо.
Есть ли решение данной проблемы?
Home Assistant Core 2022.6.7 Home Assistant Supervisor 2022.05.3 Home Assistant OS 8.2 Xiaomi Gateway 3 v2.1.0 gateway 1.5.0_0102
me too
For those who are using firmware 1.5.0 - can you see this sensor in MiHome in Gateway child devices screen?
@AlexxIT
Yes, we are see it.
I'm also on 1.5.0 with this issue suddenly occurring after having made no changes. I see the devices (temp sensors) within the BLE gateway in app (vevs mod), however it the values displayed are the values that HA last saw before they became unavailable.
If I click one of my temp sensors elsewhere in the app, my phones BT is utilised and the current temp is displayed. However, returning to the gateways BLE view, the temp sensors are still displaying old values.
So it seems to be a issue with the gateway device itself perhaps?
I'm using a lumi.gateway.mgl03, if that's any help!
For those who are using firmware 1.5.0 - can you see this sensor in MiHome in Gateway child devices screen?
Yup. they all show up perfectly on the Mi App.
I'm also on 1.5.0 with this issue suddenly occurring after having made no changes. I see the devices (temp sensors) within the BLE gateway in app (vevs mod), however it the values displayed are the values that HA last saw before they became unavailable.
If I click one of my temp sensors elsewhere in the app, my phones BT is utilised and the current temp is displayed. However, returning to the gateways BLE view, the temp sensors are still displaying old values.
So it seems to be a issue with the gateway device itself perhaps?
I'm using a lumi.gateway.mgl03, if that's any help!
I have exactly the same issue! Exact same devices and firmware versions too They all went offline at about 6:30pm AEST yesterday and have been unavailable ever since. I can see them in the Mi Home app, but it connects via my phones BT and they seem to not be reporting the correct values to the Mi Hub, which isn't passing on data to HA.
They all went offline at about 6:30pm AEST
Almost exactly hour earlier for me, same timezone
Certainly seems like it isn't an issue with this integration, but Mi Home.
Out of curiosity... What region are you set to? Are you running the modded version of Mi Home?
I'm running modded and set to the recommended Singapore region
Question only for supported gateway firmwares:
Do you have another BLE devices? Do they continue to work properly in Home Assistant while LYWSD03MMC unavailable?
I'm running on supported firmware. Only BLE device I have other than the LYWSD03MMC temp sensors (which aren't working) is the XMMF01JQD Xiaomi Magic Rubik's Cube, which seems to work just fine!
They all went offline at about 6:30pm AEST
Almost exactly hour earlier for me, same timezone
Certainly seems like it isn't an issue with this integration, but Mi Home.
Out of curiosity... What region are you set to? Are you running the modded version of Mi Home?
I'm running modded and set to the recommended Singapore region
I'm running the modded gateway software yeah, my region is set to Australia
I only have the LYWSD03MMC sensors, I have 3 of them and they all seemed to go unavailable at roughly the same time. I've also noticed that my "Gateway Cloud Link" shows as "Disconnected", and it seems to have happened about 10-12 hours after the temperature sensors went offline. I've tried a few things and can't get it to show connected again.
I'm running on supported firmware. I do not have other BLE devices on the hub.
Question only for supported gateway firmwares:
Do you have another BLE devices? Do they continue to work properly in Home Assistant while LYWSD03MMC unavailable?
I don't use other BLE , only zigbee devices, but this work well.
@AlexxIT any idea what this is? all my BLE devices are shown as unavailable as well:

Shown properly in the mi home app:
@sagilo are you using supported firmware?
I was using 1.5.0_0102 but recently updated to 1.5.4_0090, however, the issue isnt a new one and occurred for 1.5.0_0102 as well. I see there are other users on this thread who are having the same issue with the supported v1.5.0_0102. If you believe this is a fw issue, I can probably flash custom one but since other users experience the same i dont have high hopes. Im available for sharing logs or anything you need in order to troubleshoot the issue, but it looks like BLE functionality is dead for now for all the component users?
There is no need for logs. v1.5.4 is not supported
@AlexxIT there are more than 3 users on this thread who use v1.5.0_0102 and it doesn't work either.. Anyway, I do appreciate the component and the development, but that's an odd way to handle issues. coming from your users. If issues aren't going to be fixed and the repo isn't maintained (for any reason) - that's perfectly fine, but it's better to reflect that in the repo info so users can know to find alternatives and not waste time to onboard
And thousands of users, including me, who have 1.5.0 working with BLE...
Support for new BLE devices is added with each release. No need to doubt that it works: https://github.com/AlexxIT/XiaomiGateway3/milestone/1
And thousands of users, including me, who have 1.5.0 working with BLE...
Support for new BLE devices is added with each release. No need to doubt that it works: https://github.com/AlexxIT/XiaomiGateway3/milestone/1
As mentioned, there are 3 users on this thread which BLE devices doesn't work for them. If downgrading to a supported version will help you troubleshoot this issue faster, I can try doing that and assist. But first I want to make sure it do any good or I'll just be wasting time as there are no bug fixes at this point?
As mentioned, there are 3 users on this thread which BLE devices doesn't work for them.
I was one of those users.
The issue myself and others have encountered likely had nothing to do with this integration. It was a xiaomi app and/or server problem. I am also using a modified app, putting another variable in the mix.
Throw a sensor in your fridge and see if the official Mi Home app updates the temperature for it. They were online in my app and were displaying temps that looked correct, but were the value was actually many hours out of date.
My solution was to remove the trouble sensors and re add them, didn't happen smoothly but I eventually resolved my issues.
I lost all my 6 LYWSD03MMC at about 3:30 UTC yesterday. Just re-added them to MiHome and now it works again.
The difference I spotted - previously when getting devices info from MiCloud the Bindkey
was Not needed
. Now it is set.


It definitely looks like MiHome issue, but I think it's worth mentioning in FAQ or something.