blueman2

Upgraded without any issues. Everything appears to operate as before. I do have several 2475D's which were noted to have increased functionality? I am not seeing anything different with them. Mine are v.38, so maybe my firmware was not included (not sure what A1 meant).

Yes, that will reset it. Also, I can just turn the KPL off and on using main off/on button, and that too will reset it. But flipping the leviton connected to the CFLs on and off a few times will still cause the KPL to go flaky again. Very annoying.

This has nothing to do with the ISY, but I hope someone here has run into this issue with Insteons. I have 2 spots in my house where I have KPL dimmers connected to regular incandescent lights. However, in both cases, they are right next to (in the same gang box) regular old leviton switches that control a circuit of CFLs. Very often when I turn the Leviton switch on or off, it will cause the KPL to go nuts! All of the KPL LEDs go off, like it is being reset, then it comes back on and blinks the load on and off repeatedly. It also makes some weird buzzing and clicking noises as it does this. Anyone else seen this behavior? The fact that it is happening in 2 different areas, with 2 KPLs of different firmwares bought at different times, tells me this is not just a KPL issue. It is as if the CFL coming on or off throws some transients into the power line that is causing the KPL dimmer to freak out.

LOL! Well, I am OK just keeping them as regular switchlincs. The check box that disables timer function seems to be working, as the switches are operating like a normal switchlinc. If they act up any more, I will just return them. I think it is pretty clear why they discontinued these switches!!

OK, things are getting more weird. I ended up using one of the broken SLT's on my kitchen lights as a regular switchlinc. Been working fine for 4 days. Tonight, my lights turned themselves off. I turned them back on, and about 15 minutes later they went off again. It really started freaking my wife out! I looked at my log, and saw that 3 times over the past 4 days, my SLT turned itself off after EXACTLY 15 minutes. All the other times, it stayed on for hours. So now my switch is actually randomly acting as a SLT, but mostly still acting as a regular switchlinc. To solve this, I have turned off the timer check box in options. I hope this keeps it acting as a dumb switchlinc. My wife is threatening to pull the plug on HAL!!!

Can you also confirm that the timer function is working on the switch itself? In other words, press the on paddle once. The switch should go on for 15 minutes then shut down.

Frankly, I am having trouble believing this can happen. I keep thinking I will realize there is something wrong I am doing. I am going to continue playing with my 3 SLTs. Having the Timer function non-operational is no big deal for me really. I can always create a program with the ISY to do pretty much the same thing. But I am fascinated by the fact that the function can be killed in a way that a factory reset does not fix. Definitely a bug in the design of the switch. A well designed switch firmware would make this impossible. Perhaps related to why they discontinued this switch?? Michel, I would say put this on the back burner for when you have time to investigate, and don't waste a lot of cycles on it. I am OK with the switches as they are. But it is a very interesting puzzle!

OK, I did repeated factory resets and I think returned one of my SLT's to working factory condition, including timer. At least, it now reads 15 minutes rather than 255 or 0. I will confirm once I do some tests of actual count downs. But this is good news. Frankly, I cannot image it is possible to ever write something to a switchlinc that cannot be erased with factory reset. EDIT: OK, I spoke too soon. The older switches remain broken in terms of timer function. A factory reset does change the timer in the ISY screen back to 15, but the countdown timer itself remains non-operational. My 2476ST's have been turned into 2476S's. Again, positive news in a strange way. It does show that somehow you can mess with the timer function. But it also shows that, contrary to what I would have ever believed, it is possible to mess up a switch by writing to it so that even a factory reset will not return it to normal operation. Very very odd.

Michel, after further usage, I am sad to say I am getting the exact same result as Teken. A newly installed SWT works fine in all regards, including all check boxes and acting as a timer, except of course for the timer value cannot be changed. It just stays at 15. It was based on this 'new' switch that I gave my prior positive results post. However, my OLD SWTs which I had originally installed about 1-2 months ago and which were originally installed with 3.1.7 ISY firmware are totally hosed in terms of being able to be used as a timer. My guess is that something in the 3.1.7 or later firmware made changes which killed the timer function of these switches. I will try to so some more factory resets to get them back, but so far this seems like permanent damage to the SWT timer function. I guess I will continue to use these as standard relay switches. The only hope I see is that if we are able to write enough to the timer function to kill it, then maybe the timer function can indeed be changed. So perhaps over time there is hope for being able to 1) restore our switches to Timers, and 2) be able to custom set the time.

