Jump to content

Failed to add devices (reason 3)


ENaiman

Recommended Posts

Hi,

 

I do realize this will be "another" of these posts about communication troubles and I apologize if I am asking a stupid question.

 

I have at home an Insteon Hub which has no problem talking to any of my Insteon Devices. I have recently got an ISY-994 and started to add my devices to it.

Out of about 10 Insteon devices (light bulbs, micro switches, motion detectors and plug-in modules) I was able to add only 4 to my ISY - 3x plug-in modules (2633-522) and one light bulb - all of them are added as "Unknown Device x.yy"

For all others, the majority of failures were "Cannot determine Insteon Engine" and in a couple cases was about the Link Table (reason 9)

 

I have captured the communication in the case of "Cannot determine Insteon Engine" and you can see it below here:

Fri 12/12/2014 10:31:02 PM : [27 13 b     ] Added to list of devices to link to ISY

Fri 12/12/2014 10:31:02 PM : [INST-TX-I1  ] 02 62 27 13 0B 0F 0D 00

Fri 12/12/2014 10:31:02 PM : [INST-ACK    ] 02 62 27.13.0B 0F 0D 00 06                 (00)

Fri 12/12/2014 10:31:04 PM : [INST-SRX    ] 02 50 27.13.0B 1E.A1.67 AB 0D FF           (FF)

Fri 12/12/2014 10:31:04 PM : [Std-Direct Nack] 27.13.0B-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

Fri 12/12/2014 10:31:04 PM : [INST-TX-I2CS] 02 62 27 13 0B 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6

Fri 12/12/2014 10:31:04 PM : [INST-ACK    ] 02 62 27.13.0B 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6 06 LNK-ON (01)

Fri 12/12/2014 10:31:05 PM : [INST-SRX    ] 02 50 27.13.0B 1E.A1.67 2B 09 01    LNK-ON (01)

Fri 12/12/2014 10:31:05 PM : [Std-Direct Ack] 27.13.0B-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

Fri 12/12/2014 10:31:05 PM : [LNK-BGN     ] 02 64 01 00 06 

Fri 12/12/2014 10:31:09 PM : [27 13 B 0   ] Failed to add device, reason 3

Fri 12/12/2014 10:31:09 PM : [LNK-END     ] 02 65 06 : : Unexpected, ignored (65)

I have tried several times more and the log looked fairly similar.

 

I tried to find more info about the serial communication protocol but I haven't had much success. If anyone can spare the time to have a look at the log and let me know what is wrong (a link to some info to help me understand some of this exchange would be awesome) that would be much appreciated.

 

Thank you,

 

 

 

Link to comment
Share on other sites

After pairing almost 200 devices yesterday for an upcoming job, here are some things to try.

 

1) Unplug your Smarthome hub.

2) Try to move your base of operations to a different room to pair. You might have interference in the room you're in.

3) Pair your plug-in modules first, they'll help with communications.

4) Factory reset your devices prior to pairing.

 

I'd try #1 & #3 first then #4.. then #2

 

As far as the log, tx & rx are PLM communications, srx's are good - that's the device responding.

 

(Sorry for brevity - on mobile tapatalk)

Link to comment
Share on other sites

COM's look good only required one hop. I suggest you confirm the new PLM is not plugged into a line sharing other computers / electronic.

 

Confirm proper coupling / bridging via the 4 tap beacon test outlined in the full users manual for your dual band devices.

 

How many dual band devices do you have? Keep in mind you should have hard reset all those devices prior to linking to the ISY and unplug the HUB.

 

 

Encrypted By: Phoenix Security Solutions

Link to comment
Share on other sites

Thank you all for your help.

 

I think it might be my fault in here because I never reset those devices nor I let the ISY to remove any links. Here is the reason why: I have an Insteon Hub which controls all my devices at the moment and I have configured it pretty well with schedules and stuff. I was afraid that if I let the ISY remove links then (if I couldn't get the ISY to work 100%) I won't be able to go back to my hub and have everything intact. I was afraid I had to start back from the beginning.

 

Dual-band devices there are about 4 out of 10 (all plug-in modules) and these are kinda spread throughout the house to ensure proper coverage - I can't think of having more than 8m between two of them (8m straight line but in the same straight line I have 1 light bulb and 3 micro switches). I kept in mind that every device is a repeater and I tried to have my dual band devices here and there just to keep a strong signal.

Location: the ISY is in the same place as my hub (my comms rack) and it is connected to rack's PDU so there are a few (switch, router, server) ... sharing the same power line.

I only have 1 power phase at home so there isn't any bridging issues.

 

Another thing is I live in Australia and ISY is just at the beginning here; there isn't any "official" PLM to work here and I have a modified hub to work as my PLM.

I believe that there aren't many devices (Aus/NZ) supported by ISY so far (in the discovery list I have found only two xxxx.522 devices) and that might add to the complexity.

 

@MWareman - My ISY has the latest firmware 4.2.18

 

@Mike Ippolito - done 1 and 3 in that order and I was able to link 3 out of my 5 plug-ins (they are the closest physically to my ISY); they are still "Unsupported Device 2.54" and they seem to work. It looks like what is left to me is to try another location next prior to any reset.

 

@Tekken - 5 dual bands and didn't reset any of them. The 4 beacon test - thank you, I'll check it right away.

 

 

Update:

I have changed location of the ISY and PLM and I've managed to link all plug-ins and light bulbs. Now I have 3 micro switches (2443-522) left which are giving me the same error - and they are damn close to PLM/ISY. Unfortunately these switches are inside the wall and it's not easy at all for me to reach them and reset them. How can the damn Hub reach them so easy?

 

 

 

 

Thanks again, I think some more experimentation is in order :)

