Jump to content

2477D communication issue

Envirogreen

By Envirogreen
in INSTEON Communications Issues

Recommended Posts

Envirogreen Advanced

Envirogreen

Posted
Posted

I have a new 2477d.  I can do a manual link with another instead device but cannot get it to link into my ISY.

 

When I click and hold the set button it will only go to linking or unlinking mode.

 

When I try to link from within the ISY (new instead device) I get the following cannot determine instead device type.

 

Fri 09/22/2017 10:35:25 PM : [ELK         ] Connect

Fri 09/22/2017 10:35:29 PM : Start Insteon Device Linking Mode
Fri 09/22/2017 10:35:29 PM : [LNK-BGN     ] 02 64 01 00 06 
Fri 09/22/2017 10:35:35 PM : [ELK         ] Connect Failed
Fri 09/22/2017 10:35:39 PM : Stop Insteon Device Linking Mode, Final processing to follow
Fri 09/22/2017 10:35:40 PM : [LNK-END     ] 02 65 06 : : Unexpected, ignored (65)
Fri 09/22/2017 10:35:40 PM : [All         ] Writing 0 bytes to devices
Fri 09/22/2017 10:35:40 PM : [All         ] Writing 0 bytes to devices
Fri 09/22/2017 10:35:49 PM : [ELK         ] Connect
Fri 09/22/2017 10:35:59 PM : [ELK         ] Connect Failed
Fri 09/22/2017 10:36:02 PM : [45 a3 2b    ] Added to list of devices to link to ISY
Fri 09/22/2017 10:36:02 PM : [iNST-TX-I1  ] 02 62 45 A3 2B 0F 0D 00
Fri 09/22/2017 10:36:02 PM : [iNST-ACK    ] 02 62 45.A3.2B 0F 0D 00 06                 (00)
Fri 09/22/2017 10:36:03 PM : [iNST-SRX    ] 02 50 45.A3.2B 40.D2.E7 2B 0D 02           (02)
Fri 09/22/2017 10:36:03 PM : [std-Direct Ack] 45.A3.2B-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Fri 09/22/2017 10:36:03 PM : [iNST-TX-I1  ] 02 62 45 A3 2B 0F 10 00
Fri 09/22/2017 10:36:03 PM : [iNST-ACK    ] 02 62 45.A3.2B 0F 10 00 06          ID-REQ (00)
Fri 09/22/2017 10:36:03 PM : [iNST-SRX    ] 02 50 45.A3.2B 40.D2.E7 2B 10 00    ID-REQ (00)
Fri 09/22/2017 10:36:03 PM : [std-Direct Ack] 45.A3.2B-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Fri 09/22/2017 10:36:12 PM : [iNST-TX-I1  ] 02 62 45 A3 2B 0F 10 00
Fri 09/22/2017 10:36:12 PM : [iNST-ACK    ] 02 62 45.A3.2B 0F 10 00 06          ID-REQ (00)
Fri 09/22/2017 10:36:14 PM : [ELK         ] Connect
Fri 09/22/2017 10:36:21 PM : [iNST-TX-I1  ] 02 62 45 A3 2B 0F 10 00
Fri 09/22/2017 10:36:21 PM : [iNST-ACK    ] 02 62 45.A3.2B 0F 10 00 06          ID-REQ (00)
Fri 09/22/2017 10:36:22 PM : [iNST-SRX    ] 02 50 45.A3.2B 40.D2.E7 2B 10 00    ID-REQ (00)
Fri 09/22/2017 10:36:22 PM : [std-Direct Ack] 45.A3.2B-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Fri 09/22/2017 10:36:25 PM : [ELK         ] Connect Failed
Fri 09/22/2017 10:36:26 PM : [45 A3 2B 0  ] Cannot determine device type
Fri 09/22/2017 10:36:26 PM : [45 A3 2B 0  ] Failed to add device, reason 2
Fri 09/22/2017 10:36:26 PM : [All         ] Writing 0 bytes to devices
Fri 09/22/2017 10:36:39 PM : [ELK         ] Connect
Fri 09/22/2017 10:36:49 PM : [ELK         ] Connect Failed
Fri 09/22/2017 10:36:53 PM : CLI-HAMW: Connecting to api.aerisapi.com
Fri 09/22/2017 10:36:53 PM : CLI-HAMW: No Response from api.aerisapi.com
Fri 09/22/2017 10:36:53 PM : CLI-HAMW: Connecting to api.aerisapi.com
Fri 09/22/2017 10:36:53 PM : CLI-HAMW: No Response from api.aerisapi.com
Fri 09/22/2017 10:36:53 PM : CLI-HAMW: Connecting to api.aerisapi.com
Fri 09/22/2017 10:36:53 PM : CLI-HAMW: No Response from api.aerisapi.com
Fri 09/22/2017 10:37:04 PM : [ELK         ] Connect
 
 
When I try to add it and tell the device type vs auto I get cannot determine device link table address
 
