LeeG Posted January 29, 2013 Share Posted January 29, 2013 MikeD Can you add a Fast On paddle press into the mix. After the Fast On followed by Off paddle press the next On paddle press goes to 100% rather than the expected 50% for the OP. scastano What Tom is suggesting is a test that will eliminate the ISY as a possible cause of this because the interface to an I2CS SwitchLinc Dimmer has changed. Disable the ISY Program that changes the Local On Levels. Use the SwitchLinc Dimmer User Guide, setting the Local On Level to 100% to confirm the manual change. Then set the Local On Level to 50% and verify that the simple On paddle press does now go to 50% On. Then add the Fast On paddle press into the mix. If the Fast On does not affect later On paddle press operations the I2CS SwitchLinc Dimmer has changed the commands needed to correctly set the Local On Level. I don't think this is the case but Tom raises a good point. Other I2CS devices (I/O Linc being the last one I remember) have required alternate approaches to setting options. Link to comment
Steven M Castano Posted January 29, 2013 Author Share Posted January 29, 2013 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 Mike, THANKS! I will test this as soon as I get home. I'm almost 100% sure I DID try this and the last press of the ON button put them back up to full instead of 50%. I should be home in about 3 hours, I'll let you all know! Link to comment
Steven M Castano Posted January 29, 2013 Author Share Posted January 29, 2013 scastano What Tom is suggesting is a test that will eliminate the ISY as a possible cause of this because the interface to an I2CS SwitchLinc Dimmer has changed. Disable the ISY Program that changes the Local On Levels. Use the SwitchLinc Dimmer User Guide, setting the Local On Level to 100% to confirm the manual change. Then set the Local On Level to 50% and verify that the simple On paddle press does now go to 50% On. Then add the Fast On paddle press into the mix. If the Fast On does not affect later On paddle press operations the I2CS SwitchLinc Dimmer has changed the commands needed to correctly set the Local On Level. I don't think this is the case but Tom raises a good point. Other I2CS devices (I/O Linc being the last one I remember) have required alternate approaches to setting options. I will test this ASAP when I get home also. Thanks! Link to comment
MikeD Posted January 29, 2013 Share Posted January 29, 2013 Can you add a Fast On paddle press into the mix. After the Fast On followed by Off paddle press the next On paddle press goes to 100% rather than the expected 50% for the OP. Started with the my SwitchLinc (2477D v.41) in the Off condition 1) Paddle press Fast On - the lights come on 100% 2) Paddle press Off - the lights go completely off 3) Paddle press On - the lights go to my "On Level [Applied Locally]" setting ~Mike Link to comment
LeeG Posted January 29, 2013 Share Posted January 29, 2013 Thanks Mike. That is actually great news. Means the OP SwitchLinc is not working as yours is. Actually that raises another question. The Local On Level is being set with the Admin Console On Level (applied locally) slider? That is something else the OP can try. The scenario being used thus far is using Adjust Scene to set the Local On Level. Should be the same extended command but that is a variable to eliminate. Thanks again. scastano I believe Mike is using the Admin Console to set what amounts to a static Local On Level. Don't think that will make any difference but that is another test you can run. Click the SwitchLinc node and move the On Level (applied locally) slider to something different such as 55% percent and then do the Fast On, Off, On paddle test after the Progress Bar completes making the slider change. Link to comment
Steven M Castano Posted January 29, 2013 Author Share Posted January 29, 2013 I believe Mike is using the Admin Console to set what amounts to a static Local On Level. Don't think that will make any difference but that is another test you can run. Click the SwitchLinc node and move the On Level (applied locally) slider to something different such as 55% percent and then do the Fast On, Off, On paddle test after the Progress Bar completes making the slider change. Perfect, I'll add that as another test case. I'm also going to disable all programs in my ISY-994i other than the "Query All" that was there when I started. I'm just itching to get out of work and try it... I may leave shortly, a few minutes early, just to get home and test this. Link to comment
oberkc Posted January 29, 2013 Share Posted January 29, 2013 I have only a single v.41 switch, but it is a relay. The two switches I tested (both v.38) behaved just as did MikeD. When off, pressing the on button brings it up to preset levels. This happens always, regardless of recent paddle presses fast on or not. Link to comment
Steven M Castano Posted January 29, 2013 Author Share Posted January 29, 2013 Ok, I'm home! Here we go with the first test. First off, to set everything up I have disable every program in my ISY except for the "Query All" program that was on my default when the unit shipped. I have also gone into my "DR-Scene-CrossLink" scene, selected the "Dinning Room Chandelier" (which is a controller in this scene) and set its [Applied Locally] On Level to 60% and the Ramp Rate to 2.0 seconds. 1) First ON press, I expect lights to go to 60% - THIS WORKS 2) Second ON press, I expect lights to go to 100% - THIS WORKS 3) Third ON press, I expect lights to go to 60% - THIS DOESN'T Here is the log: Tue 01/29/2013 05:47:21 PM : [iNST-SRX ] 02 50 20.AD.6D 00.00.01 C3 11 00 LTONRR (00) Tue 01/29/2013 05:47:21 PM : [std-Group ] 20.AD.6D-->Group=1, Max Hops=3, Hops Left=0 Tue 01/29/2013 05:47:21 PM : [ 20 AD 6D 1] DON 0 Tue 01/29/2013 05:47:21 PM : [ 20 AD 6D 1] ST 153 Tue 01/29/2013 05:47:21 PM : [iNST-SRX ] 02 50 20.AD.6D 11.00.01 C3 06 00 (00) Tue 01/29/2013 05:47:21 PM : [std-Group ] 20.AD.6D-->11.00.01, Max Hops=3, Hops Left=0 Tue 01/29/2013 05:47:21 PM : [iNST-SRX ] 02 50 20.AD.6D 11.00.01 C3 06 00 (00) Tue 01/29/2013 05:47:21 PM : [std-Group ] 20.AD.6D-->11.00.01, Max Hops=3, Hops Left=0 Tue 01/29/2013 05:47:21 PM : [iNST-DUP ] Previous message ignored. Tue 01/29/2013 05:47:46 PM : [iNST-SRX ] 02 50 20.AD.6D 00.00.01 CB 11 00 LTONRR (00) Tue 01/29/2013 05:47:46 PM : [std-Group ] 20.AD.6D-->Group=1, Max Hops=3, Hops Left=2 Tue 01/29/2013 05:47:46 PM : [ 20 AD 6D 1] DON 0 Tue 01/29/2013 05:47:46 PM : [iNST-SRX ] 02 50 20.AD.6D 11.00.01 C3 06 00 (00) Tue 01/29/2013 05:47:46 PM : [std-Group ] 20.AD.6D-->11.00.01, Max Hops=3, Hops Left=0 Tue 01/29/2013 05:47:46 PM : [iNST-SRX ] 02 50 20.AD.6D 11.00.01 C3 06 00 (00) Tue 01/29/2013 05:47:46 PM : [std-Group ] 20.AD.6D-->11.00.01, Max Hops=3, Hops Left=0 Tue 01/29/2013 05:47:46 PM : [iNST-DUP ] Previous message ignored. Tue 01/29/2013 05:48:01 PM : [iNST-SRX ] 02 50 20.AD.6D 00.00.01 CB 11 00 LTONRR (00) Tue 01/29/2013 05:48:01 PM : [std-Group ] 20.AD.6D-->Group=1, Max Hops=3, Hops Left=2 Tue 01/29/2013 05:48:01 PM : [ 20 AD 6D 1] DON 0 Tue 01/29/2013 05:48:01 PM : [iNST-SRX ] 02 50 20.AD.6D 11.00.01 C3 06 00 (00) Tue 01/29/2013 05:48:01 PM : [std-Group ] 20.AD.6D-->11.00.01, Max Hops=3, Hops Left=0 So, now I can keep trying a few things. My next test will be the FAST ON test to see if I get any better behavior: 1) Double ON press for FAST on, expect lights to come on at 100% with no ramp rate - THIS WORKS 2) Single OFF press, expect list to go off to 0% ramp rate? - THIS WORKS (at the normal ramp rate of 2 seconds) 3) Single ON press, expect lights to come back to 60% - THIS DOESN'T WORK (it goes back to 100%, but the ISY reports 60%!) Here is the log: Tue 01/29/2013 05:47:21 PM : [iNST-SRX ] 02 50 20.AD.6D 00.00.01 C3 11 00 LTONRR (00) Tue 01/29/2013 05:47:21 PM : [std-Group ] 20.AD.6D-->Group=1, Max Hops=3, Hops Left=0 Tue 01/29/2013 05:47:21 PM : [ 20 AD 6D 1] DON 0 Tue 01/29/2013 05:47:21 PM : [ 20 AD 6D 1] ST 153 Tue 01/29/2013 05:47:21 PM : [iNST-SRX ] 02 50 20.AD.6D 11.00.01 C3 06 00 (00) Tue 01/29/2013 05:47:21 PM : [std-Group ] 20.AD.6D-->11.00.01, Max Hops=3, Hops Left=0 Tue 01/29/2013 05:47:21 PM : [iNST-SRX ] 02 50 20.AD.6D 11.00.01 C3 06 00 (00) Tue 01/29/2013 05:47:21 PM : [std-Group ] 20.AD.6D-->11.00.01, Max Hops=3, Hops Left=0 Tue 01/29/2013 05:47:21 PM : [iNST-DUP ] Previous message ignored. Tue 01/29/2013 05:47:46 PM : [iNST-SRX ] 02 50 20.AD.6D 00.00.01 CB 11 00 LTONRR (00) Tue 01/29/2013 05:47:46 PM : [std-Group ] 20.AD.6D-->Group=1, Max Hops=3, Hops Left=2 Tue 01/29/2013 05:47:46 PM : [ 20 AD 6D 1] DON 0 Tue 01/29/2013 05:47:46 PM : [iNST-SRX ] 02 50 20.AD.6D 11.00.01 C3 06 00 (00) Tue 01/29/2013 05:47:46 PM : [std-Group ] 20.AD.6D-->11.00.01, Max Hops=3, Hops Left=0 Tue 01/29/2013 05:47:46 PM : [iNST-SRX ] 02 50 20.AD.6D 11.00.01 C3 06 00 (00) Tue 01/29/2013 05:47:46 PM : [std-Group ] 20.AD.6D-->11.00.01, Max Hops=3, Hops Left=0 Tue 01/29/2013 05:47:46 PM : [iNST-DUP ] Previous message ignored. Ok, so now what? Link to comment
LeeG Posted January 29, 2013 Share Posted January 29, 2013 Since the observed results do not match the other v.41 SwitchLinc let’s see if there is a difference between the commands being issued to establish the Local On Level. With the Event Viewer running at LEVEL 3, click Clear to clear any current trace activity. Select the SwitchLinc node, use the On Level (applied locally) slider to set a 45% On Level. When the Progress bar is complete do the On, Off, On paddle test and the Fast On, Off, On paddle test. Post the trace so that the command used to set the Local On Level can be identified and whether the paddle tests have any results different from when the Adjust Scene statements are used to set the Local On Level. Link to comment
Steven M Castano Posted January 29, 2013 Author Share Posted January 29, 2013 Since the observed results do not match the other v.41 SwitchLinc let’s see if there is a difference between the commands being issued to establish the Local On Level. With the Event Viewer running at LEVEL 3, click Clear to clear any current trace activity. Select the SwitchLinc node, use the On Level (applied locally) slider to set a 45% On Level. When the Progress bar is complete do the On, Off, On paddle test and the Fast On, Off, On paddle test. Post the trace so that the command used to set the Local On Level can be identified and whether the paddle tests have any results different from when the Adjust Scene statements are used to set the Local On Level. 1) slider set to 45% - lights come on at 45% 2) pressed single off - lights go off 3) single on - lights at 45% 4) single off - lights go off 5) single on - lights at 45% again 6) single off - lights at 0% again 7) double on - lights quickly jump to 100% single off - lights obey ramp rate and go off 9) single on - light obey ramp rage, but go to 100% NOT 45%, however the ISY admin console reports it as 45% Here is the trace: Tue 01/29/2013 06:20:05 PM : [iNST-TX-I1 ] 02 62 20 AD 6D 0F 11 72 Tue 01/29/2013 06:20:05 PM : [iNST-ACK ] 02 62 20.AD.6D 0F 11 72 06 LTONRR (72) Tue 01/29/2013 06:20:05 PM : [iNST-SRX ] 02 50 20.AD.6D 1E.80.B1 2B 11 72 LTONRR (72) Tue 01/29/2013 06:20:05 PM : [std-Direct Ack] 20.AD.6D-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Tue 01/29/2013 06:20:05 PM : [ 20 AD 6D 1] ST 114 Tue 01/29/2013 06:20:05 PM : [ 20 AD 6D 1] OL 114 Tue 01/29/2013 06:20:05 PM : [iNST-TX-I2CS] 02 62 20 AD 6D 1F 2E 00 01 06 72 00 00 00 00 00 00 00 00 00 00 59 Tue 01/29/2013 06:20:05 PM : [iNST-ACK ] 02 62 20.AD.6D 1F 2E 00 01 06 72 00 00 00 00 00 00 00 00 00 00 59 06 (00) Tue 01/29/2013 06:20:05 PM : [iNST-SRX ] 02 50 20.AD.6D 1E.80.B1 27 2E 00 (00) Tue 01/29/2013 06:20:05 PM : [std-Direct Ack] 20.AD.6D-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Tue 01/29/2013 06:20:34 PM : [iNST-SRX ] 02 50 20.AD.6D 00.00.01 CB 13 00 LTOFFRR(00) Tue 01/29/2013 06:20:34 PM : [std-Group ] 20.AD.6D-->Group=1, Max Hops=3, Hops Left=2 Tue 01/29/2013 06:20:34 PM : [ 20 AD 6D 1] DOF 0 Tue 01/29/2013 06:20:34 PM : [ 20 AD 6D 1] ST 0 Tue 01/29/2013 06:20:34 PM : [iNST-SRX ] 02 50 20.AD.6D 13.00.01 C3 06 00 (00) Tue 01/29/2013 06:20:34 PM : [std-Group ] 20.AD.6D-->13.00.01, Max Hops=3, Hops Left=0 Tue 01/29/2013 06:20:50 PM : [iNST-SRX ] 02 50 20.AD.6D 00.00.01 CB 11 00 LTONRR (00) Tue 01/29/2013 06:20:50 PM : [std-Group ] 20.AD.6D-->Group=1, Max Hops=3, Hops Left=2 Tue 01/29/2013 06:20:50 PM : [ 20 AD 6D 1] DON 0 Tue 01/29/2013 06:20:50 PM : [ 20 AD 6D 1] ST 114 Tue 01/29/2013 06:20:50 PM : [iNST-SRX ] 02 50 20.AD.6D 11.00.01 C7 06 00 (00) Tue 01/29/2013 06:20:50 PM : [std-Group ] 20.AD.6D-->11.00.01, Max Hops=3, Hops Left=1 Tue 01/29/2013 06:21:11 PM : [iNST-SRX ] 02 50 20.AD.6D 00.00.01 CB 13 00 LTOFFRR(00) Tue 01/29/2013 06:21:11 PM : [std-Group ] 20.AD.6D-->Group=1, Max Hops=3, Hops Left=2 Tue 01/29/2013 06:21:11 PM : [ 20 AD 6D 1] DOF 0 Tue 01/29/2013 06:21:11 PM : [ 20 AD 6D 1] ST 0 Tue 01/29/2013 06:21:11 PM : [iNST-SRX ] 02 50 20.AD.6D 13.00.01 C3 06 00 (00) Tue 01/29/2013 06:21:11 PM : [std-Group ] 20.AD.6D-->13.00.01, Max Hops=3, Hops Left=0 Tue 01/29/2013 06:21:30 PM : [iNST-SRX ] 02 50 20.AD.6D 00.00.01 CB 11 00 LTONRR (00) Tue 01/29/2013 06:21:30 PM : [std-Group ] 20.AD.6D-->Group=1, Max Hops=3, Hops Left=2 Tue 01/29/2013 06:21:30 PM : [ 20 AD 6D 1] DON 0 Tue 01/29/2013 06:21:30 PM : [ 20 AD 6D 1] ST 114 Tue 01/29/2013 06:21:30 PM : [iNST-SRX ] 02 50 20.AD.6D 11.00.01 C7 06 00 (00) Tue 01/29/2013 06:21:30 PM : [std-Group ] 20.AD.6D-->11.00.01, Max Hops=3, Hops Left=1 Tue 01/29/2013 06:21:53 PM : [iNST-SRX ] 02 50 20.AD.6D 00.00.01 CB 13 00 LTOFFRR(00) Tue 01/29/2013 06:21:53 PM : [std-Group ] 20.AD.6D-->Group=1, Max Hops=3, Hops Left=2 Tue 01/29/2013 06:21:53 PM : [ 20 AD 6D 1] DOF 0 Tue 01/29/2013 06:21:53 PM : [ 20 AD 6D 1] ST 0 Tue 01/29/2013 06:22:04 PM : [iNST-SRX ] 02 50 20.AD.6D 00.00.01 C3 12 00 LTON-F (00) Tue 01/29/2013 06:22:04 PM : [std-Group ] 20.AD.6D-->Group=1, Max Hops=3, Hops Left=0 Tue 01/29/2013 06:22:04 PM : [ 20 AD 6D 1] DFON 0 Tue 01/29/2013 06:22:04 PM : [ 20 AD 6D 1] ST 255 Tue 01/29/2013 06:22:04 PM : [iNST-SRX ] 02 50 20.AD.6D 12.00.01 CB 06 00 (00) Tue 01/29/2013 06:22:04 PM : [std-Group ] 20.AD.6D-->12.00.01, Max Hops=3, Hops Left=2 Tue 01/29/2013 06:22:25 PM : [iNST-SRX ] 02 50 20.AD.6D 00.00.01 C7 13 00 LTOFFRR(00) Tue 01/29/2013 06:22:25 PM : [std-Group ] 20.AD.6D-->Group=1, Max Hops=3, Hops Left=1 Tue 01/29/2013 06:22:25 PM : [ 20 AD 6D 1] DOF 0 Tue 01/29/2013 06:22:25 PM : [ 20 AD 6D 1] ST 0 Tue 01/29/2013 06:22:25 PM : [iNST-SRX ] 02 50 20.AD.6D 13.00.01 C3 06 00 (00) Tue 01/29/2013 06:22:25 PM : [std-Group ] 20.AD.6D-->13.00.01, Max Hops=3, Hops Left=0 Tue 01/29/2013 06:22:43 PM : [iNST-SRX ] 02 50 20.AD.6D 00.00.01 CB 11 00 LTONRR (00) Tue 01/29/2013 06:22:43 PM : [std-Group ] 20.AD.6D-->Group=1, Max Hops=3, Hops Left=2 Tue 01/29/2013 06:22:43 PM : [ 20 AD 6D 1] DON 0 Tue 01/29/2013 06:22:43 PM : [ 20 AD 6D 1] ST 114 Tue 01/29/2013 06:22:43 PM : [iNST-SRX ] 02 50 20.AD.6D 11.00.01 C3 06 00 (00) Tue 01/29/2013 06:22:43 PM : [std-Group ] 20.AD.6D-->11.00.01, Max Hops=3, Hops Left=0 Link to comment
LeeG Posted January 29, 2013 Share Posted January 29, 2013 This is the command that was traced for the Adjust Scene Local On Level adjustment 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 This is the command that was traced when using the On Level (applied locally) slider. Tue 01/29/2013 06:20:05 PM : [iNST-TX-I2CS] 02 62 20 AD 6D 1F 2E 00 01 06 72 00 00 00 00 00 00 00 00 00 00 59 They are the same (except for slightly different On %), yet MikeD sees results on his v.41 different from yours. I would Factory Reset the SwitchLinc followed by a Restore Device to get the link database back. Then try either the Admin Console test with the On Level (applied locally) slider or click the Program name and run the Then Clause. As before, the ISY will not write Local On Level values it thinks it already wrote so it will be necessary to change the value. The slider test is the easier of the two since all that is necessary to set it up is move the slider a little. Trying to keep relevant information together. This is what MikeD reported Started with the my SwitchLinc (2477D v.41) in the Off condition 1) Paddle press Fast On - the lights come on 100% 2) Paddle press Off - the lights go completely off 3) Paddle press On - the lights go to my "On Level [Applied Locally]" setting His step 3 result and your step 9 result do not track. Link to comment
Steven M Castano Posted January 30, 2013 Author Share Posted January 30, 2013 I'm going to try the factory reset and restoration right now, but I've discovered ANOTHER behavior I'm not totally found of: So, even with the scene working as planned... Single ON turns the lights to 50% and Single OFF turns them off. I can repeat this back and forth, back and forth and it keeps working. However, if the lights are on... and I PRESS AND HOLD the ON paddle in order to increase the brightness.... the next time I turn off, and back on the lights... it goes right back to the INCREASE light level, not the preset level and the ISY still thinks its at 50%. Let's see if the factory reset and restore works, I'll let you know. Link to comment
LeeG Posted January 30, 2013 Share Posted January 30, 2013 A Factory Reset will not change that. It is called Resume Dim. Look at the SwitchLinc User Guide under Local On Level. It covers that reaction under Resume Dim. Link to comment
Steven M Castano Posted January 30, 2013 Author Share Posted January 30, 2013 I want so badly to know that it god's name was going on with that think.... HOWEVER, since it works now.... I don't care, I'm just happy to have the behavior I'd like!! Sure enough, single on bring its up to 50%, a second single on takes it up too 100%, single off is off and another single on brings it back up to 50% as expected!!! Same thing works for the fast on also... a double tap for fast on hits 100% right away, single off is off... and yet another single on is back up to 50% exactly how I'd like it. Lastly, I tried running both the THEN and ELSE statements of my program and it surely does change the on level exactly how I planned it!! HOLY HELL THIS WAS DRIVING ME CRAZY!!!!! It's been about 24 hours of me pulling my hair out, but thanks to you guys I really have learned a TON about the devices themselves, logging, the ISY, the Insteon protocol and some basic ISY programming. Thanks so much to all of you for the help, it's MUCH appreciated. If you're ever in the DC area, I owe you all a few beers! *SMC Link to comment
LeeG Posted January 30, 2013 Share Posted January 30, 2013 Glad the Factory Reset cleared it up. This was a difficult one because the device was reacting inconsistent with other SwitchLinc Dimmers at lower firmware levels. Once MikeD reported his v.41 was working as the other SwitchLinc firmware it was either a defective device or something got scrambled requiring a factory reset to clear. Thank you MikeD! Link to comment
MikeD Posted January 30, 2013 Share Posted January 30, 2013 Lee, Glad this was something I could assist with. I'm fairly new to the ISY world and read most of the posts. With that in mind I must say you are the one, along with a few others here, that I have to thank for giving the most thorough explanations that help new individuals understand how the ISY operates. ~Mike Link to comment
fitzpatri8 Posted January 30, 2013 Share Posted January 30, 2013 Lee, I'm glad you stuck with it to a successful conclusion. Ditto the other comments--your detailed knowledge of the technology and your willingness to share it are unparalleled and appreciated, and I learn new stuff from your posts all the time! Mike, thanks for your input, it really helped set the right direction for the rest of the conversation. It's been around for a bit and it's very easy to set (intentionally *or* accidentally), so I'm actually a little surprised that the Resume Dim feature (SmartLabs actually calls it 'resume bright' in the docs) doesn't get more attention. Operation is consistent with previous firmware versions that I've tried--you simply single-tap the Set button while the switch is Off to turn the feature on, then the level of the switch is saved each time you turn it off and it returns to that level the next time you press on. It's actually handy for folks who don't have an ISY to easily reset levels, since it means that you can easily reset the light to a dimmer level before turning the lights off when you put the baby to bed, then the light comes on at that lower level when you are bleary-eyed and called for a middle-of-the-night diaper change. Link to comment
Steven M Castano Posted January 30, 2013 Author Share Posted January 30, 2013 What I would love to see is a way to query the device and see if any of these modes (in particular, this one since it plaqued me for two days) are enabled. Maybe in a grahical, easy to use way like in the ISY admin GUI? A little more advanced status from the device? I've been learning about modes the SwitchLinc Dimmer can have, like this "resume bright" feature, as well as the ability to use it as a wired phase coupler also. For now, to make sure I stay on the same page as my devices... if I get confused.... I just factory reset and restore the device. A powerful lesson learned from the last 2 days of posting. Link to comment
fitzpatri8 Posted January 30, 2013 Share Posted January 30, 2013 Performing a factory reset is sort of a 'nuclear flyswatter' option--it'll work, but it might be considered a little excessive. If you accidentally turn on Resume Bright again, the easiest thing to do is reset it. Simply adjust the switch back to the desired On level and single-tap the Set button. If you find you have to do it again in the future and you are reasonably certain no one is walking around your house tapping Set buttons on switches in the Off position, be sure to post back--that could mean that your particular set of circumstances (the four back-to-back commands to set local level, set ramp rate, set local level, set ramp rate without any pauses in between; the marginal signal environment; perhaps even the particular unit addresses involved) are setting up a storm of bits that are being misconstrued as a 'turn on Resume Bright' message and would merit further testing. Link to comment
Steven M Castano Posted January 30, 2013 Author Share Posted January 30, 2013 If you find you have to do it again in the future and you are reasonably certain no one is walking around your house tapping Set buttons on switches in the Off position, be sure to post back--that could mean that your particular set of circumstances (the four back-to-back commands to set local level, set ramp rate, set local level, set ramp rate without any pauses in between; the marginal signal environment; perhaps even the particular unit addresses involved) are setting up a storm of bits that are being misconstrued as a 'turn on Resume Bright' message and would merit further testing. That is a VERY good point. I was actually just doing a TON of reading on improving signal strength in my network. I've already got 2 2443 access points, and another LampLinc Dimmer (which I understand works as an access point also, correct?) The LampLinc Dimmer and a single access point are all in the same room as the PLM, so that should work pretty well. I also walked around this morning and hit the set button on the access points to make sure they are on different phases in my condo... it would appear that the second one (in my living room) didn't blink at all, so it should surely be on a different phase correct? Also, I've got another SwitchLinc Dimmer, another SwitchLinc Relay and 2 more LampLinc Dimmers on their way... so that should help a bit. I'll have those early next week.... and from the posts I see.... I'm going to order 3 or 4 FilterLincs from my home theatre system in the living room, computer in the office area and TV/Stereo in the master bedroom. If there a good way, in the ISY or with tools I have now, do to a baselinc signal test to see if adding gear next week improves the signal strength? (Also, after moving one of the Acess Point last nights after a bunch of this reading.... I see much fewer Hop=0 messages, but did have some intermitant communications issues) I see there is an option to use the SwitchLinc Dimmer as a phase coupler... is this a good idea? Should I enable it? Link to comment
LeeG Posted January 30, 2013 Share Posted January 30, 2013 "I see there is an option to use the SwitchLinc Dimmer as a phase coupler... is this a good idea? Should I enable it?" Can you post a link or describe where this option is discussed. Normally the RF aspects of a Dual Band are automatic and not under control of the user. Link to comment
Steven M Castano Posted January 30, 2013 Author Share Posted January 30, 2013 It's in the 2477D manual list as "Phase Bridging" http://wiki.smarthome.com/index.php?tit ... se_Bridger Link to comment
LeeG Posted January 30, 2013 Share Posted January 30, 2013 Thanks. The 4 tap Set button process is for testing RF range and same/opposite phase power. The RF aspect of a Dual Band Insteon device is functional from the time power is applied. It is not dependent on the 4 tap test to be operational. When the Set button on a Dual Band device is tapped 4 times the device transmits a test RF message. Other Dual Band devices that are in range of the RF signal will blink the status LED and indicate whether on the same or opposite electrical phase by color/intensity of status LED. Access Points will blink Red when on the same phase, blink Green when on the opposite phase which indicates these two devices are capable of coupling the phases. The 4 tap Set button test is not required for the RF to function. It does show how many devices are in range of each other and how many are on the opposite phase. Link to comment
Steven M Castano Posted January 30, 2013 Author Share Posted January 30, 2013 When the Set button on a Dual Band device is tapped 4 times the device transmits a test RF message. Other Dual Band devices that are in range of the RF signal will blink the status LED and indicate whether on the same or opposite electrical phase by color/intensity of status LED. Access Points will blink Red when on the same phase, blink Green when on the opposite phase which indicates these two devices are capable of coupling the phases. The 4 tap Set button test is not required for the RF to function. It does show how many devices are in range of each other and how many are on the opposite phase. Sounds like this could be a pretty useful test tool.... I think I'll go home and try it to see what happens! Link to comment
LeeG Posted January 30, 2013 Share Posted January 30, 2013 It is the only way of knowing for sure there are two Dual Band devices in RF range of each other and they are on opposite phases (both conditions needed for phase coupling). Since any Dual Band device in RF range will react it also shows how many RF devices can hear any specific Dual Band device. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.