It can transfer BLE only devices’ data into Xiaomi Cloud, then you can gain data through Wifi network. Kind of like MQTT broker. Now HA’s approach for BLE devices is catching local BLE communication like what miflora does. But if HA based system is far away from BLE devices since signal is weak, it is hard to get data from device itself. If we can use this built-in function then signal would not be a problem.
There are only few devices with this function supported, such as Yeelight Ceiling Light, Philips Ceiling Light, 2nd Bedside Lamp, Xiaomi Smart Camera and Yeelight AI Speaker.
It does work when configured manually, but I don’t think it works through discovery.
Perhaps we can support it officially and make it a bit easier for guys who have it (and update the documentation on Yeelight component, which seems a bit out of date, now that ceiling lights is about to be added to the officially supported ones as well).
Hmm if you can show me how I’ll do it of course
I know the devices IP & Mac but I’ve never searched for mDNS value?
btw. I’m on windows, and HA Raspberry is on Hass.io.
Does your gateway/router provide a list of devices at your local network? Does it provide a hostname next to the IP adress? What’s the hostname? (examples: yeelink-light-ceiling1_[...], yeelink-light-bslamp1_[...])
Are you sure the discovery doesn’t work out of the box? You should find the warning “Unknown miio device found” in your log but the light should be discovered nevertheless. I made a pull request to get rid of the warning:
Do you already know how to enter your homeassistant docker container via SSH and docker exec? Do you own miio device and use the xiaomi_miio component? In this case the home assistant system has a console tool installed called “mirobo”. If you execute mirobo discover it will output the desired informations:
$ mirobo discover
INFO:miio.discovery:Discovering devices with mDNS, press any key to quit...
/srv/homeassistant/lib/python3.5/site-packages/miio/discovery.py:66: UserWarning: Please consider using python-yeelight for more complete support.
dev = device_cls(ip=addr)
INFO:miio.discovery:Found a supported 'Yeelight' at 192.168.130.27 - token:
INFO:miio.discovery:Found a supported 'Yeelight' at 192.168.130.25 - token:
INFO:miio.discovery:Found a supported 'Yeelight' at 192.168.130.28 - token:
INFO:miio.discovery:Found a supported 'AirPurifier' at 192.168.130.64 - token:
INFO:miio.discovery:lumi-gateway-v3_miio52244965._miio._udp.local. @ 192.168.130.29, check https://github.com/Danielhiversen/PyXiaomiGateway: token:
^C
Aborted!
(homeassistant) homeassistant@elroy:~ $
Yes I can SSH into root@hassio container and/or core-ssh.
I do believe I have miio component installed, my devices work (robot, bulbs etc.)
But if I type “mirobo” it’s just “command not found”. Sorry, total linux noobcake here
On the windows side of things, I installed that “Bonjour” and “Mono” as suggested, I’m still reading on how to make it work, can’t make sense of it yet.
Thanks! In this case the desk lamp cannot be auto discovered at the moment. As far as the lamp shows up (after a firmware update) in your bonjour browser please contact me!
In the meantime I got official response from the Yeelight staff as well:
First. thanks for choosing our products
However, mDNS is not integrated into Desk Lamp and likely will not be in the future - due to resource issue. There are not many free bytes of ram left on the device and we are avoiding to stuff in any heavy feature so as not to make the whole system unstable.
just reporting back about the moon mode. I used it now for some days and did not encounter any problems. Everything works, no errors - great work!
Thank you very much.
