recover/replace console user/password

[Harold]

I have had to replace the PLC. It has been a long time since it was working and I have forgotten how to access the console. I can not find a record of the information (once resolved, I will make a better file containing this information).

 

Could someone please explain how to access the admin and other functions without knowing the existing ID/password?

[jerlands]

You can reset the username/password back to admin/admin by following instructions from the Wiki...

 

Reset Username and Password to Defaults

• Use a sharp object to push in the Reset Button till the RX, TX, Mem, Error lights start blinking (every second)
• Hold for 5 seconds till the RX, TX, Mem, Error lights turn on/off consecutively (RX -> Tx -> Mem -> Error)
• Release

 

 

Jon...

[Harold]

Thank you.

[jerlands]

Good luck on the PLM replacement but be sure to follow the instructions for replacing and NOT to delete modem.

Thanks for posting back...

 

To replace a PLM:

• Unplug ISY from the power outlet
• Unplug the PLM from ISY and power outlet
• Connect ISY’s port A to the new PLM
• Plug the new PLM into a power outlet
• Plug ISY into a power outlet
• Go to Admin Console and wait for system initialization to complete
  • If you have PRO Series, click on the Battery icon at the top. This will prevent ISY from trying to update programming on your RF devices which are probably in sleep mode
• Click on the Restore Modem (PLM) menu option
  • In case ISY cannot communicate (or decides not to if an RF device/PRO Series) during the process, you will have a series of nodes with green 1011 icons in the device tree. For each one of those nodes:
    • If an RF device, ensure that the device is in Programming mode
    • Right mouse click | Write pending updates ...

 

 

Jon...

[Harold]

I am still getting nowhere.

 

The ISY is a 994i/IR-PRO. Serial 0013xxx.

 

I tried resetting the user/password to default three times. admin/admin still did not work.

 

I had several admin console icons on the desktop and start menu. Managed to get rid of them and went to your announcement of version 4.2.22 (what I had loaded, I believe). Opened console from that post in case I had mismatched versions.

 

A comment for UD - it would be nice if these things could generate more meaningful messages. And if a  release level issue is causing a problem, the console would notify the user that that was a problem.

 

I have cleared cache repeatedly after each attempt.

 

I tried setting new name/password but that never worked.

 

The only thing I can use in the console when it loads is the configuration page. I have filled all the info out several times. No results. The next time it is empty again.

 

I have tried to tell the little link finder application what the IP address of my ISY is. It always says it did not find the ISY at startup, and when I input the IP it always returns a message that it is an invalid URL. It has been doing that for a very long time.

 

The ISY is set with a static IP address. This still seems to be working. My router sees it as does arp.

 

Unless someone has some magic for me to use, I could possibly do a bare metal reset. But I am really not happy with that solution as the next step.

 

The ISY just does not seem to be willing to talk to my PC. I have tried different cables and switch ports, I don't have a spare power supply to test that. The 2 green lights on the ISY are on on. Only the one on the right is blinking. Seems to be trying to do something; but not successful. The switch has one light blinking, the other not on. I believe the right light on the switch is just displaying LAN speed of the connection. The ISY appears to be 100 mb.

[jerlands]

I am still getting nowhere.

 

The ISY is a 994i/IR-PRO. Serial 0013xxx.

 

I tried resetting the user/password to default three times. admin/admin still did not work.

 

I had several admin console icons on the desktop and start menu. Managed to get rid of them and went to your announcement of version 4.2.22 (what I had loaded, I believe). Opened console from that post in case I had mismatched versions.

 

A comment for UD - it would be nice if these things could generate more meaningful messages. And if a  release level issue is causing a problem, the console would notify the user that that was a problem.

 

I have cleared cache repeatedly after each attempt.

 

I tried setting new name/password but that never worked.

 

The only thing I can use in the console when it loads is the configuration page. I have filled all the info out several times. No results. The next time it is empty again.

 

I have tried to tell the little link finder application what the IP address of my ISY is. It always says it did not find the ISY at startup, and when I input the IP it always returns a message that it is an invalid URL. It has been doing that for a very long time.

 