Link to comment
Share on other sites

Thank you all for your help.

 

I think it might be my fault in here because I never reset those devices nor I let the ISY to remove any links. Here is the reason why: I have an Insteon Hub which controls all my devices at the moment and I have configured it pretty well with schedules and stuff. I was afraid that if I let the ISY remove links then (if I couldn't get the ISY to work 100%) I won't be able to go back to my hub and have everything intact. I was afraid I had to start back from the beginning.

 

Dual-band devices there are about 4 out of 10 (all plug-in modules) and these are kinda spread throughout the house to ensure proper coverage - I can't think of having more than 8m between two of them (8m straight line but in the same straight line I have 1 light bulb and 3 micro switches). I kept in mind that every device is a repeater and I tried to have my dual band devices here and there just to keep a strong signal.

Location: the ISY is in the same place as my hub (my comms rack) and it is connected to rack's PDU so there are a few (switch, router, server) ... sharing the same power line.

I only have 1 power phase at home so there isn't any bridging issues.

 

Another thing is I live in Australia and ISY is just at the beginning here; there isn't any "official" PLM to work here and I have a modified hub to work as my PLM.

I believe that there aren't many devices (Aus/NZ) supported by ISY so far (in the discovery list I have found only two xxxx.522 devices) and that might add to the complexity.

 

@MWareman - My ISY has the latest firmware 4.2.18

 

@Mike Ippolito - done 1 and 3 in that order and I was able to link 3 out of my 5 plug-ins (they are the closest physically to my ISY); they are still "Unsupported Device 2.54" and they seem to work. It looks like what is left to me is to try another location next prior to any reset.

 

@Tekken - 5 dual bands and didn't reset any of them. The 4 beacon test - thank you, I'll check it right away.

 

 

Update:

I have changed location of the ISY and PLM and I've managed to link all plug-ins and light bulbs. Now I have 3 micro switches (2443-522) left which are giving me the same error - and they are damn close to PLM/ISY. Unfortunately these switches are inside the wall and it's not easy at all for me to reach them and reset them. How can the damn Hub reach them so easy?

 

 

 

 

Thanks again, I think some more experimentation is in order :)

 

I believe you and another fellow has *modified* their HUB to act like a PLM for the ISY. I would be very interested in reading what the steps were to accomplish this goal. As I am sure this would be a interim fix for those wanting to use a ISY.

 

Keeping in mind a global PLM is already being worked on and expected release is 2015.

 

Having said this the HUB and other PLM devices must never be attached to a source of power which shares other electronic devices such as computers, UPS, motors, ballast, LCD, LED, Baby monitors, as many will either cause noise or suck the insteon signal from being heard / received.

 

The 4 tap beacon test will confirm you have coupled / bridged both sides of the electrical system. My apologies for using the word phase as this only applies to single phase / three phase.

 

There are no more *true* two phase in any part of the world I am aware now?

 

As you noted ( thanks for the clarification ) you should never have two controllers operating together unless you have a sure method to isolate or determine which controller will do the work.

 

If your intent is to use the ISY its highly suggested that you let it be the soul controller otherwise odd things will happen,. The end result is your confidence in any of the product will be questioned and ultimately your satisfaction will be nil.

 

If you have a wife the (WAF) (Wife Acceptance Factor) will quickly go south and you will find yourself in the dog house. None of us want to see you there!

 

You will need to decide if you want to continue to use the HUB or the ISY. This of course means you need to hard reset all devices to ensure a clean slate and no factory settings are in place. Once done, only use the ISY to add, program, and make scene creations.

 

As I noted above this all hinges on two elements that must be done, accomplished, and confirmed as so.

 

1. Bridging / Coupling

 

2. Identify all noise makers / signal suckers and filter or remove them.

 

Keep in mind all the coupling / bridging in the world will not compensate or resolve a noise maker / signal sucker environment.

Link to comment
Share on other sites

There are no more *true* two phase in any part of the world I am aware now?

 

Info only: some buildings in Philadelphia still have two-phase electric power and, possibly, some farmland. Two-phase power, BTW, is a four wire system that has two line wires and two neutral wires.

