LeeG

My mistake. The 15 from the PLM for the 6F command is one of the very few 15 responses that does not necessarily indicate an error. The 026F request is to update an existing record or add a new record if one does not exist. The 15 can indicate the record did not exist and a new one was added. What is the PLM firmware? Tools | Diagnostices | PLM Info/Status

The link record add to the PLM was rejected by the PLM. The 15 in the last byte indicates the PLM could not perform the requested operation. Sat 07/14/2012 08:17:36 PM : [MNG-LNK-RSP ] 02 6F 40 E2 16 19 2E 19 02 1E 40 15 The following trace entry is from my system adding button H as a Controller. Note the 06 in the last byte which indicates the PLM accepted the request. Sat 07/14/2012 08:32:17 PM : [MNG-LNK-RSP ] 02 6F 40 E2 44 0B 4A AD 02 0F 33 06

It was using an 8 button. I have been having the same thoughts. I will convert one of my 6 button KPLs that has already been defined to the ISY as a 6 button. Perhaps that has something to do with it although I don’t believe this is a device error. If you want to run an Event Viewer with Level 3 selected of adding button H as a Controller I will confirm it is not related to an Insteon/device error. It was not the only other time someone reported the Platform Error message.

Defined a new Scene, added some of the Secondary buttons as Responders, added button H as Controller. All worked as expected with no error messages.

Should be able to if all is working properly. I've got to run an errand with a neighbor. Will run that tests, H as a Controller when I get back.

The 'h' button is not associated with the 6 button OFF button at all. The ON/OFF buttons in 6 button mode use Scene (Group) number 1. The 'h' button uses Scene (Group) number 8 with is not used at all in 6 button mode.

Using the same Program Action statement for turning the device On/Off, scroll down through the selections to the Backlight level settings.

hbsh01 The following two messages are the thermostat reporting the Cool Set Point. Except for the difference in Set Point Value the messages are identical. The last message was the result of pressing the Set Point button on the thermostat. The first message reflecting a new Cool Set Point was NOT the result of pressing the Set Point button on the thermostat. There is nothing in the Set Point message which indicates how the Set Point was established. Fri 07/13/2012 01:56:20 PM : [iNST-SRX ] 02 50 1D.6C.D6 19.70.06 01 71 56 (56) Fri 07/13/2012 01:58:23 PM : [iNST-SRX ] 02 50 1D.6C.D6 19.70.06 01 71 57 (57) It is not a matter of If Control working differently, the thermostat does not have the same command set other Insteon devices have that If Control is based on.

"is there really any difference between using status & control when the condition is "if on/off"?" Sorry, I did not see the relationship to an If Control/If Status for On/Off versus the numeric value change of a set point value for the thermostat. My mistake. EDIT: note that how a Program works with an If Control versus If Status is the same regardless of the device type. The underlying characteristics of If Control and If Status do not change because it is a thermostat.

If Status versus If Control is very different. Using If Control 'xxxx' is switched On will trigger the Program only when an On command is received and it will trigger each time the On command is received. If the On paddle is pressed two times in a row the Program is triggered twice. Some folks use this to perform different actions. That is, when two On commands occur in a row within a particular time frame. Using If Status 'xxxx' is On will trigger the Program only when the Status changes. If the On paddle is pressed two times in a row the Program is triggered only once when the Status changes from Off to On. There is no "change" in Status for an On to On situation. Also, with the Program being triggered when the Status changes allows the Then clause to be used when the Status changes to On and the Else clause when the Status changes to something other than On. The UDI Wiki has some good information about stuff like this.

I've not seen a report of a problem with the Dual Band SwitchLinc Relay. The device must be added to the ISY under 3.2.6 and Scene must be created under 3.2.6. Check Help | About to be sure both the Firmware and UI lines show 3.2.6. 3.2.6 is the latest ISY image. What Scene problem are you having?

Move the MorningLinc to the PLM plug point and try again being sure Level 3 is selected. The MorningLinc device would be at the end of the defined nodes until the Admin Console is restarted

