How do I add the hidden door sensor?

edokid · September 11, 2014

Been trying with no luck for an hour to add it to the ISY994. I had them linked previously to the Insteon Hub which I did by using auto detect with no issue. I understand the ISY can't auto detect it so I have to add it manually but it just never works. I type the device name, put it into linking mode, but nothing happens. I did a factory reset but no go.

The device name is 2B.32.DE and when I add it as an Insteon device, it pops up properly as INSTEON Hidden Door Sensor, but then it shows a box that says:

Add Failed 2B.32.DE INSTEON Hidden Door Sensor

Adding 25.E3.2F

I have no idea what 25.E3.2F is but it always pops up. I'm also checking the option to Add devices found in links and remove existing links.

A box then pops up devices could not be added. 2B.32.DE Hidden Door Sensor Cannot add Insteon Device. 25.E3.2F Cannot determine Insteon Engine.

If I pick the first option, Remove existing links, it pops up a window then immediately says Cannot add Insteon device.

I have 2 of these door sensors and neither will work. They worked fine with the Hub, so I'm at a loss. All my other devices added without issue, not sure what else to do!

LeeG · September 11, 2014

Run Tools | Diagnostics | Event Viewer at LEVEL 3.

Use New INSTEON Device. Enter the Insteon address of the Hidden Door Sensor, Name of device, Auto Discover, use the top option Remove existing links.

Put the Hidden Door Sensor into link mode, place it near the ISY PLM, click Ok.

If it does not add successfully post the Event Trace.

PurdueGuy · September 11, 2014

I have been emailing with Steve about this. I can't get mine added to 4.2.10. I had it added once for testing (not sure which firmware), thought I was giving it away so I deleted it, then got it back. So no amount of trying gets it added.

I have factory reset the device multiple times, been close to ISY/PLM (comms seem fine), and rebooted the PLM, and ISY. Here is the event trace. The line that has "INST-ERX" is where something bad happens and it gives up. It does get far enough to see that it is a v.43 Hidden Door Sensor.

I have added by going to:

Link Management -> Link a sensor -> Hidden Door Sensor

Link Management -> New Insteon Device

(both selecting from the drop down and letting ISY auto determine the device type).

I did a screen recording while adding it:

https://www.dropbox.com/s/64vopo76d01fbvw/Isy_FailToAdd_B.mov?dl=0

Wed 09/10/2014 10:33:07 PM : [2B 2F 99    ] Added to list of devices to link to ISY
Wed 09/10/2014 10:33:07 PM : [INST-TX-I1  ] 02 62 2B 2F 99 0F 0D 00
Wed 09/10/2014 10:33:07 PM : [INST-ACK    ] 02 62 2B.2F.99 0F 0D 00 06                 (00)
Wed 09/10/2014 10:33:08 PM : [INST-SRX    ] 02 50 2B.2F.99 24.1C.5A 2B 0D 02           (02)
Wed 09/10/2014 10:33:08 PM : [Std-Direct Ack] 2B.2F.99-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Wed 09/10/2014 10:33:08 PM : [INST-TX-I1  ] 02 62 2B 2F 99 0F 10 00
Wed 09/10/2014 10:33:08 PM : [INST-ACK    ] 02 62 2B.2F.99 0F 10 00 06          ID-REQ (00)
Wed 09/10/2014 10:33:09 PM : [INST-SRX    ] 02 50 2B.2F.99 24.1C.5A 2B 10 00    ID-REQ (00)
Wed 09/10/2014 10:33:09 PM : [Std-Direct Ack] 2B.2F.99-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Wed 09/10/2014 10:33:09 PM : [INST-SRX    ] 02 50 2B.2F.99 10.11.43 8B 02 11           (11)
Wed 09/10/2014 10:33:09 PM : [Std-Broadcast] 2B.2F.99-->10.11.43, Max Hops=3, Hops Left=2
Wed 09/10/2014 10:33:09 PM : [2B 2F 99 0  ] Calibrating engine version
Wed 09/10/2014 10:33:09 PM : [INST-TX-I2CS] 02 62 2B 2F 99 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0
Wed 09/10/2014 10:33:09 PM : [INST-ACK    ] 02 62 2B.2F.99 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06        (00)
Wed 09/10/2014 10:33:09 PM : [INST-SRX    ] 02 50 2B.2F.99 24.1C.5A 2B 2F 00           (00)
Wed 09/10/2014 10:33:09 PM : [Std-Direct Ack] 2B.2F.99-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Wed 09/10/2014 10:33:09 PM : [INST-ERX    ] 02 51 2B 2F 99 24 1C 5A 11 2F 00 00 01 0F FF 01 00 00 00 00 00 00 00 00 C1 
Wed 09/10/2014 10:33:09 PM : [Ext-Direct  ] 2B.2F.99-->ISY/PLM Group=0, Max Hops=1, Hops Left=0
Wed 09/10/2014 10:33:09 PM : [2B 2F 99 0  ] Using Database Link Table offset 0x0FF8 (reported 0x0FF8)
Wed 09/10/2014 10:33:10 PM : [2B 2F 99 0  ] Failed to add device, reason 1
Wed 09/10/2014 10:33:10 PM : [All         ] Writing 0 bytes to devices

