I'm trying to have the LED on an I3 switch (not keypad) be off when the switch is off and on when the switch is ON. I have tried various combinations of LED and Backlight and the best I can get is either getting the LED off always or getting it very low but NOT off. Using the EISY administrative console.

Not sure about the I3 (haven't needed to dive in there yet), but my other older insteon switches have a "Backlight" option on the set command. I THINK this may be what you are looking for.

Program would require 2 "Set" commands: 1) turn on the light and 2) set backlight to 100% (or whatever floats your boat). Off program would be the inverse.

That said, I just tested it. It no worky. While I can set the program to set the backlight level, nothing happens. I CAN however, change the backlight on the device itself on the Main tab in the AC. So, you would assume that setting the backlight in a program would work since it's there but what do I know??

~jim

EDIT: Doh! I keep a test program that I try stuff like this with, and did not notice it was DISABLED! This actually works.

TestSwitch - [ID 0063][Parent 0001]

If

'Office Light' Status is Off

Then

Set 'Office Light' Backlight 0%

Wait 2 seconds

Set 'Office Light' Write Changes

Else

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

Edited August 16Aug 16 by JimTurner
more info

I'll give a try and report back. Thanks

Program causes EISY to go system busy crazy. The IF statement appears to cause an endless loop. I have tried both Control is Switched off and Status is Off, both go into system busy as soon as the switch is turned off. Turning switch back on the System busy will eventually go away.

1 minute ago, jckinneman said:

Program causes EISY to go system busy crazy. The IF statement appears to cause an endless loop. I have tried both Control is Switched off and Status is Off, both go into system busy as soon as the switch is turned off. Turning switch back on the System busy will eventually go away.

Weird. I didn't test with an I3 device, just a regular switch... It responded almost instantly.

@jckinneman remove the "write changes" and the wait lines.

2 minutes ago, Geddy said:

@jckinneman remove the "write changes" and the wait lines.

I added those lines trying to test what was a disabled program. Just did the same and it works.

I removed the write changes, still the same, goes into an endless loop repeated system busy messages when I switch to off, only get control back if I switch to ON

32 minutes ago, jckinneman said:

I removed the write changes, still the same, goes into an endless loop repeated system busy messages when I switch to off, only get control back if I switch to ON

Can you paste your program?

Edited Wednesday at 07:59 PM5 days by jckinneman

@jckinneman do you have a program that is turning the backlight ON when the switch is turned on or status on? And that one isn't causing an issue?

Be sure to remove the "wait 2 seconds" line too

I do not have an i3 device, but on a simple on/off module the program as you have it and as @JimTurner posted works for switched and status. But when I turn the light back on the led (backlight) stays out. I'm not sure if the i3 is acting different and causing the program to run in a loop because it's always seeing the "status" as off. Do you have the device set as an "on/off" switch or is it a dimmer? If it's a dimmer maybe we can edit the program somehow.

Also, for future reference, the best way to post a program to the forums is to right click the program and select "COPY to Clipboard" then paste it as text. It helps others edit the program rather than describing on a picture.

This worked in my test:

led-test - [ID ####][Parent ####]

If

'Office' Status is Off

Then

Set 'Office' Backlight 0%

Else

Set 'Office' Backlight 100%

My test has 2 simple programs: 1 for backlight off and 1 for backlight on (based on switch status). They work flawlessly. My device is actually a dimmer (2477D), but I just tested the same thing in a switch (2477S).

TestSwitch - [ID 0063][Parent 0001][Enabled]

If

'Office Light' Status is Off

Then

Set 'Office Light' Backlight 0%

Else

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

Edited Wednesday at 11:10 PM5 days by JimTurner
more info

Thanks for all the suggestions.

TestSwitch - [ID 000C][Parent 0001][Enabled]

If

$DinningRoom is 1

And 'I-Dining - Living / Dining Foyer Paddle' Status is Off

Then

$DinningRoom = 0

Set 'I-Dining - Living / Dining Foyer Paddle' Backlight 0%

Else

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

This still goes into system busy loop. It is a I3 set for dimmer mode. it is part of a three way scene with an older dimmer 2477D. I tried putting in a variable that the if statements checks for it being 1 in that switch was previously ON. The routine sets the variable to 0 to indicate switch is now off. If this worked I would add a second program that handles the ON routine. I have also tried using Control switched off instead of status. And 'I-Dining - Living / Dining Foyer Paddle' is switched Off

@jckinneman strange. I wonder if an issue with it being an i3 device. Sorry can't test any of those.

What if you tested one program, but making the else the off setting.

led-test - [ID ####][Parent ####]

If

'Office' Status is not Off

Then

Set 'Office' Backlight 100%

Else

Set 'Office' Backlight 0%

This is since it's a dimmer if there's any brightness level set then the backlight would be 100%, but when it was off would be 0%. I don't use status often and wonder if that's causing the loop since it's always checking the status. The scene could also be an issue. Do you have any other i3 devices not in scenes to test with?

It appears to be something with i3 switches. I have one i3 that is not part of a scene; it is set as a relay. Using your recent suggestion, I still get the system busy

TestSwitch - [ID 000C][Parent 0001][Enabled]

If

'I-Garage / Garage Door Left Paddle' Status is not Off

Then

Set 'I-Garage / Garage Door Left Paddle' Backlight 100%

Else

Set 'I-Garage / Garage Door Left Paddle' Backlight 0%

@jckinneman This might be something that would help UD if you open a support ticket. Especially if this is something that can be duplicated in the Java Admin Console before they move everything into eisy_ui.

https://www.universal-devices.com/my-tickets/

Maybe include a link to this thread.

Before you open the support ticket can you also run event viewer on level 3 and see if there's anything being generated in there?

This might be a case where support for the i3 is almost perfect, but something is off. Glad it seems to be narrowed down to a device situation.

I opened a ticket, and will let you know the results.