sidoh/esp8266_milight_hub 1.6.0 on GitHub

New features

FUT089/B8 remotes, which allow for control of up to eight groups with one remote.

State for all devices -- that is, (device type, device id, group) triplets -- is now passively tracked and persisted.
Add a REST route to retrieve the state of a given device.
Add support for publishing full device state to MQTT.
Add support for sending raw commands and arguments in MQTT and REST integrations.
REST endpoint to change bulb state now returns the new state of the bulb instead of just true.
Switching devices in the UI will update settings to known values for that ID (e.g., on/off switch, brightness, etc. will be set to last known values).
Add the ability to select which keys (brightness, color, etc.) are sent in MQTT updates (and REST state responses). Defaults to keys used by HomeAssistant's mqtt_json component, but you can now select alternatives like level, or hue/saturation instead of color.

@khmann cut a lot of unnecessary work and added optimizations in the nRF radio handler code which improved performance by 40% (!).

MQTT state updates are published as retained messages. New subscribers to state topics will receive the last published message. This means, for example, HomeAssistant will boot with the correct bulb states.
( #103 ) Add ability to select which fields (brightness, level, etc.) are sent in MQTT updates and state messages.

Compile against Arduino 2.4.0-rc2, which includes a fix for the KRACK vulnerability in WPA2.
@speendo added a password for the setup AP. The password is milightHub. This prevents your wifi credentials from being transmitted in plaintext.

@bombcheck fixed a bug with handling night mode for RGBW bulbs.
FUT092 (RGB+CCT) packets encoded with the key 0xD4 were getting decoded incorrectly. This has been fixed.
Removed improper usage of PROGMEM which might've caused crashes when compiled in some environments.
Fixed crashes when compiled in a Windows environment.
Fix edge case where wrong packets being sent in V5 UDP integrations.
The GET /settings endpoint returned the raw settings file on flash, which meant newly added setting keys weren't populated with their default value. The value returned by this endpoint is now populated with default values for otherwise undefined settings.
Loading settings from the UI (and the POST /settings REST endpoint) were not working properly. This has been fixed.
Fixed bug where packet repeats weren't set correctly when settings were saved.
@speendo fixed a bug causing the "Clear Wifi Config" feature to not work.
( #155 ) Fix buffer overrun for commands that buffer lots of packets (like level controls for CCT bulbs).