blueman2

No, I did not think to check. Yes, there are some locals that are 30 minutes off. But I am not aware of any that are 30 minutes ahead of Pacific Time zone. That is why I was so surprised. I just hope it does not come back again!!

Add me to the people having time issues with the ISY 99i. Started about a week or two ago. Clock on the ISY was 30 minutes ahead. I logged on and set it to my computer time and it corrected. But I then decided to update ISY to the pool.ntp.org and it once again went 30 minutes off! I reset my location (Pacific) and that finally fixed it. NTP now sets to right time. Somehow, my location info was causing the problem. The odd thing is that I am not aware of ANY location that is 30 minutes behind Pacific time!!! Also, I never changed it. Maybe something to do with DST change? Problem started right around that time. I hope this does not crop up again, as having the time set correctly is really critical to some of my programs. Running 3.3.3 on ISY 99i/IR (1030).

Upgraded ISY99IR from 3.3.2 to 3.3.3. Rather lengthy startup after upgrade. I guess it was querying all my devices (?). My IOLink #2450 options settings now seem to work correctly. In the past, the settings for things like momentary settings did not work. Now working perfectly.

In my view, purchasing the ELK module is a MUST. Yes, it is expensive at $100, but it is totally worth it. Best $100 I have spent in quite a while. The ELK module creates a seamless interface between the 2. While you will still use the RP program that came with the ELK for setting up the alarm system, you will find you will use the ISY for all other elements of automation and programming.

Do what I do. Just cover the labels with another clear labels (2 layers, with the top layer protecting the printed lower layer). Works perfectly and instantly!

I did not ask, but on my unit, it does work just fine still as a controller. I tested this by switching the unit using the built in buttons, and my ISY saw it changing states just fine. You are right, however, in that controller makes little sense if the load feature does not work!!! SmartHome really messed up on this one.

Yes, even the manual that came with the ones I bought still show it as a feature. It must have been something very odd that caused them to pull it. Maybe a liability issue of some type? Or maybe issues with new LED bulbs that draw so little power? Not sure, but yes, this is VERY surprising. I will PM you about some used lamplincs!

You are right, this has nothing to do with ISY. I just called Smarthome. They informed me that lamplincs now no longer have Load Sense. It has been disabled in all units manufactured in the past 3-4 months. They gave no reason why, but said it has been permanently removed. So I am returning them for a refund. Really too bad, as I need that feature! Only option right now is their inline module which still has load sense.

OK, well I have the EXACT same issue. I just bought 2 2457D2 lamplincs from Amazon. I am using them to replace 2 older version lamplincs (2457D2 R1.9 0912). I cannot get either of them to respond to lamp load. The old lamplincs work just fine responding to load. I am using 60W incandescent lights. Out of the box, nether responded. I did the triple press listed in the manual, but that did not help. I did a full factory reset, and that did not help. I find it hard to believe that both can be bad! Any thoughts?

Has anyone had experience triggering the 2476S sense wire using 120V from a phase that is different from the line voltage driving the 2476S? I assume this would be a big no-no since it potentially puts 240V across an internal circuit in the switch depending on how it is designed, but I was curious if anyone knew anything for sure?

I have a bunch of the older lamplinc that are receivers only (2856D2). The bad thing is that when I turn a lamp on via the lamp itself (which causes the lamplinc to detect this and turn itself on), there is no signal sent back to indicate its new 'on' state. Does the newer 2457D2X provide an update then it is turned on via the lamp sense feature? I do have a timer lamplinc (2456S3T) that has 2 way communications, but I find it does not provide any update when turned on via lamp sense. It does provide update when turned on via its local switch, but not via lamp sense.

Upgraded from 3.2.5 no issues. Basic testing shows all working fine as before. Not tested for HTTPS or UDAjax. And speaking of UDAjax, is there a site/thread that talks about this and how to develop with it? I found a few posts referring to it, but no real details. EDIT: nevermind. Found a site listed in the index.html code. http://sites.google.com/site/isyajax/

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.