smokegrub

I am going to knock off for the day; I am getting tired. Will do a factory reset tomoroow and go through the drill. If that diesn't work, II will then try the one additional device I have on hand. If it links successfully, I will call Smarthome and get a replacement for the one that doesn't work.

It wasn't, but I carried it back to within 2 feet of the PLM and tapped the button. Nothing. The firmware is 4.2.10. As I stated above, I have already linked one of these devices, programmed it and it is working beautifully.

I have already done that several times and it still does not show its state.

I deleted the device, factory reset it, linked it and waited until the flashing light was off (several minutes). The device's current state is still not displayed. The Low Battery state is presented; the Heartbeat is not.

Didn't know that. will chack again later.

I was able to get the device to link by positioning it near the PLM. However, it does not display its state after linking. Moreover, the linking display on the device (flashing green light) keeps blinking after linking. I have deleted the device from ISY, factory rest the device and relinked with the same result.

Here is the events log: Fri 10/03/2014 02:57:13 PM : [ IR] 014A Press Fri 10/03/2014 02:57:24 PM : [ IR] 0156 Press Fri 10/03/2014 02:58:03 PM : [ IR] 014A Press Fri 10/03/2014 02:58:26 PM : [2B 2F 26 ] Added to list of devices to link to ISY Fri 10/03/2014 02:58:26 PM : [iNST-TX-I1 ] 02 62 2B 2F 26 0F 0D 00 Fri 10/03/2014 02:58:26 PM : [iNST-ACK ] 02 62 2B.2F.26 0F 0D 00 06 (00) Fri 10/03/2014 02:58:35 PM : [iNST-TX-I1 ] 02 62 2B 2F 26 0F 0D 00 Fri 10/03/2014 02:58:35 PM : [iNST-ACK ] 02 62 2B.2F.26 0F 0D 00 06 (00) Fri 10/03/2014 02:58:44 PM : [iNST-TX-I1 ] 02 62 2B 2F 26 0F 0D 00 Fri 10/03/2014 02:58:44 PM : [iNST-ACK ] 02 62 2B.2F.26 0F 0D 00 06 (00) Fri 10/03/2014 02:58:48 PM : [2B 2F 26 0 ] Failed to add device, reason 3

I have already linked and I am using a Hidden Door Sensor (2845-222). I am trying to link a second device and, under Link Management, I have selected Link a Sensor, Hidden Door Sensor, typed in the device’s address and assigned it a name. I then put the device in linking mode and proceed. I get the message “Cannot determine Insteon Engine". I then tried Link Management, New Insteon/A10/X-10 device with the same results. I have done a factory reset and repeated the foregoing steps with the same outcome. The device is located the width of a doorway from 2 dual band devices that are linked and functioning properly.

Stusviews: Your suggestion worked perfectly. Also, I learned a couple of things that will prove valiable in the future. !) Using a program within a program and 2) A program that is disabled will run when used in another program. My thanks to those of you who provide such tremendous help.

I want to press a kpl button (g), wait 5 minutes and if a door sensor is on send a notification. It appears I need a second "if statement" and I can find no way to do that. If g is on Then wait 5 minutes ????? I have the notification process set up and can activate it w/o the wait step so I know that part of the process works. Thanks for your help.

Thanks, Michel. I apologize. I overlooked that.

Thanks, Michel. That is a key bit of information that should be brought front and center in the Zigbee Module description.

I am confused. I thought that the ISY Zigbee module would provide for communication with Zigbee devices.

Thanks, Lee. It seems clear I have a failed device. I will contact Smarthome.

If you change the name in the Admin Console then sync in MobiLinc the revised name will appear in MobiLinc.

Stusviews: Yes, the air gap switch is held all the way on for the full 10 seconds. Given your feedback, the device does not respond to Restore since I get no popup. Thus, I cannot Write Updates to the device since it does not respond to Restore. I can create the device links table---how do I post it?

I did a factory reset and the light on the main load slowly ramped up but the LED did not light. I selected the primary load button in the KPL and used the Restore selection. Nothing apparent happened. I changed the ramp rate to zero and tried to turn the light off with the KPL. It would not turn off. I turned it off at the Admin Console and again tried the KPL. It ramped up slowly. I tried cutting it off with the KPL and could not. I could cut it off and on easily with the Admin Console but it ramped on and off slowly despite the fact that the rate was set to zero. The other buttons perfomed as programmed but their LED's stayed off through the process. I repeated the foregoing process and got the same result. Is a window supposed to open when the Restore slection is active? None did. Was I correct in selecting the main load button to Restore?

Techman: Following a factory reset with the Restore function restore the device to its former settings?

paulbates: I did this twice. Ech time when I pushed the set paddle back in the buttons flashed once and went right back out. I tested the on/off buttons and they ramped to thei position slowly. The remaining buttons still do not work.

After working well for months, a KPL's LEDs flickered when I pressed a button controlling a scene. A few seconds later all its LEDs went out and only two of the buttons still serve as controllers, those being the "On" and "Off" buttons. When pressed they slowly ramp a light on and off (they were instant on/off). I can access all the KPL's buttons using the Admin Console and control them as previously. Apparently, I need to do a factory reset of the KPL, but I want to ensure that I can restore all its programs/scenes following the factory reset. I would think that I could do that by first resetting the KPL then, if that is successful, use Restore for the device. Of course, if it is dead I will be wanting to replace it and retain the programs/scenes assigned to its buttons. ISY 994i IR Pro Firmware 4.2.10 Mac OS 10.9.4

The standard way where ISY discovers the device when it is placed in linking mode. That would not work in this case. I had to use the procedure above.

I found the answer by researching the forum: Place the Door Sensor in linking mode. Select Link Management in the Admin Console. Select New Insteon Device. Type in the Device's Insteon Address. Type in a name for the device. Select Auto Discover. Select Remove Exiting Links. This will install the device and 3 nodes that will be self-explanatory. The reason I ran into problems is that when I initailly linked the device I did so with an earlier version of the ISY firmware. That version did not support the nodes. When I upgraded firmware to a version that supported the nodes apparently that "confused" the device and I had to do the above workaround. If only these devices were PNP!

A few days ago I easily linked a Hidden Door Sensor. I deleted it as a device and updated my firmware to 4.2.10. Now, when I press the set button I get the 3 beeps and the light turns green but no device appears. I have factory reset the device several times, positioned the device near the PLM, near other dual-band devices and tried to relink. Nothing! Anyone know what is going on?

Thanks, ravedog.

I sure hope so!