Print

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

[sfphototour]

I made two macros, one on and the other off. I can get the macros to trigger a module only when I click run macro on computer. when I use the palm pad the switch on the screen changes to on but the light does not work. For some reason the switch is not receiving the commands from macro. This is the first macro I have tried to make. I have downloaded it saved it and tried on run from PC and store in interface.

[Puck]

sfphototour: Welcome to the forum. Can you post a copy of your macro? Please provide more information like house/unit codes of the macro, lamp, remote, and what is transceived along with any macro conditions. The more information you supply, the better our chances of figuring out what may be wrong.

[sfphototour]

The macro name is Bath on, the trigger is set to B3, next  Clicked the on button, and it resides in Bath Room. After that I added the Module Bath WS467 and its trigger is A6 and says On 100%. In the Use Conditions box it says Turn Bath WS467 On and the on is green. I clicked Store in interface. The other Macro is the same except I changed every thing to Off. When I click run Macro on each of them they work fine, but when I press the B3 button on palm pad, A6 module switch on screen says it turned on and both macros flash but the light does not come on, when I press the Off button on palm pad the switch on screen says Off but macros do not flash. I can click the switch on screen on&off or press A6 on pad and the light works works.

[Tuicemen]

sfphototour Are house codes A & B set to transceive in your Hardware Configuration Screen?
The Auto setting doesn't always detect 100%  and you may have to select specific!

[Puck]

Two other things to try (check):

After that I added the Module Bath WS467 and its trigger is A6 and says On 100%.

Under Tools/Preferences/Macro Options do you have "Issue On in place of Bright 100%" selected?

In the Use Conditions box it says Turn Bath WS467 On and the on is green. I clicked Store in interface.

Remove the conditions. If I am interpreting what you are saying correctly, you have a condition set up so that your macro will only turn on the WS467 if it is already on.

[sfphototour]

I clicked the box in macro options and set delay to zero. I then downloaded to interface and it works fine now. Thank you very much!!! I am going to try to make a macro now to turn entry light on at night when my x10 doorbell rings and turn off after 5 minutes. Thanks again!

[Jenn D]

I have tried everything that I could find, on this site, regarding macros that do not work.  This thread title fits my issue so I am posting it here.  Here is what I have...

Trigger Conditions Front Door - Sensor Triggered and
System is Armed Away or
System is Armed Home
End Trigger Conditions
Start Camera Scan
Start Recording Video
Start Automatic Still Record every 5 Seconds
E-mail Images - (to my e-mail)
E-mail Images - (to second e-mail)
Stop Automatic Still Record
WAIT for 5 minutes
Stop Recording Video
Stop Camera Scan

The :Armed" conditions are, I assume, sent from the remotes for the voice dialer.  I do have them set up and I can see them triggered from AHP.  I can see the door sensor opening and closing from the AHP interface.

I have checked my Hardware Configuration and have set the transceiver to Specific A
I have downloaded Macros and Timers, purged the macro events, saved, closed, and reopend AHP

If I arm the system and open the front door, nothing happens (except the phone call from the voice dialer telling me the sensor was activated).  If I press the macro button on the AHP interface, the macro runs as expected.

The one thing that I did notice, below the Conditions screen (at the bottom of the macro screen) is 2 buttons, "Store in Interface" and "Run from PC".  Next to that it says "Macro must be run from the PC".  I'm not sure if that is relevant but I am trying to give as much info as I can. I also can't find any place to tell it to run from the actual trigger (if there is such a thing).

I will say that I have had this macro running properly before and it triggered when I opened the door, but it stopped working and I do not know why.  I feel as though I'm missing something simple, but for the life of me I can't not figure out what.  I have had this system since Tuesday and have not been able to get it to work consistently.  Sensors work, and then don't.  I have to load a different interface (logmein has been suggested by many) in order to log in remotely when necessary, The low light cameras don't give any different picture than the "regular" cameras, and because I can't get the lamp module to work without unplugging my fios, I have to leave a light on to see anything in the video.  I am at my wits end, and am very frusterated. 

