Banichi

True. Though this was filtering a non-Insteon dimmer. There are some 1000W dimmers from lutron but this one was not one of those. Sent from my Pixel XL using Tapatalk

Yeah I did think about current rating. Was hoping to find a 15A rated one but the fixture won't be pulling anywhere near that so I think I'll be okay. I would be a little worried if any single light circuit was pulling more than 10A in a residential setting, (not to say that it's unheard of, just not common I wouldn't think). Sent from my Pixel XL using Tapatalk

The choke that I ended up with that worked well was this guy at digikey. I of course needed to wrap it in an insulator so that it wouldn't short with the ground, so I got a large enough piece of heat shrink and did that. The posts were just long enough to wire nut the hot going to the dimmer to 2 posts. The other 2 posts were not needed. Meaning I only needed to filter on the hot and not also the neutral going to the fixture.

I am installing an ISY at a site and I wanted to make sure that I had full remote access. So using my laptop at the site I logged into my office machine and then copied the admin console URL from ISY portal. I then add that URL to the ISY finder and it discovers the UUID just fine and brings me to the login screen. From here if I put in the proper credentials, (my isy portal credentials) then admin console returns the [LIB_ERRORS-403] message. Any subsequent attempt to login just results in the authentication box showing a "Failed, Retry, Authenticating ISY" at the title of the box. If I just attempt a definitely wrong user/pass combination no specific error. It is just the first time that I put in the correct user/pass that the error pops up. I am guess/hoping that this may just be a cyclical issue with being at the site and trying to remote to a computer and then remote back. But, in case I am wrong about that, please let me know if any of you have encountered this issue before. EDIT: I realized that I was also logged into admin console locally and thought that that may have been causing the issue but I reattempted without being logged in locally and I got the same result. Nathan

Yeah finally found it buried in some tech spec PDFs. They refer to it as a "lamp debuzzing coil" aka a filter choke. But simply Lurton filter did not yield any products. Perseverance wins the battle. Part numbers CPW0035 (100W-200W); CPW0036 (200W-400W), CPW0037 (400W-800W); CPW1346-OCP (600W-1200W) Sent from my iPad using Tapatalk

well the lights on the kpl were fixed by replacing the bulbs with some $6 Cree bulbs instead of the $2 Westinghouse bulbs from the supply house. Can't specifically find that Lutron filter kit but then again using the Google is a skill in itself. Looks like it's just a choke though. Maybe I can work something up. I wonder if even one of the induction snap on ones would work. Sent from my XT1575 using Tapatalk

Okay so the incandescent load that is on the Lutron dimmer it sounds like it's the dinner that's the problem. And on the kpl maybe I can do the flash on tx device option and see if that helps. I'll get another switchlinc for that incandescent load. I'll report back with results. Sent from my XT1575 using Tapatalk

So I have 2 circuits that flicker if the loads are not at full when there is insteon activity on the network. Is it possible that the phase bridge(s) is causing the problem? I have 2 phase bridges as I have 2 panels, (not a sub-panel) in this install. I thought at first that it was just because there were some crappy LED's installed in the one circuit but the other circuit is an incandescent one. Also to be clear the one circuit is through and 8-button dimmer and the other, (incandescent load) is on a regular luton dimmer. I'll have to see what my electrician did in the panel. I'm wondering if he piggy-backed on those circuits with the phase bridges and maybe that's why? I dunno thoughts? Oh and also, there are about 40 insteon light circuits in this house and the only ones flickering are the 2 that I mentioned.

Wondering if there is a way to force a device to beep like it does when it enters programming mode?

All of the buttons in the scene light and turn off when the scene is triggered on or off respectively except for the new Dining room KPL button B. Its led stays in its current state unless the scene is triggered from that button specifically and then the LED turns off and on, (ie a local press of the button is the only thing that toggles the LED on that button).

I have a very similar problem with my KPL that I just replaced. The new unit keys do not respond when part of a scene. I think that they may not have been added to the scene correctly. I have 4 KPL's and a mini remote that control the same scene and the other three LED's match the status of the scene when triggered, as did the unit that was pulled. The scene is setup in the following manner: In-linelinc is the load controller - Dining Room -- in scene as responder Dining room KPL Button B - Button/KPL that is the issue at hand -- in scene as controller Master Bedroom KPL - Button D -- in scene as controller Bedside table KPL - Button D -- in scene as controller Kitchen KPL - Button D -- in scene as controller All are set to the default non-toggle to "off". When I hit the button on the KPL in question it triggers the scene and the LED responds as expected as do all the other KPLs. It's just when the scene is triggered from another controller that it doesn't respond. Since I replaced this KPL is it possible that the scene is somehow corrupted?

