The basics.....

[Steven M Castano]

I have a very basic requirement, but being totally new to ISY programming.... I could use a bit of a hand.

 

I've got a SwithLinc Dimmer connected to a single light in my dinning room. I'd like to figure out how to create time dependant ON levels. I'd like the lights to come up at 50% from Sunset to Sunrise, and 100% the rest of the time. I'd also like to be able to trigger this behavior from both the SwitchLinc itself and MobiLinc Pro.

 

I've got some basic ideas on where to begin, but can't be too sure. Here's what I've got so far:

 

1) a scene called "DR-Automated" with only 1 member, the SwitchLinc Dimmer

2) a program called "DR-Automation" with a time clause of "If From Sunrise To Sunset (same day)" Then "In Scene 'DR-Automated' Set 'DR-Light' 100% (On Level)" followed by a "Wait 2 minutes"

 

Then I've got an Else statement that sets the on level to 50% and also waits 2 minutes.

 

So the question is, how do I make this actually work now?

 

Ideally, I'd like the on button to make the lights come on full during the day, 50% at night, a double press to bring them on full regardless of time and a single press to always turn them off.

 

So... where do I actually start?

[LeeG]

The first statement in the Program Then sets the Local On Level of ‘SwitchLinc Dimmer DB’ to 50% which affects what happens when the paddle is pressed On. The second statement in the Then clause sets the Scene Responder On Level to 50% which affects what happens when the Scene is invoked from MobiLinc

 

The Else clause sets the Local On Level and Responder On Level to 100%.

 

Scene ‘SceneCrossLink’ has ‘SwitchLinc Dimmer DB’ as a Controller.

 

 

If
       From    Sunset 
       To      Sunrise (next day)

Then
       In Scene 'SwitchLinc Dimmer DB' Set 'SwitchLinc Dimmer DB' 50% (On Level)
       In Scene 'SceneCrossLink' Set 'SwitchLinc Dimmer DB' 50% (On Level)

Else
       In Scene 'SwitchLinc Dimmer DB' Set 'SwitchLinc Dimmer DB' 100% (On Level)
       In Scene 'SceneCrossLink' Set 'SwitchLinc Dimmer DB' 100% (On Level)

[Steven M Castano]

Ok, I think that makes sense.... I'm headed home for work in a few minutes and I'll try this out. I'll let you know how it goes, thanks!

 

*SMC

[Steven M Castano]

Ok... so, it seems to work, but it's got some strange issues.

 

I've got a scene called "DR-Scene-Automated" with the SwitchLinc dimmer as a responder and a scene called "DR-Scene-CrossLink" with the SwitchLinc Dimmer as a controller.

 

The program is basically

 

IF:  
    From Sunset to Sunrise (next day)
THEN: 
    In Scene "DR-Scene-Automated" Set "DR-SwitchLincDimmer" 50% (On Level)
    In Scene "DR-Scene-CrossLink" Set "DR-SwitchLincDimmer" 50% (On Level)
ELSE:
    In Scene "DR-Scene-Automated" Set "DR-SwitchLincDimmer" 100% (On Level)
    In Scene "DR-Scene-CrossLink" Set "DR-SwitchLincDimmer" 100% (On Level)

 

This seems to work perfectly from MobiLinc, I'll test again in the morning to confirm it works at the 100% level, but it seems to be operating perfectly.

 

The strange behavior is from the SwitchLinc Dimmer itself. If you press the paddle ON, it goes up to 50% as expected. Press the paddle OFF, it lights go off as expected. If you press the paddle ON twice, go activate a FAST ON, which I understand is the way the SwitchLinc Dimmers work by default, the lights come on to 100%, as expected. Then pressing the paddle OFF turns them off as expected. The problem is.... if you press the paddle ON once again, the lights go right back up to 100% in stead of 50%. This happens every time until I turn the scene on and off again from MobiLinc.

 

