-
Notifications
You must be signed in to change notification settings - Fork 76
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
API for Alarms #16
Comments
Any update on this? Right now Lightbow approximates alarms and timers by sending the commands from the running app after the appropriate amounts of time, but it isn't nearly as good as the experience provided for Philips hue, where the timer information is stored on the lighting hardware itself, and my app is out of the equation (in case the phone is off or the app isn't open) It's especially obvious in a mixed setup, where users have the Philips hue react on time, but the LIFX doesn't know about the alarm. |
I know its possible to "schedule" some things using IFTTT. Also the LIFX App itself supports alarm features. The first uses LIFX cloud, the latter doesn't require any internet connection at all I believe (after you've scheduled the alarm of course). So it seems possible, but it's not open for developers? |
I'm trying to avoid using IFTTT because users always complain (rightfully so) about latency and security, and the more I can accomplish locally, the better. I was trying to avoid reverse-engineering the messages sent by the LIFX app in case they change those later, and I don't want to accidentally interfere with normal bulb operation. The best solution is official API, but if nothing comes soon, I may try one of those two alternatives. Thank you for the suggestions. |
The title says it all. It would be great to take out all the warning strings I have in my app about alarms and timers unable to be stored on LIFX hardware and allow feature parity with Philips hue on this front. Ideally, you guys would expose both Alarms and Timers, but Alarms is the more highly requested feature from my LIFX users.
The text was updated successfully, but these errors were encountered: