X10 Community Forum

🖥️ActiveHome Pro => ActiveHome Pro General => Software Problems & Bugs => Topic started by: X10 Ken on February 13, 2009, 04:57:48 PM

Title: PR511 Flood Light, Not a Light???
Post by: X10 Ken on February 13, 2009, 04:57:48 PM

When I use "Turn on all lights" in room "Outside", no on commands are sent for my PR511 Flood Lights.

When "Outside" "All units off" is used, an off command is   sent to the PR511.

So the question is: When is a light not a light?

The answer seems to be: When the light is a PR511.

This seems like a AHP bug to me.  Is it, or have I missed something?

Ken
===

Title: Re: PR511 Flood Light, Not a Light???
Post by: Dan Lawrence on February 13, 2009, 05:11:19 PM

It's not an AHP bug.   The commands in the Rooms are "Turn All Lights on in ROOM name" and " Turn All UNITS off in ROOM name".   A PRS11 is a devise, not a Light.

Title: Re: PR511 Flood Light, Not a Light???
Post by: HA Dave on February 13, 2009, 05:30:09 PM

My floodlight does react to the "All Lights On" command... I know that only because one of the floods are on the same House code as the alarm.

I am not sure what your problem is X10 Ken do you have a PR511 in the "outside room"... you could try replacing it with a dummy lamp module with the PR511's unit code.

Title: Re: PR511 Flood Light, Not a Light???
Post by: Tuicemen on February 13, 2009, 05:45:16 PM

X10 Ken 
Not sure which version of AHP your running!
Version 3.236 works how you discribed. Is it a bug?
Well I'd say so! Using a thirdparty program and issuing an all lights on turned it on!  ::)
So if it was classed  a "Device" as Dan States not a "Light"  then it shouldn't have turned on for  Dave or me! ::) :'
 

Title: Re: PR511 Flood Light, Not a Light???
Post by: Knightrider on February 13, 2009, 06:24:13 PM

Rooms in AHP should not be confused with House Codes.  An ALL LIGHTS ON issued by an x10 controller will trigger all lights on that house code.  Sometimes users of AHP will have different light modules in different rooms on the same house code.  To prevent these from triggering, AHP will turn on the lights in a room one at a time and not issue the ALL LIGHTS ON command over the powerlines.  I believe that the ALL LIGHTS ON command can be used in macros and the like under the advanced functions tab.
I'm also guessing that some of the SDK programs put the A-L-O command on the powerline.
Long story short, the Turn on all lights in a specific room is not the same as an A-L-O command.

Clear as mud, right?

Title: Re: PR511 Flood Light, Not a Light???
Post by: Dan Lawrence on February 13, 2009, 07:29:15 PM

I ran a test (AHP 3.228, BTW) for my Outside room (PRS511 and a Lamppost).  When Turn all Units off, both the PRS551 and the Lamppost turned off, but when Turn all Lamps on was clicked, only the Lamppost turned on.  My PRS511 is defined as a Device, not as a lamp in AHP.

Title: Re: PR511 Flood Light, Not a Light???
Post by: X10 Ken on February 13, 2009, 08:16:51 PM

Quote from: Dan Lawrence on February 13, 2009, 07:29:15 PM

My PRS511 is defined as a Device, not as a lamp in AHP.

Yes AHP is defining it as a Device, not a lamp.  However, "All Lights On" on a hard wired controller set to house code K does turn on the flood light.  This means that the flood responds to "K All Lights On" and the flood thinks of itself as a light.

In that:
1.  It is a light.
2.  It responds "All Lights On"
3.  AHP does not consider it a light.

This situation must be defined as a bug in AHP.

Anyone disagree?

Ken
===

Title: Re: PR511 Flood Light, Not a Light???
Post by: Knightrider on February 13, 2009, 08:20:48 PM

I'd consider it a programming oversight. 

Title: Re: PR511 Flood Light, Not a Light???
Post by: HA Dave on February 13, 2009, 08:55:52 PM

Quote from: X10 Ken on February 13, 2009, 08:16:51 PM

This situation must be defined as a bug in AHP.

OK.... AHP has another bug.

Title: Re: PR511 Flood Light, Not a Light???
Post by: Dan Lawrence on February 13, 2009, 11:13:39 PM

Quote from: Dave_x10_L on February 13, 2009, 08:55:52 PM

Quote from: X10 Ken on February 13, 2009, 08:16:51 PM

This situation must be defined as a bug in AHP.

OK.... AHP has another bug.

That "bug" has been part of AHP since the first release.  Every version I've had has it.