LeeG

Then a Scene would not be acted upon if I understand the point. Are you asking Insteon to invent a new function where a Scene is specified but only for identifying a list of Responders, where then Direct commands are actually used rather than Scene commands? Something like Set List 'xxxxx' 50% where xxxxx is a Scene definition that provides the device list but Direct commands are used? If you want to use Direct commands where an On Level is in the architecture that would certainly work. Perhaps I don't understand the proposal.

What Scene is invoked when KPL button pressed? That Scene can be invoked from phone but that would NOT also turn On KPL button.

The Vacation Scene, if this is the Scene being run from the phone, turns the KPL button On but that action does NOT cause the KPL button action to run. Need to invoke something from phone that turns the KPL button On AND invokes the action that happens when the KPL button is physically pressed.

If none of the previous suggestions have resolved the symptom, display the link records in one of the KPLs, post the link records along with the Insteon address of both KPLs.

To restore a Backup file issue File | Restore ISY. The concern using a Backup from May is that it will not have the latest Device/Scene/Program information. The ISY firmware level is not an issue. You may have to manually resolve missing/changed information to Devices/Scenes/ Programs that happened after May.

If All the devices are missing E2 xx aa.bb.cc ........ that point to the PLM, at some point you will have to accept that a Delete Modem (PLM) was done. The A2 ....... records would allow the device to receive messages from the PLM, but since the PLM was deleted those A2 records are not important. The need for an E2 xx aa.bb.cc ...... record in the device pointing to the PLM is an Insteon requirement. The first step is to restore an ISY Backup taken before the new PLM was connected. This will restore the missing PLM information in the Show ISY Links Table albeit it with the old PLM address. Remove power from ISY and new PLM.for 60 seconds. Restore power to new PLM. After 30 seconds apply power to ISY. Run File | Restore Modem (PLM). Then run File | Restore devices.

For the devices that are not working do a Show ISY Links Table. This is the link records that the ISY thinks should be there. Any device that would normally send messages to the ISY/PLM must have at least one link record that starts with E2 and have the PLM Insteon address. E2 xx aa.bb.cc ........ - where aa.bb.cc is the PLM Insteon address. If all the devices that do not work are missing this type of link record it is important to know.

Thanks for the trace, it was very helpful. There is a comm problem with 39.7C.DD. The Hops Left count is both low and changing over short periods of time. One of the command attempts got no response from device.. Thu 09/24/2015 15:24:57 : CLI-HAMW: Connecting to api.aerisapi.com Thu 09/24/2015 15:24:57 : [iNST-TX-I2CS] 02 62 39 7C DD 1F 2E 00 01 00 00 00 00 00 00 00 00 00 00 00 00 D1 Thu 09/24/2015 15:24:57 : [iNST-ACK ] 02 62 39.7C.DD 1F 2E 00 01 00 00 00 00 00 00 00 00 00 00 00 00 D1 06 (00) Thu 09/24/2015 15:24:57 : CLI-HAMW: Successfully Processed HAMW Response Thu 09/24/2015 15:24:57 : [iNST-SRX ] 02 50 39.7C.DD 34.E7.21 27 2E 00 (00) Thu 09/24/2015 15:24:57 : [std-Direct Ack] 39.7C.DD-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Thu 09/24/2015 15:24:59 : [iNST-ERX ] 02 51 39 7C DD 34 E7 21 13 2E 00 01 01 00 00 20 20 1F FF 05 00 88 00 00 00 Thu 09/24/2015 15:24:59 : [Ext-Direct ] 39.7C.DD-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 - cannot get worse and work Via Button A Thu 09/24/2015 15:28:41 : [ Time] 15:28:41 0(0) Thu 09/24/2015 15:28:41 : [iNST-TX-I1 ] 02 62 39 7C DD 0F 19 00 Thu 09/24/2015 15:28:41 : [iNST-ACK ] 02 62 39.7C.DD 0F 19 00 06 LTSREQ (LIGHT) Thu 09/24/2015 15:28:41 : [iNST-SRX ] 02 50 39.7C.DD 34.E7.21 27 21 00 (00) Thu 09/24/2015 15:28:41 : [std-Direct Ack] 39.7C.DD-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Thu 09/24/2015 15:28:41 : [iNST-TX-I2CS] 02 62 39 7C DD 1F 2E 00 01 00 00 00 00 00 00 00 00 00 00 00 00 D1 Thu 09/24/2015 15:28:41 : [iNST-ACK ] 02 62 39.7C.DD 1F 2E 00 01 00 00 00 00 00 00 00 00 00 00 00 00 D1 06 (00) - NO RESPONSE FROM DEVICE Thu 09/24/2015 15:28:50 : [iNST-TX-I2CS] 02 62 39 7C DD 1F 2E 00 01 00 00 00 00 00 00 00 00 00 00 00 00 D1 Thu 09/24/2015 15:28:50 : [iNST-ACK ] 02 62 39.7C.DD 1F 2E 00 01 00 00 00 00 00 00 00 00 00 00 00 00 D1 06 (00) Thu 09/24/2015 15:28:51 : [iNST-SRX ] 02 50 39.7C.DD 34.E7.21 2B 2E 00 (00) Thu 09/24/2015 15:28:51 : [std-Direct Ack] 39.7C.DD-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Thu 09/24/2015 15:29:00 : [iNST-TX-I2CS] 02 62 39 7C DD 1F 2E 00 01 00 00 00 00 00 00 00 00 00 00 00 00 D1 Thu 09/24/2015 15:29:00 : [iNST-ACK ] 02 62 39.7C.DD 1F 2E 00 01 00 00 00 00 00 00 00 00 00 00 00 00 D1 06 (00) Thu 09/24/2015 15:29:01 : [iNST-SRX ] 02 50 39.7C.DD 34.E7.21 27 2E 00 (00) Thu 09/24/2015 15:29:01 : [std-Direct Ack] 39.7C.DD-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Thu 09/24/2015 15:29:05 : [D2D EVENT ] Event [39 7C DD 4] [sT] [0] uom=0 prec=-1 Thu 09/24/2015 15:29:05 : [ 39 7C DD 4] ST 0