PurdueGuy · September 11, 2014

I just re-read your first message, and notice that you also had it previously linked to something. I wonder if the door sensor firmware has a bug, and is ignoring these new link requests. I'll see if I can dig up my developer documentation and see what the "INST-ERX" message is.

LeeG · September 11, 2014

PurdueGuy

The device is presenting the wrong device type information for a Hidden Door Sensor. It is passing back 02 11. the device type for a Hidden Door Sensor is 10 11

Bad analysis. Both devices are reporting the correct device type (in blue)

Wed 09/10/2014 10:33:08 PM : [INST-TX-I1 ] 02 62 2B 2F 99 0F 10 00
Wed 09/10/2014 10:33:08 PM : [INST-ACK ] 02 62 2B.2F.99 0F 10 00 06   ID-REQ (00)
Wed 09/10/2014 10:33:09 PM : [INST-SRX ] 02 50 2B.2F.99 24.1C.5A 2B 10 00   ID-REQ (00)
Wed 09/10/2014 10:33:09 PM : [Std-Direct Ack] 2B.2F.99-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Wed 09/10/2014 10:33:09 PM : [INST-SRX ] 02 50 2B.2F.99 10.11.43 8B 02 11     (11)

This is a trace of one of my Hidden Door Sensors. It does not have the right information either but is different from yours.

Thu 09/11/2014 02:15:58 AM : [iNST-ACK ] 02 62 2B.09.AE 0F 10 00 06 ID-REQ (00)

Thu 09/11/2014 02:15:58 AM : [iNST-SRX ] 02 50 2B.09.AE 22.80.0B 2B 10 00 ID-REQ (00)

Thu 09/11/2014 02:15:58 AM : [std-Direct Ack] 2B.09.AE-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

Thu 09/11/2014 02:15:58 AM : [iNST-SRX ] 02 50 2B.09.AE 10.11.43 8B 02 00 (00)

Thu 09/11/2014 02:15:58 AM : [std-Broadcast] 2B.09.AE-->10.11.43, Max Hops=3, Hops Left=2

It appears Smartlabs changed the device type response to something that is still not correct but different from what the ISY is expecting from the Hidden Door Sensor

The INST-ERX response is correct. It shows the link database ending at 0FFF which is the correct value.

PurdueGuy · September 11, 2014

It's so strange that it added once. I did switch it to a 2-node config. I wonder if that has something to do with it?

I am almost done decoding the messages, but I disagree on what the sensor is reporting.

My trace has:

Wed 09/10/2014 10:33:09 PM : [iNST-SRX ] 02 50 2B.2F.99 10.11.43 8B 02 11 (11)

