No, but generally speaking, if you can control it with a browser, you can control it with AMX, you just need to reverse engineer the HTML a bit. I suppose the same could be said if it's app controlled, just not quite as easily. It really depends on how much work you want to put into it. Honestly, I can't make any money doing things like that for a customer, I tell them just to launch the app. For myself, I might putter around a bit, but I'd just get what I needed working, it wouldn't be production level.
You're in luck! The LIFX guys released a beta of their cloud API two weeks ago. The only bummer is though, as with every self respecting modern API endpoint, it's https (which for some reason I cannot possibly comprehend, AMX still don't have any method for enabling you do deal with this neatly in NetLinx).
If it's just for a demo, you may find it simpler to spin up a proxy machine with the LIFX ruby gem along with the lifx-http gem which will provide a local web service.
Not more https .. sheesh.. for a light bulb.. sheesh.
I have created a https gateway app for PC, that netllinx can pass commands to. That's been my answer to the lack of https in netlinx. I may be able to give you a copy if you wish to consider it as a beta test.
This https issue is going to come up more and more. Damn nuisance.
Not more https .. sheesh.. for a light bulb.. sheesh.
What's wrong with a little SSL? It's 2015, using unencrypted comms for anything that's not on a completely isolated communication bus is just plain irresponsible.
Although it's 'just a light bulb', obtain access to read the state of every bulb in a premises and you can run a monitoring script on that for a couple of weeks, see common movement patterns and pick the optimum time to knock over the place. That and the 13 year old kid next door can switch the bedroom lights on at 3am. Their 60LoWPAN mesh is also encrypted now after this.
Yeah, I was just being a little sarcastic. Although, I frankly wouldn't be making too many devices available to the outside world in the first instance, such as these lights (note that we've been doing networks behind routers for a long time now).
As for the 13 year old next door getting in, well, someone didn't protect the house network correctly in the first place and there will be more vunerable devices available, like computers.
Anyway, I don't really object to https, but like most things in life, I should be given an option, not dictated to; that's what I object to
(Update: I suppose, since these bulbs are wifi servers in their own right, there is a hieghtened security requirement. I've not had any experience with them yet, so I'm not sure if they are wifi clients or servers. If they are simple clients, it's not so bad).
I have two LIFX bulbs (got them from the Kickstarter campaign) and their slick. I created an Android app to control them and it was just straight UDP. I've not messed with them lately since the whole cloud thing, but I'd imagine you can still control them via UDP.
I'll have to open up my app and see if it can be used with Duet. I believe I wrote it against the 6 or 7 language, so not sure if it'll work 100% with 1.4.
I have two LIFX bulbs (got them from the Kickstarter campaign) and their slick. I created an Android app to control them and it was just straight UDP. I've not messed with them lately since the whole cloud thing, but I'd imagine you can still control them via UDP.
I'll have to open up my app and see if it can be used with Duet. I believe I wrote it against the 6 or 7 language, so not sure if it'll work 100% with 1.4.
Hi jjames,
very interesting, with which protocol you've worked to control Lifx with AMX, SDK or API?
Can you write an example of command?
I know it was a while back when I said I'd look through my app, but I can't seem to find it. However, they (LIFX) just opened up their LAN and HTTP protocol, so it should be pretty easy to hack something up.
What's wrong with a little SSL? It's 2015, using unencrypted comms for anything that's not on a completely isolated communication bus is just plain irresponsible.
Although it's 'just a light bulb', obtain access to read the state of every bulb in a premises and you can run a monitoring script on that for a couple of weeks, see common movement patterns and pick the optimum time to knock over the place. That and the 13 year old kid next door can switch the bedroom lights on at 3am. Their 60LoWPAN mesh is also encrypted now after this.
I think any crook with the means to do this would simply get a high paying tech job. The average B&E is not done by people with a degree in computer science. SSL for a lightbulb is like having a combination lock on every door in your house. I guess its secure, but it takes a half an hour to get from the kitchen to the bathroom.
Paul
I think any crook with the means to do this would simply get a high paying tech job. The average B&E is not done by people with a degree in computer science. SSL for a lightbulb is like having a combination lock on every door in your house. I guess its secure, but it takes a half an hour to get from the kitchen to the bathroom.
Paul
fortunately SSL is now supposed to be supported now in the Netlinx side.
fortunately SSL is now supposed to be supported now in the Netlinx side.
Still, spending 10 seconds to create an SSL packet so I can turn off the light is dumb. I just don't get why anyone would want a $100 lightbulb in the first place. Its a solution looking for a problem if you ask me.
Paul
Comments
now that we have these we just need the last step: Low voltage lighitng/wiring in all our homes.
I need the lamp for an exhibition, not for a customer.
http://developer.lifx.com/
If it's just for a demo, you may find it simpler to spin up a proxy machine with the LIFX ruby gem along with the lifx-http gem which will provide a local web service.
I have created a https gateway app for PC, that netllinx can pass commands to. That's been my answer to the lack of https in netlinx. I may be able to give you a copy if you wish to consider it as a beta test.
This https issue is going to come up more and more. Damn nuisance.
What's wrong with a little SSL? It's 2015, using unencrypted comms for anything that's not on a completely isolated communication bus is just plain irresponsible.
Although it's 'just a light bulb', obtain access to read the state of every bulb in a premises and you can run a monitoring script on that for a couple of weeks, see common movement patterns and pick the optimum time to knock over the place. That and the 13 year old kid next door can switch the bedroom lights on at 3am. Their 60LoWPAN mesh is also encrypted now after this.
Yeah, I was just being a little sarcastic. Although, I frankly wouldn't be making too many devices available to the outside world in the first instance, such as these lights (note that we've been doing networks behind routers for a long time now).
As for the 13 year old next door getting in, well, someone didn't protect the house network correctly in the first place and there will be more vunerable devices available, like computers.
Anyway, I don't really object to https, but like most things in life, I should be given an option, not dictated to; that's what I object to
(Update: I suppose, since these bulbs are wifi servers in their own right, there is a hieghtened security requirement. I've not had any experience with them yet, so I'm not sure if they are wifi clients or servers. If they are simple clients, it's not so bad).
I'll have to open up my app and see if it can be used with Duet. I believe I wrote it against the 6 or 7 language, so not sure if it'll work 100% with 1.4.
Seriously! I have so many things in my house that run off of 12volts DC.
As far as lighting, I just installed super bright LED strips (also 12VDC) under my kitchen cupboard and love it.
Hi jjames,
very interesting, with which protocol you've worked to control Lifx with AMX, SDK or API?
Can you write an example of command?
Thank You
http://www.lifx.com/blogs/light-matters/39514435-introducing-the-lifx-developer-zone
I think any crook with the means to do this would simply get a high paying tech job. The average B&E is not done by people with a degree in computer science. SSL for a lightbulb is like having a combination lock on every door in your house. I guess its secure, but it takes a half an hour to get from the kitchen to the bathroom.
Paul
fortunately SSL is now supposed to be supported now in the Netlinx side.
Still, spending 10 seconds to create an SSL packet so I can turn off the light is dumb. I just don't get why anyone would want a $100 lightbulb in the first place. Its a solution looking for a problem if you ask me.
Paul