I have an Action Group that turns on all of the window air conditioners (and a corresponding one that turns them all off). I don't want all three of them -- including a large whole-floor unit on the first floor, and an old inefficient unit in the master bedroom -- coming on at once, but I do want them all on in a relatively short period of time.

I set this up in 1.8 with one unit coming on right away, the second delayed by .33 minutes (20 seconds), and the third delayed by .67 minutes (40 seconds). Indigo rounded both of these to the nearest tenth -- .3 and .7 respectively -- but that's no biggie: they still came on within roughly 20 seconds of each other, and, most importantly, all were on within one minute.

I want to add a fan to this sequence, but when I open the group in 2.0 b8, my .33-minute delay is now 0 minutes and my .67-minute delay is now 1 minute. I can't enter a fraction of a minute delay. My attempt to enter a "Delay by" value of .25 minutes (15 seconds) immediately turns to 0. Attempting to do .5 immediately turns into 1. This happens when trying to edit the existing action group. I have not attempted to create a new group from scratch in 2.0.

Is this a feature or a bug waiting to be fixed before b9 or final product? If "Delay by" entries have a bottom limit of 1 minute, this could render some sequences way too long. Am I missing something?

Byron

Hi Byron,

This is definitely a bug. I'm not sure what the problem is exactly yet, but it appears to not happen if you use the mouse to press the OK button (don't use the enter/return key).

Matt

This one turned out to be a Cocoa (Apple) bug. The next Indigo build has a workaround so you shouldn't see the problem anymore.

Matt