I have just posted my initial version on GitHub. You can get to it
https://github.com/neilkplugins/WLED-indigo-plugin/blob/master/README.md and it is very much quick and dirty, but functional and evolving very quickly. Some brief notes :-
1) It should install like a normal plugin. I don't really know what I am doing with GitHub, so any problems let me know, bit you should be able to download a release from the releases tab. The only plugin configuration right now is to turn debugging on or off.
2) You create a WLED device for each controller by IP Address, using the normal "New Device Model", and configure an IP Address.
3) The device you create should operate as a dimmer, and responds to the UI controls as well as the universal actions for a dimmer (On/Off/Toggle/Set Brightness/Dim by/Brighten by). These impact the WLED Master Dimmer as I think that makes the most sense. I will soon get the primary RGB settings in the native Indigo device (when I figure out what I am doing wrong), with secondary RGB configurable by a Set Secondary R/G/B action. These colours are used as a base for some effects.
4) I have created WLED Actions to Set Effect by name, Set effect Intensity and Set Effect Speed - both of these are currently not validated and expect a value in the range 1- 255. I will look to add Palette actions. and ultimately all of the things that make sense and can be controlled by the API. This will be a function of time and everyones requirements (I haven't played too much yet with the WLED itself).
5) Each WLED device state is available for inspection on the device. I have done zero testing here other than the states that I have actions for. I will add text states for Effects, Palettes and other things that make sense and that you may want to expose to a control page or otherwise. Let me know I have have missed something. I know Palette is not updating. I currently poll every 60 seconds, but will add a configuration option for this (and you can change in in the plugin manually if you want to make it more responsive to reflect changes from the WLED app)
I have no idea what impact the polling has on the WLED/NodeMCU, especially with longer strip lengths (testing to date has been on a single 5m strip with 150 LEDS)
The code is really ugly and I will be optimising, adding error checking and validation and generally learning how to do things properly, but given people seemed keen to get going then I focussed on getting something done.
Enjoy, I will keep working on it and will try and be responsive to any questions. I guess we can use this thread for now for questions, I have requested a sub forum (but that was only today) .
Neil