The items in red mean category 0x10, subcategory 0x11, version 0x43, which is all correct.

The message decodes as:



Wed 09/10/2014 10:33:09 PM : [INST-SRX    ] 02 50 2B.2F.99 10.11.43 8B 02 11           (11)

Wed 09/10/2014 10:33:09 PM : [Std-Broadcast] 2B.2F.99-->10.11.43, Max Hops=3, Hops Left=2

02        = Start

50        = INSTEON standard message receive

2B.2F.99  = From (Hidden Door Sensor)

10.11.43  = To (Cat = 0x10, Subcat = 0x11, Version = 0x43)

8B        = Message Flags (100 0 10 11 = Broadcast, Standard, 2 hops remaining, 3 hops max))

02        = Controller Only

11        = Hardware version

I'll post the entire decoded trace when I'm done.

LeeG · September 11, 2014

You are absolutely correct. I was looking at the wrong bytes, Both Hidden Door Sensors are reporting 10.11 with v43 firmware.

What level UI are you running?

PurdueGuy · September 11, 2014

I'm running 4.2.10 UI and firmware.

As promised, here is my parsing of the trace.

Everything looks good, until the sensor responds with an empty first ALDB record. Perhaps ISY doesn't lime the empty record?

I'm also curious why the record address is 0x0FFF, and ISY says "Using Database Link Table offset 0x0FF8." I guess that could mean it will start at 0x0FF8 and continue for 8 bytes to 0x0FFF (ISY uses the lower byte to address, and the device uses the upper byte to address).

DoorSensor_FailToAdd.txt

LeeG · September 11, 2014

The 0FFF is the ending byte with 0FF8 the start of the last physical link record which is the first logical link record. Each new link record is added at the next lower address( -8 ).

The 8 zeros for the link record is the result of a factory reset. Nothing wrong with that. I'm running 4.2.10 as well and have no issues adding the door sensor. Very strange.

PurdueGuy · September 11, 2014

OK, that's what I was leaning towards.

I find it odd that I could add it before, delete it, and not re-add it.

Got an extra sensor that you can add, delete, and re-add? :-)

LeeG · September 11, 2014

Here is another Hidden Door Sensor. Both door sensors were Deleted and added back. There is more trace available. I posted to the point where link records were being added

Thu 09/11/2014 03:35:04 AM : [2b 9 59 ] Added to list of devices to link to ISY

Thu 09/11/2014 03:35:04 AM : [iNST-TX-I1 ] 02 62 2B 09 59 0F 0D 00

Thu 09/11/2014 03:35:04 AM : [iNST-ACK ] 02 62 2B.09.59 0F 0D 00 06 (00)

Thu 09/11/2014 03:35:04 AM : [iNST-SRX ] 02 50 2B.09.59 22.80.0B 2B 0D 02 (02)

Thu 09/11/2014 03:35:04 AM : [std-Direct Ack] 2B.09.59-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

Thu 09/11/2014 03:35:04 AM : [iNST-TX-I1 ] 02 62 2B 09 59 0F 10 00

Thu 09/11/2014 03:35:04 AM : [iNST-ACK ] 02 62 2B.09.59 0F 10 00 06 ID-REQ (00)

Thu 09/11/2014 03:35:05 AM : [iNST-SRX ] 02 50 2B.09.59 22.80.0B 2B 10 00 ID-REQ (00)

Thu 09/11/2014 03:35:05 AM : [std-Direct Ack] 2B.09.59-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

Thu 09/11/2014 03:35:05 AM : [iNST-SRX ] 02 50 2B.09.59 10.11.43 8B 02 00 (00)

Thu 09/11/2014 03:35:05 AM : [std-Broadcast] 2B.09.59-->10.11.43, Max Hops=3, Hops Left=2

Thu 09/11/2014 03:35:05 AM : [2B 9 59 0 ] Calibrating engine version

Thu 09/11/2014 03:35:05 AM : [iNST-TX-I2CS] 02 62 2B 09 59 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0

