As there has been quite some discussion already about some plugins for the milight aka IWY and a shitload of other names.
And as well wifi370 LED controller.
I created a plugin for milight, not knowing that IWY = milight but a different name.
From here on i will use MiLight as brand name for all of them (i believe that is the original name)
So current status:
2 plugins: 1 from @philip1986 which supports wifi370 and IWY. And 1 from me that only supports Milight.
The plugin from @philip1986 has a better GUI, (i completly suck at it) but i belive my plugin has better support for milight. (correct me if i’m wrong!)
There has been quite some talk about integrating, thank you @mwittig
So instead of spreading it all over different theads, and spamming the main plugin threads for this, a new one!
My point of view at the moment: the @philip1986 IWY plugin has 1 module backing it for controlling either WIfi 370 and Milight. And i’m not really fond of the way it it loading either 1.
my idea: 1 plugin. With 2 devices:
Both those device use a different backend library to connect to the controlling device.
But they will both use the same GUI.
This way we can work on the backend library for 1 of the devices without having to worry about breaking the other one, and the other way around.
As well, if it happens that 1 of the devices needs a specific setting, we can make that very easy as they are different devices, they just happen to be in the same plugin.
Lets say for example color setting: The MiLight can only accept 255 different colors. where Wifi370 can accept RGB, and all 3 of them can hold a value of 255. So this means different calculations. But the Gui can keep the same.
Could you guys give your opinion about this plan? perhaps @sweetpi has some additional idea’s?