Fri 09/22/2017 10:37:39 PM : [ELK         ] Connect Failed
Fri 09/22/2017 10:37:45 PM : [iNST-SRX    ] 02 50 45.A3.2B 01.20.45 83 01 00           (00)
Fri 09/22/2017 10:37:45 PM : [std-Broadcast] 45.A3.2B-->01.20.45, Max Hops=3, Hops Left=0
Fri 09/22/2017 10:37:45 PM : [iNST-DUP    ] Previous message ignored.
Fri 09/22/2017 10:37:54 PM : [ELK         ] Connect
Fri 09/22/2017 10:38:04 PM : [ELK         ] Connect Failed
Fri 09/22/2017 10:38:19 PM : [iNST-SRX    ] 02 50 40.FC.A6 40.D2.E7 46 13 01    LTOFFRR(01)
Fri 09/22/2017 10:38:19 PM : [std-Cleanup ] 40.FC.A6-->ISY/PLM Group=1, Max Hops=2, Hops Left=1
Fri 09/22/2017 10:38:19 PM : [D2D EVENT   ] Event [40 FC A6 1] [DOF] [0] uom=0 prec=-1
Fri 09/22/2017 10:38:19 PM : [  40 FC A6 1]      DOF   0
Fri 09/22/2017 10:38:19 PM : [D2D EVENT   ] Event [1D 52 8F 1] [sT] [0] uom=0 prec=-1
Fri 09/22/2017 10:38:19 PM : [  1D 52 8F 1]       ST   0
Fri 09/22/2017 10:38:19 PM : [D2D EVENT   ] Event [1C E3 7 3] [sT] [0] uom=0 prec=-1
Fri 09/22/2017 10:38:19 PM : [   1C E3 7 3]       ST   0
Fri 09/22/2017 10:38:19 PM : [D2D EVENT   ] Event [40 FC A6 1] [sT] [0] uom=0 prec=-1
Fri 09/22/2017 10:38:19 PM : [  40 FC A6 1]       ST   0
Fri 09/22/2017 10:38:19 PM : [D2D EVENT   ] Event [40 FB 21 1] [sT] [0] uom=0 prec=-1
Fri 09/22/2017 10:38:19 PM : [  40 FB 21 1]       ST   0
Fri 09/22/2017 10:38:19 PM : [ELK         ] Connect
Fri 09/22/2017 10:38:25 PM : [45 a3 2b    ] Added to list of devices to link to ISY
Fri 09/22/2017 10:38:25 PM : [iNST-TX-I1  ] 02 62 45 A3 2B 0F 0D 00
Fri 09/22/2017 10:38:25 PM : [iNST-ACK    ] 02 62 45.A3.2B 0F 0D 00 06                 (00)
Fri 09/22/2017 10:38:27 PM : [iNST-SRX    ] 02 50 45.A3.2B 40.D2.E7 27 0D 02           (02)
Fri 09/22/2017 10:38:27 PM : [std-Direct Ack] 45.A3.2B-->ISY/PLM Group=0, Max Hops=3, Hops Left=1
Fri 09/22/2017 10:38:27 PM : [iNST-TX-I1  ] 02 62 45 A3 2B 0F 10 00
Fri 09/22/2017 10:38:27 PM : [iNST-ACK    ] 02 62 45.A3.2B 0F 10 00 06          ID-REQ (00)
Fri 09/22/2017 10:38:29 PM : [ELK         ] Connect Failed
Fri 09/22/2017 10:38:36 PM : [iNST-TX-I1  ] 02 62 45 A3 2B 0F 10 00
Fri 09/22/2017 10:38:36 PM : [iNST-ACK    ] 02 62 45.A3.2B 0F 10 00 06          ID-REQ (00)
Fri 09/22/2017 10:38:36 PM : [iNST-SRX    ] 02 50 45.A3.2B 40.D2.E7 2B 10 00    ID-REQ (00)
Fri 09/22/2017 10:38:36 PM : [std-Direct Ack] 45.A3.2B-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Fri 09/22/2017 10:38:36 PM : [iNST-SRX    ] 02 50 45.A3.2B 40.D2.E7 23 10 00    ID-REQ (00)
Fri 09/22/2017 10:38:36 PM : [std-Direct Ack] 45.A3.2B-->ISY/PLM Group=0, Max Hops=3, Hops Left=0
Fri 09/22/2017 10:38:44 PM : [ELK         ] Connect
Fri 09/22/2017 10:38:45 PM : [iNST-TX-I1  ] 02 62 45 A3 2B 0F 10 00
Fri 09/22/2017 10:38:45 PM : [iNST-ACK    ] 02 62 45.A3.2B 0F 10 00 06          ID-REQ (00)
Fri 09/22/2017 10:38:49 PM : [45 A3 2B 0  ] Calibrating engine version
Fri 09/22/2017 10:38:49 PM : [iNST-TX-I2CS] 02 62 45 A3 2B 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0
Fri 09/22/2017 10:38:49 PM : [iNST-ACK    ] 02 62 45.A3.2B 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06        (00)
Fri 09/22/2017 10:38:50 PM : [iNST-SRX    ] 02 50 45.A3.2B 40.D2.E7 27 2F 00           (00)
Fri 09/22/2017 10:38:50 PM : [std-Direct Ack] 45.A3.2B-->ISY/PLM Group=0, Max Hops=3, Hops Left=1
Fri 09/22/2017 10:38:54 PM : [ELK         ] Connect Failed
Fri 09/22/2017 10:38:59 PM : [iNST-TX-I2CS] 02 62 45 A3 2B 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0
Fri 09/22/2017 10:38:59 PM : [iNST-ACK    ] 02 62 45.A3.2B 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06        (00)
Fri 09/22/2017 10:39:08 PM : [iNST-TX-I2CS] 02 62 45 A3 2B 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0
Fri 09/22/2017 10:39:08 PM : [iNST-ACK    ] 02 62 45.A3.2B 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06        (00)
Fri 09/22/2017 10:39:09 PM : [ELK         ] Connect
Fri 09/22/2017 10:39:12 PM : [45 A3 2B 0  ] Failed to add device, reason 9
Fri 09/22/2017 10:39:12 PM : [All         ] Writing 0 bytes to devices
Fri 09/22/2017 10:39:19 PM : [ELK         ] Connect Failed
Fri 09/22/2017 10:39:34 PM : [ELK         ] Connect
Fri 09/22/2017 10:39:44 PM : [ELK         ] Connect Failed
 
 
I've got about 50 instead devices all working, recently added two others devices.
 
Suggestions?
Techman Advanced

Techman

Posted
Posted

What is you ISY firmware and UI version?

 

Do a factory reset on the device then try to link it to the ISY using Link management | new Insteon device. No need to put the device into linking mode just put the device address in and use auto discover.

larryllix Advanced

larryllix

Posted
Posted

From your event records you have comm problems. Your Elk shows every second poll failed. I assume this is over Ethernet though.

 

The Insteon engine  message happens when there is a comm failure during the longer session to get all the information out of the Insteon device during first first linking to it.

 

Try again using Techman's advice above. All Insteon devices should be factory reset before usage.

Archived

This topic is now archived and is closed to further replies.

Go to topic listing
×
×
  • Create New...