Link to comment
Share on other sites

Grrr ... bloody Windows 8 rebooting my comp to finish updating just when I was about to finish writing a long story here ... now I have to do it again...

 

@Michel Kohanim - thank you very much for your kind suggestion. I'm not really entitled to any official support because I am using a non supported PLM and I didn't want to abuse the Tech Support.

 

@Teken - I am really in love with the ISY and I did went to some lengths to have one here in Australia :)

 

I have ordered an ISY and a USB PLM :oops:  from B&H Photo Video in the US - a week later, imagine my surprise when I realized that the ISY really needs a serial PLM to work ...

Ordered another serial PLM this time and another week later I get in in the mail; it was the time for my "big experiment" - read further and have fun on me :)

 

My idea was to use a power transformer to get the 110V needed to power the PLM, but that will separate the PLM from my electrical network making any communication impossible. But what if I will use a plugin module right next to the PLM which will be able to talk to the PLM and bridge the gap to my Insteon Network via wireless (told you it will get funny)?

I did that and it didn't work and my ISY seemed to be destined to gather dust in a drawer until a proper PLM will be available ...

 

A few days later, a Google search returned a possible solution - to modify an Insteon Hub to act like a PLM for ISY.

 

Managed to get the instructions on how to do it from a kind soul which agreed to help me.

 

A few days later my friend - Google - finds somebody here in Australia selling ISYs - naturally that piqued my curiosity and one email later I find that they were doing exactly the same thing as I was preparing to do. Since their price covered the equipment cost (fitting a PLM board inside a Hub and replacing the Hub's RJ45) plus a reasonable labour cost, I decided to go ahead.

 

Two days ago I've got the modified Hub here and my second fun part began :)

 

At this point I have all but these 3 bloody micro switches working. Adding them failed exactly the same for every device - it ended up in less than 10 seconds and I have looked and looked at the Communication Log. It looks like every end responds and it's doing its job and there is only 1 attempt and that fails. I really don't know how my bloody Hub has no problems with them - everything just works, and it is plugged into the same heavily shared power outlet and dealing with the same noise ... it just works, no sweat.

 

What is really puzzling - on the same electrical circuit (fed from the same circuit breaker) as these 3 micro switches, I have also 2 Insteon Light Bulbs and I was able to add them but that doesn't help me at all. More so, the communication from the ISY reaches the micro switch directly (0 hops) and it still fails.

 

The problem in ditching the Hub for good at this point is that I don't have yet installed the iOS App to allow me to control the ISY but that might change soon. Those 3 micro switches are really the most important part.

 

I'll really start working on that in a few days and I'll start with a reset on those switches. In regard with the noise on the line, I really doubt I can do anything about that - any suggestions?

 

Thanks Gents for your patience, hope you had a funny reading :)

 

Link to comment
Share on other sites

The Hub/ISY combination fails to get a specific device response noted in Red.  The missing message has the device type and device firmware shown in Blue

 

Sat 12/13/2014 05:57:32 AM : [1c fd d5    ] Added to list of devices to link to ISY
Sat 12/13/2014 05:57:32 AM : [iNST-TX-I1  ] 02 62 1C FD D5 0F 0D 00
Sat 12/13/2014 05:57:32 AM : [iNST-ACK    ] 02 62 1C.FD.D5 0F 0D 00 06                 (00)
Sat 12/13/2014 05:57:32 AM : [iNST-SRX    ] 02 50 1C.FD.D5 22.80.0B AB 0D FF           (FF)
Sat 12/13/2014 05:57:32 AM : [std-Direct Nack] 1C.FD.D5-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Sat 12/13/2014 05:57:32 AM : [iNST-TX-I2CS] 02 62 1C FD D5 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6
Sat 12/13/2014 05:57:32 AM : [iNST-ACK    ] 02 62 1C.FD.D5 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6 06 LNK-ON (01)
Sat 12/13/2014 05:57:32 AM : [iNST-SRX    ] 02 50 1C.FD.D5 22.80.0B 2B 09 01    LNK-ON (01)
Sat 12/13/2014 05:57:32 AM : [std-Direct Ack] 1C.FD.D5-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Sat 12/13/2014 05:57:32 AM : [LNK-BGN     ] 02 64 01 00 06 
Sat 12/13/2014 05:57:33 AM : [LNK-STAT    ] 02 53 M(01) gid=00 1C.FD.D5 0700 41 
Sat 12/13/2014 05:57:33 AM : [iNST-TX-I1  ] 02 62 1C FD D5 0F 0D 00
Sat 12/13/2014 05:57:33 AM : [LNK-END     ] 02 65 06 
Sat 12/13/2014 05:57:33 AM : [std MH      ] Unexpected Ack imCmd=65 cmd1= 0xD5
Sat 12/13/2014 05:57:34 AM : [iNST-ACK    ] 02 62 1C.FD.D5 0F 0D 00 06                 (00)
Sat 12/13/2014 05:57:34 AM : [iNST-SRX    ] 02 50 1C.FD.D5 22.80.0B 2B 0D 02           (02)
Sat 12/13/2014 05:57:34 AM : [std-Direct Ack] 1C.FD.D5-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Sat 12/13/2014 05:57:38 AM : [iNST-TX-I1  ] 02 62 1C FD D5 0F 0D 00
Sat 12/13/2014 05:57:38 AM : [iNST-ACK    ] 02 62 1C.FD.D5 0F 0D 00 06                 (00)
Sat 12/13/2014 05:57:39 AM : [iNST-SRX    ] 02 50 1C.FD.D5 22.80.0B 2B 0D 02           (02)
Sat 12/13/2014 05:57:39 AM : [std-Direct Ack] 1C.FD.D5-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Sat 12/13/2014 05:57:39 AM : [iNST-TX-I1  ] 02 62 1C FD D5 0F 10 00
Sat 12/13/2014 05:57:39 AM : [iNST-ACK    ] 02 62 1C.FD.D5 0F 10 00 06          ID-REQ (00)
Sat 12/13/2014 05:57:39 AM : [iNST-SRX    ] 02 50 1C.FD.D5 22.80.0B 2B 10 00    ID-REQ (00)
Sat 12/13/2014 05:57:39 AM : [std-Direct Ack] 1C.FD.D5-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Sat 12/13/2014 05:57:39 AM : [iNST-SRX    ] 02 50 1C.FD.D5 07.00.41 8B 01 00           (00)
Sat 12/13/2014 05:57:39 AM : [std-Broadcast] 1C.FD.D5-->07.00.41, Max Hops=3, Hops Left=2
Sat 12/13/2014 05:57:39 AM : [1C FD D5 0  ] Calibrating engine version
Sat 12/13/2014 05:57:39 AM : [iNST-TX-I2CS] 02 62 1C FD D5 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0
Sat 12/13/2014 05:57:39 AM : [iNST-ACK    ] 02 62 1C.FD.D5 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06        (00)
Sat 12/13/2014 05:57:40 AM : [iNST-SRX    ] 02 50 1C.FD.D5 22.80.0B 2B 2F 00           (00)
Sat 12/13/2014 05:57:40 AM : [std-Direct Ack] 1C.FD.D5-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Sat 12/13/2014 05:57:40 AM : [iNST-ERX    ] 02 51 1C FD D5 22 80 0B 11 2F 00 01 01 0F FF 00 A2 00 22 80 0B 00 00 00 72 
Sat 12/13/2014 05:57:40 AM : [Ext-Direct  ] 1C.FD.D5-->ISY/PLM Group=0, Max Hops=1, Hops Left=0
Sat 12/13/2014 05:57:40 AM : [1C FD D5 0  ] Using Database Link Table offset 0x0FF8 (reported 0x0FF8)
Sat 12/13/2014 05:57:41 AM : [1C FD D5 1  ] Start : Adding device to ISY
Sat 12/13/2014 05:57:41 AM : [1C FD D5 1  ] Finish : Adding device to ISY was Successful
Sat 12/13/2014 05:57:41 AM : [MNG-LNK-RSP ] 02 6F 40 E2 00 1C FD D5 07 00 41 15 
Sat 12/13/2014 05:57:41 AM : [1C FD D5 1  ] Link    0 : 0FF8 [A20022800BFF1F01] Saving  [A20022800BFF1F01]
Sat 12/13/2014 05:57:41 AM : [1C FD D5 1  ] Link    1 : 0FF0 [E20122800B010001] Saving  [E20122800B010001]
Sat 12/13/2014 05:57:41 AM : [iNST-TX-I1  ] 02 62 1C FD D5 0F 1F 02
Sat 12/13/2014 05:57:41 AM : [iNST-ACK    ] 02 62 1C.FD.D5 0F 1F 02 06          GOF    (02)
Sat 12/13/2014 05:57:42 AM : [iNST-SRX    ] 02 50 1C.FD.D5 22.80.0B 2B 1F 00    GOF    (FLAGS)
Sat 12/13/2014 05:57:42 AM : [std-Direct Ack] 1C.FD.D5-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Sat 12/13/2014 05:57:42 AM : [iNST-TX-I2CS] 02 62 1C FD D5 1F 2E 00 01 00 00 33 01 00 00 00 00 00 00 00 00 9D
Sat 12/13/2014 05:57:42 AM : [iNST-ACK    ] 02 62 1C.FD.D5 1F 2E 00 01 00 00 33 01 00 00 00 00 00 00 00 00 9D 06        (00)
Sat 12/13/2014 05:57:42 AM : [iNST-SRX    ] 02 50 1C.FD.D5 22.80.0B 2B 2E 00           (00)
Sat 12/13/2014 05:57:42 AM : [std-Direct Ack] 1C.FD.D5-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Sat 12/13/2014 05:57:43 AM : [iNST-ERX    ] 02 51 1C FD D5 22 80 0B 11 2E 00 01 01 00 14 20 00 20 00 06 34 00 00 00 72 
Sat 12/13/2014 05:57:43 AM : [Ext-Direct  ] 1C.FD.D5-->ISY/PLM Group=0, Max Hops=1, Hops Left=0
Sat 12/13/2014 05:57:43 AM : [iNST-TX-I1  ] 02 62 1C FD D5 0F 1F 00
Sat 12/13/2014 05:57:43 AM : [iNST-ACK    ] 02 62 1C.FD.D5 0F 1F 00 06          GOF    (FLAGS)
Sat 12/13/2014 05:57:43 AM : [iNST-SRX    ] 02 50 1C.FD.D5 22.80.0B 2B 1F 02    GOF    (02)
Sat 12/13/2014 05:57:43 AM : [std-Direct Ack] 1C.FD.D5-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Sat 12/13/2014 05:57:43 AM : [1C FD D5 2  ] Start : Adding device to ISY
Sat 12/13/2014 05:57:43 AM : [1C FD D5 2  ] Finish : Adding device to ISY was Successful
Sat 12/13/2014 05:57:44 AM : [iNST-TX-I1  ] 02 62 1C FD D5 0F 19 01
Sat 12/13/2014 05:57:44 AM : [iNST-ACK    ] 02 62 1C.FD.D5 0F 19 01 06          LTSREQ (01)
Sat 12/13/2014 05:57:44 AM : [iNST-SRX    ] 02 50 1C.FD.D5 22.80.0B 2B 01 01           (01)
Sat 12/13/2014 05:57:44 AM : [std-Direct Ack] 1C.FD.D5-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Sat 12/13/2014 05:57:44 AM : [D2D EVENT   ] Event [1C FD D5 1] [sT] [255] uom=0 prec=-1
Sat 12/13/2014 05:57:44 AM : [  1C FD D5 1]       ST 255
Sat 12/13/2014 05:57:44 AM : [iNST-TX-I1  ] 02 62 1C FD D5 0F 19 00
Sat 12/13/2014 05:57:44 AM : [iNST-ACK    ] 02 62 1C.FD.D5 0F 19 00 06          LTSREQ (LIGHT)
Sat 12/13/2014 05:57:44 AM : [iNST-SRX    ] 02 50 1C.FD.D5 22.80.0B 2B 01 00           (00)
Sat 12/13/2014 05:57:44 AM : [std-Direct Ack] 1C.FD.D5-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Sat 12/13/2014 05:57:44 AM : [D2D EVENT   ] Event [1C FD D5 2] [sT] [0] uom=0 prec=-1
Sat 12/13/2014 05:57:44 AM : [  1C FD D5 2]       ST   0
Sat 12/13/2014 05:57:44 AM : [1C FD D5 0  ] Successfully added device
Sat 12/13/2014 05:57:45 AM : [All         ] Writing 17 bytes to devices
Sat 12/13/2014 05:57:45 AM : [1C FD D5 1  ] Link    0 : 0FF8 [A20022800BFF1F01] Writing [A20022800BFF1F01]
Sat 12/13/2014 05:57:45 AM : [iNST-TX-I2CS] 02 62 1C FD D5 1F 2F 00 00 02 0F FF 08 A2 00 22 80 0B FF 1F 01 4B
Sat 12/13/2014 05:57:45 AM : [iNST-ACK    ] 02 62 1C.FD.D5 1F 2F 00 00 02 0F FF 08 A2 00 22 80 0B FF 1F 01 4B 06        (00)
Sat 12/13/2014 05:57:46 AM : [iNST-SRX    ] 02 50 1C.FD.D5 22.80.0B 2B 2F 00           (00)
Sat 12/13/2014 05:57:46 AM : [std-Direct Ack] 1C.FD.D5-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Sat 12/13/2014 05:57:46 AM : [MNG-LNK-RSP ] 02 6F 40 E2 00 1C FD D5 07 00 41 15 
Sat 12/13/2014 05:57:46 AM : [PLM         ] Group   0 : Writing Controller Link matching [1C FD D5 1  ] Link    0 : 0FF8 [A20022800BFF1F01]
Sat 12/13/2014 05:57:46 AM : [1C FD D5 1  ] Link    1 : 0FF0 [E20122800B010001] Writing [E20122800B010001]
Sat 12/13/2014 05:57:46 AM : [iNST-TX-I2CS] 02 62 1C FD D5 1F 2F 00 00 02 0F F7 08 E2 01 22 80 0B 01 00 01 2F
Sat 12/13/2014 05:57:46 AM : [iNST-ACK    ] 02 62 1C.FD.D5 1F 2F 00 00 02 0F F7 08 E2 01 22 80 0B 01 00 01 2F 06        (00)
Sat 12/13/2014 05:57:47 AM : [iNST-SRX    ] 02 50 1C.FD.D5 22.80.0B 2B 2F 00           (00)
Sat 12/13/2014 05:57:47 AM : [std-Direct Ack] 1C.FD.D5-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Sat 12/13/2014 05:57:47 AM : [MNG-LNK-RSP ] 02 6F 41 A2 01 1C FD D5 07 00 41 15 
Sat 12/13/2014 05:57:47 AM : [PLM         ] Group   1 : Writing Responder Link matching [1C FD D5 1  ] Link    1 : 0FF0 [E20122800B010001]
Sat 12/13/2014 05:57:47 AM : [1C FD D5 1  ] Link    2 : 0FE8 [0000000000000000] Writing [00..............]
Sat 12/13/2014 05:57:47 AM : [iNST-TX-I2CS] 02 62 1C FD D5 1F 2F 00 00 02 0F EF 08 00 00 00 00 00 00 00 00 C9
Sat 12/13/2014 05:57:47 AM : [iNST-ACK    ] 02 62 1C.FD.D5 1F 2F 00 00 02 0F EF 08 00 00 00 00 00 00 00 00 C9 06        (00)
Sat 12/13/2014 05:57:48 AM : [iNST-SRX    ] 02 50 1C.FD.D5 22.80.0B 2B 2F 00           (00)
Sat 12/13/2014 05:57:48 AM : [std-Direct Ack] 1C.FD.D5-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Sat 12/13/2014 05:57:48 AM : [1C FD D5 1  ] Link    3 : 0FE0 : Writing High Water Byte
Sat 12/13/2014 05:57:48 AM : [iNST-TX-I2CS] 02 62 1C FD D5 1F 2F 00 00 00 0F E7 01 00 00 00 00 00 00 00 00 DA
Sat 12/13/2014 05:57:48 AM : [iNST-ACK    ] 02 62 1C.FD.D5 1F 2F 00 00 00 0F E7 01 00 00 00 00 00 00 00 00 DA 06        (00)
Sat 12/13/2014 05:57:49 AM : [iNST-SRX    ] 02 50 1C.FD.D5 22.80.0B 2B 2F 00           (00)
Sat 12/13/2014 05:57:49 AM : [std-Direct Ack] 1C.FD.D5-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Sat 12/13/2014 05:57:49 AM : [iNST-SRX    ] 02 50 1C.FD.D5 22.80.0B 23 2F 00           (00)
Sat 12/13/2014 05:57:49 AM : [std-Direct Ack] 1C.FD.D5-->ISY/PLM Group=0, Max Hops=3, Hops Left=0
Sat 12/13/2014 05:57:49 AM : [iNST-SRX    ] 02 50 1C.FD.D5 22.80.0B 23 2F 00           (00)
Sat 12/13/2014 05:57:49 AM : [std-Direct Ack] 1C.FD.D5-->ISY/PLM Group=0, Max Hops=3, Hops Left=0
Sat 12/13/2014 05:57:49 AM : [iNST-ERX    ] 02 51 1C FD D5 22 80 0B 11 2F 00 01 01 0F E7 20 00 00 00 00 00 00 00 00 B9 
Sat 12/13/2014 05:57:49 AM : [Ext-Direct  ] 1C.FD.D5-->ISY/PLM Group=0, Max Hops=1, Hops Left=0
Sat 12/13/2014 05:57:49 AM : [iNST-TX-I2CS] 02 62 1C FD D5 1F 2F 00 00 00 0F E7 01 00 00 00 00 00 00 00 00 DA
Sat 12/13/2014 05:57:49 AM : [iNST-ACK    ] 02 62 1C.FD.D5 1F 2F 00 00 00 0F E7 01 00 00 00 00 00 00 00 00 DA 06        (00)
Sat 12/13/2014 05:57:50 AM : [iNST-SRX    ] 02 50 1C.FD.D5 22.80.0B 2B 2F 00           (00)
Sat 12/13/2014 05:57:50 AM : [std-Direct Ack] 1C.FD.D5-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Sat 12/13/2014 05:57:50 AM : [iNST-ERX    ] 02 51 1C FD D5 22 80 0B 11 2F 00 01 01 0F E7 20 00 00 00 00 00 00 00 00 B9 
Sat 12/13/2014 05:57:50 AM : [Ext-Direct  ] 1C.FD.D5-->ISY/PLM Group=0, Max Hops=1, Hops Left=0
Sat 12/13/2014 05:57:50 AM : [iNST-TX-I2CS] 02 62 1C FD D5 1F 2F 00 00 02 0F E7 08 00 00 00 00 00 00 00 00 D1
Sat 12/13/2014 05:57:50 AM : [iNST-ACK    ] 02 62 1C.FD.D5 1F 2F 00 00 02 0F E7 08 00 00 00 00 00 00 00 00 D1 06        (00)
Sat 12/13/2014 05:57:51 AM : [iNST-SRX    ] 02 50 1C.FD.D5 22.80.0B 2B 2F 00           (00)
Sat 12/13/2014 05:57:51 AM : [std-Direct Ack] 1C.FD.D5-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Sat 12/13/2014 05:57:51 AM : [1C FD D5 1  ] Memory : Write dbAddr=0x4003 [0B] cmd1=0x20 cmd2=0x0B
Sat 12/13/2014 05:57:51 AM : [iNST-TX-I2CS] 02 62 1C FD D5 1F 20 0B 00 00 00 00 00 00 00 00 00 00 00 00 00 D5
Sat 12/13/2014 05:57:51 AM : [iNST-ACK    ] 02 62 1C.FD.D5 1F 20 0B 00 00 00 00 00 00 00 00 00 00 00 00 00 D5 06        (0B)
Sat 12/13/2014 05:57:51 AM : [iNST-SRX    ] 02 50 1C.FD.D5 22.80.0B 2B 20 0B           (0B)
Sat 12/13/2014 05:57:51 AM : [std-Direct Ack] 1C.FD.D5-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Link to comment
Share on other sites