I'm thinking the program needs to loop maybe? Or have some command set for when the paddle is pressed off?

 

Or did I just miss something completely?

 

(I can attach screen shots if needed)

 

Thanks in advance! (again!!)

[LeeG]

To change the SwitchLinc Dimmer Local On Level the Adjust Scene 'In Scene' parameter must specify the node name of the Switchlinc Dimmer, not the Scene name.

 

Also, the only way to know for sure the speed of the paddle double tap On press is generating a Fast On is run Tools | Diagnostics | Event Viewer at LEVEL 3. The annotation of the command name will indicate a Fast On plus the command for a Fast On is 0x12. The Standard On command is 0x11. The double tap On paddle press might be generating two On commands.

 

Regardless of the double tap results the Adjust Scene must specify the SwitchLinc node in both the 'In Scene' and 'Set' parameters. That is the combination the ISY uses to indicate the Local On Level is to be changed.

[Steven M Castano]

To change the SwitchLinc Dimmer Local On Level the Adjust Scene 'In Scene' parameter must specify the node name of the Switchlinc Dimmer, not the Scene name.

 

So, I've change the program to use the device itself as the first line of both the THEN and ELSE statements as follows:

IF:  
    From Sunset to Sunrise (next day)
THEN: 
    In Scene "DR-SwitchLincDimmer" Set "DR-SwitchLincDimmer" 50% (On Level)
    In Scene "DR-Scene-CrossLink" Set "DR-SwitchLincDimmer" 50% (On Level)
ELSE:
    In Scene "DR-SwitchLincDimmer" Set "DR-SwitchLincDimmer" 100% (On Level)
    In Scene "DR-Scene-CrossLink" Set "DR-SwitchLincDimmer" 100% (On Level)

 

 

Also, the only way to know for sure the speed of the paddle double tap On press is generating a Fast On is run Tools | Diagnostics | Event Viewer at LEVEL 3. The annotation of the command name will indicate a Fast On plus the command for a Fast On is 0x12. The Standard On command is 0x11. The double tap On paddle press might be generating two On commands.

 

So here's for the hard to read part. The first paste here is 3 steps:

1) I right click on the program and click to run the "If" portion since I just updated it

2) A single paddle press on

3) A single paddle press off

 