The Scene (where PLM is Controller) is fine. Click on one of the Red KPL buttons and set the required responders to 0 On Level. When that update is complete click the other Red KPL button and make the same changes. From Insteon's view point they are different scenes which is each has to be updated.

Try clicking the More Reply Options button to go to the editor where the file may be selected. I'm not familiar with all the supported file types. I have tested the Set Scene ..... Query and it does update the Admin Console Status of the Secondary buttons.. I manually linked a device to the KPL button so I could change the button state without the Admin Console being aware. Then ran the Set Scene ..... Query which updated the Admin Console status for that button whether On or Off. Suggest either moving the ISY to 4.3.18 or use the 3.2.30 Admin Console. I always worry when the ISY and the Admin Console are not at the same level. Would still like to see a LEVEL 3 trace of activity to the KPL. There is a Copy to Clipboard button at the bottom of the event trace window. Simply copy to clipboard and paste into post.

Good evaluation of the KPL button states byte, buttons D (0x08) and button H (0x80) are On. I would have expected the Admin Console status to be updated. I'll do some testing here. Suggest ending and restarting Admin Console. It is not designed to run for long periods of time. If the subscription is dropped from the router the state information is not updated in the display even though the ISY has the correct information. What ISY Firmware and UI is being used.

My last post handles getting the KPL buttons resync'ed using Primary button for Query. Now run Tools | Diagnostics | Event Viewer at LEVEL 3 with the new Scenes querying the Primary buttons of the KPLs. Right click Program name and select Run Then. This will show the comm at this point in the day. It sounds like comm is either marginal all the time or there is something causing interference at those times of the day.

Sorry, bad suggestion. The Set Scene 'kplbuttonx' Query/On/Off/ etc does not return device information so the Program is not accomplishing anything. Change the Scene device to the KPL primary button. It is okay for it to be a Responder in the Scene. This will Query the KPL. Here is event trace when Program runs that is querying Primary button Thu 09/24/2015 02:06:36 PM : [ Time] 14:06:32 2(0) Thu 09/24/2015 02:06:36 PM : [iNST-TX-I1 ] 02 62 33 14 C5 0F 19 00 Thu 09/24/2015 02:06:36 PM : [iNST-ACK ] 02 62 33.14.C5 0F 19 00 06 LTSREQ (LIGHT) Thu 09/24/2015 02:06:36 PM : [iNST-SRX ] 02 50 33.14.C5 22.80.0B 2B 05 00 (00) Thu 09/24/2015 02:06:36 PM : [std-Direct Ack] 33.14.C5-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Thu 09/24/2015 02:06:36 PM : [iNST-TX-I2CS] 02 62 33 14 C5 1F 2E 00 01 00 00 00 00 00 00 00 00 00 00 00 00 D1 Thu 09/24/2015 02:06:36 PM : [iNST-ACK ] 02 62 33.14.C5 1F 2E 00 01 00 00 00 00 00 00 00 00 00 00 00 00 D1 06 (00) Thu 09/24/2015 02:06:37 PM : [iNST-SRX ] 02 50 33.14.C5 22.80.0B 2B 2E 00 (00) Thu 09/24/2015 02:06:37 PM : [std-Direct Ack] 33.14.C5-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Thu 09/24/2015 02:06:37 PM : [iNST-ERX ] 02 51 33 14 C5 22 80 0B 11 2E 00 01 01 00 00 20 20 1C FE 05 00 08 00 00 00 Thu 09/24/2015 02:06:37 PM : [Ext-Direct ] 33.14.C5-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 The Blue 0x08 is showing button D of 8 button KPL is On QueryKPLScene - [iD 0099][Parent 0001] If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Set Scene 'SceneKPL2Primary' Query Else - No Actions - (To add one, press 'Action')

