I can watch the macro execute (blink
Basicaly a dummy/phantom module Makes AHP think it needs to send a plc signal for that device.
You can then trigger macros from that signal /trigger( the device isn't real but the signal sent from AHP is ;) )
AHP needs a module house code/unit code as a macro trigger.
There are many uses for Phantom Modules and users keep thinking up more uses for them with each added plug-in!
I'll start a thread listing some uses and that may help you under stand, others can then post uses they came up with for the Phantom Modules!
Why does this work in the daytime?Have you checked your AHP time Zone configuration? ??? ;)
First yom make a module A4 then you make a macro that is triggered when ever that module is turned "On or Off" via palm pad,macro or flipping the vertual switch in AHP!
Your "A4" is only a macro trigger it does Nothing else except you can see in AHP that it was triggered by the state of the Phantom switch!
In your case:[/color][/b]
- make the module
- Be sure that the house code you assigned it to is in AHP as a transcieved housecode
- In the macro your having problems with add it as the trigger!("A4 ON")
- Save to the interface
- Test with a plam pad
Now once it works as you wish!
[/color][/b]
- Make another macro using the trigger you wish eg: security sensor
- in this macro simply add your phantom module ("A4 ON")nothing else
- Save
- trigger the security sensor
I think it is too easy to get hung up on the email as a source of problem. For a lot of us email is the first and most reliable (in our mind) way of testing
Well, I saved it and down loaded it to the interface and it shows in the macro report file.
Why does this work in the daytime?