My 2.4.9 report

[MikeB]

- triggers based on FAST OFFs from relay switches are now possible

- "New Folder" button in the Program Details tab now creates a correctly named folder

- Insteon addresses now showing in the Device View

 

This is all I've been able to test so far.

 

I've got something odd going on with a room when the ISY-26 is plugged in, but I'm going to recreate my programs related to that room, restore the devices, and test a bit more before I jump to conclusions.

[MikeB]

OK, I've got something odd going on here.

 

In a few rooms/areas of my house, I'm using double-taps (FAST ON/FAST OFF) to turn on entire rooms.

 

For example, in my bathrooms, if I double-tap on my main light switch (FAST ON), I have it turn on a BATHROOM ALL scene, which includes the main bathroom light, the bathroom vent, and the mirror lights.

 

When I double-tap the main switch off (FAST OFF), the ISY-26 turns off the BATHROOM ALL scene.

 

I created these under 2.4.8, and they all seemed to be working fine.

 

Under 2.4.9 I'm noticing one room that is not working correctly. The only thing different about this room is that I have a virtual 3-way circuit with 2 switches controlling the main lights. This means that I want double-taps on either of those 2 switches to control the entire scene.

 

So, here goes:

 

I have a scene called THEATERALL that contains TheaterTable, TheaterMain1, and TheaterMain2. TheaterMain1 and TheaterMain2 are also members of the scene THEATERMAIN (a virtual 3-way circuit).

 

I have a trigger called THEATERALLON that runs as follows:

 

If
       Control 'TheaterMain1'is Fast On
    Or Control 'TheaterMain2'is Fast On

Then
       Set  Scene 'TheaterAll' On

Finally
  - No Actions - (To add one, press 'Action')

 

I also have a trigger called THEATERALLOFF that runs as follows:

 

If
       Control 'TheaterMain1'is Fast Off
    Or Control 'TheaterMain2'is Fast Off

Then
       Set  Scene 'TheaterAll' Off

Finally
  - No Actions - (To add one, press 'Action')

 

This basically works the same as my bathroom triggers, except for the OR statement under IF, because I want this to work from either TheaterMain1 or TheaterMain2.

 

This seemed to be working fine under 2.4.8, didn't notice any issues, nor get any complaints. Under 2.4.9 I have odd things happening.

 

For example, if I double-tap TheaterMain2 on, all lights go on as expected. But, if I go up to TheaterMain1 and then try to turn the light off, it goes back on. If I look at the ISY-26, it runs the trigger THEATERALLON which makes the light go back on.

 

For the life of me, I can't figure out why it's executing that trigger.

 

I have other odd things happening, times when I go to turn the switch on but it jumps back to off. Times when I double-tap them all on, but they go off for a second, then jump back to on.

 

Again - this seemed to be working fine under 2.4.8, so I'm not sure what it could be - but it's very reproduceable. If I disable these 2 triggers, the lights function fine on their own.

 

Hopefully this makes sense to someone..

 

Thanks!

[Chris Jahn]

What you are saying does make sense, and it looks like the non-toggle fix went a little too far.

 

The logic should be:

A program is run if the button changes to the specified value and the 'If' condition is true

 

But it currently is:

A Program is run if the button changes and the 'If' condition is true.

 

This will be fixed for the next drop.

[MikeB]

What you are saying does make sense, and it looks like the non-toggle fix went a little too far.

 

The logic should be:

A program is run if the button changes to the specified value and the 'If' condition is true

 

But it currently is:

A Program is run if the button changes and the 'If' condition is true.

 

This will be fixed for the next drop.

 

Glad it made sense to you, because it had me going bonkers.

 

Thanks Chris!

[MikeB]

This seems to be fixed in the latest beta.

 

Thanks!!