@LeeG - thank you very much for providing the example. I can see exactly what you mean.

 

Guess I'll be up for some more tests soon enough :) probably I'll have to reset these switches.

That was a most excellent write up about how this conversion was done. I am sure others in s similar place may contact you directly wanting to do the same.

 

Sometimes being first blazing a trail has its ups and downs.

 

Having said this easiest thing to do is confirm are you using the latest firmware of 4.2.18? If not please update as this gives us all the same point of reference.

 

Next bring the devices not able to connect hard reset them a few times per the manual. Then being it close to the HUB / ISY combo and try again.

 

Report back success / failure and do capture the level 3 event log and post back up for LeeG for review.

 

Lastly, it might be easier to use a long extension cord and move the devices somewhere else to see if this helps.

 

This would at least reduce the amount of noise or give you some insight as to the problem.

 

 

Encrypted By: Phoenix Security Solutions

Link to comment
Share on other sites

@Teken

 

Yep - it definitely have ups and downs; the geek's kind of adrenaline rush :) It's just getting better with age :)

 

Yes, I can confirm the firmware being 4.2.18

I have already already moved the ISY/PLM closer but the PLM and switches will always be in different circuits because lights and power points always feed from different circuit breakers.

Once I put them closer, I tried again with the same results. Next I used a long chord to plug the PLM in different outlets and it was still the same until I plugged the PLM somewhere and the ISY couldn't see it; guess that was a bit too far :)

 

