LeeG

A File | Restore Modem (PLM) does not update devices unless a new PLM is being used where the Restore Modem (PLM) is changing the PLM address in all the devices. A simple File | Restore Modem (PLM) rebuilds the PLM link data base only.

When multiple devices fail to show state changes it is usually either a comm issue or the PLM has lost link records. It only takes a few minutes to run File | Restore Modem (PLM) which rewrites the PLM link records.

As was noted in your other post things are usually in Alpha order. Restart the Admin Console. Also if My Lighting/ISY is selected each column can be sorted by clicking on column heading.

The Scenes are not in Alpha order which makes me think the Admin Console has not been restarted in some time. I think the same thing applies to the devices in the Scenes. Exit the Admin Console and restart.

Cannot put all battery powered devices into linking mode any more than you would put all powered units into linking mode at the same time. When done updating the battery powered devices one at a time do a Restore Device to both devices that were manually linked together. Suggest terminating Admin Console and restarting after all devices have been updated with the new PLM address. That may put the Elk entries were they were before. Need objective information about KPL button and thermostat. Does Program trigger, is a command sent to the thermostat, and so on. The "doesn't work" does not help.

That can only be done by another Program. If the posted Program is allowed to trigger the Wait (if active) is always terminated. There are no ISY Program functions available. Would need a variable set by the posted Program that indicates the Program is running. Normally a Program is allowed to trigger and issue a fresh Wait with another motion indication.

The wiring has to be verified as Stu is pursuing. Also click on the Red Slave Controller entry below the ISY Scene name and check the Master Responder On Level and Responder Ramp Rate. LEDs are technically not supported by Insteon Dimmers (although many LEDs work pretty well) but a slow Ramp Rate or partial On Level for the Master Responder can create the condition. What is the Responder Ramp Rate and Responder On Level of the Master when the Slave is the Controller?

"Does that happen every time the temperature changes?" Yes, each temperature change triggers the Program. Values equal to or greater than 80 cause the Then clause to execute. The router is dropping the connection to the Admin Console. Could be security software that is causing the IP connection to drop. Look at the Log and Error Log to see if it documents the activity.

Doing a Factory Reset is fine but now you need to wait 24+ hours to see if the Heartbeat message is sent. It is sent once every 24 hours (approx).

Link record content problems are not intermittent. With things working correctly now the most likely causes are intermittent comm problems, an appliance that generates noise or signal absorption, general comm issue because of device distance, etc. or the power supply in the PLM has become marginal. The PLM capacitor failures are well documented in this forum. The choice is to examine the general comm reliability of whatever devices/Scenes that were not working before. Run Tools | Diagnostics | Event Viewer at LEVEL 3. Perform the activities that were not working before looking at command retry, Hops Left count stability, for example to see if comm is marginal. The fact that a light turns On or Off does not indicate comm is good.

The PLM firmware is displayed by Tools | Diagnostics | PLM Info/Status. This can be done remotely. The ISY only works with a Serial interface PLM. The File | Restore Modem (PLM) can be done remotely. There is a known issue with the capacitors in the older 2413S PLMs. Restoring the PLM is a logical point in evaluating the problems with the new devices. The PLM records would have to be updated with the new device addresses. There is no absolute way of knowing for sure about the PLM without taking some corrective steps. If the PLM Restore is successful but the device issues remain then more analysis will be necessary.

The link is pointing to a 2413U (USB interface). The PLM must be Serial 2413S. Try File | Restore Modem (PLM) to refresh PLM. DO NOT DO a Delete Modem (PLM)!

Delete the MorningLinc from ISY. Factory Reset MorningLinc Link MorningLinc to lockset Follow Wiki instructions for adding MorningLinc http://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Linking_a_MorningLinc

Right click on Program name, select last entry in pulldown list, Copy to Clipboard. Paste into post to have Program in post. Is the solution discussed providing the function you need?

Happy to. Can be a challenge when there are multiple causes for Scene Test errors.

What is the device type on the device label (2856S for example) and is there a load attached to the ApplianceLinc? The ApplianceLinc is sending back a NAK indicating there is a condition it is not happy with.

Deleting all devices from Scene but getting errors on two device links when Scene used tells me there are likely duplicate link records under that Scene number.

Accent Spot Light has a Responder link for PLM Scenes 10, 1A, 27, 2C, 31, 36. The first post is using PLM Scene 10 but not sure that is the one used in this Scene Test. For whatever PLM Scene is being used need to confirm there is an E2 xx ........ (where xx is Scene number) for every Responder and Controller/Responder in the Scene. If all the Controller (E2 ......) link records are in the PLM then a comm issue will be the next thing to look at. Do ALL devices fail this Scene Test? The PLM is v.98 which has the capacitor issue. If some of the capacitors have failed (or started to) then the PLM can have issues with the signals it sends. What is the hardware level of the new PLM that had problems with old RemoteLincs?

Post the new LampLinc link table (along with current PLM address). If that is correct the PLM link records associated with the new LampLinc need to be posted. Either the lampLinc link table is wrong, the PLM link table is wrong, or a comm problem has developed.

The varying number is not a PLM failure. Any inbound or outbound PLM traffic that occurs during the Show PLM Links Table alters the count. The 445/447 is the actual link record count. Having upgraded the PLM and then regressed to an older PLM likely resulted in some of the device link records not being returned to the old PLM address. First look at the PLM link records to be sure none have the wrong PLM address. Then run File | Restore Devices to rebuild the link records in the devices.

Several Show PLM Link Table commands must be issued and get the same link count to know if the count is accurate. The File | Restore Modem (PLM) should not change devices unless the PLM has been replaced.

There are a number of forum posts that address the issue of 2413S PLMs failing because of failing capacitors. SmartLabs has resolved the issue with the newest 2413S PLMs. If electronically inclined the failing capacitors can be replaced if the PLM is outside of warranty. If inside the 2 year warranty they should replace the PLM.

If there are no links after 5 minutes the PLM link database is empty Run File | Restore Modem (PLM). Then run another Show PLM Links Table.

The devices have to be the same 'type', dimmer for dimmer, relay for relay. The Programs could be adjusting brightness levels, ramp rates, which are not possible replacing a dimmer with a relay.

Run Tools | Diagnostics | Show PLM Links Table. It sounds more like the PLM has lost some/all of it link records.