I am aware that you must remove a device from and folders before you can actually remove the device from the ISY and thus remove the links. I personally find this a bit irritating but curios if this is a deliberate sort of safety measure or something?

Ok. I did that and it seems to be working as expected. Thanks. Now I think I have to rebuild some scenes because the other buttons aren't lighting up when the scene is activated from another kpl or mini remote. Fun times. Thanks techman! Sent from my XT1575 using Tapatalk

I'm just replacing an 8-button KPL in my house and I'm having trouble configuring the LED backlight properly. It has no load attached to it. It only controls in-line and other insteon modules. I'm pretty sure that I there was something I had to do to my original unit to make it so that it would ignore any load sensing and turn the LED off when toggled off. But as it is now it gets brighter when on and then dims to maybe level 3 or something. I tried setting it to 0 in the admin console, changed it away from 0 and then back again but to no avail. What can't I remember here? Nathan

Thanks for the help guys. I do keep a list of the devices and the insteon addresses. I like the date code and firmware version. I'll add that to my spreadsheets. With large numbers of in-line units I usually hand them off to the electrician and he installs them as needed during rough-in and then notes the address and the circuit that it is wired to on the box. I then note that on my spreadsheet. I'll need to find a good way to get him to note which specific fixture it is in as well so that if it needs to ever be replaced I don't have to go looking for it in every can of the 8-can circuit. Maybe a cell phone shot. Nathan

Thanks for all of the suggestions. Chris I think that it would be nice to have in a future release as an option. Unfortunately I didn't think about powering and creating a file with my own ISY 8 months ago when most of these were handed off to the electrician so most of the in-lines are already buried. Not that we can't pull them out if necessary but it'll be a pain now. But for future I will totally do that. I suppose I can just do a regular restore PLM with the PLM at the site and it will update the PLM links in the devices just fine.

I'm pretty sure that the answer is no but is there a way to build a links table of devices that aren't installed yet. I have a large installation and would love to build it so that I don't have to manually add each device at the site. Trying to make it less time consuming at the job site. I know that I can manually add a device in the admin console via the address which is what I'll have to do anyway but it won't add without the devices visible on the network since it can't determine the insteon engine. Again I'm pretty sure that I have to do these one at a time at the site but just checking.

This change was preceded by lack of communication between Alexa and ISY. Rebooted both like I did when they moved the portal closer to the Amazon servers. Then I got the chimes. I kinda like the chimes but the option would be preferred. Sent from my Moto X using tapatalk

So to clarify if I said "Alexa, dim [scene] by 20%" the scene would dim by 9% And regardless of what percentage I speak over 9% it will only dim by that 9%. And if I speak less than 9% it will dim by that much? - Nathan Sent using tapatalk.

I tend to use the .2" deep variety when actually in cabinet, (as opposed to under) and I have the cabinet guy route a channel and then glue the aluminum channel inside so the lens sits flush with the cabinet surface. Sent from my Moto X using tapatalk

This is expected from your browser. Most browsers these days have those big splash pages indicating that the certificate isn't quite right for some reason. With some browsers you can "add a permanent exception" like in Firefox. In some other browsers like chrome you will have to add that certificate into the trusted certs section which is annoying itself. And of course that cert will only help you when you're using that same IP address. For example, always using it from inside your network. If you go to use your public IP address with port forwarding then you will get that same message and will need to add another permanent exception. And that will only hold as long as your public IP address doesn't change. Sent from my Moto X using tapatalk

Yeah I had the same question about scenes. Contributed to the referenced thread. Otherwise connected home works well. Are thermostats and door locks deliberately omitted from being supported as connected home devices? Door locks I can see, (for security reasons) though I feel there could be a safe way to implement them. But what's holding thermostats back? - Nathan Sent using tapatalk.