Thanks, guys. That is what I thought, but wanted to confirm.

I am curious if it is possible to have a switchlinc not control its own load when turned on or off, but have its load controlled only by another switch? I assume not, but just had to ask.

Michel, Again, thanks for the work on this one. It is very interesting that I now have 3 2476ST's. All are v.40. All 3 show different values in default timeout! One shows 15. Another shows 255. 3rd shows 0. All do timeout just fine at 15 minutes for one paddle toggle. Just weird!

Just to update on the Switchlinc Timer 2476ST, I can confirm that ALL of the checkbox items under "Set Options" work correctly. Specifically, the "Countdown Timer Enabled" box does in fact control whether the switch acts as a regular relay switch or a timer switch. This was the big thing I was looking for. The "default timeout" value does not work, but I think it is becoming clear that this is not a value that can be changed anyway.

My integrated Venstar (2491T1E, firmware v2.4) is working flawlessly with 3.2.4.

Thanks! I will check tonight!

I had something similar happen with a particular brand of CFL bulbs.

The humidity on this unit always reads about 85%. All the time. No way my house is that high for humidity during the winter. Anyone else seeing this type of high reading?

OK, I am home and able to do more testing. I can confirm that all the "set options" check boxes work exactly as labeled. If i check 'LED on' it switches the LED on the SWL Timer. If I switch "LED on TX", I can see the LED flash off/on when it is communicating. These values also survive closing the "set options" box and re-opening. So all good there. The only thing not working is the Default Timeout. It keeps going back to 255. As I open the set options box, it first starts at 0, then reads from the switch (I see the switch LED flash), and it goes to 255. I set it to 5, see the LED flash indicating it is getting communicaiton. I close the set options box, then open it again. I see the LED flash when I open the box, indicating I guess reading the values. But the value is back to 255. Because the switch is linked to my whole house fan, I cannot actually turn it on to see if it is perhaps responding to the Default Timout value, but perhaps just not reading it back correctly when reopening. Maybe this weekend I can disconnect from the fan and test it fully.

I have not done this myself on the 2476ST, but are you saying the following (from the manual) does not work? Ugh if so!

My 2476ST is v.40. Teken, I am curious, have you tried to do a factory reset on your SWL Timer? Maybe they need to be unlinked from ISY, factory reset, then relinked. A factory reset should return everything to the original settings for 15 minute based and 1 hour per paddle click, for example. Here is my log when I try to update the SWL Timer 'timer' option to 5 minutes from the 255 value it shows: Tue 04/10/2012 10:53:26 AM : [All ] Writing 0 bytes to devices Tue 04/10/2012 10:53:32 AM : [All ] Writing 0 bytes to devices

- Installed 3.2.4 no problems. Upgraded from 3.2.3. - Got ability to edit folders back (great!) - Initially, got "request failed" on setting options for SWL Timer. But I removed the device and re-added it manually. It then worked!!! Has a weird 255 value in timer, but I will play with it to see what it does. edit: everything works with SWL Timer except the timer value always reverts to 255. Frankly, I am not sure this switch will even support changing the value, so we may be chasing our tails on this one. But thanks so much for the effort on this legacy module (no longer being sold). I will play with this more tonight to see what impact the timer setting has, if any.

Upgraded to 3.2.3 from 3.2.2 no problem. But I continue to get the same "Request Failed" when setting options on my timer switch (2476ST), same as Teken.

I have had a recurring problem for the past 4 months since I got my ISY-99i. About 1/2 the time I launch the Admin Console, the 'current state' of devices does not display. I close the console and my browser, clear the java cache, and about 1/2 the time the current state shows up again. When it still does not, I just wait a couple ours and clear cache again and try again. Mostly will work then. This is happening on all 4 of my computers. None of them have firewall turned on. None of them have any avast type software that messes with ports. I do have McAfee Anti Virus installed. But even when I turn that off, the problems remain. Any ideas what is going on? Very frustrating to take 5-10 minutes or longer to finally get the Admin Console working.

I have the Venstar with v2.4. I upgraded to the 3.2.2 firmware on my ISY-99i. Finally got everything working both as a responder and controller. By the way, my Venstar shows up as v.95 in the ISY screen.

That is what I thought. Thanks for the great help!!!!