The ISY is set with a static IP address. This still seems to be working. My router sees it as does arp.

 

Unless someone has some magic for me to use, I could possibly do a bare metal reset. But I am really not happy with that solution as the next step.

 

The ISY just does not seem to be willing to talk to my PC. I have tried different cables and switch ports, I don't have a spare power supply to test that. The 2 green lights on the ISY are on on. Only the one on the right is blinking. Seems to be trying to do something; but not successful. The switch has one light blinking, the other not on. I believe the right light on the switch is just displaying LAN speed of the connection. The ISY appears to be 100 mb.

 

A possible solution is to Telnet into ISY (using admin/admin) where you can change user id to default admin/admin and also check the currently installed firmware version using VE command.

Last resort might be to factory reset ISY and load last good backup but you'd lose any changes made from that period of time to the present.

 

 

Jon...

[jerlands]

The ISY just does not seem to be willing to talk to my PC. I have tried different cables and switch ports, I don't have a spare power supply to test that. The 2 green lights on the ISY are on on. Only the one on the right is blinking. Seems to be trying to do something; but not successful. The switch has one light blinking, the other not on. I believe the right light on the switch is just displaying LAN speed of the connection. The ISY appears to be 100 mb.

 

I just noticed your light status in ISY... You might try rebooting to see if it clears to just showing power light lit.

 

Edit: remove power from ISY, wait about 30 sec then plug back in.

 

 

Jon...

[jerlands]

Also, here's a link to troubleshooting ISY flowchart that might help.

 

 

Jon...

[Harold]

I tried Telnet yesterday. No joy.

 

Jerlands - I think you are confusing the green lights on the Ethernet port I mentioned with the front panel lights.  I have rebooted many times. Two lights are on. Power and Rx. Should have included that info.

 

I will look at the link.

[jerlands]

I tried Telnet yesterday. No joy.

 

Jerlands - I think you are confusing the green lights on the Ethernet port I mentioned with the front panel lights.  I have rebooted many times. Two lights are on. Power and Rx. Should have included that info.

 

I will look at the link.

 

One solution that always works is to open a ticket with UDI

 

 

Jon...

[Harold]

That seems like what I should do. Nothing that I could try in that link did anything useful.

 

Done.

[jerlands]

That seems like what I should do. Nothing that I could try in that link did anything useful.

 

Done.

 

Once resolved, and for the sake of any interested, you might post back the fix.

 

 

Jon...

[Michel Kohanim]

Hi Jon,

 

I have a remote session setup with Harold today.

 

With kind regards,

Michel

[Harold]

Just a minor update if anyone was following this.

 

Still not working correctly. Initial problem; I had the wrong cable connected to the PLM. Duhh. But I had re positioned/rewired everything in the room. So it was not that stupid. There are still problems. I have several devices that just will not talk to the PLM. I hate the idea, but I may have at least 4 bad devices. That seems excessive.

 

Michel spent quite a bit of time with me (I had already correct the cable thing). He went through a bunch of things. Took over my PC. Can't fool me; he has done this before. I frequently could not follow what he was doing because his fingers are that fast. Not to mention him reall really understanding things. Impressive.

 

I have not been back to this because other crises have intruded. Broken dishwasher, and I applied a "harmless" program to stop MS from trying to install win 10 without me agreeing. Worked on my machine; really hosed my wife's machine. Not on my computer as much since I am sleeping in the garage.

[jerlands]

Just a minor update if anyone was following this.

 

Still not working correctly. Initial problem; I had the wrong cable connected to the PLM. Duhh. But I had re positioned/rewired everything in the room. So it was not that stupid. There are still problems. I have several devices that just will not talk to the PLM. I hate the idea, but I may have at least 4 bad devices. That seems excessive.

 

Michel spent quite a bit of time with me (I had already correct the cable thing). He went through a bunch of things. Took over my PC. Can't fool me; he has done this before. I frequently could not follow what he was doing because his fingers are that fast. Not to mention him reall really understanding things. Impressive.

 