Tue 01/29/2013 06:18:37 AM : [        Time] 06:18:37 0(0)
Tue 01/29/2013 06:18:37 AM : [  20 AD 6D 1]       OL 127
Tue 01/29/2013 06:18:37 AM : [iNST-TX-I2CS] 02 62 20 AD 6D 1F 2F 00 00 02 0F D7 08 A2 17 1E 80 B1 7F 1F 01 3A
Tue 01/29/2013 06:18:37 AM : [iNST-ACK    ] 02 62 20.AD.6D 1F 2F 00 00 02 0F D7 08 A2 17 1E 80 B1 7F 1F 01 3A 06        (00)
Tue 01/29/2013 06:18:39 AM : [iNST-SRX    ] 02 50 20.AD.6D 1E.80.B1 23 2F 00           (00)
Tue 01/29/2013 06:18:39 AM : [std-Direct Ack] 20.AD.6D-->ISY/PLM Group=0, Max Hops=3, Hops Left=0
Tue 01/29/2013 06:18:39 AM : [iNST-TX-I2CS] 02 62 20 AD 6D 1F 2E 00 01 06 7F 00 00 00 00 00 00 00 00 00 00 4C
Tue 01/29/2013 06:18:39 AM : [iNST-ACK    ] 02 62 20.AD.6D 1F 2E 00 01 06 7F 00 00 00 00 00 00 00 00 00 00 4C 06        (00)
Tue 01/29/2013 06:18:39 AM : [iNST-SRX    ] 02 50 20.AD.6D 1E.80.B1 23 2E 00           (00)
Tue 01/29/2013 06:18:39 AM : [std-Direct Ack] 20.AD.6D-->ISY/PLM Group=0, Max Hops=3, Hops Left=0
Tue 01/29/2013 06:19:02 AM : [iNST-SRX    ] 02 50 20.AD.6D 00.00.01 C3 11 00    LTONRR (00)
Tue 01/29/2013 06:19:02 AM : [std-Group   ] 20.AD.6D-->Group=1, Max Hops=3, Hops Left=0
Tue 01/29/2013 06:19:02 AM : [  20 AD 6D 1]      DON   0
Tue 01/29/2013 06:19:02 AM : [  20 AD 6D 1]       ST 127
Tue 01/29/2013 06:19:02 AM : [iNST-SRX    ] 02 50 20.AD.6D 11.00.01 C3 06 00           (00)
Tue 01/29/2013 06:19:02 AM : [std-Group   ] 20.AD.6D-->11.00.01, Max Hops=3, Hops Left=0
Tue 01/29/2013 06:19:10 AM : [iNST-SRX    ] 02 50 20.AD.6D 00.00.01 C3 13 00    LTOFFRR(00)
Tue 01/29/2013 06:19:10 AM : [std-Group   ] 20.AD.6D-->Group=1, Max Hops=3, Hops Left=0
Tue 01/29/2013 06:19:10 AM : [  20 AD 6D 1]      DOF   0
Tue 01/29/2013 06:19:10 AM : [  20 AD 6D 1]       ST   0
Tue 01/29/2013 06:19:10 AM : [iNST-SRX    ] 02 50 20.AD.6D 13.00.01 C3 06 00           (00)
Tue 01/29/2013 06:19:10 AM : [std-Group   ] 20.AD.6D-->13.00.01, Max Hops=3, Hops Left=0

 

It would seem to me that the "ST 127" line is the on level in the range of 0 - 255, it's right at 50% like I'd expect. The next one is the double paddle press ON that seems to get me:

 

Tue 01/29/2013 06:20:41 AM : [iNST-SRX    ] 02 50 20.AD.6D 00.00.01 C7 12 00    LTON-F (00)
Tue 01/29/2013 06:20:41 AM : [std-Group   ] 20.AD.6D-->Group=1, Max Hops=3, Hops Left=1
Tue 01/29/2013 06:20:41 AM : [  20 AD 6D 1]     DFON   0
Tue 01/29/2013 06:20:41 AM : [  20 AD 6D 1]       ST 255
Tue 01/29/2013 06:20:41 AM : [iNST-SRX    ] 02 50 20.AD.6D 12.00.01 C3 06 00           (00)
Tue 01/29/2013 06:20:41 AM : [std-Group   ] 20.AD.6D-->12.00.01, Max Hops=3, Hops Left=0
Tue 01/29/2013 06:20:43 AM : [iNST-SRX    ] 02 50 20.AD.6D 00.00.01 C3 13 00    LTOFFRR(00)
Tue 01/29/2013 06:20:43 AM : [std-Group   ] 20.AD.6D-->Group=1, Max Hops=3, Hops Left=0
Tue 01/29/2013 06:20:43 AM : [  20 AD 6D 1]      DOF   0
Tue 01/29/2013 06:20:44 AM : [  20 AD 6D 1]       ST   0
Tue 01/29/2013 06:20:44 AM : [iNST-SRX    ] 02 50 20.AD.6D 13.00.01 C3 06 00           (00)
Tue 01/29/2013 06:20:44 AM : [std-Group   ] 20.AD.6D-->13.00.01, Max Hops=3, Hops Left=0
Tue 01/29/2013 06:20:46 AM : [iNST-SRX    ] 02 50 20.AD.6D 00.00.01 C7 11 00    LTONRR (00)
Tue 01/29/2013 06:20:46 AM : [std-Group   ] 20.AD.6D-->Group=1, Max Hops=3, Hops Left=1
Tue 01/29/2013 06:20:46 AM : [  20 AD 6D 1]      DON   0
Tue 01/29/2013 06:20:46 AM : [  20 AD 6D 1]       ST 127
Tue 01/29/2013 06:20:46 AM : [iNST-SRX    ] 02 50 20.AD.6D 11.00.01 C3 06 00           (00)
Tue 01/29/2013 06:20:46 AM : [std-Group   ] 20.AD.6D-->11.00.01, Max Hops=3, Hops Left=0
Tue 01/29/2013 06:20:48 AM : [iNST-SRX    ] 02 50 20.AD.6D 00.00.01 C3 13 00    LTOFFRR(00)
Tue 01/29/2013 06:20:48 AM : [std-Group   ] 20.AD.6D-->Group=1, Max Hops=3, Hops Left=0
Tue 01/29/2013 06:20:48 AM : [  20 AD 6D 1]      DOF   0
Tue 01/29/2013 06:20:48 AM : [  20 AD 6D 1]       ST   0
Tue 01/29/2013 06:20:48 AM : [iNST-SRX    ] 02 50 20.AD.6D 13.00.01 C3 06 00           (00)
Tue 01/29/2013 06:20:48 AM : [std-Group   ] 20.AD.6D-->13.00.01, Max Hops=3, Hops Left=0
Tue 01/29/2013 06:20:51 AM : [iNST-SRX    ] 02 50 20.AD.6D 00.00.01 C7 11 00    LTONRR (00)
Tue 01/29/2013 06:20:51 AM : [std-Group   ] 20.AD.6D-->Group=1, Max Hops=3, Hops Left=1
Tue 01/29/2013 06:20:51 AM : [  20 AD 6D 1]      DON   0
Tue 01/29/2013 06:20:51 AM : [  20 AD 6D 1]       ST 127
Tue 01/29/2013 06:20:51 AM : [iNST-SRX    ] 02 50 20.AD.6D 11.00.01 C3 06 00           (00)
Tue 01/29/2013 06:20:51 AM : [std-Group   ] 20.AD.6D-->11.00.01, Max Hops=3, Hops Left=0
Tue 01/29/2013 06:20:52 AM : [iNST-SRX    ] 02 50 20.AD.6D 00.00.01 C7 13 00    LTOFFRR(00)
Tue 01/29/2013 06:20:52 AM : [std-Group   ] 20.AD.6D-->Group=1, Max Hops=3, Hops Left=1
Tue 01/29/2013 06:20:52 AM : [  20 AD 6D 1]      DOF   0
Tue 01/29/2013 06:20:52 AM : [  20 AD 6D 1]       ST   0
Tue 01/29/2013 06:20:52 AM : [iNST-SRX    ] 02 50 20.AD.6D 13.00.01 C3 06 00           (00)
Tue 01/29/2013 06:20:52 AM : [std-Group   ] 20.AD.6D-->13.00.01, Max Hops=3, Hops Left=0

 

This last log is a few steps:

1) a quick double paddle press, which I assume by the "ST 255" is the on level at 100% as expected, also I think the first line ending in "12 00 LTON-F (00)" indicated the "FAST ON" since that's how the light acted. (quickly came on, no ramp rate)

2) next is a single paddle press off (turns light off as expected

3) a single paddle press on, which appears to be at the 50% level.... however the light comes on full

4) single paddle press off which does turn the light off

5) single paddle press on (to make sure I'm not crazy) and the light does come on full again

6) single paddle press off followed by me coming back here to post this!

 

Regardless of the double tap results the Adjust Scene must specify the SwitchLinc node in both the 'In Scene' and 'Set' parameters. That is the combination the ISY uses to indicate the Local On Level is to be changed.

 

So I would think at this point, I've got everything setup exactly as you described, but still not the behavior I'm looking for. Thanks again for all your help, this is great and I sure am learning a TON! Hopefully things like this will keep me moving forward and I can start helping others in return!

[oberkc]

I only have a couple of things to observe. One is unrelated.

 

First, the hop cound (hops left = 0) I see in your event viewer suggest (to me at least) that you have something going on that makes communication between devices a little troublesome.

 

Regarding your stated problem, I don't see anything in the program that would cause the observed behavior. I cannot help but wonder about your switchlinc, however. It sounds as if it is reverting to last state, somehow, for "on" levels. I had a couple of X-10 devices that did this. What kind of device is this "switchlinc dimmer"?

[Steven M Castano]

I only have a couple of things to observe. One is unrelated.

Which one is the unrelated one?

 

First, the hop cound (hops left = 0) I see in your event viewer suggest (to me at least) that you have something going on that makes communication between devices a little troublesome.

It's possible... I did have some odd network issues for a while, but it seems like everything is 100% working all the time. Every time I issue a command from the ISY to this device (and all the others) it works every single time.... so I'm not sure.

 

Regarding your stated problem, I don't see anything in the program that would cause the observed behavior. I cannot help but wonder about your switchlinc, however. It sounds as if it is reverting to last state, somehow, for "on" levels. I had a couple of X-10 devices that did this. What kind of device is this "switchlinc dimmer"?

It does seem to be reverting to the last state, especially since the log appears to be attempting to turn the device on at "ST 127" or 50%, but the lights are surely coming on at 100%. As for the SwithLinc Dimmer, it's a smarthome dual-band 2477D v6.9

[Steven M Castano]

Just a side note: while doing some testing of my own here I create 2 programs, but are copies of the original:

IF:   its between sunset and sunrise
THEN: set both switchlinc and scene levels to 100%
ELSE: set both switchlinc and scene levels to 100%

 

The only difference is that one of them has the additional 'Condition' of "Status 'DR-SwitchLincDimmer' is On" and the other says "Status 'DR-SwitchLincDimmer' is Off". Seems to work great. As long as I give the ISY a chance to write that on level back out to the device it works. Just not sure why it doesn't work as expected the other way.

[LeeG]

The Hops Left=0 indicates the comm between the PLM and the SwitchLinc is working at the very extreme of reliability. May be producing consistent command response but any additional interference and the setup has nowhere to go except fail. Something to look at after the On Level is resolved.

 

When testing new Program variations keep in mind the ISY does not write the Local On Level information when the ISY thinks the device already has that information. Changing the Program If section and running the Program again is not actually sending the Local On Level information again. To insure the SwitchLinc is receiving the Local On Level change it is necessary to change the Local On Level percentage in the Program, Save change then run the Program. Also a good idea to run the actual section being tested rather than running the If. Run Then or Run Else.

 

Seeing pseudo code rather than the actual Program code leaves open questions. Right click the Program name, select Copy to Clipboard. Then Paste into posts.

 

What is the SwitchLinc firmware level? Right pane, line 2. below device name.

 

I have not been able to recreate the described behavior here. The SwitchLinc goes to the lower On Level with a single paddle press even after a Fast On so long as there is an Off paddle press in between. Thus the question of SwitchLinc firmware level.

[Steven M Castano]

The Hops Left=0 indicates the comm between the PLM and the SwitchLinc is working at the very extreme of reliability. May be producing consistent command response but any additional interference and the setup has nowhere to go except fail. Something to look at after the On Level is resolved.

 

When testing new Program variations keep in mind the ISY does not write the Local On Level information when the ISY thinks the device already has that information. Changing the Program If section and running the Program again is not actually sending the Local On Level information again. To insure the SwitchLinc is receiving the Local On Level change it is necessary to change the Local On Level percentage in the Program, Save change then run the Program. Also a good idea to run the actual section being tested rather than running the If. Run Then or Run Else.

 

Seeing pseudo code rather than the actual Program code leaves open questions. Right click the Program name, select Copy to Clipboard. Then Paste into posts.

 

If
       From    Sunset 
       To      Sunrise (next day)

