-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LIFX Example integration #5
Comments
I added an LIFX example on neeo-sdk-examples Github. you can see the pull request here. |
Thanks @GeertWille for the first working version, great job! I think the following (minor) features might improve the adapter:
@GeertWille maybe you know more - there is currently no other option to control the LIFX lamp but communicate with the public REST (cloud) API? Like can we communicate directly with the LIFX lamp? |
@neophob what do you mean exactly with the Discrete Power commands for a single lamp? There is a power toggle button right now for every bulb? Yes it is possible to use the lan-api though I didn't find a good node implementation of it yet that's why I started with the Cloud API. I'll take a look or I can write a node implementation for the lan-api myself or if you find a good one let me know ;). |
@GeertWille This one looks interesting. https://github.com/MariusRumpf/node-lifx |
@nklerk Cool, I'll try to make time and make an example ;) |
@GeertWille @nklerk sounds interesting. the local lan protocol might be easier to implement - we dont need an API key. and it looks like discovery is also supported. @GeertWille: with "Discrete Power commands" I mean a power on/off button. for example you want to power on your lights when a sensor triggers - then the power toggle is not the best option if you want to ensure the lights are on |
thanks @nklerk and @GeertWille, will be included with the next release! |
Feature Request
CoS
The text was updated successfully, but these errors were encountered: