Status request

Posted on
Sat May 01, 2004 8:20 pm
jrickmd offline
Posts: 109
Joined: Jun 01, 2003
Location: Texas

Status request

I've been working with some new equipment and have just started using status requests. I was annoyed in that I send one status request to my I/O link and it sends me 13 status answers in a row. What annoyed me more is that my time stamp attachment fired off with every one. So I went into the attachment to ignore those requests and saw that the statement was already there:

Code: Select all
If functionType is NOT x10StatusRequest


Hmmm. So I had the script log what an "x10StatusRequest" was ("xF15") and what it was receiving when is sent a

Code: Select all
send x10 status request to address "G1"


That ended up being "xF13". Therefore it was allowing all status requests through... where is the mix up here and why does the I/O link send so many status reports when requested ONCE. :shock:

Rick

Rick

Posted on
Sun May 02, 2004 8:33 am
matt (support) offline
Site Admin
User avatar
Posts: 21429
Joined: Jan 27, 2003
Location: Texas

Re: Status request

Morning Rick,

x10StatusRequest = xF15
x10StatusOn = xF13
x10StatusOff = xF14

Typically, you send an X10 status request to a 2-way module, then it responds with either a status on or status off. Some 2-way modules respond with a normal on/off command instead, and some send additional information like a preset dim value. I think you want to ignore multiple x10StatusOn/Off responses.

Are you receiving the multiple responses back-to-back very quickly? If so, then I wonder if your interface is sending the commands to Indigo multiple times -- I somewhat doubt that the I/O link is really sending 13 status answers onto the power line. What kind of repeater do you have? I wonder if that might have something to do with it...

Regards,
Matt

Posted on
Sun May 02, 2004 11:29 am
jrickmd offline
Posts: 109
Joined: Jun 01, 2003
Location: Texas

(No subject)

Here's a sample of the log output:

Code: Select all
11:56:43 AM, 5/2/04   Sent X10   "Garage open sensor" status request
11:56:43 AM, 5/2/04   Received X10   "Garage open sensor" status off
11:56:43 AM, 5/2/04   Script   updated time stamp for F2 (index 82) to Sunday, May 2, 2004 11:56:43 AM
11:56:43 AM, 5/2/04   Received X10   "Garage open sensor" status off
11:56:43 AM, 5/2/04   Script   updated time stamp for F2 (index 82) to Sunday, May 2, 2004 11:56:43 AM
11:56:44 AM, 5/2/04   Received X10   "Garage open sensor" status off
11:56:44 AM, 5/2/04   Script   updated time stamp for F2 (index 82) to Sunday, May 2, 2004 11:56:44 AM
11:56:44 AM, 5/2/04   Received X10   "Garage open sensor" status off
11:56:44 AM, 5/2/04   Script   updated time stamp for F2 (index 82) to Sunday, May 2, 2004 11:56:44 AM
11:56:44 AM, 5/2/04   Received X10   "Garage open sensor" status off
11:56:44 AM, 5/2/04   Script   updated time stamp for F2 (index 82) to Sunday, May 2, 2004 11:56:44 AM
11:56:44 AM, 5/2/04   Received X10   "Garage open sensor" status off
11:56:44 AM, 5/2/04   Script   updated time stamp for F2 (index 82) to Sunday, May 2, 2004 11:56:44 AM
11:56:45 AM, 5/2/04   Received X10   "Garage open sensor" status off
11:56:45 AM, 5/2/04   Script   updated time stamp for F2 (index 82) to Sunday, May 2, 2004 11:56:45 AM
11:56:45 AM, 5/2/04   Received X10   "Garage open sensor" status off
11:56:45 AM, 5/2/04   Script   updated time stamp for F2 (index 82) to Sunday, May 2, 2004 11:56:45 AM
11:56:45 AM, 5/2/04   Received X10   "Garage open sensor" status off
11:56:45 AM, 5/2/04   Script   updated time stamp for F2 (index 82) to Sunday, May 2, 2004 11:56:45 AM
11:56:45 AM, 5/2/04   Received X10   "Garage open sensor" status off
11:56:45 AM, 5/2/04   Script   updated time stamp for F2 (index 82) to Sunday, May 2, 2004 11:56:45 AM
11:56:45 AM, 5/2/04   Received X10   "Garage open sensor" status off
11:56:45 AM, 5/2/04   Script   updated time stamp for F2 (index 82) to Sunday, May 2, 2004 11:56:45 AM
11:56:46 AM, 5/2/04   Received X10   "Garage open sensor" status off
11:56:46 AM, 5/2/04   Script   updated time stamp for F2 (index 82) to Sunday, May 2, 2004 11:56:46 AM
11:56:46 AM, 5/2/04   Received X10   "Garage open sensor" status off
11:56:46 AM, 5/2/04   Script   updated time stamp for F2 (index 82) to Sunday, May 2, 2004 11:56:46 AM
11:56:46 AM, 5/2/04   Received X10   "Garage open sensor" status off
11:56:46 AM, 5/2/04   Script   updated time stamp for F2 (index 82) to Sunday, May 2, 2004 11:56:46 AM
11:56:46 AM, 5/2/04   Received X10   "Garage open sensor" status off


