Jump to content

Cannot determine Insteon Engine - Motion Sensor


mrbudin

Recommended Posts

Posted

I am running ISY 994i IR/Pro with PLM v9C (Firmware: 4.2.16). I've got the following errors when trying to add Motion Sensor and Mini Remote:

 

- Cannot determine Insteon Engine

- Cannot determine device link table addres

 

With other dual-band devices like Switch Linc or Open Close, my ISY 994i and PLM work fine.

 

I know someone has posted the same problems on this forum but i still need a help to solve my issue.

 

Thanks

 

 

 

Posted

Both of those devices are battery powered.   Put the Motion Sensor into linking mode using the Motion Sensor Set button.  Use New INSTEON Device, enter Insteon address of Motion Sensor, Name of choice, and Auto Discover.  Be sure Motion Sensor is near a Dual Band device.  Being near Dual Band 2413 PLM is good.   When New INSTEON Device is complete be sure to take Motion Sensor out of linking mode before following the same procedure for the Mini Remote.

Posted (edited)

Already done what you said above but it still doesn't work.

 

 

Fri 10/31/2014 11:18:32 AM : [  27 40 1E 1]       ST   0
 
Fri 10/31/2014 11:18:33 AM : [  27 40 1E 1]       ST 255
 
Fri 10/31/2014 11:18:36 AM : [  27 3F 24 1]       ST 255
 
Fri 10/31/2014 11:25:19 AM : [27 17 6     ] Added to list of devices to link to ISY
 
Fri 10/31/2014 11:25:44 AM : [27 17 6 0   ] Failed to add device, reason 9
 
Fri 10/31/2014 11:25:45 AM : [All         ] Writing 0 bytes to devices
 
Fri 10/31/2014 11:28:15 AM : [27 14 FB    ] Added to list of devices to link to ISY
 
Fri 10/31/2014 11:28:40 AM : [27 14 FB 0  ] Failed to add device, reason 9
 
Fri 10/31/2014 11:28:40 AM : [All         ] Writing 0 bytes to devices
Edited by mrbudin
  • 2 weeks later...
Posted

I can not add most of my insteon RF-only (None dual band) devices such as: Motion Sensor, Remote Linc, LED Bulb.

 

Every time it happens "Can not add insteon engine"

 

Very frustrated

Posted (edited)

Run Tools | Diagnostics | Event Viewer at LEVEL 3.

 

Follow steps in post 2, attempt to add Motion Sensor. Post the event trace.

 

Be sure event trace is set for LEVEL 3. Below is from the previous trace which was not at LEVEL 3. Note the 25 second gap in trace where the LEVEL 3 information should be.

 

Fri 10/31/2014 11:25:19 AM : [27 17 6 ] Added to list of devices to link to ISY

 

Fri 10/31/2014 11:25:44 AM : [27 17 6 0 ] Failed to add device, reason 9

 

Click Help | About

 

What is displayed for Firmware?

 

What is displayed for UI?

Edited by LeeG
Posted (edited)

My ISY 994i information

 

Firmware: 4.2.17

UI: 4.2.17

PLM: v9C

 

 

 

 

 

Here are the error code:

 

 

Mon 11/10/2014 10:03:22 PM : [27 17 6     ] Added to list of devices to link to ISY
 
Mon 11/10/2014 10:03:22 PM : [iNST-TX-I1  ] 02 62 27 17 06 0F 0D 00
 
Mon 11/10/2014 10:03:22 PM : [iNST-ACK    ] 02 62 27.17.06 0F 0D 00 06                 (00)
 
Mon 11/10/2014 10:03:22 PM : [iNST-SRX    ] 02 50 27.17.06 2B.50.EA 2B 0D 02           (02)
 
Mon 11/10/2014 10:03:22 PM : [std-Direct Ack] 27.17.06-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
 
Mon 11/10/2014 10:03:22 PM : [iNST-TX-I1  ] 02 62 27 17 06 0F 10 00
 
Mon 11/10/2014 10:03:22 PM : [iNST-ACK    ] 02 62 27.17.06 0F 10 00 06          ID-REQ (00)
 
