The app supports Hue, Nanoleaf, and LIFX which all support transitions in hardware (I’m unfamiliar with Avea’s capabilities).
There’s a script available that performs transitions in software for lighting technologies that don’t support it in hardware. There’s a practical upper limit to the number of lights that can be controlled simultaneously, with good results, and it depends on the communication speed and bandwidth.
-
For hardware-based, the light only needs to receive one command and then manages its own transition. It’s very efficient even if dozens of lights are involved. Plus all lights start transitioning simultaneously.
-
For software-based, the light needs to receive a stream of commands to perform the transition. This presents a traffic congestion problem when many lights are involved. There may also be a perceptible lag between the first and last light because they don’t receive the commands simultaneously.
Each lighting technology’s integration is responsible for implementing the core set of lighting commands (found in the Light integration). If a lighting technology doesn’t support transactions natively, then requests to perform a transition action are simply ignored.
In theory, the integration’s author could simulate transitions in software but, to my knowledge, no one has chosen to do it. My guess is because it’s beyond the normal responsibilities of an integration which only serves to expose the device’s native functionality (i.e. it’s a protocol translator).