Print

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

[rock99rock]

Howdy!

I've searched a bit, and found some interesting posts that have not solved my issue.  http://forums.x10.com/index.php?topic=13843.0 was the most relevant.   I'm running the latest version of AHP, and have the Smart Macros and OnAlert plugins installed & registered.  The monitored house code is "A".  The server running the AHP is always on.  The time on the server and CM15A are correct, and correspond.  The timers have been downloaded and saved.

I want my front door sensor (DS10A sensor triggered) to turn on all lights (LM465 with soft start x2 Housecode "A") with timed condition (between 5pm and 8pm).  

The macro works with the time condition removed.  I tried setting up 2 macros, where the front door sensor would enable a ghost appliance sensor, then the second macro took the ghost sensor as a trigger, and threw in the timed condition.  This idea from the earlier linked post.  Here is a pic of the optimal setup:


What am I missing?  Thanks in advance!

-Rock

[peg-leg]

I believe there's an issue with time conditions on any AHP version beyond 3.296.  You try reverting back to that version and see what happens.

[lviper]

I had the same problem using conditions with the ds10a. What you need to do is hace the ds10a turn on a phantom module when triggered and off when closed. Then you use the phantom module to trigger your lights on macro with the time conditions.

For example, ds10a triggered turns P1 on.
P1 on triggers your macro to turn on all living room lights between the time condition.

P1 is just an appliance module on an unsed house code. Take a look at my macro at http://forums.x10.com/index.php?topic=22396.0

[rock99rock]

I had the same problem using conditions with the ds10a. What you need to do is hace the ds10a turn on a phantom module when triggered and off when closed. Then you use the phantom module to trigger your lights on macro with the time conditions.

For example, ds10a triggered turns P1 on.
P1 on triggers your macro to turn on all living room lights between the time condition.

P1 is just an appliance module on an unsed house code. Take a look at my macro at http://forums.x10.com/index.php?topic=22396.0

I don't know if you saw my entire post, but I tried that already
"I tried setting up 2 macros, where the front door sensor would enable a ghost appliance sensor, then the second macro took the ghost sensor as a trigger, and threw in the timed condition.  This idea from the earlier linked post. "

Thanks however for your input.

I believe there's an issue with time conditions on any AHP version beyond 3.296.  You try reverting back to that version and see what happens.

Is there a way to revert back without having to reinstall all of the extra plugins I purchased?  Where can I download previous versions?  I don't see it listed here: http://www.x10.com/support/support_soft1.htm

I was going to ask if anyone submitted this issue to a bug tracker, but I can't seem to find one   I just started using X10 about a month ago along with Activehome Pro, and already have about 3 major bugs that need to be addressed to prevent instability.  Thank you for your suggestion.

If anyone else has any suggestions that don't involve reverting, that would be great.  It would also be nice to be able to turn off Activehome updating, so as not to auto-update to buggy versions.  Is there an option for that?

Thanks,

-Rock

[dave w]

Sidebar question for those in the know: Does AHP 3.305 take care of the "identify all your lamp modules as LM14A's" problem? That was for timers not working wasn't it?

[Tuicemen]

Sidebar question for those in the know: Does AHP 3.305 take care of the "identify all your lamp modules as LM14A's" problem? That was for timers not working wasn't it?

Kind of!
But is a bit of a pain for older setups.
All softstart lamp modules now must be set as lamp modules
All old lamps (no soft start) must be set as "Older Lamps(no softstart)" so all light modules now must be edited
A Update to 3.305 may fix rock99rocks issue
rock99rock do not revert to an earlier version as you most likely have softstart lamp modules.
What you could try in your macro (once you've updated to 3.305) is specify each light you want to come on!
 

[rock99rock]

Sidebar question for those in the know: Does AHP 3.305 take care of the "identify all your lamp modules as LM14A's" problem? That was for timers not working wasn't it?

A Update to 3.305 may fix rock99rocks issue
rock99rock do not revert to an earlier version as you most likely have softstart lamp modules.
What you could try in your macro (once you've updated to 3.305) is specify each light you want to come on!
 

Thanks for the heads up.  When I "Check for update", it says I have the latest version (its not, its actually 3.302).  Will downloading the latest from here: http://www.x10.com/support/support_soft1.htm and overwriting the current install be a proper way to upgrade?

Thanks,

-Rock

[Tuicemen]

The check for update button hasn't worked since 3.228 I believe.
 
And the programmers are worried about confusing newbies!  
Just so sad I have to laugh

[rock99rock]

The check for update button hasn't worked since 3.228 I believe.
 
And the programmers are worried about confusing newbies!  
Just so sad I have to laugh

Wow.  Thanks for the prompt reply.  So downloading from that link I provided then overwriting the main install should update it, and not make me have to reinstall all the plugins and import the setup again?  Is there a bug tracker that can be referenced so we can keep track that they know of certain issues?

Thanks,

-Rock

[Tuicemen]

Yep, it's that easy!
I usualy have a thread going with latest bugs for that release but now have one thread for all on going issues.
Topic: New & Old (outstanding) AHP Bugs
Simply reading the first post should keep you updated as I add remove from it as I'm aware of the issues or fixes!
 

[rock99rock]

Yep, it's that easy!
I usualy have a thread going with latest bugs for that release but now have one thread for all on going issues.
Topic: New & Old (outstanding) AHP Bugs
Simply reading the first post should keep you updated as I add remove from it as I'm aware of the issues or fixes!
 

Unfortunately, the situation still exists with the updated software.  How is it that some of these bugs have been around for so long?

[Tuicemen]

The main reason is X10 doesn't keep their programers very long and when they get new ones they have to learn every thing from scratch!

[rock99rock]

Well I sent X10 my data file a month ago, haven't heard back after repeated attempts.  I'm pretty sure they only have one guy developing/fixing bugs.

[JMac]

Believe it or not you need three macros.  There is an example here in the forum which works very well, and I have a similar setup for some of my doors.
The door switch turns on a phantom switch triggering macro #1, which turns on phantom switch #2 triggering macro #2 (time conditionals are here), and the third macro does the actionable items.  Rube Goldberg would be proud and there is a substantial time delay before any action (5 or 6 seconds).  If the times don't work, set a flag, and have the macro check for a flag before acting.

It's here: "Time condition in macro not working" by KDR

[mike]

how about trying the reverse of what others are saying?

ERASED

My time range works