I have scoured this forum for things to try but I am fresh out of ideas as far as this module goes.  Any ideas would be helpful.  I can't even call support because their website say that they are only open Monday - Friday and the hours are when I am at work.  Help me Obee-one-kenobee (this forum), you are my only hope!

[HA Dave]

..................The one thing that I did notice, below the Conditions screen (at the bottom of the macro screen) is 2 buttons, "Store in Interface" and "Run from PC".  Next to that it says "Macro must be run from the PC".  I'm not sure if that is relevant but I am trying to give as much info as I can. I also can't find any place to tell it to run from the actual trigger (if there is such a thing).

OnAlert macros MUST be run from the PC.... which means the PC must be on and connected to the CM15A interface, and the AHP program running (although that may be debatable). If your running your cameras and such on the same house code (the letters) as your alarm... that could be (likely is) your problem. To cut down on the "clutter" of PLS (X10 Powerline Signals) you may want to just keep the camera ON (it actually can run 24/7).

............ I am at my wits end, and am very frusterated. 

It isn't really frustration.... there is a special emotional feeling people experience just before these things start working.... it does resemble frustration and could easily be misinterpreted for that. Hang in there... you got the forums attention... this will work.

[Jenn D]

OnAlert macros MUST be run from the PC.... which means the PC must be on and connected to the CM15A interface, and the AHP program running (although that may be debatable). If your running your cameras and such on the same house code (the letters) as your alarm... that could be (likely is) your problem. To cut down on the "clutter" of PLS (X10 Powerline Signals) you may want to just keep the camera ON (it actually can run 24/7).

I do have the PC connected and the program running, at least the program is open on my screen.  I changed the camera to house code B.  Still not responding to anything other than pressing the macro button in AHP.  Checked B in the Hardware Config, still nothing.  As far as keeping the cameras on... On means what?  I assume on means that they are powered on so you can view the picture when you click the module (which I believe I do)  I do not want them recording 24/7.  I just want them to start recording, for 5 minutes while cycling through the 3 cameras I have set up, when the door sensors are triggered AND when the voice dialer is armed (we're not home).  I hope on does not mean recording. 

I know I will eventually figure this out, I just hope it's soon. 

It isn't really frustration.... there is a special emotional feeling people experience just before these things start working.... it does resemble frustration and could easily be misinterpreted for that. Hang in there... you got the forums attention... this will work.

Well, if this means that it's getting ready to work, considering the way I'm feeling, it should be a flawless system when it finally decides to cooperate, which at my current level of misinterpreted frustration, should be any second now!  LOL... 

[Jenn D]

Well, it seems that my level of misinterpretted frustration was indeed an indicator!  I have a resolution that is working (for now).  Hopefully, it will continue to work from now on as I have had things working before that decided to quit working for reasons unknown.

I created macros that set a flag and told the cameras to start scanning when the system was armed and another to clear the flag and stop the scan when the system was disarmed.  Then I editted the sensor macros to just start recording when the sensors were triggered AND the flag was set.

We'll see how this works by testing it the rest of the weekend. 

[PajamaGuy]

It isn't really frustration.... there is a special emotional feeling people experience just before these things start working.... it does resemble frustration and could easily be misinterpreted for that. Hang in there... you got the forums attention... this will work.

You have such a way with words!  I'll bet your WAF stays high even when all the lights come on unexpectedly at 3 a.m.! 

[HA Dave]

Well, it seems that my level of misinterpretted frustration was indeed an indicator!  I have a resolution that is working................We'll see how this works by testing it the rest of the weekend. 

It does take a little while for it all to come together.... I think X10 usually quotes 30 minutes... it normally takes me a bit longer.

You have such a way with words!  I'll bet your WAF stays high..........

No errant lights here... but, I do have a perimeter detection system that has been tripped by critters a few times in the middle of the night. I took picture of the heard of deer that tripped it at 3 AM. The wife likes the pics.