X10 Community Forum
🖥️ActiveHome Pro => Plug-ins => Smart Macros => Topic started by: bt54 on April 18, 2011, 09:26:57 AM
-
I've written a few Smart Macros that do not operate correctly with time period conditions. I have set my preferences to the appropriate region. I am using the newest versions of Smart Macros and AHP and have a CM15A.
If I use Dusk to Dawn the macro's work but ignore the time - they trigger all of the time.
If I use specified time periods (If Time is Between) 6PM to 11PM - the macros do not trigger. I've entered the time manually and alternatively used the up\down arrows to set it.
If I remove the time conditions the macro's trigger.
Also - none of the macros will store in the interface - they are all listed as being required to run from the computer. The computer is on 24/7 but I believe that they should store in the CM15A.
Any Ideas ???
-
I've written a few Smart Macros that do not operate correctly with time period conditions. I have set my preferences to the appropriate region. I am using the newest versions of Smart Macros and AHP and have a CM15A.
If I use Dusk to Dawn the macro's work but ignore the time - they trigger all of the time.
If I use specified time periods (If Time is Between) 6PM to 11PM - the macros do not trigger. I've entered the time manually and alternatively used the up\down arrows to set it.
If I remove the time conditions the macro's trigger.
Also - none of the macros will store in the interface - they are all listed as being required to run from the computer. The computer is on 24/7 but I believe that they should store in the CM15A.
Any Ideas ???
Macros that require any of the newer plugins cannot be stored in the interface. Most of the newer plugins, including the security ones, require a live connection to the PC to run, wince the functionality wasn't built into the CM15A when it was designed many years ago.
What types of macros are you using, that it won't let you store in the interface?
-
Macro One
DS10A on front door triggers hall light on then delay then off
Macro Two
Security Motion Detector triggers lamp module on then 5 min delay then off
-
Macro One
DS10A on front door triggers hall light on then delay then off
Macro Two
Security Motion Detector triggers lamp module on then 5 min delay then off
I don't have the security plugins, but I'm pretty sure those require the 24/7 connection to the PC.
-
Noam,
All of the devices are listed in AHP so I would not think that security would have anything to do with it. I am having another problem with my CM15A - it refuses to work with time conditions. I spoke to tech support and they think that the unit is defective.
-
Yes, I saw that on the other thread.
-
Unless X10 has drastically changed something, any use of Security switches or Security motion sensors in a macro requires that the PC be running and connected to the CM15A at all times. The macro actually runs on the PC and can't be stored in the CM15A for standalone operation.
>!
-
UPDATE !!!
Replacing the CM15A did not solve the time condition problem. You guys were right !!!
-
UPDATE !!!
Replacing the CM15A did not solve the time condition problem. You guys were right !!!
I'm going to let the developers know about this one. They were looking for examples, as they couldn't reproduce this on their own.
-
I agree with -Bill-. The computer has to be on with AHP running......
-
I agree with -Bill-. The computer has to be on with AHP running......
Anything involving the security plugins requires the PC, which is why those macros cannot be stored in the interface.
The only exception would be triggering a macro from a motion sensor. In that case, since the motion sensors just send an RF "On" or "Off" command, the CM15A doesn't see any difference between it and a PalmPad.
As for the time condition issue, I got a reply back from one of the developers that they ARE interested in getting some files from you (at least your AHX file, and perhaps some config files), so they can try to reproduce the problem. Stay tuned, someone should be in touch with you in the next few days.
-
I think I'm having exactly same problem
except I'm triggering an email from a motion sensor between certain times/days
I tried it SEVERAL times and like the original poster it works without conditions but not with.
Anybody who had this issue get it resolved somehow?
-
Send a Private Message to "ErikP". He is the developer who is looking into this. He will reply with instructions of how to send him the files her needs.
-
Send a Private Message to "ErikP". He is the developer who is looking into this. He will reply with instructions of how to send him the files her needs.
Well its more better if ErikP will share here for everyone, because its a forum information should be available for everyone who wants to learn.
-
Send a Private Message to "ErikP". He is the developer who is looking into this. He will reply with instructions of how to send him the files her needs.
Well its more better if ErikP will share here for everyone, because its a forum information should be available for everyone who wants to learn.
If you are experiencing the problem, you should contact ErikP (private forum message is the preferred method to do so), so he can assist you in getting him the files he needs to investigate.
The developers have not been able to duplicate the problem yet, so they are looking for examples of the problem, so they can investigate, and try to determine what is causing it. Once they can identify it and produce a fix, they will put that into a new release that is available to everyone.
-
Well its more better if ErikP will share here for everyone, because its a forum information should be available for everyone who wants to learn.
As soon as I have something shareable I will do this ASAP. Right now i do not have any work arounds or fixes. I am just collecting data to try to develop a fix. Since the data i need from everyone is kind of personal. I am asking for PMs so no one has to share that information with the world.
-
I just sent you a PM Erik. Let me know if you've got any thoughts on it please.
-
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.
Please try it out, and report back here.
--Noam
What was the problem that this fix is supposed to fix?
What about the time based macro conditions was not working?
I may (or may not) have this problem and would like to know what was(n't) happening to see.
Thanks!
-
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
What was the problem that this fix is supposed to fix?
What about the time based macro conditions was not working?
I may (or may not) have this problem and would like to know what was(n't) happening to see.
Thanks!
Some users (not a large percentage - which is why it took so long to find a fix) reported problems where time-based conditions in macros didn't work. If they based the conditions on flags or module status, then those macros worked fine. However, conditions based on time (duck/dawn, time of day, day of the week) wouldn't work properly, and those macros wouldn't run.
Some users were able to get around it by creating macros with timers to turn flags on and off at certain times of the day, and then have their other macros use the flags as conditions.
This fix is supposed to correct that problem, and those users should be able to use macros with time-based conditions properly.
If you were having this problem before, please upgrade to version 3.315, and try it out again to see if the problem has been resolved for you.
-
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
What was the problem that this fix is supposed to fix?
What about the time based macro conditions was not working?
I may (or may not) have this problem and would like to know what was(n't) happening to see.
Thanks!
Some users (not a large percentage - which is why it took so long to find a fix) reported problems where time-based conditions in macros didn't work. If they based the conditions on flags or module status, then those macros worked fine. However, conditions based on time (duck/dawn, time of day, day of the week) wouldn't work properly, and those macros wouldn't run.
Some users were able to get around it by creating macros with timers to turn flags on and off at certain times of the day, and then have their other macros use the flags as conditions.
This fix is supposed to correct that problem, and those users should be able to use macros with time-based conditions properly.
If you were having this problem before, please upgrade to version 3.315, and try it out again to see if the problem has been resolved for you.
Thanks for the reply!
I don't think I had any of those problems. The only thing I had to "compensate" for was the "crossing midnight" condition when I wanted to specify a macro to run, say, between 2000 hrs and 0100 hrs. I got around it by having the macro end at 2359 hrs., and another macro start at 0001 hrs. (two minutes of dead time).
Is this what you are referring to as the problem/fix?
I did upgrade to 3315 "just for fun".
Thanks!