Then
       In Scene 'Dining Room / Devices / Dining Room Chandelier' Set 'Dining Room / Devices / Dining Room Chandelier' 50% (On Level)
       In Scene 'Dining Room / Devices / Dining Room Chandelier' Set 'Dining Room / Devices / Dining Room Chandelier' 2.0 Sec (Ramp Rate)
       In Scene 'Dining Room / Scenes / DR-Scene-CrossLink' Set 'Dining Room / Devices / Dining Room Chandelier' 50% (On Level)
       In Scene 'Dining Room / Scenes / DR-Scene-CrossLink' Set 'Dining Room / Devices / Dining Room Chandelier' 2.0 Sec (Ramp Rate)

Else
       In Scene 'Dining Room / Devices / Dining Room Chandelier' Set 'Dining Room / Devices / Dining Room Chandelier' 100% (On Level)
       In Scene 'Dining Room / Devices / Dining Room Chandelier' Set 'Dining Room / Devices / Dining Room Chandelier' 2.0 Sec (Ramp Rate)
       In Scene 'Dining Room / Scenes / DR-Scene-CrossLink' Set 'Dining Room / Devices / Dining Room Chandelier' 100% (On Level)
       In Scene 'Dining Room / Scenes / DR-Scene-CrossLink' Set 'Dining Room / Devices / Dining Room Chandelier' 2.0 Sec (Ramp Rate)

 

What is the SwitchLinc firmware level? Right pane, line 2. below device name.

 

I have not been able to recreate the described behavior here. The SwitchLinc goes to the lower On Level with a single paddle press even after a Fast On so long as there is an Off paddle press in between. Thus the question of SwitchLinc firmware level.

 

20.AD.6D - (2477D) Dual Band SwitchLinc Dimmer v.41

 

The odd part is that after a double paddle press FAST ON, then a paddle press OFF.... the switch continues to go up to the full brightness, every time. However, if I run through my "DC-Scene-CrossLink" from MobiLinc it works without issue. The strange part is that after I run the scene in MobiLinc, the switch begins to act normally again.... until another double paddle press ON.

[LeeG]

I am concerned the SwitchLinc v.41 firmware has changed the way the SwitchLinc is responding. I am testing on a v.38 which does not go back to 100% after a Fast On. I'll see if I have v.41 available for test.

[Steven M Castano]

That would be awesome! Thanks!!

 

Then, if it turns out it is different... I'll probably need a hand figuring out how to program around it!

[LeeG]

Sorry, my latest Dual Band SwitchLinc is v.40 which works as the v.38 does. The Fast On does not affect the next On paddle press. It comes back to 50% On with a Fast On, Off, On.

 

20.AD.6D is the SwitchLinc in question?

[Steven M Castano]

20.AD.6D is the SwitchLinc in question?

 

Yes, it is.....

 

And from the logs I posted above... why does it seem like the ISY is sending the command to turn the lights on at 50% (ST 127), but they still come up at 100%. That's what seems odd to me.

 

The programming seems like its working fine, yet the FAST ON paddle press seems to be remembered on successive paddle ONs. Almost like its remembering its previous state. I'd suspect a missed connection or something, but all the traffic is obviously making it to the ISY from the logs....

 

So, what next?

[LeeG]

The ISY is not sending a command to turn the SwitchLinc On. The trace entries show an On paddle press which the ISY marks the device at 50% because that is what the Local On Level is set to. The ISY is expecting the device to react to the Local On Level value.

 

When the SwitchLinc paddle is pressed On or Off it initiates an Insteon Group protocol sequence. The messages sent to the PLM indicate which paddle/button is pressed (On or Off) but carries no information about the actual On level the device went to. This is why the ISY relies on Local On Level information to mark the device On Level. Nothing in these Insteon Group protocol messages contain actual On level.

 

Tue 01/29/2013 06:20:51 AM : [iNST-SRX ] 02 50 20.AD.6D 00.00.01 C7 11 00 LTONRR (00)

Tue 01/29/2013 06:20:51 AM : [std-Group ] 20.AD.6D-->Group=1, Max Hops=3, Hops Left=1

Tue 01/29/2013 06:20:51 AM : [ 20 AD 6D 1] DON 0

Tue 01/29/2013 06:20:51 AM : [ 20 AD 6D 1] ST 127

Tue 01/29/2013 06:20:51 AM : [iNST-SRX ] 02 50 20.AD.6D 11.00.01 C3 06 00 (00)

Tue 01/29/2013 06:20:51 AM : [std-Group ] 20.AD.6D-->11.00.01, Max Hops=3, Hops Left=0

 

I have no next. The trace shows the Local On Level being set to 0x7F which is nominally 50% Local On Level. Your relating of the actual device reaction is that this is ignored after a Fast On. Testing on a V.38 and V.40 shows these devices honor the Local On Level after a Fast On. Conclusion, v.41 operates differently. Would have to see this from more than one v.41 to know this is not a specific device issue rather than a v.41 firmware design change.

[Steven M Castano]

Another things that puzzles me.... how long do you have to wait before a second paddle press isn't considers a "doube tap" anymore? and simply another "on" command?

 

Even if I wait a few seconds between then.... I tap the ON paddle, lights come on to %50.... then I wait 10 seconds and tap the ON paddle again, lights go up to 100%.... then they're back up to 100% on each ON tap until I rub through the scene in MobiLinc again.

 

I may try to take this thread over to the SmartHome forum also... maybe dig for some more info there too. Maybe even call the Orchestrated Home guys where I bought everything. They should have everything with the exact right firmware to test.

 

Thanks for all the help as always. I will post more info when I get some more testing done!

[oberkc]

This is not something I routinely do with my system, however, my recollection is that if I press ON once, it goes to the pre-defined level. If starting at the pre-defined level and I press ON again (regardless of wait time) it goes to full bright. If starting at full bright and I press ON again, the device will revert back to the the local ON settings. In effect, repetitive presses of the ON button would toggle between full and the locaol ON level.

 

I don't know why mine would be different than yours, other than some change made by smarthome, or a device defect.

 

Is it possible that you have some program running which would cause this behavior? Do you see any program status who's last run time corresponds to switch input?

[Steven M Castano]

This is not something I routinely do with my system, however, my recollection is that if I press ON once, it goes to the pre-defined level. If starting at the pre-defined level and I press ON again (regardless of wait time) it goes to full bright. If starting at full bright and I press ON again, the device will revert back to the the local ON settings. In effect, repetitive presses of the ON button would toggle between full and the locaol ON level.?

 

This first half of this behavior is true. If I press the ON once, it goes up to 50%, this if I press it again... regardless of time, it does infact go to full brightness. I don't think I've tried to press it again a third time and I'm at work for the day now, but I will surely try that when I get home.

 

I don't know why mine would be different than yours, other than some change made by smarthome, or a device defect.

 

How does yours behave on successive ONs? This would be the test to confirm if the behavior is the same:

1) Press ON, let the lights come up to the defined level

2) Press ON again, let the lights come up to full brightness

3) Press OFF, let the lights go completely off.

4) Now press ON once, what happens?

 

Is it possible that you have some program running which would cause this behavior? Do you see any program status who's last run time corresponds to switch input?

 

I had a bunch of programs that I was testing, but when I was working on this issue this mornig, I disable EVERYTHING other than the program I posted earlier in this thread for LeeG. Since it's not tied to any actions and only intended to exectue when the ISY comes on, and at Sunset and Sunrise, it seemed to be working fine. As in, it did not get triggered with any ON or OFFs from the SwitchLinc Dimmer.

[LeeG]

"Even if I wait a few seconds between then.... I tap the ON paddle, lights come on to %50.... then I wait 10 seconds and tap the ON paddle again, lights go up to 100%...."

 

All the SwitchLincs I have tested over the years behave this way. Repetitive On paddle presses (not Fast On) cycle the SwitchLinc from the Local On Level to Full On to Local On Level. All the SwitchLincs I have tested operate this way.

 

The difference with the v.41 firmware is that Fast On causes the repetitive On paddle presses to go to full On. That I have not seen before and is not the way my v.38 and v.40 operate.

 

SmartLabs does not publish changes so whether this is by design or an oops or something limited to your SwitchLinc only testing with other v.41 devices will answer.

[Steven M Castano]

"Even if I wait a few seconds between then.... I tap the ON paddle, lights come on to %50.... then I wait 10 seconds and tap the ON paddle again, lights go up to 100%...."

 

All the SwitchLincs I have tested over the years behave this way. Repetitive On paddle presses (not Fast On) cycle the SwitchLinc from the Local On Level to Full On to Local On Level. All the SwitchLincs I have tested operate this way.

 

Ok, this means 2 things:

1) The SwitchLinc isn't broken

2) I'm not crazy! (I was starting to wonder)

 

The question is, is there a way to reset it? So when I turn the lights off again... the next time a single paddle press ON is executed, the lights come on to the local on level, instead of full on?

 

The difference with the v.41 firmware is that Fast On causes the repetitive On paddle presses to go to full On. That I have not seen before and is not the way my v.38 and v.40 operate.

 

SmartLabs does not publish changes so whether this is by design or an oops or something limited to your SwitchLinc only testing with other v.41 devices will answer.

 

I will surely have to test this more when I get home today. Thanks for discovering the change here.... I'm going to post about it on the SmartHome forums also and see if I can get an answer there.

[LeeG]

"The question is, is there a way to reset it? So when I turn the lights off again... the next time a single paddle press ON is executed, the lights come on to the local on level, instead of full on?"

 

Unfortunately I do not have a v.41 to test against so see if the Fast On change is on all the V.41 SwitchLinc or just yours. Nor do I have a vehicle to test against to find some way to bypass the Fast On results.

 

Perhaps someone with a v.41 can add additional information.

[oberkc]

How does yours behave on successive ONs? This would be the test to confirm if the behavior is the same:

1) Press ON, let the lights come up to the defined level

2) Press ON again, let the lights come up to full brightness

3) Press OFF, let the lights go completely off.

4) Now press ON once, what happens?

 

Based on memory, mine is the same as LeeG. At step four, mine would go to defined level, not full on. I will confirm when I get home, as well as check to see if I have any v.41 devices.

[Steven M Castano]

Thanks guys, I'm posting about it now over at the smarthome forums also and when I get home I will test 2 things:

 

1) will a third press of the on paddle return the lights to 50%.

2) will a fast on (quick double press) behave the same way as the slower "on - on" double press.

 

Thanks again for all the help!!! I can't wait to have this resolved and for the rest of my switches and modules to come in.... there's a lot more house to automate!

[MikeD]

All the SwitchLincs I have tested over the years behave this way. Repetitive On paddle presses (not Fast On) cycle the SwitchLinc from the Local On Level to Full On to Local On Level. All the SwitchLincs I have tested operate this way.

 

The difference with the v.41 firmware is that Fast On causes the repetitive On paddle presses to go to full On. That I have not seen before and is not the way my v.38 and v.40 operate.

 

I have v.41 SwitchLincs and they operate the way you describe all previous versions operate. Repetitive On paddle presses (not Fast On) cycle the SwitchLinc from the Local On Level to Full On to Local On Level.

 

Also tested the following sequence:

1) Press ON, let the lights come up to the defined level - Correct

2) Press ON again, let the lights come up to full brightness - Correct

3) Press OFF, let the lights go completely off. - Correct

4) Now press ON once, what happens? - The lights come up to the defined level

 

~Mike