gwarthur

This was my experience as well: I followed the directions for migrating from V2 to V3 in the "ISY Portal Amazon Echo Integration V3" wiki, but when I performed a Discover under Smart Home > Devices, it picked up the devices but none of my ISY-based scenes. What worked was to delete each scene in the portal's Amazon Echo device list and then re-add each (Add > Scene) as a Light (Switch designation might work, too. But not scene) under the Alexa Category drop-down in the portal's Spoken Mapping pop-up. I just tried this and for some reason, after performing a Discover devices in the Alexa app, the spoken command failed the first time. After that, they all worked.

I have 36 Insteon devices, not including six disabled ApplianceLincs I use seasonally. PLM link count is down to 224 from 243 after performing a Restore PLM. (It is apparently relevant that I recently replaced my 99i with a 994i but did not know to perform a Restore PLM at that time). Will attempt a "Show Device Links Table against a device that is not reporting...", but I confess that I do not really understand what I will be doing or looking for.

Michael, I was surprised to discover that some devices report status to the 994i and others don't. The PLM links table count was 243.

When I turn it on or off from the 994i, in the Event Viewer, I see an entry for each command (ST 255 and ST 0), but when I operate the fan switch locally, no events are shown.

I definitely did not set it up as a controller, but I don't really have another device for it to control. I just need it to control the 994i. How do I do that?

I just installed an Insteon 2443-222 micro on-off controller for a ceiling fan. It responds correctly to commands from my 994i and its sense wire correctly detects and responds to inputs from the mechanical SPST wall switch. However, when I operate the mechanical switch, even though the 2443-222's relay opens or closes in response to the mechanical switch locally being turned on or off, its state is not updated in the 994i's status display. Put another way, when I command it on or off from the 994i, it works and its state is correctly shown, But when I locally operate the wall fan switch, no state change is shown at the 994i. The 2443-222 is not telling the 994i that it was locally switched on or off. I have unlinked the device, deleted it, reset it to factory defaults and relinked it. BTW, it would not link automatically; on both occasions, I had to link it using the New Insteon Device option by entering its address manually. Does anyone have a theory why it is not talking to the 994i when it is locally operated? -gwarthur

LeeG, thank you for your quick response. I have repeatedly tried to remove the scene, but I always get the same error. I will try your suggestion. Firmware version is 3.1.17. -GA 02-29-2012: Just ran diagnostics. Scene name is "Dad's Office". Here's the diagnostic log: Wed 02/29/2012 03:53:42 PM : [iNST-ACK ] 02 62 00.00.1F CF 11 00 06 LTONRR (00) Wed 02/29/2012 03:53:42 PM : [ C C3 37 1] ST 255 Wed 02/29/2012 03:53:42 PM : [ 19 2A A4 3] ST 255 Wed 02/29/2012 03:53:42 PM : [GRP-RX ] 02 61 1F 13 00 06 Wed 02/29/2012 03:53:43 PM : [iNST-SRX ] 02 50 19.2A.A4 0F.41.D9 62 13 1F LTOFFRR(1F) Wed 02/29/2012 03:53:43 PM : [standard-Cleanup Ack][19.2A.A4-->ISY/PLM Group=0] Max Hops=2, Hops Left=0 Wed 02/29/2012 03:53:45 PM : [CLEAN-UP-RPT] 02 58 06 Wed 02/29/2012 03:53:45 PM : [iNST-SRX ] 02 50 0C.C3.37 0F.41.D9 67 13 1F LTOFFRR(1F) Wed 02/29/2012 03:53:45 PM : [standard-Cleanup Ack][0C.C3.37-->ISY/PLM Group=0] Max Hops=3, Hops Left=1 ----- Dad's Office Test Results ----- ----- Dad's Office Test Results ----- Wed 02/29/2012 03:53:50 PM : [iNST-ACK ] 02 62 00.00.1F CF 13 00 06 LTOFFRR(00) The addresses I recognize are 0C.C3.37, the rec room SLR to which it was cross-linked and 19.2A.A4, which is a KPL relay button also assigned to the rec room. How can I pry these devices loose from this useless and unneeded scene? -GA

I have an Insteon 2474D, which consists of a special 2-wire dimmer and a control module that is installed at the fixture to be controlled. It is installed in my basement office, adjacent to my rec room. I was playing around with my ISY-99i Admin console the other night and found two things: (1) the switch component was listed as a model 00, Unsupported Item, and (2) it was cross-linked to my rec room scene. Neither the switch nor the fixture component is a listed device in the rec room scene. Switching the 2474D switch on or off did not activate the rec room lights, nor (I do not believe) vice versa. But turning the rec room scene on or off from within the Admin console caused the office light to do the same. I deleted the 2474D 2-wire switch and control module from the basement office scene, then deleted and re-added both devices. This time, both devices showed up with their correct model numbers. I created a new basement office scene with a different name and added the two 2474D devices. It works fine. Nor does it seem to be linked to my rec room scene. But when I went to delete the now-empty and unused previous basement office scene, I got this error: "Removing device from scene incomplete (scene name) [-200000/-21] Does anyone know a relatively benign method for to unsnarling this mess so I can delete this useless scene? I do not want to delete all the devices in my rec room scene if I can avoid it. -GA

I'll try it. Thanks.