I don't have any repeaters or signal amplifiers installed. :cry:

Rick

Rick

Posted on
Sun May 02, 2004 12:06 pm
matt (support) offline
Site Admin
User avatar
Posts: 21429
Joined: Jan 27, 2003
Location: Texas

(No subject)

Do you have any other 2-way modules that respond to the status request command? If so, do they also show this problem? I'm thinking there is an incompatibility between the I/O link and your X10 interface (PowerLinc USB or CM11?) that is causing the interface to get confused. I could try to add some filter logic to ignore these commands -- the trick will be to not ignore commands that were really put on the power line multiple times. :(

Matt

Posted on
Sun May 02, 2004 2:53 pm
jrickmd offline
Posts: 109
Joined: Jun 01, 2003
Location: Texas

(No subject)

support wrote:
Do you have any other 2-way modules that respond to the status request command? If so, do they also show this problem? I'm thinking there is an incompatibility between the I/O link and your X10 interface (PowerLinc USB or CM11?) that is causing the interface to get confused. I could try to add some filter logic to ignore these commands -- the trick will be to not ignore commands that were really put on the power line multiple times. :(

Matt


I had a LampLinc 2-way sitting around. plugged it in and set it up with the device name "Tester". This is the log of its resulting status request:

Code: Select all
3:45:33 PM, 5/2/04   Sent X10   "Tester" status request
3:45:35 PM, 5/2/04   Received X10   "Tester" preset dim to 100
3:45:35 PM, 5/2/04   Script   updated time stamp for A6 (index 6) to Sunday, May 2, 2004 3:45:35 PM
3:45:35 PM, 5/2/04   Received X10   "Tester" preset dim to 100
3:45:35 PM, 5/2/04   Script   updated time stamp for A6 (index 6) to Sunday, May 2, 2004 3:45:35 PM
3:45:35 PM, 5/2/04   Received X10   "Tester" preset dim to 100
3:45:35 PM, 5/2/04   Script   updated time stamp for A6 (index 6) to Sunday, May 2, 2004 3:45:35 PM
3:45:35 PM, 5/2/04   Received X10   "Tester" preset dim to 100
3:45:35 PM, 5/2/04   Script   updated time stamp for A6 (index 6) to Sunday, May 2, 2004 3:45:35 PM
3:45:35 PM, 5/2/04   Received X10   "Tester" preset dim to 100
3:45:35 PM, 5/2/04   Script   updated time stamp for A6 (index 6) to Sunday, May 2, 2004 3:45:35 PM
3:45:35 PM, 5/2/04   Received X10   "Tester" preset dim to 100
3:45:35 PM, 5/2/04   Script   updated time stamp for A6 (index 6) to Sunday, May 2, 2004 3:45:35 PM
3:45:36 PM, 5/2/04   Received X10   "Tester" preset dim to 100
3:45:36 PM, 5/2/04   Script   updated time stamp for A6 (index 6) to Sunday, May 2, 2004 3:45:36 PM
3:45:36 PM, 5/2/04   Received X10   "Tester" preset dim to 100
3:45:36 PM, 5/2/04   Script   updated time stamp for A6 (index 6) to Sunday, May 2, 2004 3:45:36 PM
3:45:36 PM, 5/2/04   Received X10   "Tester" preset dim to 100
3:45:36 PM, 5/2/04   Script   updated time stamp for A6 (index 6) to Sunday, May 2, 2004 3:45:36 PM
3:45:36 PM, 5/2/04   Received X10   "Tester" preset dim to 100
3:45:36 PM, 5/2/04   Script   updated time stamp for A6 (index 6) to Sunday, May 2, 2004 3:45:36 PM
3:45:36 PM, 5/2/04   Received X10   "Tester" preset dim to 100
3:45:36 PM, 5/2/04   Script   updated time stamp for A6 (index 6) to Sunday, May 2, 2004 3:45:36 PM
3:45:36 PM, 5/2/04   Received X10   "Tester" preset dim to 100
3:45:36 PM, 5/2/04   Script   updated time stamp for A6 (index 6) to Sunday, May 2, 2004 3:45:36 PM
3:45:36 PM, 5/2/04   Received X10   "Tester" preset dim to 100
3:45:37 PM, 5/2/04   Script   updated time stamp for A6 (index 6) to Sunday, May 2, 2004 3:45:37 PM
3:45:37 PM, 5/2/04   Received X10   "Tester" preset dim to 100
3:45:37 PM, 5/2/04   Script   updated time stamp for A6 (index 6) to Sunday, May 2, 2004 3:45:37 PM
3:45:37 PM, 5/2/04   Received X10   "Tester" preset dim to 100
3:45:37 PM, 5/2/04   Script   updated time stamp for A6 (index 6) to Sunday, May 2, 2004 3:45:37 PM
3:45:37 PM, 5/2/04   Received X10   "Tester" preset dim to 100
3:45:37 PM, 5/2/04   Script   updated time stamp for A6 (index 6) to Sunday, May 2, 2004 3:45:37 PM
3:45:37 PM, 5/2/04   Received X10   "Tester" preset dim to 100
3:45:37 PM, 5/2/04   Script   updated time stamp for A6 (index 6) to Sunday, May 2, 2004 3:45:37 PM
3:45:37 PM, 5/2/04   Received X10   "Tester" preset dim to 100
3:45:37 PM, 5/2/04   Script   updated time stamp for A6 (index 6) to Sunday, May 2, 2004 3:45:37 PM
3:45:37 PM, 5/2/04   Received X10   "Tester" preset dim to 100
3:45:37 PM, 5/2/04   Script   updated time stamp for A6 (index 6) to Sunday, May 2, 2004 3:45:37 PM
3:45:37 PM, 5/2/04   Received X10   "Tester" preset dim to 100
3:45:37 PM, 5/2/04   Script   updated time stamp for A6 (index 6) to Sunday, May 2, 2004 3:45:37 PM
3:45:38 PM, 5/2/04   Received X10   "Tester" preset dim to 100
3:45:38 PM, 5/2/04   Script   updated time stamp for A6 (index 6) to Sunday, May 2, 2004 3:45:38 PM
3:45:38 PM, 5/2/04   Received X10   "Tester" preset dim to 100
3:45:38 PM, 5/2/04   Script   updated time stamp for A6 (index 6) to Sunday, May 2, 2004 3:45:38 PM
3:45:38 PM, 5/2/04   Received X10   "Tester" preset dim to 100
3:45:38 PM, 5/2/04   Script   updated time stamp for A6 (index 6) to Sunday, May 2, 2004 3:45:38 PM
3:45:38 PM, 5/2/04   Received X10   "Tester" preset dim to 100
3:45:38 PM, 5/2/04   Script   updated time stamp for A6 (index 6) to Sunday, May 2, 2004 3:45:38 PM
3:45:38 PM, 5/2/04   Received X10   "Tester" preset dim to 100
3:45:38 PM, 5/2/04   Script   updated time stamp for A6 (index 6) to Sunday, May 2, 2004 3:45:38 PM
3:45:38 PM, 5/2/04   Received X10   "Tester" preset dim to 100
3:45:38 PM, 5/2/04   Script   updated time stamp for A6 (index 6) to Sunday, May 2, 2004 3:45:38 PM
3:45:38 PM, 5/2/04   Received X10   "Tester" preset dim to 100
3:45:38 PM, 5/2/04   Script   updated time stamp for A6 (index 6) to Sunday, May 2, 2004 3:45:38 PM
3:45:39 PM, 5/2/04   Received X10   "Tester" preset dim to 100
3:45:39 PM, 5/2/04   Script   updated time stamp for A6 (index 6) to Sunday, May 2, 2004 3:45:39 PM
3:45:39 PM, 5/2/04   Received X10   "Tester" preset dim to 100
3:45:39 PM, 5/2/04   Script   updated time stamp for A6 (index 6) to Sunday, May 2, 2004 3:45:39 PM
3:45:39 PM, 5/2/04   Received X10   "Tester" preset dim to 100
3:45:39 PM, 5/2/04   Script   updated time stamp for A6 (index 6) to Sunday, May 2, 2004 3:45:39 PM
3:45:39 PM, 5/2/04   Received X10   "Tester" preset dim to 100
3:45:39 PM, 5/2/04   Script   updated time stamp for A6 (index 6) to Sunday, May 2, 2004 3:45:39 PM
3:45:39 PM, 5/2/04   Received X10   "Tester" preset dim to 100
3:45:39 PM, 5/2/04   Script   updated time stamp for A6 (index 6) to Sunday, May 2, 2004 3:45:39 PM
3:45:39 PM, 5/2/04   Received X10   "Tester" preset dim to 100
3:45:39 PM, 5/2/04   Script   updated time stamp for A6 (index 6) to Sunday, May 2, 2004 3:45:39 PM
3:45:39 PM, 5/2/04   Received X10   "Tester" preset dim to 100
3:45:39 PM, 5/2/04   Script   updated time stamp for A6 (index 6) to Sunday, May 2, 2004 3:45:39 PM
3:45:39 PM, 5/2/04   Received X10   "Tester" preset dim to 100
3:45:40 PM, 5/2/04   Script   updated time stamp for A6 (index 6) to Sunday, May 2, 2004 3:45:40 PM
3:45:40 PM, 5/2/04   Received X10   "Tester" preset dim to 100
3:45:40 PM, 5/2/04   Script   updated time stamp for A6 (index 6) to Sunday, May 2, 2004 3:45:40 PM
3:45:40 PM, 5/2/04   Received X10   "Tester" preset dim to 100
3:45:40 PM, 5/2/04   Script   updated time stamp for A6 (index 6) to Sunday, May 2, 2004 3:45:40 PM
3:45:40 PM, 5/2/04   Received X10   "Tester" preset dim to 100
3:45:40 PM, 5/2/04   Script   updated time stamp for A6 (index 6) to Sunday, May 2, 2004 3:45:40 PM
3:45:40 PM, 5/2/04   Received X10   "Tester" preset dim to 100
3:45:40 PM, 5/2/04   Script   updated time stamp for A6 (index 6) to Sunday, May 2, 2004 3:45:40 PM
3:45:40 PM, 5/2/04   Received X10   "Tester" preset dim to 100
3:45:40 PM, 5/2/04   Script   updated time stamp for A6 (index 6) to Sunday, May 2, 2004 3:45:40 PM
3:45:41 PM, 5/2/04   Received X10   "Tester" preset dim to 100
3:45:41 PM, 5/2/04   Script   updated time stamp for A6 (index 6) to Sunday, May 2, 2004 3:45:41 PM
3:45:41 PM, 5/2/04   Received X10   "Tester" preset dim to 100
3:45:41 PM, 5/2/04   Script   updated time stamp for A6 (index 6) to Sunday, May 2, 2004 3:45:41 PM
3:45:41 PM, 5/2/04   Received X10   "Tester" preset dim to 100
3:45:41 PM, 5/2/04   Script   updated time stamp for A6 (index 6) to Sunday, May 2, 2004 3:45:41 PM
3:45:41 PM, 5/2/04   Received X10   "Tester" preset dim to 100
3:45:41 PM, 5/2/04   Script   updated time stamp for A6 (index 6) to Sunday, May 2, 2004 3:45:41 PM


