deirwin Posted March 26, 2011 Posted March 26, 2011 I have a 2476d Switchlinc Dimmer that after I turn it on (whether regular on or fast on), dims slowly off and on and off and on repeatedly. I also have an ISY-99i Pro and an ELK M1 Gold. I've removed the switch from all programs on both ISY and ELK. I've also manually Factpry reset switch. Nothing seems to help. Has anybody had this problem?
apostolakisl Posted March 26, 2011 Posted March 26, 2011 Sounds like a bad switch. You might try removing it from ISY completely (not just deleting from programs), and, if still behaving like that, wiring it into a home that has no other Insteon devices.
LeeG Posted March 26, 2011 Posted March 26, 2011 deirwin What type of load is being controlled by the SwitchLinc Dimmer? Check the wiring to be sure the line, load and neutral are correct. Lee
Wolf Posted March 26, 2011 Posted March 26, 2011 I ended up turning my breaker off and then back on. And my finally worked. You may want to try that.
deirwin Posted March 26, 2011 Author Posted March 26, 2011 I turned my breaker off and back on and it appears to have fixed it. Strange. Hopefully it's fixed. Thanks for your help apostolakisl, LeeG, and Wolf!
deirwin Posted April 3, 2011 Author Posted April 3, 2011 I'm still having problems. It has at times gone through the dim cycle, but the odd issue is that the lights do not turn on or off, unless i double tap. has anyone had this problem?
fitzpatri8 Posted April 3, 2011 Posted April 3, 2011 I'm still having problems. It has at times gone through the dim cycle, but the odd issue is that the lights do not turn on or off, unless i double tap. has anyone had this problem? It can appear as though the device isn't responding if you have programmed the device with a long ramp rate. When you select the device, what does it report as the current local rate?
deirwin Posted April 3, 2011 Author Posted April 3, 2011 It currently shows 0.1 sec ramp rate and 100% on level. I wonder if an old program could be hidden or still operating in background from either my ELK M1 or ISY?
fitzpatri8 Posted April 3, 2011 Posted April 3, 2011 You may want to adjust the local ramp rate to longer and dimmer settings, allow the ISY to write the change, then put them back to the current settings to rewrite the local settings.
deirwin Posted April 3, 2011 Author Posted April 3, 2011 Thanks fitz. it went through the process and now when i turn it on, it shows current status at new setting (62% and ramp rate at 21.5 sec.).
deirwin Posted April 3, 2011 Author Posted April 3, 2011 The lights eventually turned on. I turned them off and they are turning off. probably at a 2 minute rate. I will try to change settings a few times again and see if any results.
LeeG Posted April 3, 2011 Posted April 3, 2011 deirwin I just ran tests with a SwitchLinc Dimmer hardware sticker v5.15 firmware v.38. Changing the Local On Level and Local Ramp Rate DO NOT take effect until the SwitchLinc is power cycled (AC power removed). This can be done by turning the circuit breaker Off/On or pulling the Air Gap switch to remove power from the device. The SwitchLinc should be left off for 20/30 seconds before restoring power. If the Air Gap switch is used be careful to push it FLUSH only with the SwitchLinc frame. If pressed too far in a factory reset can be done. Lee
deirwin Posted April 3, 2011 Author Posted April 3, 2011 Thanks Lee. On and off now work. However, lights still turn off after a while. once they stayed off and once they went back on. i used to have a test program with the nearby motion sensor theough elk 1. maybe it's connected? they just turned off and ramped back on again, then turned off.
LeeG Posted April 3, 2011 Posted April 3, 2011 deirwin Very possible. If the device is being commanded from the ISY it is easy to determine. Run Tools | Diagnostics | Event Viewer with Device communications events selected. Walk past the motion sensor to trigger motion. The Event Viewer will trace any Insteon commands sent by the ISY to the SwitchLinc. If the event viewer trace is not familiar save the file and copy/paste the trace. I can interpret (need SwitchLinc Insteon address). If the ELK is doing it all on its own (I don't own an ELK so not familiar with its capability) that would not show up. Lee
deirwin Posted April 3, 2011 Author Posted April 3, 2011 Thanks again Lee. My kids were running through room, so taht provided some activity. Here's what I have: 0D.2D.38 - (2476D) Switchlinc Dimmer v.27 Sun 04/03/2011 07:41:12 PM : [iNST-SRX ] 02 50 0D.2D.38 00.00.01 C7 27 8C (8C) Sun 04/03/2011 07:41:12 PM : [standard-Group][0D.2D.38-->Group=1] Max Hops=3, Hops Left=1 Sun 04/03/2011 07:41:15 PM : [iNST-SRX ] 02 50 0D.2D.38 00.00.01 C3 27 FF (FF) Sun 04/03/2011 07:41:15 PM : [standard-Group][0D.2D.38-->Group=1] Max Hops=3, Hops Left=0 Sun 04/03/2011 07:41:50 PM : [iNST-SRX ] 02 50 0D.2D.38 00.00.01 C3 27 FF (FF) Sun 04/03/2011 07:41:50 PM : [standard-Group][0D.2D.38-->Group=1] Max Hops=3, Hops Left=0 Sun 04/03/2011 07:41:52 PM : [iNST-SRX ] 02 50 0D.2D.38 00.00.01 C7 27 8C (8C) Sun 04/03/2011 07:41:52 PM : [standard-Group][0D.2D.38-->Group=1] Max Hops=3, Hops Left=1 Sun 04/03/2011 07:41:54 PM : [iNST-SRX ] 02 50 0D.2D.38 00.00.01 C3 27 FF (FF) Sun 04/03/2011 07:41:54 PM : [standard-Group][0D.2D.38-->Group=1] Max Hops=3, Hops Left=0 Sun 04/03/2011 07:43:33 PM : [iNST-SRX ] 02 50 0D.2D.38 00.00.01 C3 27 FF (FF) Sun 04/03/2011 07:43:33 PM : [standard-Group][0D.2D.38-->Group=1] Max Hops=3, Hops Left=0 Sun 04/03/2011 07:43:35 PM : [iNST-SRX ] 02 50 0D.2D.38 01.FF.FF C7 27 84 (84) Sun 04/03/2011 07:43:35 PM : [standard-Group][0D.2D.38-->01.FF.FF] Max Hops=3, Hops Left=1 Sun 04/03/2011 07:43:38 PM : [iNST-SRX ] 02 50 0D.2D.38 00.00.01 C7 27 FF (FF) Sun 04/03/2011 07:43:38 PM : [standard-Group][0D.2D.38-->Group=1] Max Hops=3, Hops Left=1 Sun 04/03/2011 07:44:10 PM : [iNST-SRX ] 02 50 0D.2D.38 00.00.01 C7 27 00 (00) Sun 04/03/2011 07:44:10 PM : [standard-Group][0D.2D.38-->Group=1] Max Hops=3, Hops Left=1
LeeG Posted April 4, 2011 Posted April 4, 2011 deirwin Well that is an Insteon command I have never seen used before. It is a Light Set Status (0x27) that “Updates SwitchLinc Companion’s LEDsâ€. Is that SwitchLinc part of a special package order that included multiple SwitchLincs that are prelinked together? The 0x27 command is not normal Insteon device to device control of individual devices. Lee
deirwin Posted April 4, 2011 Author Posted April 4, 2011 It is possible it was part of a 3-way packaged purchase, but not sure. I know I purchased one once. It was working fine prior to installing Elk and changing this to control different lighting. I think all of this activity is related to the Elk motion detector. That was the only thing changing. FYI, when we put in the Elk M1G, i programmed a Test Rule in the Elk to turn these lights on and off when motion was detected (just to see if it would work). I later deleted that Rule.
LeeG Posted April 4, 2011 Posted April 4, 2011 deirwin I’ve been using Insteon almost from the beginning of Insteon. The basic structure of the commands being traced indicates a “from†device address of the SwitchLinc in question. That normally indicates the SwitchLinc paddle is being pressed but the command being sent (0x27) is not the normal command for a simple paddle press (unless related to some package of “companion†switchlincs). Can you cover the ELK motion sensor (I assume it is not the Insteon motion sensor) so that it cannot signal motion to eliminate the ELK as the source of the SwitchLinc changing On levels? Lee
deirwin Posted April 4, 2011 Author Posted April 4, 2011 I really appreciate your help Lee. I checked and it does not appear to be the unit that was part of a prepackaged 3-way system. I covered motion detector, cleared log, then turned on light. following are results: Sun 04/03/2011 08:48:57 PM : [iNST-SRX ] 02 50 0D.2D.38 00.00.01 C7 27 FF (FF) Sun 04/03/2011 08:48:57 PM : [standard-Group][0D.2D.38-->Group=1] Max Hops=3, Hops Left=1 Sun 04/03/2011 08:55:17 PM : [ Time] 20:55:18 5(0) Sun 04/03/2011 08:55:32 PM : [iNST-SRX ] 02 50 0D.2D.38 00.00.01 C3 27 00 (00) Sun 04/03/2011 08:55:32 PM : [standard-Group][0D.2D.38-->Group=1] Max Hops=3, Hops Left=0
LeeG Posted April 4, 2011 Posted April 4, 2011 deirwin From the cmd2 values I think the SwitchLinc was turned On at 08:48:57 Sun 04/03/2011 08:48:57 PM : [iNST-SRX ] 02 50 0D.2D.38 00.00.01 C7 27 FF (FF) And turned Off at 08:55:32 Sun 04/03/2011 08:55:32 PM : [iNST-SRX ] 02 50 0D.2D.38 00.00.01 C3 27 00 (00) I doubt the Admin Console will reflect the fact that the SwitchLinc was turned On/Off manually because of the unusual Insteon command being used to control the “companion†device. Since the SwitchLinc thinks it has a “companion†device, that companion device may also be controlling this SwitchLinc. Tom Can you shed any light on a SwitchLinc companion package from years ago (firmware is v.27 so the SwitchLinc would seem to be vintage). Lee
deirwin Posted April 4, 2011 Author Posted April 4, 2011 FYI, I manually turned the switch on, but it turned itself off.
LeeG Posted April 4, 2011 Posted April 4, 2011 deirwin I have no explanation for the SwitchLinc turning itself Off. I would look for the “companion†to this SwitchLinc. This SwitchLinc is issuing a command sequence I have never seen before. Best guess at this point is there is another SwitchLinc that is a “companion†to this one and they are interacting with each other. Lee
deirwin Posted April 4, 2011 Author Posted April 4, 2011 Thanks LeeG. It worked perfectly prior to Elk M1G. I initially set a test rule in the Elk to have these lights turn on for a couple of minutes when motion was detected, then turn off. I think it has to be related to that. It appears all of the activity went away when i covered motion sensor and they never turned back on. Perhaps you never saw the command from Elk? Has anyone else seen this or familiar with Elk?
deirwin Posted June 2, 2011 Author Posted June 2, 2011 This problem persists. I think my only option at this point is to replace and trash this unit unfortunately.
Michel Kohanim Posted June 3, 2011 Posted June 3, 2011 Hello deirwin, A simple test would be to remove ELK configuration (the IP address/port) from ISY and see if the problem persists. This way, at least we know if the problem is ELK related. With kind regards, Michel
Recommended Posts