I will keep trying and I will definitely come back with updates in the next days.

 

Thank you for your patience and for all your help guys.

Link to comment
Share on other sites

Resetting the switches did it. They were added seconds later without trouble; they were even recognized as micro-switches (if I remember, they were on the list of supported devices) ... I'll be waiting for future firmware updates for ISY to add support for these devices on Australian market.

 

Thank you guys for your help :) now that the admin is happy, I'll have to start worrying about user's happiness :)

Link to comment
Share on other sites

Well, there is still a small issue - I cannot add any of my motion detectors. Tried everything, factory reset, moving them closer to PLM ... it failed because it couldn't get the address table.

 

Log attached

Mon 12/15/2014 05:24:53 PM : [21 53 d4    ] Added to list of devices to link to ISY

Mon 12/15/2014 05:24:53 PM : [INST-TX-I1  ] 02 62 21 53 D4 0F 0D 00

Mon 12/15/2014 05:24:53 PM : [INST-ACK    ] 02 62 21.53.D4 0F 0D 00 06                 (00)

Mon 12/15/2014 05:24:54 PM : [INST-SRX    ] 02 50 21.53.D4 1E.A1.67 2F 0D 02           (02)

Mon 12/15/2014 05:24:54 PM : [Std-Direct Ack] 21.53.D4-->ISY/PLM Group=0, Max Hops=3, Hops Left=3

