Cannot link 2477D to new ISY 994i

[aa9876]

I recently upgraded my ISY from a 99i to a 994i, partially because I had a few new devices I needed to add.

 

When I try to link my switch, I can't seem to do it.  See below for the log.  Note it is taking two hops to get there, but for some reason, the direct message near the bottom is saying Max Hops=1 while the earlier messages say Max Hops=3.  Is this normal?   Any way to get around this?

 

I should add that I have tried this on both 4.2.16 and 4.2.18.   I have also tried using the linking mode and directly adding the device by address.  

 

Thanks

 

Sun 11/09/2014 07:45:18 AM : [29 db a2    ] Added to list of devices to link to ISY

Sun 11/09/2014 07:45:18 AM : [iNST-TX-I1  ] 02 62 29 DB A2 0F 0D 00

Sun 11/09/2014 07:45:18 AM : [iNST-ACK    ] 02 62 29.DB.A2 0F 0D 00 06                 (00)

Sun 11/09/2014 07:45:19 AM : [iNST-SRX    ] 02 50 29.DB.A2 0F.D6.5E 27 0D 02           (02)

Sun 11/09/2014 07:45:19 AM : [std-Direct Ack] 29.DB.A2-->ISY/PLM Group=0, Max Hops=3, Hops Left=1

Sun 11/09/2014 07:45:19 AM : [iNST-TX-I1  ] 02 62 29 DB A2 0F 10 00

Sun 11/09/2014 07:45:19 AM : [iNST-ACK    ] 02 62 29.DB.A2 0F 10 00 06          ID-REQ (00)

Sun 11/09/2014 07:45:19 AM : [iNST-SRX    ] 02 50 29.DB.A2 0F.D6.5E 27 10 00    ID-REQ (00)

Sun 11/09/2014 07:45:19 AM : [std-Direct Ack] 29.DB.A2-->ISY/PLM Group=0, Max Hops=3, Hops Left=1

Sun 11/09/2014 07:45:19 AM : [iNST-SRX    ] 02 50 29.DB.A2 01.20.41 87 01 74           (74)

Sun 11/09/2014 07:45:19 AM : [std-Broadcast] 29.DB.A2-->01.20.41, Max Hops=3, Hops Left=1

Sun 11/09/2014 07:45:19 AM : [29 DB A2 0  ] Calibrating engine version

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

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)

Sun 11/09/2014 07:45:20 AM : [29 DB A2 0  ] Failed to add device, reason 1

Sun 11/09/2014 07:45:20 AM : [All         ] Writing 0 bytes to devices

[LeeG]

Click Help | About.

 

What is displayed for Firmware?

 

What is displayed for UI?

 

The Max Hops=3 Hops Left=1 is normal for a device on the opposite 120v leg. As long as the Hops Left=x number is consistently 1 that number is fine.

 

The Max Hops=1 Hops Left=0 is associated with an 02 51 .... Extended message that indicates link database size.

 

The failed to add, reason 1 often indicates a missing device response but that is not indicated in the trace. Hoping the Firmware and UI information provide some guidence.

 

Nice job of documenting the question.

[aa9876]

Both Firmware and UI display: 4.2.18

 

I had the same results when both were also at 4.2.16, but just did the upgrade this morning to see if that affected it--it did not.

[aa9876]

Here is the current trace:

 

Sun 11/09/2014 11:50:09 AM : [29 db a2    ] Added to list of devices to link to ISY

Sun 11/09/2014 11:50:09 AM : [iNST-TX-I1  ] 02 62 29 DB A2 0F 0D 00

Sun 11/09/2014 11:50:09 AM : [iNST-ACK    ] 02 62 29.DB.A2 0F 0D 00 06                 (00)

Sun 11/09/2014 11:50:09 AM : [iNST-SRX    ] 02 50 29.DB.A2 0F.D6.5E 27 0D 02           (02)

Sun 11/09/2014 11:50:09 AM : [std-Direct Ack] 29.DB.A2-->ISY/PLM Group=0, Max Hops=3, Hops Left=1

Sun 11/09/2014 11:50:09 AM : [iNST-TX-I1  ] 02 62 29 DB A2 0F 10 00

Sun 11/09/2014 11:50:09 AM : [iNST-ACK    ] 02 62 29.DB.A2 0F 10 00 06          ID-REQ (00)

Sun 11/09/2014 11:50:09 AM : [iNST-SRX    ] 02 50 29.DB.A2 0F.D6.5E 27 10 00    ID-REQ (00)

Sun 11/09/2014 11:50:09 AM : [std-Direct Ack] 29.DB.A2-->ISY/PLM Group=0, Max Hops=3, Hops Left=1

Sun 11/09/2014 11:50:10 AM : [iNST-SRX    ] 02 50 29.DB.A2 01.20.41 87 01 74           (74)

Sun 11/09/2014 11:50:10 AM : [std-Broadcast] 29.DB.A2-->01.20.41, Max Hops=3, Hops Left=1

Sun 11/09/2014 11:50:10 AM : [29 DB A2 0  ] Calibrating engine version

Sun 11/09/2014 11:50:10 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 11:50:10 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 11:50:10 AM : [iNST-SRX    ] 02 50 29.DB.A2 0F.D6.5E 27 2F 00           (00)

Sun 11/09/2014 11:50:10 AM : [std-Direct Ack] 29.DB.A2-->ISY/PLM Group=0, Max Hops=3, Hops Left=1

Sun 11/09/2014 11:50:11 AM : [iNST-ERX    ] 02 51 29 DB A2 0F D6 5E 11 2F 00 00 01 0F FF 00 AA 00 0F D6 5E 00 1C 01 B8 