Mon 11/10/2014 10:03:23 PM : [iNST-SRX    ] 02 50 27.17.06 2B.50.EA 2F 10 00    ID-REQ (00)
 
Mon 11/10/2014 10:03:23 PM : [std-Direct Ack] 27.17.06-->ISY/PLM Group=0, Max Hops=3, Hops Left=3
 
Mon 11/10/2014 10:03:23 PM : [iNST-SRX    ] 02 50 27.17.06 00.12.37 87 02 15           (15)
 
Mon 11/10/2014 10:03:23 PM : [std-Broadcast] 27.17.06-->00.12.37, Max Hops=3, Hops Left=1
 
Mon 11/10/2014 10:03:23 PM : [27 17 6 0   ] Calibrating engine version
 
Mon 11/10/2014 10:03:23 PM : [iNST-TX-I2CS] 02 62 27 17 06 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0
 
Mon 11/10/2014 10:03:32 PM : [iNST-TX-I2CS] 02 62 27 17 06 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0
 
Mon 11/10/2014 10:03:32 PM : [iNST-ACK    ] 02 62 27.17.06 1F 2F 00 00 00 00 00 01 00 00 00 00 02 62 27 17 06 1F        (00)
 
Mon 11/10/2014 10:03:33 PM : [iNST-SRX    ] 02 50 27.17.06 2B.50.EA 2F 2F 00           (00)
 
Mon 11/10/2014 10:03:33 PM : [std-Direct Ack] 27.17.06-->ISY/PLM Group=0, Max Hops=3, Hops Left=3
 
Mon 11/10/2014 10:03:33 PM : [iNST-DUP    ] Previous message ignored.
 
Mon 11/10/2014 10:03:42 PM : [iNST-TX-I2CS] 02 62 27 17 06 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0
 
Mon 11/10/2014 10:03:42 PM : [iNST-ACK    ] 02 62 27.17.06 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06        (00)
 
Mon 11/10/2014 10:03:42 PM : [iNST-SRX    ] 02 50 27.17.06 2B.50.EA 2F 2F 00           (00)
 
Mon 11/10/2014 10:03:42 PM : [std-Direct Ack] 27.17.06-->ISY/PLM Group=0, Max Hops=3, Hops Left=3
 
Mon 11/10/2014 10:03:46 PM : [27 17 6 0   ] Failed to add device, reason 9
 
Mon 11/10/2014 10:03:46 PM : [All         ] Writing 0 bytes to devices
Edited by mrbudin
Posted (edited)

The attempt to add an 8 Scene RemoteLinc 2 failed to receive an Extended message showing size/location of the device link database. The Red message below is missing from your trace.

Sun 11/09/2014 07:45:19 AM : [iNST-TX-I2CS] 02 62 29 DB A2 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0
Sun 11/09/2014 07:45:19 AM : [iNST-ACK ] 02 62 29.DB.A2 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00)
Sun 11/09/2014 07:45:20 AM : [iNST-SRX ] 02 50 29.DB.A2 0F.D6.5E 27 2F 00 (00)
Sun 11/09/2014 07:45:20 AM : [std-Direct Ack] 29.DB.A2-->ISY/PLM Group=0, Max Hops=3, Hops Left=1

THIS MESSAGE WAS NOT RECEIVED. 
Sun 11/09/2014 07:45:20 AM : [iNST-ERX ] 02 51 29 DB A2 0F D6 5E 11 2F 00 00 01 0F FF 00 AA 00 0F D6 5E FE 1C 01 BA

Sun 11/09/2014 07:45:20 AM : [Ext-Direct ] 29.DB.A2-->ISY/PLM Group=0, Max Hops=1, Hops Left=0
Sun 11/09/2014 07:45:20 AM : [29 DB A2 0 ] Using Database Link Table offset 0x0FF8 (reported 0x0FF8)


Was the V.9C PLM obtained from Smarthome recently?

Edited by LeeG
Posted (edited)

Was the V.9C PLM obtained from Smarthome recently?

 

Yes, i've purchase this PLM since september.

Edited by mrbudin
Guest
This topic is now closed to further replies.

×
×
  • Create New...