PR511 Floodlight Deal

Started by nybuck, March 13, 2010, 10:28:27 PM

Previous topic - Next topic

Tuicemen

pomprocker   I'm using mine with a CM15A so that may be the reason I can talk to the PR511s with a StatusRequest command  ??? ::) :'
I get nothing sending a StatusOn or StatusOff from the CM15A, the PR511s send those.
>!
Please Read Topic:
General Forum Etiquette
Before you post!

Brandt

Quote from: eagle on March 23, 2010, 10:09:14 PM
I have my 2 PR511s controlling interior lights.  Hence, when one or both of those devices come on and reported on the Activity Monitor, that's when I know the PR511s were triggered.

So as a workaround ... perhaps just set the PR511 to trigger a dummy or macro code to report that it was triggered?

r,
eagle

Yep thats what I said in reply #6:
http://forums.x10.com/index.php?topic=19957.msg112679#msg112679

eagle

Yes sir.  New users or visitors who don't have the PR floods however might not be able to understand the +code features.

Just added my own personal experience to help dumb it down a little.  :)

And believe me, when I was surfing the board a few months ago as a greeny, there were a lot of things being discussed here that was going over my head.  :)

r,
eagle


Charles Sullivan

Quote from: pomprocker on March 23, 2010, 06:50:11 PM
Quote from: Tuicemen on March 23, 2010, 05:02:28 PM
it does respond to the statusrequest with a statusOn or StatusOff a query doesn't work on my setup for any X10 device for some unknown reason, but I would think it should respond to it as well.

Sorry kinda lost ya there...

With heyu and a cm11a, I get nothing with status, status_on, or status_off. however heyu statusstate returns 0 when off only because it is reading its internal tables...not sure if the same thing is happening with yours

Pomprocker:
Look in the Heyu monitor or logfile for the PR511 response (StatusOn or StatusOff) to a Status command.  It takes about 3 seconds for a response on my PR511.

If still nothing, what is the date code sticker (inside the control compartment) on your PR511 ?  Mine is 08J41
Yesterday it worked.
Today it doesn't work.
X10 on Windows is like that.

HEYU - X10 Automation for Linux, Unix, and Mac OS X     http://www.heyu.org

Brandt

#19
The only thing I see in the logs was from around 1pm yesterday and I think thats when I was sending the heyu commands trying to get its status:


03/23 13:13:59  sndc addr unit       5 : hu O5  (security_light)
03/23 13:13:59  sndc func    StatusReq : hc O
03/23 13:14:02  rcvi func    StatusOff : hc O
03/23 13:14:02  rcvi func    StatusOff : hc O
03/23 13:15:00  sndc addr unit       5 : hu O5  (security_light)
03/23 13:15:00  sndc func     StatusOn : hc O
03/23 13:16:16  sndc func         Hail : hc O
03/23 13:34:58  sndc addr unit       5 : hu O5  (security_light)
03/23 13:34:59  sndc func    StatusOff : hc O

It would not have lit up at 1pm so I know this is probably from me sending commands. I don't see any other status type commands in the logs, so I'll have to check the date code when I get home.


EDIT:

Ok so using the house and unit code returns something on the command line, but using the alias does not. However both create log entries

DiskStation> heyu status o5
03/24 14:02:03  rcvi func    StatusOff : hc O
03/24 14:02:03  rcvi func    StatusOff : hc O
DiskStation> heyu status security_light
DiskStation>

DiskStation> heyu logtail
03/24 14:02:02  sndc addr unit       5 : hu O5  (security_light)
03/24 14:02:02  sndc func    StatusReq : hc O
03/24 14:02:03  rcvi func    StatusOff : hc O
03/24 14:02:03  rcvi func    StatusOff : hc O
03/24 14:02:17  sndc addr unit       5 : hu O5  (security_light)
03/24 14:02:18  sndc func    StatusReq : hc O
03/24 14:02:21  rcvi func    StatusOff : hc O
03/24 14:02:21  rcvi func    StatusOff : hc O






Charles Sullivan


pomprocker:
You are getting the correct StatusOn/StatusOff response from the PR511 but the command line is returning before the response is sent.  A more precise measure of the response time shows 2.9 seconds for my unit.  Setting "STATUS_TIMEOUT  3" in config (and restart) should keep the command line open long enough to reliably report the status there also. 
Yesterday it worked.
Today it doesn't work.
X10 on Windows is like that.

HEYU - X10 Automation for Linux, Unix, and Mac OS X     http://www.heyu.org

Brandt

Quote from: Charles Sullivan on March 24, 2010, 09:30:00 PM

pomprocker:
You are getting the correct StatusOn/StatusOff response from the PR511 but the command line is returning before the response is sent.  A more precise measure of the response time shows 2.9 seconds for my unit.  Setting "STATUS_TIMEOUT  3" in config (and restart) should keep the command line open long enough to reliably report the status there also. 



thanks no wonder it was random

SMF spam blocked by CleanTalk