Was just trying this with my scenes and Alexa said the command wasn't available for that device. Bummer. Almost all of my "devices" are scenes as many of my lights are either 3-way setups or are utilizing in-linelincs with KPLs or switchlincs, so pretty much 3-ways. Though in talking with my wife about this she made me realize that creating multiple scenes, while somewhat bulky in the ISY, would still be a single command to the echo. For example saying: Alexa, set 'dining room lights' to 50 percent Isn't any more work than saying: Alexa, turn 'dining room lights 50' on My question in that scenario would be could I then invoke "Alexa, turn 'dining room lights' off" while the 50% scene is active and have the dining room lights go off? Or would I need to invoke the 50% scene to turn off. While the latter is likely the answer and it is doable, it is not intuitive so would not be preferred. Need to get smart home to create firmware that allows setting scenes to a brightness level. Then all will be well with scene control. Sent from my iPad using Tapatalk

That looks great!! Nicely done sir. Sent from my Moto X using tapatalk

I'm just really bad at replying to this thread apparently. So to answer your question Lee, no I never did a factory reset on the PLM. But just this last sunday I got communication issues with the PLM again. I got plenty of TX but no ACK. So I did a factory reset on the PLM and then rebooted the ISY again. Of course when I popped in to the admin console it was freaking out because it couldn't communicate with any of my insteon modules. I figure it might be because I need to restore the link database of the PLM, (but thinking about it now I would think it wouldn't need to to just get status of a module. Anyway I did try a restore modem and it gave me the following in the logs: Mon 09/21/2015 00:11:09 : [ 17 80 32 1] ERR 1 Mon 09/21/2015 00:11:22 : [ 2A A1 B7 1] Restoring PLM Mon 09/21/2015 00:11:22 : [ 16 7A D9 1] Replacing PLM links (locally and in PLM) Mon 09/21/2015 00:11:22 : [ 16 7A D9 1] Replacing PLM links Successful Mon 09/21/2015 00:11:22 : [ 17 80 32 1] Replacing PLM links (locally and in PLM) Mon 09/21/2015 00:11:22 : [ 17 80 32 1] Replacing PLM links Successful Mon 09/21/2015 00:11:22 : [ 18 1 E2 1] Replacing PLM links (locally and in PLM) Mon 09/21/2015 00:11:22 : [ 18 1 E2 1] Replacing PLM links Successful Mon 09/21/2015 00:11:22 : [ 19 43 EB 1] Replacing PLM links (locally and in PLM) Mon 09/21/2015 00:11:22 : [ 19 43 EB 1] Replacing PLM links Successful Mon 09/21/2015 00:11:22 : [ 22 F7 B4 1] Replacing PLM links (locally and in PLM) Mon 09/21/2015 00:11:22 : [ 22 F7 B4 1] Replacing PLM links Successful Mon 09/21/2015 00:11:22 : [ 22 F9 10 1] Replacing PLM links (locally and in PLM) Mon 09/21/2015 00:11:22 : [ 22 F9 10 1] Replacing PLM links Successful Mon 09/21/2015 00:11:22 : [ 23 EC C7 1] Replacing PLM links (locally and in PLM) Mon 09/21/2015 00:11:22 : [ 23 EC C7 1] Replacing PLM links Successful Mon 09/21/2015 00:11:22 : [ 23 EE 1F 1] Replacing PLM links (locally and in PLM) Mon 09/21/2015 00:11:22 : [ 23 EE 1F 1] Replacing PLM links Successful Mon 09/21/2015 00:11:22 : [ 24 23 65 1] Replacing PLM links (locally and in PLM) Mon 09/21/2015 00:11:22 : [ 24 23 65 1] Replacing PLM links Successful Mon 09/21/2015 00:11:22 : [ 24 8A 81 1] Replacing PLM links (locally and in PLM) Mon 09/21/2015 00:11:22 : [ 24 8A 81 1] Replacing PLM links Successful Mon 09/21/2015 00:11:22 : [ 24 A6 7D 1] Replacing PLM links (locally and in PLM) Mon 09/21/2015 00:11:22 : [ 24 A6 7D 1] Replacing PLM links Successful Mon 09/21/2015 00:11:22 : [ 24 A8 9B 1] Replacing PLM links (locally and in PLM) Mon 09/21/2015 00:11:22 : [ 24 A8 9B 1] Replacing PLM links Successful Mon 09/21/2015 00:11:22 : [ 24 AA EB 1] Replacing PLM links (locally and in PLM) Mon 09/21/2015 00:11:22 : [ 24 AA EB 1] Replacing PLM links Successful Mon 09/21/2015 00:11:22 : [ 24 AC 39 1] Replacing PLM links (locally and in PLM) Mon 09/21/2015 00:11:22 : [ 24 AC 39 1] Replacing PLM links Successful Mon 09/21/2015 00:11:22 : [ 25 9 C4 1] Replacing PLM links (locally and in PLM) Mon 09/21/2015 00:11:22 : [ 25 9 C4 1] Replacing PLM links Successful Mon 09/21/2015 00:11:22 : [ 26 9F C1 1] Replacing PLM links (locally and in PLM) Mon 09/21/2015 00:11:22 : [ 26 9F C1 1] Replacing PLM links Successful Mon 09/21/2015 00:11:22 : [ 26 9F D6 1] Replacing PLM links (locally and in PLM) Mon 09/21/2015 00:11:22 : [ 26 9F D6 1] Replacing PLM links Successful Mon 09/21/2015 00:11:22 : [ 27 B 2D 1] Replacing PLM links (locally and in PLM) Mon 09/21/2015 00:11:22 : [ 27 B 2D 1] Replacing PLM links Successful Mon 09/21/2015 00:11:22 : [ 2E 88 6F 1] Replacing PLM links (locally and in PLM) Mon 09/21/2015 00:11:22 : [ 2E 88 6F 1] Replacing PLM links Successful Mon 09/21/2015 00:11:22 : [ 33 68 B3 1] Replacing PLM links (locally and in PLM) Mon 09/21/2015 00:11:22 : [ 33 68 B3 1] Replacing PLM links Successful Mon 09/21/2015 00:11:22 : [ 33 82 B6 1] Replacing PLM links (locally and in PLM) Mon 09/21/2015 00:11:22 : [ 33 82 B6 1] Replacing PLM links Successful Mon 09/21/2015 00:11:22 : [ 33 83 64 1] Replacing PLM links (locally and in PLM) Mon 09/21/2015 00:11:22 : [ 33 83 64 1] Replacing PLM links Successful Mon 09/21/2015 00:11:22 : [ 4 17 34 1] Replacing PLM links (locally and in PLM) Mon 09/21/2015 00:11:22 : [ 4 17 34 1] Replacing PLM links Successful Mon 09/21/2015 00:11:22 : [ 4 21 B2 1] Replacing PLM links (locally and in PLM) Mon 09/21/2015 00:11:22 : [ 4 21 B2 1] Replacing PLM links Successful Mon 09/21/2015 00:11:22 : Reset PLM Mon 09/21/2015 00:11:31 : [ 18 1 E2 1] ERR 1 Mon 09/21/2015 00:13:46 : [RST-ACK ] 02 67 06 Mon 09/21/2015 00:13:46 : [INST-TX-I1 ] 02 62 19 43 EB 0F 19 00 Mon 09/21/2015 00:13:46 : [INST-ACK ] 02 62 19.43.EB 0F 19 00 06 LTSREQ (LIGHT) Mon 09/21/2015 00:13:55 : [INST-TX-I1 ] 02 62 19 43 EB 0F 19 00 Mon 09/21/2015 00:13:55 : [INST-ACK ] 02 62 19.43.EB 0F 19 00 06 LTSREQ (LIGHT) Mon 09/21/2015 00:14:04 : [INST-TX-I1 ] 02 62 19 43 EB 0F 19 00 Mon 09/21/2015 00:14:08 : [D2D EVENT ] Event [19 43 EB 1] [ERR] [1] uom=0 prec=-1 Mon 09/21/2015 00:14:08 : [ 19 43 EB 1] ERR 1 Mon 09/21/2015 00:14:30 : Cannot reset the PLM Mon 09/21/2015 00:14:31 : [INST-TX-I1 ] 02 62 22 F7 B4 0F 19 00 Mon 09/21/2015 00:14:31 : [All ] Writing 48 bytes to devices Mon 09/21/2015 00:14:31 : [27 B 2D 1 ] Link 12 : 0F98 [E2041943EB010004] Writing [E2041943EB010004] Mon 09/21/2015 00:14:39 : [INST-TX-I1 ] 02 62 22 F7 B4 0F 19 00 Mon 09/21/2015 00:14:48 : [INST-TX-I1 ] 02 62 22 F7 B4 0F 19 00 Mon 09/21/2015 00:14:52 : [D2D EVENT ] Event [22 F7 B4 1] [ERR] [1] uom=0 prec=-1 Mon 09/21/2015 00:14:52 : [ 22 F7 B4 1] ERR 1 Mon 09/21/2015 00:14:52 : [INST-TX-I2CS] 02 62 27 0B 2D 1F 2F 00 00 02 0F 9F 08 E2 04 19 43 EB 01 00 04 E7 Mon 09/21/2015 00:15:01 : [INST-TX-I2CS] 02 62 27 0B 2D 1F 2F 00 00 02 0F 9F 08 E2 04 19 43 EB 01 00 04 E7 Mon 09/21/2015 00:15:10 : [INST-TX-I2CS] 02 62 27 0B 2D 1F 2F 00 00 02 0F 9F 08 E2 04 19 43 EB 01 00 04 E7 Mon 09/21/2015 00:15:14 : [INST-TX-I1 ] 02 62 22 F9 10 0F 19 00 Mon 09/21/2015 00:15:14 : [27 B 2D 1 ] Link 12 : 0F98 [E2041943EB010004] *Failed Writing [E2041943EB010004] Mon 09/21/2015 00:15:15 : [2E 88 6F 1 ] Link 14 : 0F88 [E201167AD9FF0001] Writing [E201167AD9FF0001] Mon 09/21/2015 00:15:23 : [INST-TX-I1 ] 02 62 22 F9 10 0F 19 00 Mon 09/21/2015 00:15:32 : [INST-TX-I1 ] 02 62 22 F9 10 0F 19 00 Mon 09/21/2015 00:15:32 : [INST-ACK ] 02 62 22.F9.10 0F 19 00 06 LTSREQ (LIGHT) Mon 09/21/2015 00:15:36 : [D2D EVENT ] Event [22 F9 10 1] [ERR] [1] uom=0 prec=-1 Mon 09/21/2015 00:15:36 : [ 22 F9 10 1] ERR 1 Mon 09/21/2015 00:15:36 : [INST-TX-I2CS] 02 62 2E 88 6F 1F 2F 00 00 02 0F 8F 08 E2 01 16 7A D9 FF 00 01 DD Mon 09/21/2015 00:15:45 : [INST-TX-I2CS] 02 62 2E 88 6F 1F 2F 00 00 02 0F 8F 08 E2 01 16 7A D9 FF 00 01 DD Mon 09/21/2015 00:15:54 : [INST-TX-I2CS] 02 62 2E 88 6F 1F 2F 00 00 02 0F 8F 08 E2 01 16 7A D9 FF 00 01 DD Mon 09/21/2015 00:15:54 : [INST-ACK ] 02 62 2E.88.6F 1F 2F 00 00 02 0F 8F 08 E2 01 16 7A D9 FF 00 01 DD 06 (00) Mon 09/21/2015 00:15:58 : [INST-TX-I1 ] 02 62 23 EC C7 0F 19 00 Mon 09/21/2015 00:15:58 : [2E 88 6F 1 ] Link 14 : 0F88 [E201167AD9FF0001] *Failed Writing [E201167AD9FF0001] Mon 09/21/2015 00:15:58 : [INST-ACK ] 02 62 23.EC.C7 0F 19 00 06 LTSREQ (LIGHT) Mon 09/21/2015 00:16:07 : [INST-TX-I1 ] 02 62 23 EC C7 0F 19 00 Mon 09/21/2015 00:16:16 : [INST-TX-I1 ] 02 62 23 EC C7 0F 19 00 Mon 09/21/2015 00:16:20 : [D2D EVENT ] Event [23 EC C7 1] [ERR] [1] uom=0 prec=-1 Mon 09/21/2015 00:16:20 : [ 23 EC C7 1] ERR 1 Mon 09/21/2015 00:16:20 : [INST-TX-I1 ] 02 62 23 EE 1F 0F 19 00 Mon 09/21/2015 00:16:20 : [INST-ACK ] 02 62 23.EE.1F 0F 19 00 06 LTSREQ (LIGHT) Mon 09/21/2015 00:16:29 : [INST-TX-I1 ] 02 62 23 EE 1F 0F 19 00 Mon 09/21/2015 00:16:38 : [INST-TX-I1 ] 02 62 23 EE 1F 0F 19 00 Mon 09/21/2015 00:16:42 : [D2D EVENT ] Event [23 EE 1F 1] [ERR] [1] uom=0 prec=-1 Mon 09/21/2015 00:16:42 : [ 23 EE 1F 1] ERR 1 Mon 09/21/2015 00:16:42 : [INST-TX-I1 ] 02 62 24 23 65 0F 19 00 Mon 09/21/2015 00:16:51 : [INST-TX-I1 ] 02 62 24 23 65 0F 19 00 Mon 09/21/2015 00:17:00 : [INST-TX-I1 ] 02 62 24 23 65 0F 19 00 Mon 09/21/2015 00:17:04 : [D2D EVENT ] Event [24 23 65 1] [ERR] [1] uom=0 prec=-1 Mon 09/21/2015 00:17:04 : [ 24 23 65 1] ERR 1 Mon 09/21/2015 00:17:04 : [INST-TX-I1 ] 02 62 24 8A 81 0F 19 00 Mon 09/21/2015 00:17:13 : [INST-TX-I1 ] 02 62 24 8A 81 0F 19 00 Mon 09/21/2015 00:17:13 : [INST-ACK ] 02 62 24.8A.81 0F 19 00 06 LTSREQ (LIGHT) Mon 09/21/2015 00:17:22 : [INST-TX-I1 ] 02 62 24 8A 81 0F 19 00 Mon 09/21/2015 00:17:26 : [D2D EVENT ] Event [24 8A 81 1] [ERR] [1] uom=0 prec=-1 Mon 09/21/2015 00:17:26 : [ 24 8A 81 1] ERR 1 Mon 09/21/2015 00:17:26 : [INST-TX-I1 ] 02 62 24 A6 7D 0F 19 00 Mon 09/21/2015 00:17:35 : [INST-TX-I1 ] 02 62 24 A6 7D 0F 19 00 Mon 09/21/2015 00:17:44 : [INST-TX-I1 ] 02 62 24 A6 7D 0F 19 00 Mon 09/21/2015 00:17:48 : [D2D EVENT ] Event [24 A6 7D 1] [ERR] [1] uom=0 prec=-1 Mon 09/21/2015 00:17:48 : [ 24 A6 7D 1] ERR 1 Mon 09/21/2015 00:17:48 : [INST-TX-I1 ] 02 62 24 A8 9B 0F 19 00 Mon 09/21/2015 00:17:57 : [INST-TX-I1 ] 02 62 24 A8 9B 0F 19 00 Mon 09/21/2015 00:18:06 : [INST-TX-I1 ] 02 62 24 A8 9B 0F 19 00 Mon 09/21/2015 00:18:10 : [D2D EVENT ] Event [24 A8 9B 1] [ERR] [1] uom=0 prec=-1 Mon 09/21/2015 00:18:10 : [ 24 A8 9B 1] ERR 1 Mon 09/21/2015 00:18:10 : [INST-TX-I1 ] 02 62 24 AA EB 0F 19 00 Mon 09/21/2015 00:18:19 : [INST-TX-I1 ] 02 62 24 AA EB 0F 19 00 Mon 09/21/2015 00:18:28 : [INST-TX-I1 ] 02 62 24 AA EB 0F 19 00 Mon 09/21/2015 00:18:32 : [D2D EVENT ] Event [24 AA EB 1] [ERR] [1] uom=0 prec=-1 Mon 09/21/2015 00:18:32 : [ 24 AA EB 1] ERR 1 Mon 09/21/2015 00:18:32 : [INST-TX-I1 ] 02 62 24 AC 39 0F 19 00 Mon 09/21/2015 00:18:41 : [INST-TX-I1 ] 02 62 24 AC 39 0F 19 00 Much of the bottom half there was just the lack of communication between the PLM and the rest of the insteon network. At this point I think that my PLM is dead again. Though I have no idea why they are not lasting more than a year. I do have some older switchlinc relays that sometimes create interference on my network when the lights are on. Not sure if that is due to the older switchlinc or the older LEDs that might be causing that particular problem. And no idea if that is related to my PLM problem. The PLM is plugged in in the halway where these switches/lights are located so that was my only thought there. Is it the caps in these that are going bad? From what I understand a lot of other insteon modules failures are due to capacitor failure. Could that be the case here? I'm pretty sure that at the time of my last failure my ISY was at firmware 4.2.18. I'm now on 4.2.30. I did update the firmware about a week before this became a problem. I doubt that there is an association there but may as well note the correlation just in case. Nathan