Thu 09/11/2014 03:35:05 AM : [iNST-ACK ] 02 62 2B.09.59 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00)

Thu 09/11/2014 03:35:06 AM : [iNST-SRX ] 02 50 2B.09.59 22.80.0B 2B 2F 00 (00)

Thu 09/11/2014 03:35:06 AM : [std-Direct Ack] 2B.09.59-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

Thu 09/11/2014 03:35:06 AM : [iNST-ERX ] 02 51 2B 09 59 22 80 0B 11 2F 00 00 01 0F FF 01 E2 01 22 80 0B 01 00 01 2F

Thu 09/11/2014 03:35:06 AM : [Ext-Direct ] 2B.09.59-->ISY/PLM Group=0, Max Hops=1, Hops Left=0

Thu 09/11/2014 03:35:06 AM : [2B 9 59 0 ] Using Database Link Table offset 0x0FF8 (reported 0x0FF8)

Thu 09/11/2014 03:35:06 AM : [2B 9 59 1 ] Start : Adding device to ISY

Thu 09/11/2014 03:35:06 AM : [2B 9 59 1 ] Finish : Adding device to ISY was Successful

Thu 09/11/2014 03:35:06 AM : [2B 9 59 1 ] Link 0 : 0FF8 [E20122800B010001] Saving [E20122800B010001]

Thu 09/11/2014 03:35:06 AM : [iNST-TX-I2CS] 02 62 2B 09 59 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2

Thu 09/11/2014 03:35:06 AM : [iNST-ACK ] 02 62 2B.09.59 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 06 (00)

Thu 09/11/2014 03:35:07 AM : [iNST-SRX ] 02 50 2B.09.59 22.80.0B 2B 2E 00 (00)

Thu 09/11/2014 03:35:07 AM : [std-Direct Ack] 2B.09.59-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

Thu 09/11/2014 03:35:07 AM : [iNST-ERX ] 02 51 2B 09 59 22 80 0B 1B 2E 00 01 01 01 57 00 FF 40 00 00 00 00 00 00 D2

PurdueGuy · September 11, 2014

The only different is the first ALDB record. Since I factory reset mine, it is set to all zeros.

Your's still has a link to your PLM.

I had factory reset mine between delete and re-add.

Mine should be ok...the "in use" bit is 0, and the "high-water mark" is 0, so that means an empty ALDB, as you'd expect.

I guess it's bedtime here. :shock:

LeeG · September 11, 2014

I factory reset before adding the Hidden Door Sensor back to the ISY

Thu 09/11/2014 04:36:23 AM : [2b 9 59 ] Added to list of devices to link to ISY

Thu 09/11/2014 04:36:23 AM : [iNST-TX-I1 ] 02 62 2B 09 59 0F 0D 00

Thu 09/11/2014 04:36:23 AM : [iNST-ACK ] 02 62 2B.09.59 0F 0D 00 06 (00)

Thu 09/11/2014 04:36:23 AM : [iNST-SRX ] 02 50 2B.09.59 22.80.0B 2B 0D 02 (02)

Thu 09/11/2014 04:36:23 AM : [std-Direct Ack] 2B.09.59-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

Thu 09/11/2014 04:36:23 AM : [iNST-TX-I1 ] 02 62 2B 09 59 0F 10 00

Thu 09/11/2014 04:36:23 AM : [iNST-ACK ] 02 62 2B.09.59 0F 10 00 06 ID-REQ (00)

Thu 09/11/2014 04:36:23 AM : [iNST-SRX ] 02 50 2B.09.59 22.80.0B 2B 10 00 ID-REQ (00)

Thu 09/11/2014 04:36:23 AM : [std-Direct Ack] 2B.09.59-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

Thu 09/11/2014 04:36:24 AM : [iNST-SRX ] 02 50 2B.09.59 10.11.43 8B 02 00 (00)

Thu 09/11/2014 04:36:24 AM : [std-Broadcast] 2B.09.59-->10.11.43, Max Hops=3, Hops Left=2

