Open camcs1 opened 4 years ago
This is probably not something I'll have the chance to look into for a while. Here's the relevant code, for anyone brave enough to go spelunking :)
https://github.com/sidoh/esp8266_milight_hub/blob/master/lib/MiLight/RgbCctPacketFormatter.cpp#L110
Appreciate you taking a stab at it, @camcs1!
If it helps, there's some very light documentation on the protocol here: https://blog.christophermullins.com/2017/03/18/reverse-engineering-the-new-milightlimitlessled-2-4-ghz-protocol/
Let me know if there's anything I can help with :)
Describe the bug
If you are using remote forwarding and hold speed up or down on a physical remote it puts the lights into nightmode after a few seconds
Steps to reproduce
Use the remote forwarding example for Home Assistant, then hold speed down
Expected behavior
Behaves as expected in that it slows the effect speed, however the switch to nightmode is unwanted
Setup information
I am using a NodeMCUv3 Clone with a NRF24L01+PA+LNA SMA with external antenna.
For MiLight hardware I have: a FUT092 & B4 as remotes and FUT012, FUT039, FUT037 & FUT014 as lights. Both remotes trigger the bug and all lights also suffer from it. Both remotes are paired with the lights in case of Wi-Fi outage
Firmware version
1.10.5 & 1.10.6
Output of http://milight-hub.local/about
Output of http://milight-hub.local/settings
Home Assistant Setup
Additional context
You might of noticed I'm using the ESP12 binary, did this as a troubleshooting step however the bug was also present in the NodeMCU binary.