Scottmichaelj Posted January 22, 2016 Share Posted January 22, 2016 I didnt check how many links I had because the PLM died but I started restoring the new PLM at around 1pm yesterday and its still going. No errors and its going through the process. I have the log window open on level 3 and its churring along fine and quickly. But man 24 hours now and still going. Wow. Link to comment
Teken Posted January 22, 2016 Share Posted January 22, 2016 I can relate but 24 HR's seems a little out of place considering you have all the latest Insteon gear. I could understand if you had generation one devices which were not ics2. But 24 hours later wow . . . Link to comment
jerlands Posted January 22, 2016 Share Posted January 22, 2016 I replaced my PLM a little over a year ago and don't remember a wait? Jon... Link to comment
Scottmichaelj Posted January 22, 2016 Author Share Posted January 22, 2016 (edited) I can relate but 24 HR's seems a little out of place considering you have all the latest Insteon gear. I could understand if you had generation one devices which were not ics2. But 24 hours later wow . . . Its acting like its working and all the hops are 3s and 2s and its not stopping or freezing up. Watching the event log cruising through too at L3. I counted about 87 devices total. Edited January 22, 2016 by huddadudda Link to comment
Teken Posted January 22, 2016 Share Posted January 22, 2016 Wait till you need to update all the battery only devices. Ha . . . Link to comment
Scottmichaelj Posted January 23, 2016 Author Share Posted January 23, 2016 Wait till you need to update all the battery only devices. Ha . . . Hahaha yeah... Hopefully they don't time out! Even just doing one at a time. Link to comment
stusviews Posted January 23, 2016 Share Posted January 23, 2016 The only battery powered devices I've had time out were original RemoteLincs--until I moved the most stubborn ones to the detached garage which, fortunately, had a few dual-band devices. Did you back-up the ISY prior to replacing the PLM? Link to comment
Scottmichaelj Posted January 23, 2016 Author Share Posted January 23, 2016 The only battery powered devices I've had time out were original RemoteLincs--until I moved the most stubborn ones to the detached garage which, fortunately, had a few dual-band devices. Did you back-up the ISY prior to replacing the PLM? Yup then put the new PLM in, turned on the ISY, logged in and then did a restore. Seems like its working fine just taking forever. Link to comment
smokegrub Posted January 23, 2016 Share Posted January 23, 2016 I replaced my PLM a couple of months ago and the process went very quickly. Link to comment
Scottmichaelj Posted January 23, 2016 Author Share Posted January 23, 2016 So should I do a ctrl alt del and close it or just let it keep going? I do have 30 scenes, with at least six that that all the lights in the house and then change the levels as the scenes progress. IE sunset to evening to relaxing then all off. Each scene has all my inside switches and devices in them. Maybe I have more links than I think? Link to comment
stusviews Posted January 23, 2016 Share Posted January 23, 2016 The ISY should remember where it was at. It does not depend on the computer, although rebooting may help. You may need to power-cycle the ISY. Link to comment
Scottmichaelj Posted January 23, 2016 Author Share Posted January 23, 2016 The ISY should remember where it was at. It does not depend on the computer, although rebooting may help. You may need to power-cycle the ISY. So I did a control alt del on the admin console and then factory reset the PLM. I loaded up the admin console again and now its cycling through and not stopping. Its been like this for an hour. Should I factory reset the ISY? This hasn't been a good week! argh. Link to comment
Teken Posted January 23, 2016 Share Posted January 23, 2016 So I did a control alt del on the admin console and then factory reset the PLM. I loaded up the admin console again and now its cycling through and not stopping. Its been like this for an hour. Should I factory reset the ISY? This hasn't been a good week! argh. I wouldn't go that far at this point but have experienced the same thing you're going through now. In my case I simply killed the power to the ISY Series Controller and waited about 30 seconds. Once that was done I powered up the controller and did a restore from a good known back up. After that long process completed I hard reset the PLM and went through the whole PLM restore process. I absolutely disabled the battery write so it didn't slow down the PLM restore process. Given the number of devices you have this should take about 4-8 hours and this includes doing the single battery write one at a time. Don't even think about doing the auto write update option because you're going to lose more hair on your balding head and raise your stress level five bars. Go smoke a blunt and kick back a few cold ones . . . Link to comment
stusviews Posted January 23, 2016 Share Posted January 23, 2016 What you did was to start again. My suggestion was to power-cycle the ISY. Link to comment
Scottmichaelj Posted January 23, 2016 Author Share Posted January 23, 2016 What you did was to start again. My suggestion was to power-cycle the ISY. Thats what I did and now its cycling through again and I can't cancel it. Here is a snippet of the log. Fri 01/22/2016 08:19:51 PM : [iNST-SRX ] 02 50 22.35.79 00.4A.01 CF 14 01 LTOFF-F(01) Fri 01/22/2016 08:19:51 PM : [std-Group ] 22.35.79-->Group=1, Max Hops=3, Hops Left=3 Fri 01/22/2016 08:19:51 PM : [D2D EVENT ] Event [22 35 79 1] [DFOF] [1] uom=0 prec=-1 Fri 01/22/2016 08:19:51 PM : [ 22 35 79 1] DFOF 1 Fri 01/22/2016 08:19:51 PM : [iNST-SRX ] 02 50 22.35.79 00.4B.01 CF 14 01 LTOFF-F(01) Fri 01/22/2016 08:19:51 PM : [std-Group ] 22.35.79-->Group=1, Max Hops=3, Hops Left=3 Fri 01/22/2016 08:19:51 PM : [D2D EVENT ] Event [22 35 79 1] [DFOF] [1] uom=0 prec=-1 Fri 01/22/2016 08:19:51 PM : [ 22 35 79 1] DFOF 1 Fri 01/22/2016 08:19:51 PM : [iNST-SRX ] 02 50 22.35.79 00.4C.01 CF 14 01 LTOFF-F(01) Fri 01/22/2016 08:19:51 PM : [std-Group ] 22.35.79-->Group=1, Max Hops=3, Hops Left=3 Fri 01/22/2016 08:19:51 PM : [D2D EVENT ] Event [22 35 79 1] [DFOF] [1] uom=0 prec=-1 Fri 01/22/2016 08:19:51 PM : [ 22 35 79 1] DFOF 1 Fri 01/22/2016 08:19:52 PM : [iNST-SRX ] 02 50 22.35.79 00.4D.01 CF 14 01 LTOFF-F(01) Fri 01/22/2016 08:19:52 PM : [std-Group ] 22.35.79-->Group=1, Max Hops=3, Hops Left=3 Fri 01/22/2016 08:19:52 PM : [D2D EVENT ] Event [22 35 79 1] [DFOF] [1] uom=0 prec=-1 Fri 01/22/2016 08:19:52 PM : [ 22 35 79 1] DFOF 1 Fri 01/22/2016 08:19:52 PM : [iNST-SRX ] 02 50 22.35.79 00.4E.01 C7 14 01 LTOFF-F(01) Fri 01/22/2016 08:19:52 PM : [std-Group ] 22.35.79-->Group=1, Max Hops=3, Hops Left=1 Fri 01/22/2016 08:19:52 PM : [D2D EVENT ] Event [22 35 79 1] [DFOF] [1] uom=0 prec=-1 Fri 01/22/2016 08:19:52 PM : [ 22 35 79 1] DFOF 1 Fri 01/22/2016 08:19:52 PM : [iNST-SRX ] 02 50 22.35.79 00.4F.01 CF 14 01 LTOFF-F(01) Fri 01/22/2016 08:19:52 PM : [std-Group ] 22.35.79-->Group=1, Max Hops=3, Hops Left=3 Fri 01/22/2016 08:19:52 PM : [D2D EVENT ] Event [22 35 79 1] [DFOF] [1] uom=0 prec=-1 Fri 01/22/2016 08:19:52 PM : [ 22 35 79 1] DFOF 1 Fri 01/22/2016 08:19:52 PM : [iNST-SRX ] 02 50 22.35.79 00.50.01 CF 14 01 LTOFF-F(01) Fri 01/22/2016 08:19:52 PM : [std-Group ] 22.35.79-->Group=1, Max Hops=3, Hops Left=3 Fri 01/22/2016 08:19:52 PM : [D2D EVENT ] Event [22 35 79 1] [DFOF] [1] uom=0 prec=-1 Fri 01/22/2016 08:19:52 PM : [ 22 35 79 1] DFOF 1 Fri 01/22/2016 08:19:53 PM : [iNST-SRX ] 02 50 22.35.79 00.51.01 CF 14 01 LTOFF-F(01) Fri 01/22/2016 08:19:53 PM : [std-Group ] 22.35.79-->Group=1, Max Hops=3, Hops Left=3 Fri 01/22/2016 08:19:53 PM : [D2D EVENT ] Event [22 35 79 1] [DFOF] [1] uom=0 prec=-1 Fri 01/22/2016 08:19:53 PM : [ 22 35 79 1] DFOF 1 Fri 01/22/2016 08:19:53 PM : [iNST-SRX ] 02 50 22.35.79 00.52.01 CF 14 01 LTOFF-F(01) Fri 01/22/2016 08:19:53 PM : [std-Group ] 22.35.79-->Group=1, Max Hops=3, Hops Left=3 Fri 01/22/2016 08:19:53 PM : [D2D EVENT ] Event [22 35 79 1] [DFOF] [1] uom=0 prec=-1 Fri 01/22/2016 08:19:53 PM : [ 22 35 79 1] DFOF 1 Fri 01/22/2016 08:19:53 PM : [iNST-SRX ] 02 50 22.35.79 00.53.01 CF 14 01 LTOFF-F(01) Fri 01/22/2016 08:19:53 PM : [std-Group ] 22.35.79-->Group=1, Max Hops=3, Hops Left=3 Fri 01/22/2016 08:19:53 PM : [D2D EVENT ] Event [22 35 79 1] [DFOF] [1] uom=0 prec=-1 Fri 01/22/2016 08:19:53 PM : [ 22 35 79 1] DFOF 1 Fri 01/22/2016 08:19:53 PM : [iNST-SRX ] 02 50 22.35.79 00.54.01 CF 14 01 LTOFF-F(01) Fri 01/22/2016 08:19:53 PM : [std-Group ] 22.35.79-->Group=1, Max Hops=3, Hops Left=3 Fri 01/22/2016 08:19:53 PM : [D2D EVENT ] Event [22 35 79 1] [DFOF] [1] uom=0 prec=-1 Fri 01/22/2016 08:19:53 PM : [ 22 35 79 1] DFOF 1 Fri 01/22/2016 08:19:54 PM : [iNST-SRX ] 02 50 22.35.79 00.55.01 CF 14 01 LTOFF-F(01) Fri 01/22/2016 08:19:54 PM : [std-Group ] 22.35.79-->Group=1, Max Hops=3, Hops Left=3 Fri 01/22/2016 08:19:54 PM : [D2D EVENT ] Event [22 35 79 1] [DFOF] [1] uom=0 prec=-1 Fri 01/22/2016 08:19:54 PM : [ 22 35 79 1] DFOF 1 Fri 01/22/2016 08:19:54 PM : [iNST-SRX ] 02 50 22.35.79 00.56.01 CF 14 01 LTOFF-F(01) Fri 01/22/2016 08:19:54 PM : [std-Group ] 22.35.79-->Group=1, Max Hops=3, Hops Left=3 Fri 01/22/2016 08:19:54 PM : [D2D EVENT ] Event [22 35 79 1] [DFOF] [1] uom=0 prec=-1 Fri 01/22/2016 08:19:54 PM : [ 22 35 79 1] DFOF 1 Fri 01/22/2016 08:19:54 PM : [iNST-SRX ] 02 50 22.35.79 00.57.01 CF 14 01 LTOFF-F(01) Fri 01/22/2016 08:19:54 PM : [std-Group ] 22.35.79-->Group=1, Max Hops=3, Hops Left=3 Fri 01/22/2016 08:19:54 PM : [D2D EVENT ] Event [22 35 79 1] [DFOF] [1] uom=0 prec=-1 Fri 01/22/2016 08:19:54 PM : [ 22 35 79 1] DFOF 1 Fri 01/22/2016 08:19:54 PM : [iNST-SRX ] 02 50 22.35.79 00.58.01 CF 14 01 LTOFF-F(01) Fri 01/22/2016 08:19:54 PM : [std-Group ] 22.35.79-->Group=1, Max Hops=3, Hops Left=3 Fri 01/22/2016 08:19:54 PM : [D2D EVENT ] Event [22 35 79 1] [DFOF] [1] uom=0 prec=-1 Fri 01/22/2016 08:19:54 PM : [ 22 35 79 1] DFOF 1 Fri 01/22/2016 08:19:54 PM : [iNST-SRX ] 02 50 22.35.79 00.59.01 CF 14 01 LTOFF-F(01) Fri 01/22/2016 08:19:54 PM : [std-Group ] 22.35.79-->Group=1, Max Hops=3, Hops Left=3 Fri 01/22/2016 08:19:54 PM : [D2D EVENT ] Event [22 35 79 1] [DFOF] [1] uom=0 prec=-1 Fri 01/22/2016 08:19:55 PM : [ 22 35 79 1] DFOF 1 Fri 01/22/2016 08:19:55 PM : [iNST-SRX ] 02 50 22.35.79 00.5A.01 CF 14 01 LTOFF-F(01) Fri 01/22/2016 08:19:55 PM : [std-Group ] 22.35.79-->Group=1, Max Hops=3, Hops Left=3 Fri 01/22/2016 08:19:55 PM : [D2D EVENT ] Event [22 35 79 1] [DFOF] [1] uom=0 prec=-1 Fri 01/22/2016 08:19:55 PM : [ 22 35 79 1] DFOF 1 Fri 01/22/2016 08:19:55 PM : [iNST-SRX ] 02 50 22.35.79 00.5B.01 CF 14 01 LTOFF-F(01) Fri 01/22/2016 08:19:55 PM : [std-Group ] 22.35.79-->Group=1, Max Hops=3, Hops Left=3 Fri 01/22/2016 08:19:55 PM : [D2D EVENT ] Event [22 35 79 1] [DFOF] [1] uom=0 prec=-1 Fri 01/22/2016 08:19:55 PM : [ 22 35 79 1] DFOF 1 Fri 01/22/2016 08:19:55 PM : [iNST-SRX ] 02 50 22.35.79 00.5C.01 CF 14 01 LTOFF-F(01) Fri 01/22/2016 08:19:55 PM : [std-Group ] 22.35.79-->Group=1, Max Hops=3, Hops Left=3 Fri 01/22/2016 08:19:55 PM : [D2D EVENT ] Event [22 35 79 1] [DFOF] [1] uom=0 prec=-1 Fri 01/22/2016 08:19:55 PM : [ 22 35 79 1] DFOF 1 Fri 01/22/2016 08:19:55 PM : [iNST-SRX ] 02 50 22.35.79 00.5D.01 CF 14 01 LTOFF-F(01) Fri 01/22/2016 08:19:55 PM : [std-Group ] 22.35.79-->Group=1, Max Hops=3, Hops Left=3 Fri 01/22/2016 08:19:55 PM : [D2D EVENT ] Event [22 35 79 1] [DFOF] [1] uom=0 prec=-1 Fri 01/22/2016 08:19:55 PM : [ 22 35 79 1] DFOF 1 Link to comment
jerlands Posted January 23, 2016 Share Posted January 23, 2016 What device is 22 35 79 1? Jon... Link to comment
Scottmichaelj Posted January 23, 2016 Author Share Posted January 23, 2016 What device is 22 35 79 1? Jon... Upstairs Hallway Switch Link to comment
LeeG Posted January 23, 2016 Share Posted January 23, 2016 (edited) Device 22.35.79 is repeatedly sending a Fast Off, over and over again. Only the first message in a normal Fast Off message sequence is sent. The event trace shows no outbound commands. Suggest pulling Set button on device to shut it down. Fri 01/22/2016 08:19:51 PM : [iNST-SRX ] 02 50 22.35.79 00.4A.01 CF 14 01 LTOFF-F(01)Fri 01/22/2016 08:19:51 PM : [std-Group ] 22.35.79-->Group=1, Max Hops=3, Hops Left=3Fri 01/22/2016 08:19:51 PM : [D2D EVENT ] Event [22 35 79 1] [DFOF] [1] uom=0 prec=-1Fri 01/22/2016 08:19:51 PM : [ 22 35 79 1] DFOF 1Fri 01/22/2016 08:19:51 PM : [iNST-SRX ] 02 50 22.35.79 00.4B.01 CF 14 01 LTOFF-F(01)Fri 01/22/2016 08:19:51 PM : [std-Group ] 22.35.79-->Group=1, Max Hops=3, Hops Left=3Fri 01/22/2016 08:19:51 PM : [D2D EVENT ] Event [22 35 79 1] [DFOF] [1] uom=0 prec=-1Fri 01/22/2016 08:19:51 PM : [ 22 35 79 1] DFOF 1 Edited January 23, 2016 by LeeG Link to comment
Scottmichaelj Posted January 23, 2016 Author Share Posted January 23, 2016 Device 22.35.79 is repeatedly sending a Fast Off, over and over again. Only the first message in a normal Fast Off message sequence is sent. The event trace shows no outbound commands. Suggest pulling Set button on device to shut it down. Fri 01/22/2016 08:19:51 PM : [iNST-SRX ] 02 50 22.35.79 00.4A.01 CF 14 01 LTOFF-F(01) Fri 01/22/2016 08:19:51 PM : [std-Group ] 22.35.79-->Group=1, Max Hops=3, Hops Left=3 Fri 01/22/2016 08:19:51 PM : [D2D EVENT ] Event [22 35 79 1] [DFOF] [1] uom=0 prec=-1 Fri 01/22/2016 08:19:51 PM : [ 22 35 79 1] DFOF 1 Fri 01/22/2016 08:19:51 PM : [iNST-SRX ] 02 50 22.35.79 00.4B.01 CF 14 01 LTOFF-F(01) Fri 01/22/2016 08:19:51 PM : [std-Group ] 22.35.79-->Group=1, Max Hops=3, Hops Left=3 Fri 01/22/2016 08:19:51 PM : [D2D EVENT ] Event [22 35 79 1] [DFOF] [1] uom=0 prec=-1 Fri 01/22/2016 08:19:51 PM : [ 22 35 79 1] DFOF 1 I airgapped that switch then the console crashed. Now I cant login with my username and password. I tried to reset the password via the pin in the front and power cycling to no avail. This week has just turned into pure doo doo. Any thoughts? Tried my normal login and admin/admin neither work. Link to comment
jerlands Posted January 23, 2016 Share Posted January 23, 2016 This week has just turned into pure doo doo. I don't know why that's so funny sorry... here's a link for proper reset. observe the light sequence when starting. Jon... Link to comment
Scottmichaelj Posted January 23, 2016 Author Share Posted January 23, 2016 I don't know why that's so funny sorry... here's a link for proper reset. observe the light sequence when starting. Jon... Done but now I cant connect to the ISY! See DOO DOO! Link to comment
jerlands Posted January 23, 2016 Share Posted January 23, 2016 The options on that page are for 1. Reboot 2. Reset Userid/Password to admin/admin 3. Factory Reset Of course factory reset requires a fresh backup Jon... Link to comment
Scottmichaelj Posted January 23, 2016 Author Share Posted January 23, 2016 The options on that page are for 1. Reboot 2. Reset Userid/Password to admin/admin 3. Factory Reset Of course factory reset requires a fresh backup Jon... Still locked out. Can seem to reset the password because I cant login. Link to comment
jerlands Posted January 23, 2016 Share Posted January 23, 2016 From the wiki... Reset Userid/Password to admin/admin 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 You can also use Telnet to reset password... Jon... Link to comment
paulbates Posted January 23, 2016 Share Posted January 23, 2016 The default after a reset is admin/admin, I believe. Give that a try. Paul Link to comment
Recommended Posts