@AlexxIT Thank you for that. All working now. Might be worth adding solution to pinned ‘Downgrade firmware instruction’ documentation. Thank you again.
@AlexxIT Maybe this closed issue, since it seems important, keep it closed and pin it, so others can see it?
Dear Folks, finally I found a way to control my yeelight mesh lights with home assistant. Unfortunately not with this Mult-Mode Gateway. For more Detail feel free to contact me.
Why the secrecy? 
Please do share…
You are right guys. 
Because my frustration level was so high I´m decided to order the new yeelight mesh gateway.
So my hope was that I can implement it with home kit and it worked perfectly. This Gateway was automatically discovered by the HomeKit-Controller integration as well as all attached yeelight mesh lights.
1 Like
Hi, i have the Gateway 3 with firmware 1.45_0012 and my problem similar this. The Gateway no responde. Have you sucess? @AlexxIT how I resolve to be able to integrate with h.a?
Dear @AlexxIT!
I’ve a question about the devices’ reported values.
I have a LLKZMK11LM (Xiaomi 2 channel relay). It reports the state of the 2 switches, consumption (W) (I have nothing connected to it, but it shows 0. The relay module self consumption is between 1-2 W) and used energy summary (kWh) - this is shown correctly I think.
My question is: how can I view the link quality, voltage, and temperature of the unit? If I pair it with zigbee2mqtt, these values are shown…
Is it a limitation of the ZNDMWG03LM? - Maybe the MQTT server in it swallow these values? Or is it possible to modify / improve Your code, to extract these informations too?
ps: Te link quality seems not shown for any devices…
Regards, F
You can see LQ in debug logs of component. Not all users want unnecessary sensors. I need develop some settings. It’s need time.
Try reboot gw. I think in some cases gw block any connection to it.
Well, these are really not so important values, I agree.
Try to ping it, and try to login with Telnet, to see if its operating normally…
you can also try mqtt-explorer. With this tool, you can connect to your MQTT servers, and you can monitor communication, that may help solve things…
Hello all,
I am looking for a solution to receive a notification when any sensor is unavailable/offline (battery problem, disconnection,…).
In the documentation, I noticed :
**Ignore offline** device status.
# /config/customize.yaml switch.0x158d0003456789_switch: ignore_offline: 1 # any non-empty value
So, I wondered if there was a solution with this integration to detect status of the sensor (unavailable/offline) ? Do you have any idea ?
If not, how do you do it ? The idea is to be informed when any sensor is unavailable/offline
Currently, I use :
- Xiaomi Button (WXKG01LM)
- Xiaomi Door Sensor (MCCGQ01LM)
- Aqara TH Sensor (WSDCGQ11LM)
- Aqara Motion Sensor (RTCGQ11LM)
Thanks for your help !
1 Like
any luck with version 1.4.7_0065 ?
Only just found this thread and my gateway is fully updated 
I have moved all zigbee devices to a CC2531 for fun but have four BLE temp sensors that I would like to access without going via nodered to alexa and back to hass!!!
1 Like
I have model ZNDMWG03LM with firmware 1.4.6_0030, on the previous version
of Gateway integration, all thing are OK. The ZNDMWG03LM are detected 4 Plant monitor and Xiaomi smart lock N100.
With v0.11b8, the Gateway can be detected and have a token:
But when submit, the error appear:
How to fix it, Do I must to downgrade the firmware to before 1.4.6_0030?
Thanks for any advise !!!
Dzung Hoang
Hello,
I’ve updated 1.4.6_0012 to the custom fw ( https://github.com/serrj-sv/lumi.gateway.mgl03/tree/main/firmware ) with Telnet but no ble firmware is updated I suppose. I still have /data/firmware/full.gbl file present. How to update? I did few reboots already.
Is the v1.4.7_0115 enough stable to give him a try? Sometimes I have zigbee presence detector that disconnects so maybe it’s improved in 1.4.7.
Last question is it possible do downgrade from the custom 1.4.7 to custom 1.4.6 using easy telnet method?
On the screenshot we see tha you are using v1.4.6_0043 . This one is not supported
My bad. I think the support of 1.4.6_0030 was removed. Try to downgrade to the recommended 1.4.6_0012 custom firmware with Telnet…