Support for FS150-B

[zoltak]

Any chance you can add support for the Neewer FS150-B

[taburineagle]

Hi @zoltak - I'll add that one to the master list of Neewer lights! Try this, if you can see the light in NeewerLite-Python, but the controls don't work - connect to the light like normal, select that light in the list, then click on the "Light Preferences" tab - then turn on "Use Custom Color Temperature for CCT mode", use the values of 2700 for the minimum and 6500K for the maximum, then turn on "This light can only use CCT mode", and hit "Save Preferences" - this should make the light usable.

[taburineagle]

[zoltak]

Thanks for the tip @taburineagle. Unfortunately the FS150-B would not show up on the scan list.

I also have a RGB660 which worked without issue so my systems Bluetooth seems to be working correctly.

[taburineagle]

Got you, that makes sense, the name for that light might be one of the newer ways Neewer names their devices (the newer ones start with NW-, and then a bunch of characters.) I'm working on releasing a new version that adds the new name structure to NeewerLite-Python, but I keep getting waylaid by... ha, life basically, I've been working on that version since last November 😄

Try this out - I have a more modern work-in-progress version of NeewerLite-Python that adds the "new" naming structure to the light discovery method (among other upgrades), so this should at least test that theory that the naming is part of it. Back up the NeewerLite-Python.py and ui_NeewerLightUI.py files you currently use, and download the versions from the branch that's in progress (WIP-HTTP-Server-Mods) here:

NeewerLite-Python.py ui_NeewerLightUI.py

...and see if this version helps out at all.

[zoltak]

Thanks @taburineagle that worked!

[taburineagle]

Ah, excellent! Glad to hear that @zoltak - I really need to batten down the hatches and finish this new version already. It's been basically finished for a while, but I want to go over everything to make sure it's good first.