I'm sure the following question has been asked & answered many times before, but I was unable to find an example on the Forum. Perhaps someone can provide a link? There are several Insteon devices - such as the one that controls light in my daughter's closet or the one that controls the exhaust fan in the bathroom - that I would like to program to turn off after a predefined period. The task is more complex than just a simple "If on, wait ten minutes and turn off" command series because what if the device is cycled on and off multiple times in a short period? Wouldn't this potentially create loops within loops? I'm sure there is a simple way to accomplish this function but I am not a sufficiently experienced ISY-99 code writer to figure it out. Suggestions please? -GWarthur

Hi, Michael. Different ports for the thermostat and ISY. Is there a range of ports that are designated secure I must use if I want to log on https? Must a device have some additional built-in logic that will allow it to enter into a secure connection, or can any device be configured to connect https?

Michel, after experimenting with different settings on my Vz Actiontek modem, I am now reliably able to contact my ISY-99 from the internet. However, since I port-forwarded it, attempts to reach it over my intranet using its static 192.168.1.nn LAN address now fail. Oddly, my web-enabled Proliphix thermostat which I port-fowarded at the same time remains reachable via LAN or WAN. It's not a major inconvenience, but it would be useful to be able to access the ISY on the LAN since the router will occasionally change its WAN address. Also, I initially tried to set it up using a secure (https:) connection, but I could never get that working. So I settled for standard non-secure http:. I would appreciate it if you or another expert reading this could outline the steps involved in changing an existing, functioning non-secure outside connection to a secure one. As always, thank you for your assistance. -GA

I hesitate to post this because this question has been asked a million times, but here goes: I followed the steps in Michel K's tutorial to get my ISY-99i on the internet, but I still can't raise it on the internet or my intranet. When I opened Help>About, my ISY did not list a port, so I went into my Vz Actiontec MI424-WR router and forwarded its IP address to port 443 as directed. The Enable Internet Access command in the menu bar only gets to about 2% before popping up an error box and quitting. After making the changes, I tried browsing to http://isps.wan.IP.address:443/o/x (or /p). Also tried the secure https version of the same string. https flames out immediately with some sort of "could not connect" notice. The http version doesn't post an error, but just brings up an empty frame. I'm using firmware version 2.8.16. Any suggestions? -George A

Thanks, Lee. I'm pretty certain that it's connected properly, as it is operating normally from the paddle switch, the LEDs work, it switches its load, and it goes into linking mode in the normal fashion either by my holding down the paddle top or the set switch. I don't know if this means anything, but when I put the SwitchLinc into linking mode and start the linking process from the 99i, every ten seconds or so its blinking pattern pauses for a few moments and the LED remains on, apparently communicating, before it resumes blinking. Your point about it possibly being out of range is valid. I have had comms problems with devices in that area in the past. I guess I will uninstall it (I was trying to avoid that), connect it to an extension cord and attempt to link it in a location of known strong signal strength. I might have tossed it out assuming it was defective if I had not recently encountered this same problem; when I reinstalled some other SwitchLincs I had removed before a recent renovation (which had been previously linked to my 99i), some linked normally while others exhibited this same behavior. My workaround then was to use the admin console's New Insteon Device feature using the device’s address. That usually worked, although I had to link and unlink a couple of devices before they responded correctly. But without an address for this SwitchLinc, that option is unavailable. I also briefly considered restoring the 99i to an earlier, backed-up configuration, copying down the SwitchLinc's address (I know where it was used before), and then re-restoring it to the current configuration. But this seemed too risky; aside from this small problem, everything is working pretty well, so I'm very hesitant to monkey with the 99i in case everything doesn't "come back" exactly as it is now. One lesson learned: From here on, every time I handle a permanently installed Insteon device, I'll take a Sharpie and write its address on it somewhere. Unfortunately, Insteon chooses to affix the address sticker to the heat sink. After a year or two of use, you can expect its adhesive to dry out, allowing it to fall off. -GA UPDATE: I took a second 2476S V2 SwitchLinc - purchased, installed and then removed from service at the same time as the one described above - and plugged it into an extension cord as LeeG suggested. I plugged the extension cord into an outlet near the 99i and tried to link to it. Not surprisingly, that one duplicated the behavior of the first; it went into linking mode but wouldn't link. Resetting it to its factory default state did not help. (Note that if you are resetting an older Insteon device, the reset procedure may differ from that for the current model). It's becoming clear that this behavior isn't caused by a defective SwitchLinc or flawed installation; this is some sort of screwy state that these early devices that were previously linked to, unlinked, uninstalled and then reinstalled wake up in. It seems like after resetting the SwitchLinc to its factory defaults, it should have linked link to the 99i. Which leaves me wondering if its address isn't still isn't in some obscure table in the 99i that is telling it that it has already been linked to. -GA PROBLEM RESOLUTION: Turns out that all you have to do is to open the 99i Admin Console, go to Tools > Diagnostics > Events > Device Communication Events, and set the device to linking mode. Presto! The unknown device's address will immediately show up in the log window. Using the address, you can then link the device using the New Insteon Device feature. Problem solved. -GA

I have a several year old 2476S switchlinc that I had previously installed but had recently removed from service before a renovation. Afterward, the lighting plan had changed and I did not reinstall it. That was a couple of months ago. Now, after reinstalling it for another project, it refuses to link. I have repeatedly reset it and reset my 99i, but no matter how many times I run the linking process on the 99i, it does not link. If it still had its address sticker, I could run the New Insteon Device routine, but the sticker has long since fallen off so I have no way to determine the address. Any ideas as to how I can get this unit linked? -George