Thu 09/11/2014 04:36:24 AM : [2B 9 59 0 ] Calibrating engine version

Thu 09/11/2014 04:36:24 AM : [iNST-TX-I2CS] 02 62 2B 09 59 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0

Thu 09/11/2014 04:36:24 AM : [iNST-ACK ] 02 62 2B.09.59 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00)

Thu 09/11/2014 04:36:24 AM : [iNST-SRX ] 02 50 2B.09.59 22.80.0B 2B 2F 00 (00)

Thu 09/11/2014 04:36:24 AM : [std-Direct Ack] 2B.09.59-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

Thu 09/11/2014 04:36:24 AM : [iNST-ERX ] 02 51 2B 09 59 22 80 0B 11 2F 00 00 01 0F FF 01 00 00 00 00 00 00 00 00 C1

Thu 09/11/2014 04:36:24 AM : [Ext-Direct ] 2B.09.59-->ISY/PLM Group=0, Max Hops=1, Hops Left=0

Thu 09/11/2014 04:36:25 AM : [2B 9 59 0 ] Using Database Link Table offset 0x0FF8 (reported 0x0FF8)

Thu 09/11/2014 04:36:25 AM : [2B 9 59 1 ] Start : Adding device to ISY

Thu 09/11/2014 04:36:25 AM : [2B 9 59 1 ] Finish : Adding device to ISY was Successful

Thu 09/11/2014 04:36:25 AM : [2B 9 59 1 ] Link 0 : 0FF8 [E20122800B010001] Saving [E20122800B010001]

Thu 09/11/2014 04:36:25 AM : [iNST-TX-I2CS] 02 62 2B 09 59 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2

Thu 09/11/2014 04:36:25 AM : [iNST-ACK ] 02 62 2B.09.59 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 06 (00)

Thu 09/11/2014 04:36:26 AM : [iNST-SRX ] 02 50 2B.09.59 22.80.0B 2B 2E 00 (00)

Thu 09/11/2014 04:36:26 AM : [std-Direct Ack] 2B.09.59-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

Thu 09/11/2014 04:36:26 AM : [iNST-ERX ] 02 51 2B 09 59 22 80 0B 1B 2E 00 01 01 01 55 00 0C 40 00 00 00 00 00 00 D2

Thu 09/11/2014 04:36:26 AM : [Ext-Direct ] 2B.09.59-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

Thu 09/11/2014 04:36:26 AM : [iNST-TX-I1 ] 02 62 2B 09 59 0F 1F 00

Thu 09/11/2014 04:36:26 AM : [iNST-ACK ] 02 62 2B.09.59 0F 1F 00 06 GOF (FLAGS)

Thu 09/11/2014 04:36:27 AM : [iNST-SRX ] 02 50 2B.09.59 22.80.0B 2B 1F 01 GOF (DB-DELTA)

Thu 09/11/2014 04:36:27 AM : [std-Direct Ack] 2B.09.59-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

Thu 09/11/2014 04:36:27 AM : [2B 9 59 3 ] Start : Adding device to ISY

Thu 09/11/2014 04:36:27 AM : [2B 9 59 3 ] Finish : Adding device to ISY was Successful

Thu 09/11/2014 04:36:27 AM : [2B 9 59 3 ] Link 1 : 0FF0 [E20322800B010003] Saving [E20322800B010003]

Thu 09/11/2014 04:36:27 AM : [2B 9 59 4 ] Start : Adding device to ISY

Thu 09/11/2014 04:36:27 AM : [2B 9 59 4 ] Finish : Adding device to ISY was Successful

PurdueGuy · September 11, 2014

Your trace appears identical (except for PLM and device addresses).

In mine, it looks like ISY just gives up. I asked what "reason 1" was, but didn't get an answer.

Maybe Michel can chime in.

PurdueGuy · September 11, 2014

Oh my....why wouldn't this be more obvious in the log?!