Seems to not just be the I/O linc's problem. Of note, I happened to notice that when the multiple status request items are interrupted by another device's log item (i.e., "Upstairs motion" through the W800rf), the "status log items" stop at that point (e.g., if only one status log message has been received when another log item is printed, only that one status log message remains in the Log. The other 12-20 items don't get listed). Another puzzle piece? Let me know what else I can do to figure this one out.

Edit: BTW, I have a Powerlink USB.

Thanks,

Rick

Rick

Posted on
Sun May 02, 2004 3:22 pm
matt (support) offline
Site Admin
User avatar
Posts: 21429
Joined: Jan 27, 2003
Location: Texas

(No subject)

Hmmm.. the more I look into this, the more it seems like it is an Indigo bug. I cannot get the repeats in my alpha of Indigo 2.0, but do occasionally get it in 1.5. Let me dig a bit more into this one.

Matt

Posted on
Sun May 02, 2004 8:50 pm
matt (support) offline
Site Admin
User avatar
Posts: 21429
Joined: Jan 27, 2003
Location: Texas

(No subject)

Alright, I can definitely take the blame for this undesired anomaly (politically correct term for a bug). There was some confusion in my code where the status request output queue blocker didn't get along with the power failure status checker. Anyhow, it should be better behaved now. Thanks for the bug report.

http://www.perceptiveautomation.com/ind ... o_beta.dmg

Regards,
Matt

Page 1 of 1

Who is online

Users browsing this forum: No registered users and 14 guests