X10 Community Forum
🖥️ActiveHome Pro => Plug-ins => Smart Macros => Topic started by: Billaban on April 08, 2011, 02:31:49 PM
-
Having trouble getting any macros to execute ???. Running the latest AHP (3306) on a Win7 system and also tried reverting to my XP "vintage" system. Same behavior in both contexts. Everything works fine if I manually trigger. I have tried both using a unused x10 address "off" for triggering and using the security mode, i.e., DS10A state closed. No joy. Using the activity monitor (yes, it seems to work fine for me) and nothing is being broadcast when the macro(s) should trigger. Just trying to setup simple date/time constraint light controls while on vacation. Eliminated the date aspect and currently just using time windows and can't get any of the aforementioned to trigger. B:(
Currently baffled and looking for suggestions.
-
3.310 is now the latest AHP.
Available here:
http://www.x10.com/support/support_soft1.htm
-
I'm using the latest Smart Macros's, AHP and Win7. I am having the exact same problem. When I add any time condition other than Dusk to Dawn the macro's fail. Even Dusk to Dawn fails as it does not constrain time - it's always on.
-
I'm using the latest Smart Macros's, AHP and Win7. I am having the exact same problem. When I add any time condition other than Dusk to Dawn the macro's fail. Even Dusk to Dawn fails as it does not constrain time - it's always on.
Have you checked both the Hardware configuration, and the time and timezone in your windows installation, to make sure they are correct?
Do the Dusk/Dawn times in the Hardware configuration screen match up with the correct times for your location?
One other thing to keep in mind, is that you can't test the conditions by triggering the macro from within the software. Clicking on the macro in the software will ignore the conditions.
If this is what you have been doing, then it could explain what you are seeing. Try triggering them from a hand-held remote, or from a separate plug-in controller.
The developers were unable to reproduce this problem on their own, so I will let them know about this thread.
-
I called X10 and they told me that it is a defective CM15A controller. I have a replacement on order. I'll update as soon as it arrives.
-
I called X10 and they told me that it is a defective CM15A controller. I have a replacement on order. I'll update as soon as it arrives.
That seems strange to me, but I guess you can see if that fixes it. There were a number of people who reported the same issue, some of them saying it never worked on their system.
I wonder if it could have been a bunch of bad units this whole time.
Keep us posted, because if the replacement unit solves the issue, I'm sure the developers would like to know that.
-
Have you checked both the Hardware configuration, and the time and timezone in your windows installation, to make sure they are correct?
Do the Dusk/Dawn times in the Hardware configuration screen match up with the correct times for your location?
Yes, this all correct.
Try triggering them from a hand-held remote, or from a separate plug-in controller.
There is part of the issue. The only trigger should be crossing a date/time threshold. My understanding (which perhaps is erroneous) is that you can stooge the trigger paradigm by simply setting the macro trigger to OFF for a unused address, e.g., I am using P1. However if a message P1 OFF needs to be generated in order to trigger the macro then that would explain a lot. Seems like I had macros working some time ago for this same purpose of date/time based light control while away from home. Maybe it never actually worked.....
Still looking for insight....
-
My understanding (which perhaps is erroneous) is that you can stooge the trigger paradigm by simply setting the macro trigger to OFF for a unused address, e.g., I am using P1. However if a message P1 OFF needs to be generated in order to trigger the macro then that would explain a lot. Seems like I had macros working some time ago for this same purpose of date/time based light control while away from home. Maybe it never actually worked.....
Still looking for insight....
I'm not sure what you mean.
Macros can be set to be triggered by only one address, and either an "On" or an "Off" on that address. You can have two separate macros on the same address, one for the "on" and one for the "off." They do not interact with each other at all.
When triggering a conditional macro from a hand-held remote, or some other powerline controller (or a timer), they will evaluate the conditions, and execute if the conditions are met.
When you run them from within the AHP software, conditons are ignored, and the commands will always run.
-
OK. Apparently I wasn't clear. I was trying before I went of vacation to simply setup several macros within AHP. These macros would execute simply based on a date/time window, i.e., when i was away. So the only real "trigger" is the date/time. But you can't write a macro (at least I don't think you can) with defining a x10 address trigger (I'm ignoring the security triggers). So some time ago (like years) I believe I had these same macros working by using a otherwise unused address, i.e., P1, and the OFF state.
Now I'm wondering if this ever really worked and if not how would any macro ever work without a discrete x10 event/msg trigger? ???
-
OK. Apparently I wasn't clear. I was trying before I went of vacation to simply setup several macros within AHP. These macros would execute simply based on a date/time window, i.e., when i was away. So the only real "trigger" is the date/time. But you can't write a macro (at least I don't think you can) with defining a x10 address trigger (I'm ignoring the security triggers). So some time ago (like years) I believe I had these same macros working by using a otherwise unused address, i.e., P1, and the OFF state.
Now I'm wondering if this ever really worked and if not how would any macro ever work without a discrete x10 event/msg trigger? ???
Okay, now I'm REALLY not sure what you are trying to do.
How are you trying to get the macros to run?
You can trigger them with timers, so they execute at a certain time/day of the week. You can set a specific date range when the timers will run, as well.
However, they don't just run on their own.
You can ONLY write macros to trigger based on an X10 address. That's how they work.
-
Apparently I need to go back and review the documentation that I haven't looked at in years. :-\
-
Noam,
Can't you just write a macro and then assign a timer to it in the GUI?
-
Noam,
Can't you just write a macro and then assign a timer to it in the GUI?
Yes, but you still need to give it a trigger address.
-
Define an 2-pin appliance module with an unused address such as P1 and set timers for it to turn on specific dates and times. Create a macro P1 with the on condition and set the steps to perform according to what you want to accomplish, just begin the macro with a delay of 1 - 2 seconds. If needed set up off timers for the appliance module and create macros with the off condition. Lastly, be sure you check the box in Tools/Preferences/Multiple modules can use same address.
HTH,
DeliBaker
-
AHP version 3.315 was released this past Thursday (6/9/2011), and is supposed to have a fix for the time-based macro conditions.
Please try it out, and report back here.
--Noam
-
AHP version 3.315 was released this past Thursday (6/9/2011), and is supposed to have a fix for the time-based macro conditions.
Gee, how long has this problem been with us?
-
AHP version 3.315 was released this past Thursday (6/9/2011), and is supposed to have a fix for the time-based macro conditions.
Gee, how long has this problem been with us?
Apparently for quite some time, but the developers were never able to replicate it on their end. It was only in the past few weeks that they were able to get examples and files from some users having the problem, so they could track it down and correct it.
-
Has anyone been able to verify if their "time-based condition" problem was fixed by updating to 3.315?
I still haven't heard back from anyone.
-
I don't think its fixed.
http://forums.x10.com/index.php?topic=24389.0 (http://forums.x10.com/index.php?topic=24389.0)
-
I don't think its fixed.
http://forums.x10.com/index.php?topic=24389.0 (http://forums.x10.com/index.php?topic=24389.0)
That thread seems to be referring to something totally different.
The bug in question only affected time-based conditions (ex: Turn on light IF it is AFTER 10:00 PM), and ONLY if run from the PC.
Your thread seems to be a problem with a conditional macro not executing at all. That's a completely different issue.
-
I don't think its fixed.
http://forums.x10.com/index.php?topic=24389.0 (http://forums.x10.com/index.php?topic=24389.0)
That thread seems to be referring to something totally different.
The bug in question only affected time-based conditions (ex: Turn on light IF it is AFTER 10:00 PM), and ONLY if run from the PC.
Your thread seems to be a problem with a conditional macro not executing at all. That's a completely different issue.
Not true. The conditional macro is being called when triggered by the timer. It just fails to execute the action of the macro. It looks like it thinks the "flag" is NOT set, but the Status Report says it is.
I did not see where this thread was specifically associated with running from a PC, even after rereading it.
-
I don't think its fixed.
http://forums.x10.com/index.php?topic=24389.0 (http://forums.x10.com/index.php?topic=24389.0)
That thread seems to be referring to something totally different.
The bug in question only affected time-based conditions (ex: Turn on light IF it is AFTER 10:00 PM), and ONLY if run from the PC.
Your thread seems to be a problem with a conditional macro not executing at all. That's a completely different issue.
Not true. The conditional macro is being called when triggered by the timer. It just fails to execute the action of the macro. It looks like it thinks the "flag" is NOT set, but the Status Report says it is.
I did not see where this thread was specifically associated with running from a PC, even after rereading it.
The bug that was referred to, which was fixed in version 3.315, specifically affected ONLY macros run from the PC, AND only if they had a time-based condition. The logic in the AHP code was reversed, so the time-based condition would be evaluated backward (true when it should be false, false when it should be true).
This comes straight from the explanation I got directly from the developer who fixed it.
Since you are running 3.316, AND your condition is not time-based (it is flag-based), AND you are running the macro from the CM15A (not the PC), then the problem you are having is different from the one that was fixed in 3.315.
That said, it doesn't mean you didn't find a DIFFERENT bug.
I'll reply in your other thread, with some specific troubleshooting you can try.
-
Thank you very much!!! Help is appreciated..