Kakifrucht
commented
6 years ago Further test conclude that simply toggling on the lights might trigger this issue. The lights won't fall back to the last brightness they have received and instead start on brightness 0. There might not be much I could do to fix this, besides always resending a brightness command after turning the light back on. This would however cause additional congestion for a rather rare bug, that can also be fixed by physically toggling the light.
When strobing the lights via the StrobeController they sometimes do not retain the last brightness sent to them. This issue appears to be difficult to reproduce, as it either happens repeatedly throughout a listening session to always the same light bulbs, or it doesn't happen at all.
This might be an issue with Philips API or even a hardware issue, as we do send the updated brightness value with the "on" command at the same time.