Chris Mullins

@daandupau -- you'll notice that this is for the ESP IoT SDK. This is not compatible with the platform this project is developed on top of, unfortunately. The ask in...

Henryk reverse engineered one of the earlier protocols, but his work didn't include the newer devices (I [reversed this one](https://blog.christophermullins.com/2017/03/18/reverse-engineering-the-new-milightlimitlessled-2-4-ghz-protocol/)). Regardless of the core RF drivers, there's a ton of...

Probably wouldn't be too hard, but taking advantage of the (dual core) hardware would be a lot more challenging. My guess is that there are a chunk of ESP8266-specific things...

Beautiful! Thanks very much for taking a crack at this, @mrtncls. Wanna toss it into a PR?

Hey all, sorry I left you hanging here. Honestly, this is probably not something I'm going to look into myself, but I'm happy to take a look at a PR.

Hi, I somehow missed this over the holidays. Nice work, @pfink! @Clemens82, device IDs are only 2 bytes and are tied to the microcontroller. The best way to find the...

Makes sense that a rewrite would be easier given the context. As a workaround, might be able to set some debug flags and see packets in serial? @Clemens82, some bulbs...

Makes sense. Pretty easy to do in the UI because the Github API is CORS-enabled (meaning it's just some frontend code). Doing it through the backend is more heavyweight and...

Makes sense.

No active plans to pursue this, @s1nbad. The relevant section of the code has been linked. You're welcome to manually change retain to false. Would also happily collaborate on a...