Closed sinnottj closed 8 years ago
The protocol is based on UDP, which does not guarantee that the packets arrive correct. The LIFX protocol has a method to request if a packet was successful send, the implementation in this library is pending and documented in #14. I assume that the LIFX lamps go to some kind of power saving mode after a while. The mobile apps request various infos including an echo request which might wake it up again. I will see if I get info for that in the LIFX Developer Forum. Another suggestion is that these packages are lost on the way to the way to the bulb, while routed through the network.
Asking in the LIFX developer forum did not bring any clues. There is no power saving used by the lamp. I assume that this is udp or the network. Since there is a package confirmation now this should not be an issue any more. Closing this since there is nothing I can to.
Hi,
I've been testing this library and I think it's really good!
However, I've observed a problem with the 'state change' methods (light.on, light.off, light.color) occasionally not succeeding. This only happens when the client has been idle for some time (e.g. running for 1 hour without being used.)
I've observed this issue using the interactive-cli.js script. I start the script and the initial tests work fine. I then leave the script running in the background for a while (e.g. 1 hour). When I come back to the script and try to turn the lights on/off or change their colour, it seems to work but nothing happens to the physical lights. When I try again the lights start responding and all seems to be OK (and sometimes it takes a few goes before the lights start to respond.)
If it's any use, here are some examples of the debugging output from interactive-cli.js.
First - here's when I tried to turn the lights off and it failed:
Second - here's where I turned the lights off and it worked:
Regards,
James.