Suggest running Tools | Diagnostics | Event Viewer at LEVEL 3. Right click on Program and select Run Then. Post the event trace.

Was the ISY powered Off when the new PLM was connected to the ISY? Are all the other Insteon devices reporting state changes correctly which indicates they are aware of the new PLM address? The only way I know of for a device to have no links back to the PLM was to have deleted the PLM. If the I/O Linc is the only device not to be aware of PLM it is likely it will have to be deleted and readded to ISY.

With the ISY Link Table not having a link back to the PLM strongly suggests a Delete Modem (PLM) was done when the new PLM was installed. Can you confirm that a Delete Modem (PLM) was issued.

The blank Device Links Table explains why there are no Sensor state messages when door moves to Open or Closed position. Right click on Sensor node, select Restore Device. That should move the ISY Links Table information to the I/O Linc link database. When the Restore Device completes do another Diagnostics | Show Device Links Table to confirm the Device Links Table is the same as the ISY Links Table. Also verify that 13.C1.7A is the new PLM Insteon address.

Wingsy As an FYI, using a Scene (as all information in Owners Manual assumes use of a Scene) with the I/O Linc Relay as Responder and in Momentary A. With the Scene Relay Responder On Level set to 100%, On command turns Relay On. With the Scene Relay Responder On Level set to 0% the Off command turns the Relay On. In case you ever need Momentary A for something.

Right click on Sensor node, select Diagnostics | Show Device Links Table. Post the link record list.

If the I/O Linc sensor never sends Status information it may be missing a link record. Run Restore Device to rebuild the links if nothing ever comes back from the Sensor on door movement. The Query does not require the link information.

Is the I/O Linc option "Trigger Reverse" set On? This option reverses the On/Off commands the I/O Linc sends when the state of the Sensor changes. Unfortunately Trigger Reverse does not apply to Query so the Query status will be the opposite of what the I/O Linc Sensor sends when Trigger Reverse is active.

Unfortunately the Insteon Scene messages do not have a placeholder for a Scene On Level value. Therefore REST command cannot do it. In the extreme REST could invoke a Program that issues a series of Adjust Scene statements that alter each Responder link record On Level, followed by a Scene On. The problem is that changes the Scene On Level until more Adjust Scene statements are issued. Also because link records are being modified the process would be relatively slow. Not something I would recommend.

paulw Thanks for that information. I have several EZFlora devices. The latest I found not functional when I went to trace a simple Zone On command to see if there was some difference I had forgotten. There have been a few very short power outages that looked like they were switching primary power feed. I'm near the state line so the power company can switch to the adjacent state for backup if work on substation is needed. That may explain why this one EZFlora has stopped working. It is the only device i have had fail in recent history. Appreciate the input.

Do you have the Simplehomenet Utility Suite installed. The EZFlora command specs indicate the 0x00 response is from the EZFlora being in Inhibit state. The SHN Utility has the function to read the Config register where the Inhibit indicator resides. The other option is to go back to the 3.3.10 Admin Console and repeat the event trace.

The first On command was received and ACKed but the ACK did not have to expected x'80' response. The second On command was also Acked and did have the expected x'80' I am looking into it. I'm concerned about the ISY at 3.3.10 and Admin Console at 4.2.30. Thanks for the trace. Very helpful. Diagnostics Level 3: First attempt didn't work Wed 09/23/2015 03:28:15 PM : [iNST-TX-I1 ] 02 62 1E 7A 55 0F 40 00 Wed 09/23/2015 03:28:15 PM : [iNST-ACK ] 02 62 1E.7A.55 0F 40 00 06 (00) Wed 09/23/2015 03:28:15 PM : [iNST-SRX ] 02 50 1E.7A.55 13.20.08 2B 40 00 (00) Wed 09/23/2015 03:28:15 PM : [std-Direct Ack] 1E.7A.55-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Second attempt worked Wed 09/23/2015 03:28:18 PM : [iNST-TX-I1 ] 02 62 1E 7A 55 0F 40 00 Wed 09/23/2015 03:28:18 PM : [iNST-ACK ] 02 62 1E.7A.55 0F 40 00 06 (00) Wed 09/23/2015 03:28:18 PM : [iNST-SRX ] 02 50 1E.7A.55 13.20.08 2B 40 80 (80) Wed 09/23/2015 03:28:18 PM : [std-Direct Ack] 1E.7A.55-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Wed 09/23/2015 03:28:18 PM : [ 1E 7A 55 1] ST 255 My Isy99i has firmware 3.3.10 and UI 4.2.30