Mon 12/15/2014 05:24:54 PM : [INST-TX-I1  ] 02 62 21 53 D4 0F 10 00

Mon 12/15/2014 05:24:54 PM : [INST-ACK    ] 02 62 21.53.D4 0F 10 00 06          ID-REQ (00)

Mon 12/15/2014 05:24:55 PM : [INST-SRX    ] 02 50 21.53.D4 1E.A1.67 2B 10 00    ID-REQ (00)

Mon 12/15/2014 05:24:55 PM : [Std-Direct Ack] 21.53.D4-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

Mon 12/15/2014 05:24:55 PM : [INST-SRX    ] 02 50 21.53.D4 10.05.42 87 02 00           (00)

Mon 12/15/2014 05:24:55 PM : [Std-Broadcast] 21.53.D4-->10.05.42, Max Hops=3, Hops Left=1

Mon 12/15/2014 05:24:55 PM : [21 53 D4 0  ] Calibrating engine version

Mon 12/15/2014 05:24:56 PM : [INST-TX-I2CS] 02 62 21 53 D4 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0

Mon 12/15/2014 05:24:56 PM : [INST-ACK    ] 02 62 21.53.D4 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06        (00)

Mon 12/15/2014 05:24:56 PM : [INST-SRX    ] 02 50 21.53.D4 1E.A1.67 2B 2F 00           (00)

