I'm trying to set up press-and-hold macros to control my lights. I want the lights to turn on with a short press and turn off if I hold the button down for more than a second. To accomplish this, I set up the following macros:

IF (Press Time < 1 Second)
...ALIAS (Lights/Page3/#)
...ALIAS (Lights/Page3/ON)
ELSE
...BEEP
...ALIAS (Lights/Page3/#)
...ALIAS (Lights/Page3/OFF)

Note: # = the particular bank of lights to be controlled.

Everything works exactly like it should except for one small glitch. After holding the button down for one second, the beep will sound, but the actual OFF macro won't fire until I have released the button. This is not how it worked on my 900. With the 900, the OFF macro would fire by itself as soon as the specified hold time had been reached. There is either a bug in the MX-980 editor, or I'm simply doing something wrong. Since this is my first experience with IF/ELSE programming, I'm assuming it's the latter.

I have the same thing happening with my P/H Macros on the 980. The Macro will beign and will change to the "Macro In Progress" screen, then to the Go-To Page I specified, but the IR commands will not fire until the button is released. It is not a problem in my setup but it is a quirk I have noticed.

Interesting. So it appears that it may indeed be a bug in the software. Is anyone else having this problem?

Yeah, I'm seeing the same thing with press and hold. My question is: Is this a bug or is it the way they intended it to work?

i can confirm i DO NOT have this problem. the command fires as soon as the one second is up. i was having issues prior as i was not putting the ELSE commands INSIDE the IF/ELSE box, but rather i was leaving them outside the box at the end.

Did you read the other thread about unchecking the "repeat while button pressed" box for each command in the macro? Supposedly fixed in the newest live update. Double click a command that's not firing and uncheck the box. Add repeats as a last resort.

What is odd is that the Macro does begin (in my case, the Macro screensaver starts) but the IR commands do not go. If the "repeat while button pressed" issue were the cause I would think that the Macro would not begin at all until released. In my book, this is a quirk and not a bug.

All of my macros are working as planned, especially now that I went in and added UI Variable Phase switches and If/Then Parameters to them. Very powerful remote.

Thanks for the reply. Your post gave me hope, but unfortunately it appears that all of my commands ARE inside the IF/ELSE box. Anyone else have any suggestions?

I don't know how to post images on this forum, but here is a link to a screen capture of my macro setup:

I don't have an MX-980 (it should be here tomorrow), but I already have a 90% complete configuration file.

Here are some suggestions.

1. I've been programming my press and holds the opposite way. Hold commands first.

If Press Time is >= 1 second.

2. What happens if you remove the beep?


Eddie

This was the first thing I tried. I simply switched the < to >= and swapped the positions of the ON and OFF macros. Unfortunately, it didn't fix the problem.


It doesn't seem make a difference. Actually, I've come to rely on the beep. Once I hear it, I know I can release the button and the macro will fire.

So I received mine today and it's sorta weird.

It looks like it does the first two commands then waits for you to release the button before finishing the Macro.

For Instance.

Initially I had

If Press Time is >= 1 second
Turn off TV
Turn off Receiver


That worked perfectly.

I decided to add a beep before turning off TV. Now, it beeps and turns off the TV, then turns off the receiver after I release the button.

My other macros involve beeping then jumping to a macro page before doing the actual macro. So it beeps and goes to the macro page, then everything else after I release the button.

Hopefully, they can get this fixed.

Eddie

The evidence seems to be leaning more and more in the direction of this being a software related issue. I just wish someone affiliated with URC would chime in on this matter so we could know definitively if the fault lies with us or with them.

I was bored....

:>/

Thanks, smokinghot.

For future reference, how does one go about posting an image on this forum? I tried doing it the way I'm used to in a standard vBulletin based forum, but it didn't work.