Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[PajamaGuy]

Help -

My V572RF32 picks up RF from a DS10A and translates it to PLC's for Device A9 (defined in AHP as a Door/Window switch).  The HC/UC as indicated via the Reports/General show the address as A9.  It IS associated (checkbox) with the Security system DS7000.

I have an SR731 Smart  () Repeater in the same closet as the V572.  My CM15A does NOT receive the RF from either the DS10a OR the V572 (and I just ordered another CM15A).

The Activity monitor DOES show the PLC's from the V572 - A9 (FrontDoor), A9 On, etc.

So if the CM15a is picking up the PLC's from the V572, and transmitting them via USB to the PC and AHP, why doesn't AHP act on them?  The Module (A9) doesn't change its state unless it receives RF.

What am I missing??

[Puck]

What am I missing??

To run a macro that is based on a Door/Window sensor from the V572RF32's PLC signal, do not select "Use Security" in the macro. Make it a macro based solely on its HC/UC.

If you define a macro to be triggered by a security device that was installed under OnAlert, even though they occupy a normal HC/UC, their macros will not trigger from a normal PLC signal.

When using the V572RF32 for their reception, I suggest simply defining your Door/Window sensors as an appliance switch in AHP, and not defined & installed as a Door/Window sensor under OnAlert.

[PajamaGuy]

I understand the macro thing - that's not what I'm talking about.

If one wants to use the state of a security sensor as a condition in a macro, the sensor must be installed (along with OnAlert). 

When you install a sensor into AHP, it's appearing that AHP's representation of it is only via RF.  Even though AHP assigns it an address, the module only responds to RF, not PLCs. - Then again, thinking about it with a clear head  - Sensors don't "do" anything, so a PLC command wouldn't change its state.

Crap - the problem is with the CM15A and its range (lack thereof) - I've ordered a 2nd one, and have an RMA for this one - (I really think the antenna is disconnected inside). 

As an aside - the WAF dropped a tad when at 3:30 this morning, every light in the house came on 100% bright.  Gotta love x10.....

[Puck]

If one wants to use the state of a security sensor as a condition in a macro, the sensor must be installed (along with OnAlert). 

You cannot use a senor's state as a macro condition (only as a Trigger). The only macro condition added by OnAlert is whether OnAlert is Armed or not.

Even though AHP assigns it an address, the module only responds to RF, not PLCs.

A security macro will not respond to a X10 RF Address either. They will only respond to to X10 RF Security Signal. As I stated above, you cannot trigger a security macro using it's X10 address as assigned by AHP/OnAlert.

Crap - the problem is with the CM15A and its range (lack thereof)

This is not the reason why your security macros will not run from a PLC signal created by the V572RF32. This is the reason why they will not run from the sensor's RF security signal directly.

[PajamaGuy]

You cannot use a senor's state as a macro condition (only as a Trigger). The only macro condition added by OnAlert is whether OnAlert is Armed or not.

I wouldn't argue with an expert - but - I'm already doing just that.  (Please don't take offence!  )

I have AHP and all the plug-in modules.
I have a DS10A in an AHP room called "Garage"  The DS10A was "installed" the the room and had the check-box for security device checked.  It's named "Side-Door".  Another DS10A is installed the same way and is named, "Overhead Door".   If the checkbox is checked, AHP monitors their state via RF, and the devices show up in the Security Sensors dropdowns - they can be then used as both triggers and conditions.

I have a macro that is triggered by the "Security Sensor" Side-Door, with the Condition of Security Sensor "Overhead Door" being CLOSED.  And it works.  A complimentary macro with the condition of the Side-Door being closed is also working.  The outcome of the macros is that either one flips a Phantom "One of the doors is open" switch which is a trigger for a macro that turns on/off a floodlight in the garage.

All of it works just fine IF and only IF the RF from the DS10As gets to the CM15A.  I was mistakenly thinking the PLCs tranceived by the V572 would work if the RF was out of range.

I really think that with all of my repositioning the CM15a, and strapping the 18" piece of coat hanger on and off, that the antenna became disconnected internally.  (I've ordered a 2nd one, and X10 is replacing the one I already have)

This is not the reason why your security macros will not run from a PLC signal created by the V572RF32. This is the reason why they will not run from the sensor's RF security signal directly.

I understand this - I need to position all of the elements, including SR731's so that all RF reaches the DS7000 AND the CM15a(s)

[Puck]

You cannot use a senor's state as a macro condition (only as a Trigger). The only macro condition added by OnAlert is whether OnAlert is Armed or not.

I wouldn't argue with an expert - but - I'm already doing just that.  (Please don't take offence!  )

I have AHP and all the plug-in modules.
I have a DS10A in an AHP room called "Garage"  The DS10A was "installed" the the room and had the check-box for security device checked.  It's named "Side-Door".  Another DS10A is installed the same way and is named, "Overhead Door".   If the checkbox is checked, AHP monitors their state via RF, and the devices show up in the Security Sensors dropdowns - they can be then used as both triggers and conditions.

I have a macro that is triggered by the "Security Sensor" Side-Door, with the Condition of Security Sensor "Overhead Door" being CLOSED.  And it works. 

No offence taken. I don't think there exists any expert on AHP, just users with varying degrees of experience. 

That being said, I would like to see an example of your macro that uses the state of a door/window sensor as a condition for another macro. I haven't used OnAlert triggered macros for my door/window sensors since I got my V572RF32, but I did create one yesterday before I posted, just to refresh my memory. The only security condition I seen was armed... all other security macro choices were just various triggers (as I seen and can recall). So I'm curious now to see how it is done, and will look into it more when I get home.


But now I am confused about why you are using a V572RF32 for your door/window sensors if you only want them to trigger OnAlert macros directly from the CM15A receiving their RF Security Signals?

[PajamaGuy]

...so how do I insert an image??

[Puck]

Click on "Additional Options" when posting and there is a browser for adding attachments there.

[Puck]

PajamaGuy: I see that condition now. I just installed a door/window sensor and its state now shows as a condition option. I don't recall ever seeing that before. Is this new with 3.228 or did I just not notice it before?

Thanks for the new information (for me anyways).

[PajamaGuy]

It's been there since I started X10'ing last November.

I imagine you can now see why (for me) it's important to get the RF to AHP.  By using the sensors as conditions, it saves flags for other things.  And AHP doesn't care if the sensor is really installed into the security system, checking that box only enables them to be in the security modules dropdown.

My DS7000 system is finally receiving all of the registered sensors.  I did have to replace a DS10a - as a note to others, it worked except for the heartbeat transmission - Security sensors transmit (RF) their state every 60 - 90 minutes to let the console know they're alive.  I had one that must have had a problem with that heartbeat, because although it would send status successfully every time the door was opened or closed, and it seemed to send a heartbeat when it was open, at night the console would start flashing after 4 hours of not receiving the heartbeat from the closed door.  Replacing the DS10a fixed the problem.