paulw Posted March 10, 2013 Share Posted March 10, 2013 ISY has been in use for several years without issues. A couple of days ago I noticed that some lights were not going on and off as they should have been. Then I noticed that the isy was not responding to my alarm on and off's which communicate via x10. Hooked up an x10 analyzer at the modem and found readable x10 codes with no high levels of noise. But, the event viewer is not showing any recieved x10 codes (modem light if flashing when codes are being sent). The alarm and isy are on the same circuit. Find that the lights that the isy is having a problem turning on and off will work fine from other keypads that are linked. Sometimes I can turn a light on or off with the isy, other times not (see log below), some lights are fine all the time, others are ratty most if not all the time. My thought was noise, or legs not properly linked. But, with the alarm on the same circuit and the isy not seeing it and an analyzer seeing it (x10) and not showing noise..... So far I have; re-set the access points, restored the modem, re-booted the isy, none of which made any difference. In the following log, the first set of on and off worked, the second did not. Sun 03/10/2013 11:13:42 AM : [iNST-TX-I1 ] 02 62 00 00 37 CF 11 00 Sun 03/10/2013 11:13:42 AM : [iNST-ACK ] 02 62 00.00.37 CF 11 00 06 LTONRR (00) Sun 03/10/2013 11:13:42 AM : [ 13 18 14 1] ST 239 Sun 03/10/2013 11:13:42 AM : [ 13 17 97 1] ST 239 Sun 03/10/2013 11:13:42 AM : [ 12 C1 31 1] ST 239 Sun 03/10/2013 11:13:42 AM : [ 14 7B 68 1] ST 255 Sun 03/10/2013 11:13:42 AM : [ 12 C BF 1] ST 239 Sun 03/10/2013 11:13:42 AM : [ 14 C8 6D 1] ST 239 Sun 03/10/2013 11:13:42 AM : [ 7 5D EC 1] ST 239 Sun 03/10/2013 11:13:42 AM : [ 13 C0 5A 7] ST 255 Sun 03/10/2013 11:13:46 AM : [iNST-TX-I1 ] 02 62 00 00 37 CF 14 00 Sun 03/10/2013 11:13:47 AM : [iNST-ACK ] 02 62 00.00.37 CF 14 00 06 LTOFF-F(00) Sun 03/10/2013 11:13:47 AM : [ 13 18 14 1] ST 0 Sun 03/10/2013 11:13:47 AM : [ 13 17 97 1] ST 0 Sun 03/10/2013 11:13:47 AM : [ 12 C1 31 1] ST 0 Sun 03/10/2013 11:13:47 AM : [ 14 7B 68 1] ST 0 Sun 03/10/2013 11:13:47 AM : [ 12 C BF 1] ST 0 Sun 03/10/2013 11:13:47 AM : [ 14 C8 6D 1] ST 0 Sun 03/10/2013 11:13:47 AM : [ 7 5D EC 1] ST 0 Sun 03/10/2013 11:13:47 AM : [ 13 C0 5A 7] ST 0 Sun 03/10/2013 11:13:50 AM : [iNST-TX-I1 ] 02 62 00 00 37 CF 11 00 Sun 03/10/2013 11:13:50 AM : [iNST-ACK ] 02 62 00.00.37 CF 11 00 06 LTONRR (00) Sun 03/10/2013 11:13:50 AM : [ 13 18 14 1] ST 239 Sun 03/10/2013 11:13:50 AM : [ 13 17 97 1] ST 239 Sun 03/10/2013 11:13:50 AM : [ 12 C1 31 1] ST 239 Sun 03/10/2013 11:13:50 AM : [ 14 7B 68 1] ST 255 Sun 03/10/2013 11:13:50 AM : [ 12 C BF 1] ST 239 Sun 03/10/2013 11:13:50 AM : [ 14 C8 6D 1] ST 239 Sun 03/10/2013 11:13:50 AM : [ 7 5D EC 1] ST 239 Sun 03/10/2013 11:13:50 AM : [ 13 C0 5A 7] ST 255 Sun 03/10/2013 11:13:54 AM : [iNST-TX-I1 ] 02 62 00 00 37 CF 13 00 Sun 03/10/2013 11:13:54 AM : [iNST-ACK ] 02 62 00.00.37 CF 13 00 06 LTOFFRR(00) Sun 03/10/2013 11:13:54 AM : [ 13 18 14 1] ST 0 Sun 03/10/2013 11:13:54 AM : [ 13 17 97 1] ST 0 Sun 03/10/2013 11:13:54 AM : [ 12 C1 31 1] ST 0 Sun 03/10/2013 11:13:54 AM : [ 14 7B 68 1] ST 0 Sun 03/10/2013 11:13:54 AM : [ 12 C BF 1] ST 0 Sun 03/10/2013 11:13:54 AM : [ 14 C8 6D 1] ST 0 Sun 03/10/2013 11:13:54 AM : [ 7 5D EC 1] ST 0 Sun 03/10/2013 11:13:54 AM : [ 13 C0 5A 7] ST 0 Any thoughts? Link to comment
LeeG Posted March 10, 2013 Share Posted March 10, 2013 The Status changes in the event trace mean nothing unfortunately. There are no ACKs to a Scene On/Off. The ISY is marking the devices as they should theoretically be responding without any direct knowledge that the devices actually responded. Suggest running Scene Test which does get an ACK from every device in the Scene. The success or failure will be noted by device. Link to comment
paulw Posted March 10, 2013 Author Share Posted March 10, 2013 Hi Lee, When I ran the Scene Test, I could see many of the lights come on for a second or two, and then went out. Can't confirm all of them but I could see at least three of them from where I was sitting. Paul Sun 03/10/2013 01:31:09 PM : [GRP-RX ] 02 61 37 13 00 06 Sun 03/10/2013 01:31:09 PM : [iNST-SRX ] 02 50 12.0C.BF 12.9F.46 61 13 37 LTOFFRR(37) Sun 03/10/2013 01:31:10 PM : [iNST-SRX ] 02 50 12.A0.4E 12.9F.46 2B 0D 01 (01) ----- Emerg Inside Lites Test Results -----[Failed] Kit Island Pendents Lites (13 17 97 1)[Failed] Office Window Lite (13 18 14 1)[Failed] Kit KL- Chandelier (12 C1 31 1)[Failed] LR KL - A Sconce (14 C8 6D 1)[Failed] Gar Center Lite (14 7B 68 1)[Failed] Bath W Lites (atic) (12 C BF 1)[Failed] M BR KL - G Emerg Inside Lite (13 C0 5A 7)[Failed] DR Chandelier (atic) (7 5D EC 1)----- Emerg Inside Lites Test Results -----Sun 03/10/2013 01:31:17 PM : [iNST-TX-I1 ] 02 62 00 00 37 CF 13 00 Sun 03/10/2013 01:31:17 PM : [iNST-ACK ] 02 62 00.00.37 CF 13 00 06 LTOFFRR(00) Link to comment
LeeG Posted March 10, 2013 Share Posted March 10, 2013 The PLM has lost its link database. The lights that physically turned On indicate those devices have the required Scene link record in their link database. The PLM should have sent a follow up command to every device in the Scene which requires an ACK. The only device for which this was done is 12.0C.BF. This device was marked failed because of a bug in an older ISY image. What does Help | About show for Firmware? What does Help | About show for UI? The PLM link database can be restored with a File | Restore Modem (PLM). Link to comment
paulw Posted March 10, 2013 Author Share Posted March 10, 2013 Firmware and UI 3.3.4, upgraded about 5 months ago. I had tried a PLM restore before my first posting, no joy. Link to comment
LeeG Posted March 10, 2013 Share Posted March 10, 2013 Since you are running an early Beta I suggest moving to 4.0.2. You may have a defective PLM if a Restore Modem (PLM) did not fix the Scene Test issue. Once the ISY has been updated the devices that actually worked will no longer be falsely marked failed. You can run a Show PLM Links Table followed by a Count to see how many link records exist. The Show PLM Links Table can be difficult to get an accurate count as any Insteon traffic reaching the PLM during the Show PLM operation can produce a false high or low count. Link to comment
paulw Posted March 10, 2013 Author Share Posted March 10, 2013 Lee, Had to go to 3.3.10 (99i), my 994i is due in Tuesday. After installing 3.3.10, I did another plm restore, fixed the problem! Strange after so many months the beta would give a problem but, everything is resolved. Thanks again for your help!!! Link to comment
LeeG Posted March 11, 2013 Share Posted March 11, 2013 Glad the restore resolved the problem. That may be a sign the PLM is developing problems. If it continues to happen a new PLM would be in order. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.