I guess I hit the limit of a non-pro system. I deleted a test scene, and the device added without issue!

*bangs head on desk*

LeeG · September 11, 2014

At least you know why and that it is back as a device.

PurdueGuy · September 11, 2014

Thanks for all your help! I'm surprised support didn't notice that. They should add a nice up-sell message!

I had to delete a couple more things to get all the nodes.

LeeG · September 11, 2014

Your welcome. How many hours of UDI and user time would have been saved with a simple message.

larryllix · September 11, 2014

Strange that a program count limit would affect a device addition though. Am I missing something here?

MWareman · September 11, 2014

Its a link limit I believe. Removing a scene removes link records, making more available for the adding of a device.

I agree - it should be logged so its easy to spot. I hit the same issue and caused me to up to PRO a few years ago now.

edokid · September 11, 2014

Here's what the event trace shows when I add it as a new Insteon device. I'm using 4.0.5, should I update to a later version? They all seemed to be beta or something so wasn't sure if that was recommended:

Thu 09/11/2014 08:23:15 AM : [2B 32 DE ] Added to list of devices to link to ISY

Thu 09/11/2014 08:23:15 AM : [iNST-TX-I1 ] 02 62 2B 32 DE 0F 0D 00

Thu 09/11/2014 08:23:15 AM : [iNST-ACK ] 02 62 2B.32.DE 0F 0D 00 06 (00)

Thu 09/11/2014 08:23:16 AM : [iNST-SRX ] 02 50 2B.32.DE 2C.08.F8 2B 0D 02 (02)

Thu 09/11/2014 08:23:16 AM : [std-Direct Ack] 2B.32.DE-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

Thu 09/11/2014 08:23:16 AM : [iNST-TX-I1 ] 02 62 2B 32 DE 0F 10 00

Thu 09/11/2014 08:23:16 AM : [iNST-ACK ] 02 62 2B.32.DE 0F 10 00 06 ID-REQ (00)

Thu 09/11/2014 08:23:16 AM : [iNST-SRX ] 02 50 2B.32.DE 2C.08.F8 2B 10 00 ID-REQ (00)

Thu 09/11/2014 08:23:16 AM : [std-Direct Ack] 2B.32.DE-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

Thu 09/11/2014 08:23:16 AM : [iNST-SRX ] 02 50 2B.32.DE 10.11.43 8B 02 11 (11)

Thu 09/11/2014 08:23:16 AM : [std-Broadcast] 2B.32.DE-->10.11.43, Max Hops=3, Hops Left=2

Thu 09/11/2014 08:23:16 AM : [2B 32 DE 0 ] Calibrating engine version

Thu 09/11/2014 08:23:16 AM : [iNST-TX-I2CS] 02 62 2B 32 DE 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0

Thu 09/11/2014 08:23:16 AM : [iNST-ACK ] 02 62 2B.32.DE 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00)

Thu 09/11/2014 08:23:17 AM : [iNST-SRX ] 02 50 2B.32.DE 2C.08.F8 2B 2F 00 (00)

Thu 09/11/2014 08:23:17 AM : [std-Direct Ack] 2B.32.DE-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

Thu 09/11/2014 08:23:17 AM : [iNST-ERX ] 02 51 2B 32 DE 2C 08 F8 11 2F 00 00 01 0F FF 01 E2 01 25 E3 2F 03 00 00 A4

Thu 09/11/2014 08:23:17 AM : [Ext-Direct ] 2B.32.DE-->ISY/PLM Group=0, Max Hops=1, Hops Left=0

Thu 09/11/2014 08:23:17 AM : [2B 32 DE 0 ] Using Database Link Table offset 0x0FF8 (reported 0x0FF8)

Thu 09/11/2014 08:23:17 AM : [2B 32 DE 0 ] Failed to add device, reason 1

Thu 09/11/2014 08:23:17 AM : [All ] Writing 0 bytes to devices

edokid · September 11, 2014

If I choose the option Add devices found in links and remove existing links, here's that log: