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!

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? 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.

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. 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? 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.

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!

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?

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!

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) 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.

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.

Which one is the unrelated one? 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. 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

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) 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! 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!

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!!)

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

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?