Mon 12/15/2014 05:24:56 PM : [Std-Direct Ack] 21.53.D4-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

Mon 12/15/2014 05:25:05 PM : [INST-TX-I2CS] 02 62 21 53 D4 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0

Mon 12/15/2014 05:25:05 PM : [INST-ACK    ] 02 62 21.53.D4 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06        (00)

Mon 12/15/2014 05:25:06 PM : [INST-SRX    ] 02 50 21.53.D4 1E.A1.67 2B 2F 00           (00)

Mon 12/15/2014 05:25:06 PM : [Std-Direct Ack] 21.53.D4-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

Mon 12/15/2014 05:25:15 PM : [INST-TX-I2CS] 02 62 21 53 D4 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0

Mon 12/15/2014 05:25:15 PM : [INST-ACK    ] 02 62 21.53.D4 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06        (00)

Mon 12/15/2014 05:25:16 PM : [INST-SRX    ] 02 50 21.53.D4 1E.A1.67 2B 2F 00           (00)

Mon 12/15/2014 05:25:16 PM : [Std-Direct Ack] 21.53.D4-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

Mon 12/15/2014 05:25:20 PM : [21 53 D4 0  ] Failed to add device, reason 9

Any help is appreciated.

 

Thank you,

Link to comment
Share on other sites

The device is not responding with Extended message that shows link database location.

 

 

Sat 12/13/2014 05:57:39 AM : [1C FD D5 0  ] Calibrating engine version
Sat 12/13/2014 05:57:39 AM : [iNST-TX-I2CS] 02 62 1C FD D5 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0
Sat 12/13/2014 05:57:39 AM : [iNST-ACK    ] 02 62 1C.FD.D5 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06        (00)
Sat 12/13/2014 05:57:40 AM : [iNST-SRX    ] 02 50 1C.FD.D5 22.80.0B 2B 2F 00           (00)
Sat 12/13/2014 05:57:40 AM : [std-Direct Ack] 1C.FD.D5-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Sat 12/13/2014 05:57:40 AM : [iNST-ERX    ] 02 51 1C FD D5 22 80 0B 11 2F 00 01 01 0F FF 00 A2 00 22 80 0B 00 00 00 72 
Sat 12/13/2014 05:57:40 AM : [Ext-Direct  ] 1C.FD.D5-->ISY/PLM Group=0, Max Hops=1, Hops Left=0
Sat 12/13/2014 05:57:40 AM : [1C FD D5 0  ] Using Database Link Table offset 0x0FF8 (reported 0x0FF8)
 
Also the device is identifying itself as 10.5.42 (Cat=10 Subcat=05 Firmware=42)
 
Mon 12/15/2014 05:24:55 PM : [INST-SRX ] 02 50 21.53.D4 10.05.42 87 02 00 (00)
 
My motion sensor is indicting 10.01.41.   The firmware is one level lower than yours but it is indicating 10.01 which is the code for a 2842-222 motion sensor.   Are your motion sensors 2842-222?  
 
Mon 12/15/2014 04:57:02 AM : [iNST-TX-I1  ] 02 62 14 99 51 0F 10 00
Mon 12/15/2014 04:57:02 AM : [iNST-ACK    ] 02 62 14.99.51 0F 10 00 06          ID-REQ (00)
Mon 12/15/2014 04:57:03 AM : [iNST-SRX    ] 02 50 14.99.51 22.80.0B 2B 10 00    ID-REQ (00)
Mon 12/15/2014 04:57:03 AM : [std-Direct Ack] 14.99.51-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Mon 12/15/2014 04:57:03 AM : [iNST-SRX    ] 02 50 14.99.51 10.01.41 8B 02 01           (01)
Mon 12/15/2014 04:57:03 AM : [std-Broadcast] 14.99.51-->10.01.41, Max Hops=3, Hops Left=2
 
Link to comment
Share on other sites

That would explain the difference in Subcat number.  

 

The ISY asked the motion sensor three times for the link database location.  That information should have come back as an Extended message.  After three attempts, none of which got the expected Extended message,  the add process was terminated.   I would normally suggest a Factory Reset of motion sensor but the earlier post indicates that was already done.  The same command sequence is used to get the link database location for all devices so this sequence is not unique to a motion sensor.

 

How far from the PLM is the motion sensor. 

Link to comment
Share on other sites

Archived

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


×
×
  • Create New...