Any help, please? For example, let's say that I want to buy a USB interface (for a controller), a motion sensor, and a light switch (eg. a micro dimmer). I want to plug the USB interface into a modern Linux distribution and speak to it to read motion and the switch and control the light (and configure the switch to operate the light directly without the controller).
Where do I find documentation on:
* What drivers I'll need for the USB interface to get to something I can talk to from userspace, whether this is Free Software, whether I'll need external drivers or not and where I might get these.
* The protocol to speak to the USB interface from userspace.
* The protocol to speak to each of the devices over the interface.
I've spent hours looking, and I only feel that I have half the answers. For example the dimmer is documented at http://www.insteon.com/developer/#devdocs but the motion sensor is not. And I still have no idea about the USB end.
The madreporite.com site I provided above has some decent documentation on device IDs and commands for a lot of devices. And as you can see from the link I provided, communication with the devices is generally pretty simple, 8 or 21 bytes sent over a serial connection, that can be written in a few lines of code. Receiving is a bit more complicated, but he provides sample code for that as well.
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.
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.
Since I've been so unhappy with home automation software I've found, not doing exactly what I want, I've started building my own in VB .NET. The basics, plus what I specifically want it to do.
X10 is outright terrible. It was designed before nearly as much signal interference existed on powerline, so now you need tons of phase couplers and filters to get a good signal. INSTEON's mesh network (and dual-band powerline/RF) jumps signal issues far better. INSTEON's newer devices also drop support for X10, FYI.