I have not been back to this because other crises have intruded. Broken dishwasher, and I applied a "harmless" program to stop MS from trying to install win 10 without me agreeing. Worked on my machine; really hosed my wife's machine. Not on my computer as much since I am sleeping in the garage.

 

You might first check the device links table (right click on device > Diagnostics > Show Device Links Table ) then click compare.  Links in device and ISY could be identical.

If they aren't identical you could try Restore Device (right click on device and select "Restore Device.")

Also, open event viewer to level 3 (Tools > Diagnostics > Event Viewer and change level to 3.) operate the device form the admin console then copy trace from event viewer (click the clipboard looking icon on bottom toolbar) and paste into message and post.

 

 

Jon...

[Harold]

Thanks. I did try restore several times. When I get back to it I will run a log. Like I said, I have a real feeling that I have multiple failed devices. Probably caused by a power outage a while back.

[Michel Kohanim]

Hi Harold,

 

I am so very sorry to hear. Please submit another ticket and we'd be delighted to get to the bottom of the issues you are having.

 

With kind regards,

Michel

[Harold]

I have been trying to think about what is happening. And reading a whole bunch of presumably relevant threads. Below is what I have now considered significant events and behavior from day one. I am hoping that this will generate some ideas. I toss these out for considerations by you guys that actually understand these things.

 

First - The old PLM failed. That started this  whole thing. I had noticed some switches (none of those are the primary object of this discussion). It may have been the failing PLM doing strange things.  Repair failed so new PLM attached to ISY and plugged in. If I understand correctly, this can cause the ISY to talk to incorrect addresses in the PLM and vice versa. Can we assume this took place?

 

I have restored the PLM several times. I have restored all devices as a whole and individually. Except for wireless remote controls. I set these to "don't write" while doing restores. The remotes apparently still function as expected  As do some of the other attached Insteon devices. I turned off the ISY and unplugged the PLM, and then repowered everything in the order specified for a new PLM. Probably too late.

 

Four Insteon relay switches are flagged as not being able to communicate in the UD application. Now here is something I noticed when getting ready to replace one switch. There is a set of three switches in a group. They each control a set of three three lighting circuit from their 8 button front panels. One of these started this exercise. It is the power source for the range hood lights. The lights were for a long time CFL, but several months ago I put in Cree LED bulbs. One day the lights would not light and the switch made a loud buzzing noise whenever it was turned on. I removed the two LED bulbs and put in an incandescent bulb. Same results. No light, loud buzzing in the control. My initial thought was that I had a triac based dimmer in there; but it is a relay and should not have cared about the load. This switch is one that UD says is not communicating.

 

The other two switches are odd. One of them simply reverted to believing it was only a single pole switch. The top and bottom two buttons still control the directly attached load. The third  switch still operates as an 8 button and controls ceiling lights. It is also a device showing as not communicating with the ISY. The interesting part here, is that the range hood control switch can still control the ceiling lights via that third switch. If the ceiling lights are controlled from the third switch (it is powering the ceiling lights) the lights are controlled AND the correct button in the range hood controller is activated and deactivated. These two switches not talking to the ISY, seem to be perfectly happy talking to each other.

 

Something is not right, but I am no longer convinced it is an actual failed switch. I also looked at yet another switch that buzzes if I press the button for the device it will in the future control. Nothing currently connected. I buzzes when I do that. Other buttons work fine.

 

That constitutes everything I can think of about the ongoing effort. In one place so the chain of events is clearer.

[Teken]

Hello Harold,

 

You've endured quite the journey so I will leave you with a quick thought. Normally if the KPL makes a noise it indicates improper wiring, incompatible load, or there is indeed a fault in the device.

 

As painful as it might be seeing that you have done pretty much what can be done. May I humbly suggest you take one problem KPL out and wire it to a spare extension cord you can sacrifice and wire the device to it.

 

This will allow you to bring that KPL to the PLM.

 

Since the device is already having issues you can take a staggered approach which is hard reset the KPL. Once done use the restore device and see if the KPL operates as expected. If it doesn't delete the device from the ISY and add it back once its in the system recreate the scenes and report back if it operates as expected.

 

