Yeelight Discovery

 

Nov 9, 2022

https://github.com/home-assistant-libs/netdisco, This repository has been archived by the owner before Nov 9, 2022. It is now read-only.

Example From command-line:

python3 -m netdisco
# To see all raw data:
python3 -m netdisco dump
Copy

This library is deprecated. We will no longer release new versions, fix bugs or accept pull requests. If you are looking to make your Home Assistant integration discoverable, use the zeroconf and SSDP manifest options(https://developers.home-assistant.io/docs/en/next/creating_integration_manifest.html#zeroconf).

 

 

Sep 19, 2020 

In 0.115.0, the Yeelight Integration was updated (see #37191) to use SSDP instead of mDNS discovery.

https://github.com/home-assistant/core/issues/40268#issue-704644170

 

Jun 28, 2020 

The yeelight integration now uses custom SSDP-like discovery instead of the mDNS discovery since mDNS discovery is removed in new firmwares (#26574). After this change, there will be no longer automatic configuration based on the discovery integration. Users currently using that should set up all devices through UI.

https://github.com/home-assistant/core/pull/37191#issue-646861307

 

Sep 24, 2019

 I can confirm mDNS advertisement for _miio._udp will be removed completely in the new firmware. The reason is that our App doesn't use mDNS to discover device anymore and mDNS stack from all chip vendors are not stable and good enough.

 

 

Sep 23, 2019

 mDNS discovery in Yeelight devices is never the official way, in our API spec, only ssdp-like protocol is documented. We will remove mDNS in our further firmware update. For Homekit compatible devices, mDNS is used for Apple's Bonjour protocol and should not be used for Yeelight local discovery either.

https://github.com/home-assistant/core/issues/26574#issuecomment-533934568

 

 

Sep 12, 2019

I'm from Yeelight and we recently received lots of complaint about the discovery issue. Yeelight discovery mechanism is not changed, the new firmware only adds Homekit function.

https://github.com/home-assistant/core/issues/26574#issuecomment-533433942

 

Sep 11, 2019

After debugging and talking with the developer of yeelight he informed me that with the latest firmware of the Yeelight Colour there has been no changes to the multicast discovery code.

https://github.com/home-assistant/core/issues/26574#issue-492140926

 

on Dec 23, 2018

Netdisco was initially build for the purpose of Home Assistant. We are going to change how we do discovery in Home Assistant (home-assistant/architecture#121), and will probably even stop using netdisco, only having things be specified in HA how to be discovered. So I guess we can actually close this issue and just keep the limitation in place of not merging any new discovery methods.

 

 

May 10, 2018

 

Different from SSDP protocol, we choose to send multi-cast messages to port 1982 instead of

standard SSDP port 1900. This is to avoid excessive multi-cast messages being received by

both smart LED and 3rd party devices. It's especially important if the 3rd party device is powerconsumption-sensitive (e.g. smart watch powered by battery)."

cp.http://www.yeelight.com/download/Yeelight_Inter-Operation_Spec.pdf, page 4

https://github.com/home-assistant-libs/netdisco/pull/193#issue-321844303

 

 

Comments


Comments are closed