node-lifx
node-lifx copied to clipboard
Node.js implementation of the LIFX LAN protocol :bulb:
From looking at the Git branches, there was work done to create a newer version in 2017. This work was never completed, and any merged pull request since `0.8.0` haven't...
I went ahead and ran `npm install` and it found quite a few vulnerable packages: ``` found 450 vulnerabilities (239 low, 206 moderate, 4 high, 1 critical) ``` Running `npm...
In newer versions of Node.js, using `new Buffer` is now deprecated. https://nodejs.org/en/docs/guides/buffer-constructor-deprecation/ Instead, you should use `new Buffer.alloc(size)` or `new Buffer.from('c469ea095c6adf13', 'hex')`. Changing it might cause compatibility issues in older...
I noticed the minimum Kelvin value is set to `2500`: ```js { HSBK_MINIMUM_KELVIN: 2500, HSBK_DEFAULT_KELVIN: 3500, HSBK_MAXIMUM_KELVIN: 9000, } ``` But the LIFX Mini Day & Night bulbs go down...
Using the example, the getState() and getHardwareVersion() time out, this used to work. Am I the only one experiencing this issue? Bulb is on firmware 2.1 according to the LIFX...
For whatever reason, this isn't working for me in Windows. There's no issue or error, I just don't see any clients showing up. ```js const fs = require('fs') const LifxClient...
Thanks for the great project. I'm currently using it in a non-node environment with minimal shimming on dgram. Everything works, but the webpack size is quite large. It can be...
Groups
Bulbs might be grouped together. Bulbs may be requested by group. Commands might be send to a group.
I encountered the issue while testing Node-RED node plugin [node-red-contrib-node-lifx](https://github.com/jdomeij/node-red-contrib-node-lifx). The two of my lights were not listed on Node-RED UI even though they show up when using node-lifx directly....