NOTE: If doing all of the above using the extension method and hard resetting and adding back the KPL does not yield positive results it may very well be damaged.

 

If under the 2 year warranty period engage Smarthome and they will get you squared away.

[Harold]

Is it possible (though it would be deeply stupid) that my old devices are incompatible to the new PLM? My devices:

 

(2486S/WH6) KeypadLinc Relay v.33

(2476S) SwitchLinc Relay W/ Sense v.37

(2486DWH8) KeypadLinc Dimmer 8 Button v.2D (2486S/WH6) KeypadLinc Relay v.36

[Teken]

 

Is it possible (though it would be deeply stupid) that my old devices are incompatible to the new PLM? My devices:

 

(2486S/WH6) KeypadLinc Relay v.33

(2476S) SwitchLinc Relay W/ Sense v.37

(2486DWH8) KeypadLinc Dimmer 8 Button v.2D (2486S/WH6) KeypadLinc Relay v.36

 

 

Almost anything is possible when speaking about Smartlabs these days. But, I do not for see them removing support for legacy products from the PLM.

 

Its more likely you have a communication issue, poor coupling, or defective items.

[stusviews]

Possible, but not likely. When adding a legacy device, browse the ISY list for the device you're adding. The PLM doesn't have a list of devices.

[Michel Kohanim]

Hi Harold,

 

Auto Discover should find devices as old as 2007. So, if you are still having problems, please do not hesitate to contact our tech support.

 

With kind regards,

Michel

[Harold]

Every time I turn around, it's something else. So I go to replace the first switch to buzz and not drive the load. It is a 2486S. I have a bunch of them. They don't make them anymore, but I have several spares from uncompleted expansion of the network. It appears that it is replaced by the 2487S which is dual band. Smarthome has removed the PDF manual. I found a wiki for it there, but if anyone know where a PDF manual for the device can be found. Searching was not productive. I would like a PDF so it is in a similar format to the 2483S which would make it easier to compare for differences.

 

I know I am beating on a seriously sick horse; but.

 

Every one of the devices that the PLM says it can't communicate with are the

(2486S/WH6) KeypadLinc Relay v.33.  Most of the rest of these devices are experiencing failures in scenes they belong in. Some buttons work; others not. Mostly it seems that they are behaving as if they were a single switch connected to the load.

 

Today, I tried again to restore and refresh the devices at the heart of things. Sometimes when I tell UD to write to them, it seems to do that. But the task just ends with no errors or information. Just for jollies, I used UD to change the state of the light (same type device, not behaving properly). I clicked off; the light want off. I clicked on; light went on. Repeated as needed. This particular switch has decided it is not 8 button, but a two pole switch. It has no understanding of the B button. Combine that with what I said earlier that two of these will talk to each other, but the PLM had them marked as inaccessible. The only devices that seem to be working are ones that are either a single switch on the load and dimmers (only two in the system). I use very few dimming circuits. I have always had the lights is lights view.

 

I also verified that the PLM and an access point are on different sides of the split phase power. I had two access points on the whole time in my office with the PLM. When I built the house, I had my office wired with alternate outlets being on a different "phase" for this sort of reason.

 

There is something here that is not right. I have no clue what it is. But experimentation shows that the PLM's conclusion about communications is not a hardware fault in any of the devices I have tested (4). The devices can communicate with each other just fine. That does not make any sense to me (but in this area that is not all that hard).

 

You guys that have been responding here - can you look at this post and put the thinking caps on. What is going on!! Please involve anyone you can think might be able to help. Michel's work with my machine did not appear to find any apparent problems.

 

 

[jerlands]

You might open Event Viewer to Level 3, try and operate a few devices then copy to clipboard and paste trace into message post.  A problem that sometimes isn't apparent is line noise which can come and go as the device or appliance turns on and off.  Gas fired furnaces can be a problem, and a motor that's on the fritz can inflict line noise, LED's, CFL's, electronics and UPS are all issues that don't always present themselves.

 

 

Jon...