JP Posted March 18, 2010 Posted March 18, 2010 There's several messages regarding issues with version 35 of the SWLs and suggesting upgrades (swaps). My question is do these issues affect all the memebers of the SWL v35 family including dimmers, relays, and even the newer v220 relay or just a particular product?
Sub-Routine Posted March 18, 2010 Posted March 18, 2010 Hello JP, It is v35 SwitchLinc Dimmers. And only some of them. Are you experiencing problems? Rand There's several messages regarding issues with version 35 of the SWLs and suggesting upgrades (swaps). My question is do these issues affect all the memebers of the SWL v35 family including dimmers, relays, and even the newer v220 relay or just a particular product?
upstatemike Posted March 18, 2010 Posted March 18, 2010 My understanding was that both dimmers and relays were affected.
Sub-Routine Posted March 19, 2010 Posted March 19, 2010 There are a few reports of some relays and some keypads being 'flakey'. The firmware versions are different. And there always is the chance that any device can fail in a manner which exhibits the same symptoms. By "flakey' I mean it seems that don't always responding to scene commands correctly. My understanding was that both dimmers and relays were affected. I am interested in JP's response, we can learn more. Rand
JP Posted March 19, 2010 Author Posted March 19, 2010 To save a little time (and my fingers typing), I'm coping a message response to another issue that I posted last year. To summarize, I have a lot of problems with switches failing to work. Most of the failures are to programs using scenes rather than sending commands directly to the devices. The second most frequent failure is scenes triggered from the switches themselves. Last but not least, are the programs controlling devices directly (without a program, i.e. a TriggerLinc that is within 10 feet of an AP and direct line of sight that triggers a switch on the wall next to the TriggerLinc). For some reason, the problem has recently gotten worse and I can not account for why. No new devices and no devices showing potential failure. The pool problem has been the biggest issue but I dealt with that by adding additional programs to the ISY-99i to repeatedly issue starts and stops (ons and offs). Installed I have 14+ relays, 1 dimmer, and 1 v220 relay that are reporting v35 on the ISY-99i. I also have 5 or 6 APs (sorry lost count) covering the property with one sitting on top of the ISY-99i. The non v35 devices do not seem to have the same problems and some of the v35 devices work every time without fail. The irritating thing is that some of the devices that do not fail on the same CB as one that does (and it does not always fail either). On the issue where the program commands the switch directly (no “scene), I can trigger the switch manually successfully from the ISY-99i while the program (fired by a TriggerLinc) fails at the same time (the TriggerLinc “on†state is seen on the Event Viewer). I’m getting around these problems but it is just frustrating and I dare not add anything that controls a “critical load†such as a thermostat. Not sure how much typing I really avoided here and sorry for the long dissertation (rant). JP Here’s my sad story form last year, please realize that my response then was before I had heard of the SWL v35 issue so my assumptions may now need to change (though it may still have something to do with electrical interference): I agree with Bob that the problem is with the electrical system but may also be the ability of INSTEON to deal with certain events on the line (call it quality, call it design). I have used X10 since its creation and my parent’s house has always been a problem area. At my old apartment, X10 worked great. At my townhouse it worked OK but INSTEON worked much, much better. But at my parent’s house, X10 never worked. After I bought the house, I upgraded to INSTEON (last 12 months) and things worked much better but I still have problems. All the X10 diagnostic tools that I have acquired over the years have indicated that I have nosey lines. At night, it looks like an Iraq war zone with all the INSTEON led’s flashing continuously. The ISY log shows all kinds of "null" events occurring. I have looked at installing whole house phase couplers/filters and it can not be done without replacing the 100A meter (big problem/expense due to building code and a very old house). I have isolated out all the major appliances, TVs, and PCs. I have installed numerous APs which have helped to some degree (though controversial in its own right). But in the end, what I find myself doing, as Bob does, is restoring devices selectively (based on error messages) and doing manual restores when the ISY can not successfully complete its restore. I understand that both X10 and INSTEON are at the lower end of the automation family (sorry Smartlabs), aimed at DYI’ers and I can accept a certain amount of problems. In fact, that is why I am so glad to have a device like the ISY-99i that allows me to program around a great number of these problems. The ISY-99i has given me the ability to do so much more these days than I was ever able to do the past (though my wife thinks I’m nuts for having a line of ApplianceLincs under the holiday village display this year). OK, so I like the box. The bottom line is that I may have an unusual problem, an environment that is unfriendly to PLC devices. I was just looking for an automation method that I am already doing manually with the ISY. If the ROI is not there, I can understand it. I can also understand the support fear but I’m not sure if it is sustainable (I run them during the day with other traffic and if they fail, they fail). Anyway, if there are any other suggestions, I’d be happy to hear them. JP
Sub-Routine Posted March 19, 2010 Posted March 19, 2010 Holy Cow! Yes, those are very much the symptoms of v35 failures. Scenes are not always responded to no matter the sender; ISY or another switch, button, etc. Because you can point to particular devices I would suggest that you call Smarthome and ask for replacements, no matter what the firmware version is. As for the recent increase in noise, I have seen devices that worked perfectly for 6 months or more and then suddenly exhibited such behavior. They can be really hard to find, pulling set buttons is the best way I have found. Smarthome has been good about replacing these devices so you should phone them. Rand
JP Posted March 20, 2010 Author Posted March 20, 2010 I have already contacted Smarthome by email and they seem receptive to replacing the switches. But before I do that, I was hoping to get an opinion about the number of devices that need to be replaced. It sounds like that if it is failing, then it should be replaced including the most recently installed v220 switch? If the switch itself is working without issues, it may be OK to leave? I guess my last question is can a "problem" v35 switch cause interference with the others such that they may all have to be replaced as it may not be able to point to the really bad ones? JP (former Wheeling resident)
apostolakisl Posted March 20, 2010 Posted March 20, 2010 Does anyone know the low-down on the different versions? As far as 2476D's, I don't own any v35's, but have 6 v24's, 14 v27's, 1 v28, and 14 v37's. It would be nice know if there are any common problems with any of these versions so as to assist in troubleshooting.
upstatemike Posted March 20, 2010 Posted March 20, 2010 Does anyone know the low-down on the different versions? As far as 2476D's, I don't own any v35's, but have 6 v24's, 14 v27's, 1 v28, and 14 v37's. It would be nice know if there are any common problems with any of these versions so as to assist in troubleshooting. I think you are in good shape, misssing both the paddle problem and the v.35 problem.
Sub-Routine Posted March 20, 2010 Posted March 20, 2010 It should be fine to leave switches that are not failing. Yes, a problem switch can interfere with other switches. Pulling the set button will eliminate it from the circuit. Rand I have already contacted Smarthome by email and they seem receptive to replacing the switches. But before I do that, I was hoping to get an opinion about the number of devices that need to be replaced. It sounds like that if it is failing, then it should be replaced including the most recently installed v220 switch? If the switch itself is working without issues, it may be OK to leave? I guess my last question is can a "problem" v35 switch cause interference with the others such that they may all have to be replaced as it may not be able to point to the really bad ones? JP (former Wheeling resident)
paulw Posted March 20, 2010 Posted March 20, 2010 I had 18 v35 SL's. Had about 11 of them which on a regular basis would post comm issues from a query or when used in a scene. Replaced 11, comm issues gone, for those 11. However, of the remaining ones, I have several which will post a comm error, but not every day. What is interesting is that the ones currently showing errors, never showed errors be I replaced the 11. Paul
Michel Kohanim Posted March 21, 2010 Posted March 21, 2010 Hi Paul, Quite interesting but, at the same time, the epitome of problems with all SWL 35s: randomly going bad and causing comm errors. If it were my installation, I would replace them all especially if you bought all of them at the same time and thus the likelihood of all of them being from the same manufacturing batch. With kind regards, Michel
ergodic Posted March 21, 2010 Posted March 21, 2010 Just FYI, I have an entire house full of V.35s . This issue showed up about a week after I had finished all the rewiring in the remodel and caused me a lot of worry. I even live close to SH, but in the end I just didn't have the stomach to go back and pull everything and replace it all, especially as the install appeared to be working fine. So I just gupled and crossed my fingers. That was 6 months ago. I still have my fingers crossed and all my SH invoices scanned in but so far no problems. SH indicated to me that they would be OK with replacing them down the line if they started to fail. They've been very good thus far about replacing flaky or infant mortalities with new devices. I do have a constant comm issue with one V.35 dimmer. It's for a shower light and I could care less. I've never investigated to verify it's the controller, though I suspect it is since everything else on the same branch in that room works fine. I would exchange any seemingly flaky controller with SH regardless of firmware version. Having a spare or two around for the various controller types - though I acknowledge a little costly - I find is also extremely handy in this regard.
JP Posted March 22, 2010 Author Posted March 22, 2010 I appreciate all the responses and opinions. As I’ve already started the process of exchanging the switches, I’ll continue with it. I’ll cross my fingers that the swap out will cure the majority of my issues.
C Martin Posted March 22, 2010 Posted March 22, 2010 Hi - Clarence here. I posted a problem about a week or so about my V35 having issues, but all of a sudden it started responding again. Is this typical of V35 problems - where things will go back to normal all by themselves? This self repair has stopped me from replacing my SWL Dimmer for now - am I being foolish? Should I expect to see future problems with this SWl Dimmer? Has anyone else seen this self-repair happen? Clarence
wwat Posted March 22, 2010 Posted March 22, 2010 After about a year of on going frustrating intermittent issues I bit the bullet and had all the v35's replaced. Since then the network has been working perfectly, do yourselves a favor and replace all of them asap. I just replaced about 3 each night, didn't take long. Regards,
JP Posted April 4, 2010 Author Posted April 4, 2010 Clarence, Based on my problems, yes. After I wrote all my messages above, some of my problems went away for a few days and I have experenced this in the past as well. I agree with wwat however about replacing them. I haven't yet due to an injury (hand) but will do so at my first oppertunity. JP
Recommended Posts