Sun 11/09/2014 11:50:11 AM : [Ext-Direct  ] 29.DB.A2-->ISY/PLM Group=0, Max Hops=1, Hops Left=0

Sun 11/09/2014 11:50:11 AM : [29 DB A2 0  ] Using Database Link Table offset 0x0FF8 (reported 0x0FF8)

Sun 11/09/2014 11:50:11 AM : [29 DB A2 0  ] Failed to add device, reason 1

Sun 11/09/2014 11:50:11 AM : [All         ] Writing 0 bytes to devices

[LeeG]

Open a Ticket with UDI support. The information looks good. Not obvious why the ISY rejected the add.

[aa9876]

I opened a ticket.

 

Thanks so much for your help.    These types of problems are really frustrating...

[LeeG]

Any time. UDI will find the answer, they are very good. Post back when answer is known. Normally a "reason 1" fail to add is a simple comm issue but there is no indication of that in either trace.

[aa9876]

I had to add a second 2477D today into a different part of the house.   It would also not add to the ISY.  Here is the comm log from when I tried to add it:

 

Sun 11/09/2014 03:46:43 PM : [29 dc b3    ] Added to list of devices to link to ISY

Sun 11/09/2014 03:46:43 PM : [iNST-TX-I1  ] 02 62 29 DC B3 0F 0D 00

Sun 11/09/2014 03:46:43 PM : [iNST-ACK    ] 02 62 29.DC.B3 0F 0D 00 06                 (00)

Sun 11/09/2014 03:46:43 PM : [iNST-SRX    ] 02 50 29.DC.B3 0F.D6.5E 2B 0D 02           (02)

Sun 11/09/2014 03:46:43 PM : [std-Direct Ack] 29.DC.B3-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

Sun 11/09/2014 03:46:43 PM : [iNST-TX-I1  ] 02 62 29 DC B3 0F 10 00

Sun 11/09/2014 03:46:43 PM : [iNST-ACK    ] 02 62 29.DC.B3 0F 10 00 06          ID-REQ (00)

Sun 11/09/2014 03:46:44 PM : [iNST-SRX    ] 02 50 29.DC.B3 0F.D6.5E 2B 10 00    ID-REQ (00)

Sun 11/09/2014 03:46:44 PM : [std-Direct Ack] 29.DC.B3-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

Sun 11/09/2014 03:46:44 PM : [iNST-SRX    ] 02 50 29.DC.B3 01.20.41 87 01 74           (74)

Sun 11/09/2014 03:46:44 PM : [std-Broadcast] 29.DC.B3-->01.20.41, Max Hops=3, Hops Left=1

Sun 11/09/2014 03:46:44 PM : [29 DC B3 0  ] Calibrating engine version

Sun 11/09/2014 03:46:44 PM : [iNST-TX-I2CS] 02 62 29 DC B3 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0

Sun 11/09/2014 03:46:44 PM : [iNST-ACK    ] 02 62 29.DC.B3 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06        (00)

Sun 11/09/2014 03:46:45 PM : [iNST-SRX    ] 02 50 29.DC.B3 0F.D6.5E 27 2F 00           (00)

Sun 11/09/2014 03:46:45 PM : [std-Direct Ack] 29.DC.B3-->ISY/PLM Group=0, Max Hops=3, Hops Left=1

Sun 11/09/2014 03:46:45 PM : [iNST-ERX    ] 02 51 29 DC B3 0F D6 5E 11 2F 00 00 01 0F FF 00 AA 00 0F D6 5E 00 1C 01 B8 

Sun 11/09/2014 03:46:45 PM : [Ext-Direct  ] 29.DC.B3-->ISY/PLM Group=0, Max Hops=1, Hops Left=0

Sun 11/09/2014 03:46:45 PM : [29 DC B3 0  ] Using Database Link Table offset 0x0FF8 (reported 0x0FF8)

Sun 11/09/2014 03:46:45 PM : [29 DC B3 0  ] Failed to add device, reason 1

Sun 11/09/2014 03:46:45 PM : [All         ] Writing 0 bytes to devices

[Michel Kohanim]

Hi aa9876,

 

I am so very sorry for the trouble. I suspect you have reached the maximum limit of 255 nodes for your ISY. You might want to try removing a folder or a scene and retry.

 

With kind regards,

Michel

[aa9876]

Yes, this was the issue.   I was over the device limit and the upgrade to Pro solved the issue.

 

This might be a case where a better error message would be helpful.

[Teken]

Yes, this was the issue. I was over the device limit and the upgrade to Pro solved the issue.

 

This might be a case where a better error message would be helpful.

I agree with this as well. Does a reason 1 specifically mean the unit has reached its maximum link capability?

 

I ask because that stood out and given LeeG ability to read the error logs better than anyone.

 

I have to assume a reason 1 has more then one possibility?

 

 

Encrypted By: Phoenix Security Solutions

[LeeG]

That was my mistake. The base ISY supports 256 total devices/Scenes. Going past that generates reason 1 error. I remembered reason 1 as being a missing device response (which is actually reason 3 I think). I should have verified the cause of reason 1 which would have shown my memory as wrong.

[Teken]

That was my mistake. The base ISY supports 256 total devices/Scenes. Going past that generates reason 1 error. I remembered reason 1 as being a missing device response (which is actually reason 3 I think). I should have verified the cause of reason 1 which would have shown my memory as wrong.

I'm pretty sure you can be forgiven just this once!

 

 

 

 

Encrypted By: Phoenix Security Solutions

[LeeG]

Thanks. I don't think my memory is what it was at 40, 50, 60, .....