That is not possible at this point. The thingClass definition is quite static. We’ll probably add some more dynamic stuff in there in the future, but so far enabling/disabling stateTypes didn’t come up in those thoughts. I’ll have to think about this…
One option I could think of would be to have an action like “fade” with parameters like “fromColor” and “toColor”. Not sure if that’s feasible for all the effects… Would that solve your use cases?
Also we’re thinking about an effectlight interface but not really sure yet how that would look like either. We’d need some more real world examples on what would be needed in order to define such an interface.
Then one other thing to consider is maybe the ScriptEngine. With nymea scripts one can run a ColorAnimation on a color state. Meaning, the plugin doesn’t need to implement such a loop itself but the user can enable a script which runs the animation, regardless of the actual plugin used. Right now one has to write the script manually but the plan is to have templates for that so the user would be able to enable such a color loop via the app and it would generate a script for it. This already works great when it comes to animating a single color on a light bulb (or an entire LED strip) but ideally I’d like also provide a mechanism for scripts to control multiple colors, for example on a WS2812 strip where each LED could be addressed individually. So far I was thinking of something like a state of type string which would take an array of RGB color values… But I haven’t tried that yet so not sure how well that would work.