barrygordon Posted September 7, 2013 Posted September 7, 2013 I am in the middle of a Restore PLM. It is taking quite a long time. I keep getting messages of the form "Cannot communicate with Please check connection" What is the proper procedure to use to get everything working again? Do I need to check each device from the admin console and "restore device and write updates" for the ones flagged with the red ! This had been the first failure of my complete system (PLM failed) As a thought for a major (IMHO) product improvement, - Why not connect to two PLM's, using only one at a time and switching over on a failure. I assume the one that is in active as far as the ISY is concerned could be used to link the active unit to the second side op a 220/110 power system UPDATE I have it almost all back to the way it should be. For each of the items that showed the red! after the PLM reset, I did a write updates. Most of these were battery powered mini remotes 2342. I tried to put them into linking mode before I started the PLM reset but as soon as I did the second one the first one left linking mode. I have one switchlinc dimmer switch that I can not write updates to, but it seems to be working fine. Is there any suggestions on how to resolve this one. If I query the switches links table I get a message that the links table could not be read. I suspect bad switch but ...?
LeeG Posted September 7, 2013 Posted September 7, 2013 The battery powered devices do have to be done one at a time. Establishing manual linking mode to keep the device awake is a real linking mode. Putting a second battery device into linking mode at the same time links the two devices. If the SwitchLinc is defective the only solution is to replace it. Try pulling the air gap switch for a minute or two to power cycle the device. Can also try a factory reset. If neither work either the comm to that location has a problem or the device has failed. I keep an Appliance cord for testing devices in question. Allows plugging the device into the same plug point as the PLM which eliminates the comm. question.
LeeG Posted September 7, 2013 Posted September 7, 2013 Every device has links back to the PLM. That is why the Restore Modem (PLM) takes time when the PLM has been replaced as all the link records in all the devices have to have the PLM address changed. If two PLMs existed all the devices would have to have links to the backup PLM and would be receiving all the messages in parallel. That would increase the overall Insteon traffic and expose the backup PLM to the same traffic load as the primary PLM as well as increase the device link management cost to maintain duplicate PLM link records. I suspect maintaining two PLMs would cause more problems than it solves considering how long a PLM normally lasts. Also when a PLM failed all the links to the defective PLM would have to be removed to avoid the comm failures trying to talk to a device that is not responding.
barrygordon Posted September 7, 2013 Author Posted September 7, 2013 Thanks Lee. I think I agree with you. Any thoughts on why I can't get the Switchlinc to accept an update. It appears to be working fine. I rarely address it from the ISY. I guess I could just swap it out. Is there any nice easy function/menu item to replace a failed device such as a Switchlinc? It would be nice If you could just wire in the new device and tell the ISY to replace the address of the old device with that of the new one and have everything updated; or am I missing something that is easy and obvious
barrygordon Posted September 7, 2013 Author Posted September 7, 2013 ALL RESOLVED. I dropped power to the offending switchlinc and then restored power to it. The ISY was then able to update the switchlinc
LeeG Posted September 7, 2013 Posted September 7, 2013 FYI - if a new device is ever needed there is a "Replace xxxx with ..." function. Install the new device, add it to the ISY under a dummy name. Right click the old/failed node entry, select the "Replace" function. A list of replacement candidates will be displayed. The new dummy name is selected. All Scene and Program references will be adjusted to used the new device address. The old node name continues with the new Insteon address, the dummy entry representing the new device is automatically deleted. The old Insteon address is never used by the "Replace" function so the new device can be installed in the old device location before doing the Replace. The device types have to be the same. A dimmer replacing a dimmer, a relay replacing a relay, etc.
barrygordon Posted September 24, 2013 Author Posted September 24, 2013 Lee, I have a strange problem I am trying to troubleshoot. My current conclusion is that I have may have a bad keypad. The primary device is a micro relay on/off. It seems to work fine. I do not use its sense wires. I have it linked to a button (h) on an 8 key keypadlinc. I can turn it off by the keypadlinc, but not back on. I suspect I might have the scenes screwed up. How many scenes should I have if all I want is: 1- The keypadlink to be able to turn the micro relay on and off, the keypadlinc LED showing the state 2- A program to turn the micro relay on and off and the keypadlinc to track its state I assume I should only need one scene where the microlinc is a responder and the keypadlinc key is a controller and a responder. I have other microlincs controlled by other key in the same keypad and they seem to work fine. If I determine that the keypadlinc is bad, I have a spare keypadlinc that is already installed but not used. I wish to do the "Replace with xxxx" but can not find the option no matter what I right click on. On a separate note, can a scene have as one of its items another scene? I am running 4.0.5
Xathros Posted September 24, 2013 Posted September 24, 2013 Is the keypadlinc button H configured as Non-Toggle Off ? -Xathros
LeeG Posted September 24, 2013 Posted September 24, 2013 One Scene should cover the requirements. The KeypadLinc button H is added as a Controller, the Micro Relay On/Off as a Responder. The KeypadLinc button H IS NOT added to the Scene as a Responder as the ISY assumes the button is a Responder when the button is added as a Controller. The Program turns the Scene On/Off so the KPL button LED stays in sync with the status of the Micro Relay. I would not do a Replace With until some diagnostic procedures are run. The KeypadLincs must be the same type, Relay for Relay, Dimmer for Dimmer for a Replace With. A Relay cannot Replace a Dimmer for example. The Primary KeypadLinc node has the Replace With option. The first question is what Xathros asked, is the KPL button in non-toggle mode? Does the KPL button LED toggle On and Off as the button is pressed? If in non-toggle mode it will blink twice when pressed. The best test to rule out a KPL issue is to run Tools | Diagnostics | Event Viewer at LEVEL 3. Press button H On, then press button H Off. Does the event trace show the KPL button sent an On command, then sent an Off command. Post the event trace if the results are in question. A Scene cannot be added to a Scene. Insteon does not support that. All the individual devices must added to the Scene. A specific node can be a Controller of only one Scene. Again this is an Insteon requirement.
barrygordon Posted September 24, 2013 Author Posted September 24, 2013 When I cleaned up the scenes (I had one too many and they were badly configured) all started working again Correctly. Thank you gentlemen for the good advice (as usual)
Recommended Posts