Guest mvanmeter Posted January 28, 2014 Posted January 28, 2014 What is the procedure for starting with a clean slate. I am getting "can not recognize engine" on all devices I try to install.
LeeG Posted January 28, 2014 Posted January 28, 2014 I would not expect resetting the ISY having any corrective action as one can see when resetting other Insteon devices. That message normally means an Insteon Mesh Network issue. Run Tools | Diagnostics | Event Viewer at LEVEL 3. Post the event trace of a device that is failing. Make sure the phase coupling devices are working, other devices powered from the PLM circuit are isolated with a FilterLinc, no surge/noise suppression devices powered from PLM circuit. What ISY firmware is being used?
Guest mvanmeter Posted January 28, 2014 Posted January 28, 2014 Firmware is v4.0.5 Product had been working fine. Tue 01/28/2014 01:15:57 PM : [28 BB D0 ] Added to list of devices to link to ISY Tue 01/28/2014 01:15:57 PM : [iNST-TX-I1 ] 02 62 28 BB D0 0F 0D 00 Tue 01/28/2014 01:15:57 PM : [iNST-ACK ] 02 62 28.BB.D0 0F 0D 00 06 (00) Tue 01/28/2014 01:16:06 PM : [iNST-TX-I1 ] 02 62 28 BB D0 0F 0D 00 Tue 01/28/2014 01:16:06 PM : [iNST-ACK ] 02 62 28.BB.D0 0F 0D 00 06 (00) Tue 01/28/2014 01:16:15 PM : [iNST-TX-I1 ] 02 62 28 BB D0 0F 0D 00 Tue 01/28/2014 01:16:19 PM : [28 BB D0 0 ] Failed to add device, reason 3 Tue 01/28/2014 01:16:19 PM : [All ] Writing 0 bytes to devices Tue 01/28/2014 01:17:25 PM : [ Time] 13:17:28 0(0) Tue 01/28/2014 01:24:24 PM : [iNST-SRX ] 02 50 28.BB.D0 2A.1F.EF 2B 0D 02 (02) Tue 01/28/2014 01:24:24 PM : [std-Direct Ack] 28.BB.D0-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Tue 01/28/2014 01:24:24 PM : [iNST-DUP ] Previous message ignored.
LeeG Posted January 28, 2014 Posted January 28, 2014 The device took some 8 minutes to respond to the request for Insteon Engine. I would disable all the Programs and see if that makes a difference. Since no Insteon traffic is being traced besides that device you could have a Program in a loop. Tue 01/28/2014 01:15:57 PM : [28 BB D0 ] Added to list of devices to link to ISY Tue 01/28/2014 01:15:57 PM : [iNST-TX-I1 ] 02 62 28 BB D0 0F 0D 00 Tue 01/28/2014 01:15:57 PM : [iNST-ACK ] 02 62 28.BB.D0 0F 0D 00 06 (00) Tue 01/28/2014 01:16:06 PM : [iNST-TX-I1 ] 02 62 28 BB D0 0F 0D 00 Tue 01/28/2014 01:16:06 PM : [iNST-ACK ] 02 62 28.BB.D0 0F 0D 00 06 (00) Tue 01/28/2014 01:16:15 PM : [iNST-TX-I1 ] 02 62 28 BB D0 0F 0D 00 Tue 01/28/2014 01:16:19 PM : [28 BB D0 0 ] Failed to add device, reason 3 Tue 01/28/2014 01:16:19 PM : [All ] Writing 0 bytes to devices Tue 01/28/2014 01:17:25 PM : [ Time] 13:17:28 0(0) Tue 01/28/2014 01:24:24 PM : [iNST-SRX ] 02 50 28.BB.D0 2A.1F.EF 2B 0D 02 (02) Tue 01/28/2014 01:24:24 PM : [std-Direct Ack] 28.BB.D0-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Tue 01/28/2014 01:24:24 PM : [iNST-DUP ] Previous message ignored.
Guest mvanmeter Posted January 28, 2014 Posted January 28, 2014 No programs running. Deleted all devices. Trying to install On/Off wall switch. Tue 01/28/2014 01:49:43 PM : [28 BB D0 ] Added to list of devices to link to ISY Tue 01/28/2014 01:49:43 PM : [iNST-TX-I1 ] 02 62 28 BB D0 0F 0D 00 Tue 01/28/2014 01:49:43 PM : [iNST-ACK ] 02 62 28.BB.D0 0F 0D 00 06 (00) Tue 01/28/2014 01:49:52 PM : [iNST-TX-I1 ] 02 62 28 BB D0 0F 0D 00 Tue 01/28/2014 01:50:01 PM : [iNST-TX-I1 ] 02 62 28 BB D0 0F 0D 00 Tue 01/28/2014 01:50:01 PM : [iNST-ACK ] 02 62 28.BB.D0 0F 0D 00 06 (00) Tue 01/28/2014 01:50:05 PM : [28 BB D0 0 ] Failed to add device, reason 3 Tue 01/28/2014 01:50:05 PM : [All ] Writing 0 bytes to devices
LeeG Posted January 28, 2014 Posted January 28, 2014 Something made the device wait 8 minutes before responding to the query of the Insteon Engine. The last post is the three commands issued to the device, none of which got a response. In the first trace it took 8 minutes for the device response to be received. When the response came back from the device the Hops Left count was 2 which is good communication. Has anything been added to the powerline that uses the powerline for communication? Something that does not look like X10 or Insteon would not be traced by the PLM but could interfere with a device trying to sent if it thinks the powerline is busy with something else.
Guest mvanmeter Posted January 28, 2014 Posted January 28, 2014 Tried to install motion sensor and got the same reply. Nothing has been added to the line I'm aware of. The PLM says it is connected.
LeeG Posted January 28, 2014 Posted January 28, 2014 Was the motion sensor put into linking mode before using New INSTEON Device to add the device? I have never seen a device wait 8 minutes to respond to a command. I would have thought that to be impossible without seeing it in the event trace. Suggest removing power from the PLM for 30 seconds followed by a reboot of the ISY. Only thing I can think to try is removing power from all the Insteon devices by pulling the air gap switches and unplugging the others. Than try one device and see if one device will work. That would require restoring power to the devices that are coupling.
Guest mvanmeter Posted January 28, 2014 Posted January 28, 2014 Yes, Motion was in setup mode. This is a test bed project. Only have motion and wall switch for testing. Removed wall switch. Present config is 944i, PLM and motion detector. All hardware in same room.
Xathros Posted January 28, 2014 Posted January 28, 2014 If the PLM is a 2413S then you should be able to link the MS when in close proximity to the PLM. Depending on the wall switch, you may need some access points to provide a phase bridge. A pair of access points is highly recommended for all setups. Depending on placement, these can vastly improve your wireless coverage as well as bridge the phases of your electrical system. -Xathros
Guest mvanmeter Posted January 28, 2014 Posted January 28, 2014 Tested 2413S setting on floor next to PLM. Same issue. These devices have been working up until today.
Xathros Posted January 28, 2014 Posted January 28, 2014 2413S is the PLM. I assume you mean you tested the motion sensor next to the PLM. I'm beginning to think you may have a bad PLM or you have other RF activity in the 900Mhz spectrum that is interfering with the PLM's ability to hear. Wireless baby monitors, 900Mhs cordless phones etc are likely suspects for this kind of problem. -Xathros
Guest mvanmeter Posted January 28, 2014 Posted January 28, 2014 Any way to test the PLM. All it says is that it is connected.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.