Print

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

[bitman]

One day after delving into smart macros, when I exited AHP it said "You have more modules on M, should I set the monitored house code to M for you?"

No! was the answer, because I want to monitor D. And stop being so "helpful" by the way. 
I found that I could suppress this silliness in preferences. - great.
But today when a macro that is supposed to fire after checking the state of D2 had reverted back to Checking the state of M1. Not again!

How in the world do I stop this from happening? It's bad enough that wonderful things I am able to pull off with macros and sensors don't work because of my error, but AHP conspiring against me is just criminal!

I'm running 3.236 under xp sp2.

Thanks,

:Ron

[Tuicemen]

The issue is most likely the buggy version of AHP your running!
Many that continue to run this version haven't changed their AHX file since updating to it that seems to be when the big bugs are noticed!
Try reverting to ver 3.204 then auto update to 3.228 it won't see 3.236 (good thing)!

[bitman]

Oh no!
Not me too!

Alright.

Just when I was having fun with it......

[Tuicemen]

Oh no!
Not me too!

Well I'm sure it is just a matter of time before I have to revert as well!
All of the bugs I've found don't effect my setup (yet) or at least not noticably
 

[bitman]

Ok I reverted back to 3.024 and updated to 3.228. Everything seems ok.
My monitored house code was back to M again, so I set it to D where I want it and we'll see if that sticks.

Thanks for all your help T.

:Ron

[HA Dave]

My monitored house code was back to M again, so I set it to D where I want it and we'll see if that sticks.

AHP likes to have the monitored code also be the code with the most "units" used. Meaning... you have more modules or whatever on "M" than you do on "D". Why not just create an "used D units room" and fill it with the remaining "D" codes?

[bitman]

Darn good idea Dave.
I like the way you think.

 

[steven r]

AHP likes to have the monitored code also be the code with the most "units" used. Meaning... you have more modules or whatever on "M" than you do on "D". Why not just create an "used D units room" and fill it with the remaining "D" codes?

That's basically what I did some time ago with a much earlier version of AHP. There is a setting that supposedly is suppose to keep AHP from selecting the monitored code based on the number of items for a given HC. It didn't work for me so I created a room I labeled something like "Room for the AHP Bug" and filled it with about 20 or so dummy modals for the HC I wanted to monitor. You can use the same module even if it is already being used somewhere else.

[bitman]

Well well well,

Back grading the AHP version did not fix it BUT I am now running a less buggy version and that makes me happy(?)
So tonight I'm going to create a Dummy Module room and fill it with Ds. That'll fix it's wagon.