Yes I tried and HS got the commands I issued and reject them. Both X10 and Insteon attempts are failing. With X10 devices you have an X10 address that is A1 etc. With Insteon there is no X10 address, but there is a reference number that is the order of the entry of the devices. So in the Status screen of HS there is a column marked "code." For X10 devices this has A1, A2 etc. and for Insteon devices this is #1, #2 etc.
There is also Location:Device format used in the Control:Device Operation dialogs to control Insteon devices. I tried several types of commands but I have yet to get one to work:
"#1 on"
"Attic:Hall on"
"Device:Attic:Hall on"
Now first I have to get X10 commands to work just as you have in the documentation. I had thought this was working, but now I realize it is not. In Xlobby I chose Plugin xSeer, "Command" Exec_X10, and variables A1 on. In Homeseer I found in the log "Invalid command attempted: A1 on" Without Homeseer I can go to the Command screen and set A1 on and it works. "12/16/2006 12:29:04 AM Info Device: Tap-Linked Device (A1) ON "
The plugin is connected just fine and HS prints out the command it is rejecting in the log so it is not connectivity. I must be doing something wrong.
- Daniel
fletch wrote:Anthro,
I don't have any Insteon devices running natively. But I believe that ExecX10 will work to control Insteon devices. I know there is at least one person using Insteon devices natively, he didn't mention any problems with this method. Have you tried it yet?
Aaron