Print

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

[sir_rob]

The "issue on instead of bright 100%" option makes no difference in my case.  I am not using macros.  I have the simplest timer, and it does not work properly.

What is the difference between when I manually click on a module to turn it on and when the timer does it?  The problem should be found in the difference.  Any ideas?

[-Bill- (of wgjohns.com)]

Good question.

Have you looked at the AHP event log to see what is (or isn't) sent when the timer fires and when you click the module to turn it on?   

[sir_rob]

For the timer:
The activity monitor reports: "Macro     A2 (Hall Light)" and then at the same time but on the next line: "Macro       A Bright 100% (Hall Light)"
Later the monitor reports: "Macro     A2 (Hall Light)" and then at the same time but on the next line: "Macro       A Off (Hall Light)"

For mouse clicks:
The activity monitor reports: "Transmit     A2 (Hall Light)" and then at the same time but on the next line: "Transmit       A On (Hall Light)"
Then activity monitor reports: "Transmit     A2 (Hall Light)" and then at the same time but on the next line: "Transmit       A Off (Hall Light)"

Perhaps the "issue on in place of bright 100%" check box is not working.

[sir_rob]

I have now confirmed that the "off" command DOES work at the end of the timer!

Regardless of the "issue on in place of bright 100%" check box, the light does not turn on and the monitor reports the same "Macro     A2 (Hall Light)" and then at the same time but on the next line: "Macro       A Bright 100% (Hall Light)".  I think that the check box is not doing its job.  If that is the case, how do I fix it?

[Knightrider]

Rob,

I want you to try something.  Tic the box for issue on once again, then go into hardware configuration and update the interface (maybe even download timers again).  Then check your event log and report back.

I swear my unit(s) all issue the "on" command.

[Dan Lawrence]

I suspect the timer was created by 3.236 and is corrupted.   I posted earlier to delete it and recreate it but he apparently hasn't done that.  3.236 does funny things to timers.

[sir_rob]

You posted earlier to delete and recreate the timer, and I did.  In fact, I stated "I have deleted and re-created the modules and the timer" a few posts back, just after installing the version that was recommended.  Are you saying that I should delete my entire file and start from scratch?  I have not tried that.  Let me know if that is what you are recommending, because I think that I have followed your advice.

I  have saved and downloaded timers to the interface after ever single change that I have made.  I have checked and unchecked the "issue on instead of bright 100%" option at least 15 times.  Please let me know if you think that I have missed something somewhere.

[Dan Lawrence]

What's the file name you are using?   If it was created by 3.236, the entire contents are corrupted. Don't use "MyHouse.ahx" for anything.  I have 19 different .ahx files for use at different times of the year.   I would start a new .ahx file and build everything again. 

[sir_rob]

MyHome.ahx

It was created by 3.26.  I will create a new file and start over.

[Dan Lawrence]

Don't use MyHome.ahx for anything.   Open it, delete anything it has and begin from scratch.   Save it with a new name that is your own.  As you get more used to AHP, start creating custom .ahx files for different times of the year.   That's how I got 19 different ones. 

[sir_rob]

I have created a new *.ahx file.  This time the modules in the software responded a little bit differently, but the hardware response (and no response) is exactly the same.

Initially the modules would simply go from off/full dim to off/full bright when they were supposed to turn on.  After I selected the "issue on instead of bright 100%" option, the modules showed that they went from off/full dim to on/full bright.  The problem is that in both cases, the light never turned on.  If I click on the module, it turns on, but the timer does not turn the light on.

[sir_rob]

I can get the timer to turn lights on if I set up dummy appliance modules with the same codes.  The closest I have come to getting the timer to work properly is to create the actual module and then a dummy module for every dimmable module that I want to control.  I can then use a timer to turn on the dummy appliance module, and 1 minute later I can use the actual module to control the dim/brightness level.  It is a bit clumsy and awkward, and it does not behave exactly how I would like, but at least it works.

If anyone can come up with some other ideas, I would love to hear them.

[Dan Lawrence]

Try setting the modules (I presume they are lamp modules) as LM14A Two-way modules.  The actual LM14A was eliminated by X10, but it still exists in AHP.  That is the best way to handle "SoftStart" modules.

[sir_rob]

Thanks for the advice.  Now the light itself responds properly, but the software module does not show any change.  I will take this as an improvement, but I would still like the software to work as it should.

[Brian H]

I think at the moment calling it a LM14A is what X10 says to do and when it ever gets updated is hard to say. Not much has changed in a loon time.

http://kbase.x10.com/wiki/SoftStart