Light model: NEEWER MS60C (mini RGBWW LED light, "Infinity" Bluetooth mode)
Environment:
OS: Windows 11
NeewerLite-Python version: 2025-02-01-BETA
Running via HTTP server daemon (--http)
What happened:
The light is discovered correctly and shows as Linked: Yes in the HTTP daemon's light list:
ID # Custom Name Light Type MAC Address/GUID RSSI Linked Last Sent Value
1 MS60C E8:D9:E9:A0:29:CE -69 dbM Yes (Turn light off)
Sending on/off/CCT commands via the HTTP daemon returns HTTP 200 with no errors in the console log:
[17:46:50] Processing HTTP arguments
127.0.0.1 - - [21/Jul/2026 17:46:50] "GET /NeewerLite-Python/doAction?light=E8:D9:E9:A0:29:CE&on HTTP/1.1" 200 -
[17:46:50] Going into send mode
[17:46:50] Leaving send mode and going back to background thread
However, the light itself does not turn on/off or change in any way in response to these commands.
What I've verified:
The light is in Infinity (Bluetooth) mode, confirmed by the flashing/solid "∞" icon on its display.
The official NEEWER phone app connects to and fully controls the light over Bluetooth without any issue — brightness, CCT, on/off all work correctly from the app.
This confirms the light is reachable and controllable over BLE; the issue appears isolated to NeewerLite-Python not sending a command byte sequence the MS60C's firmware recognizes.
Request: Could the MS60C be added to (or corrected in) the supported/tested light protocol list? Happy to help test candidate byte sequences or run a Bluetooth sniffer (e.g. nRF Connect / Wireshark BLE) against the official app to capture the correct command format if that would help.
Light model: NEEWER MS60C (mini RGBWW LED light, "Infinity" Bluetooth mode)
Environment:
OS: Windows 11
NeewerLite-Python version: 2025-02-01-BETA
Running via HTTP server daemon (--http)
What happened:
The light is discovered correctly and shows as Linked: Yes in the HTTP daemon's light list:
ID # Custom Name Light Type MAC Address/GUID RSSI Linked Last Sent Value
1 MS60C E8:D9:E9:A0:29:CE -69 dbM Yes (Turn light off)
Sending on/off/CCT commands via the HTTP daemon returns HTTP 200 with no errors in the console log:
[17:46:50] Processing HTTP arguments
127.0.0.1 - - [21/Jul/2026 17:46:50] "GET /NeewerLite-Python/doAction?light=E8:D9:E9:A0:29:CE&on HTTP/1.1" 200 -
[17:46:50] Going into send mode
[17:46:50] Leaving send mode and going back to background thread
However, the light itself does not turn on/off or change in any way in response to these commands.
What I've verified:
The light is in Infinity (Bluetooth) mode, confirmed by the flashing/solid "∞" icon on its display.
The official NEEWER phone app connects to and fully controls the light over Bluetooth without any issue — brightness, CCT, on/off all work correctly from the app.
This confirms the light is reachable and controllable over BLE; the issue appears isolated to NeewerLite-Python not sending a command byte sequence the MS60C's firmware recognizes.
Request: Could the MS60C be added to (or corrected in) the supported/tested light protocol list? Happy to help test candidate byte sequences or run a Bluetooth sniffer (e.g. nRF Connect / Wireshark BLE) against the official app to capture the correct command format if that would help.