News for hackers. Stuff that matters.
Re:Philips Hue blocks 3rd party lights by ocdtrekkie on Monday December 14, 2015 @05:43PM (#10734573)
In my code development, I've definitely found some fun cases. i2cs (newer protocol) devices require a checksum, and they respond a bit differently in some cases. So for instance, my code that does a Product Data Request to get the model info for a device isn't working for i2cs devices right now. I'm still working on that, probably tonight.

I'd think something like Mister House would probably do the sort of simple case you need without figuring out all of the INSTEON protocol.

Re:Philips Hue blocks 3rd party lights by rlpb on Monday December 14, 2015 @09:42PM (#10735573)
> I'd think something like Mister House would probably do the sort of simple case you need without figuring out all of the INSTEON protocol.

I'm a developer and I want to hook all kinds of things together. I don't need a GUI but would like full programmatic access. The case I have in mind would start off as a few lines of Python, probably using asyncio or something which is really powerful for this kind of thing. I'd prefer to just write a few lines against an API than have to use a framework, deal with maintaining a larger software deployment, etc.

Re:Philips Hue blocks 3rd party lights by ocdtrekkie on Tuesday December 15, 2015 @02:04AM (#10736379)
Well, as I said before, I doubt you'll find many devices easier to control than like 20 lines of Visual Basic (probably less in more concise languages).

But you are right that there are holes in their documentation. The code I'm using does a good job showing unknown commands though, so it's pretty easy to fill in what's missing. I think IoT has a lot worse devices, documentation wise.