flemingmike That sequence looks like the ISY has a record of the MorningLinc Insteon address already. Delete the MorningLinc address from the ISY, and repeat the steps. Make sure Level 3 is selected.

oberkc You are absolutely correct as far as keep existing links not affecting the link between the MorningLinc and the lockset. Even a Factory reset of the MorningLinc does not erase the MorningLinc to lockset link. However, keep existing links is critical for adding the MorningLinc to the ISY. The Start Linking Set button press establishes the link records which are needed for the PLM to be authorized to read and write to the MorningLinc. Very similar to the I2CS linking requirements. If erase existing links is selected such that the Set button link is erased, the MorningLinc will reject all further commands from the PLM. Part of the extra security the MorningLinc has to prevent an outside source from controlling the MorningLinc.

Okay. Follow these steps. Factory reset the MorningLinc. This will NOT affect the link between the lockset and the MorningLinc. Run Tools | Diagnostics | Event Viewer with Level 3 selected. Click Start Linking Register the MorningLinc with the Set button and select keep existing links Click Finish Actually I think Finish is clicked, then the link option of keep existing links is selected. Been too long since I registered my two MorningLincs Post the event trace. Many Insteon devices now require the 3.2.6 I2CS support. Have not seen anyone mention the MorningLinc requiring I2CS yet but it is possible. The Event trace will indicate that or whatever else is bothering the device add process.

Try a Search on Platform Error. Some weeks back another person reported that error message but I don't remember the activity. We ran an Event Trace which showed NO Insteon message errors at which point I stepped aside as I had never seen a Platform Error message before. Don't know the disposition of that problem. There can’t be that many references to Platform Error

Did you click the Finish button?

I was using 3.1.17 at the time.

"Has anybody been able to link a converted 2487s? Is there a limit on the number of links?" I have a few factory set 6 button KeypadLincs that I have converted to 8 button mode. The link database of a KeypadLinc supports 417 link records regardless of whether operating in 6 button or 8 button mode.

That is exactly what the device should be doing right out of the box. No need to turn On load sense as load sense should have been On by default. That is the way mine work. Set button timing can be tricky. There is no multiple Set button presses to factory reset the device which should bring back load sense On. If the device does not sense load after a factory reset a call to Smarthome Insteon Gold line is in order as the device is not working as it should.

If not an incandescent bulb switch to something that has a standard incandescent bulb. I suspect the Set button was not pressed 3 times quickly enough. It took the first two Set button taps as a request to turn Off load sense. Since the device defaults to load sense On factory reset the device which should restore load sense on and test. It will be necessary to Restore Device after the factory reset to rebuild the LampLinc link database.

What is the actual device type? The Dual Band LampLinc has load sense On by default. What were the steps done to enable load sense?

If the MobiLinc Open/Close On/Off buttons are sending Insteon Direct commands to the I/O Linc Relay that is expected result. The I/O Relay is operating in Momentary mode so the Insteon Direct On command turns the I/O Linc Relay On for a few seconds to simulate a manual button press. The I/O Linc turns the Relay Off automatically so the Off button has no affect. For On/Off commands to affect the I/O Linc Relay it is necessary to define a Scene with the I/O Linc Relay as a Responder, turning the Scene On/Off. How the I/O Linc Relay responds to the Scene On/Off commands depends on which Momentary mode the I/O Linc Relay is operating in. The various combinations are covered in the I/O Linc User Guide. Note that an I/O Linc purchased after March 2012 is an I2CS device. ISY 3.2.6 cannot set the Momentary mode of an I2CS I/O Linc. This is expected to be fixed in the next ISY release.

The I/O Linc normally sends a On command when the Green LED turns On. If the Admin Console and MobiLinc are reporting the Sensor Off when the door is open (Green LED On) the Trigger Reverse option is in effect. The Trigger Reverse option causes the I/O Linc to send an Off command when the Green LED turns On (door open in your case).

Either the Trigger Reverse option is set such that the On/Off command flow has been reversed or the wrong pair of wires is being used from the magnetic switch. Check the Green LED on the I/O Linc. Is it ON when the door is open or is it ON when the door is closed?