Switchlinc Dimmer (2476D) Communication Issue??

[GDavis01]

I am trying set up a Switchlinc Dimmer (2476D) with my ISY99i and it is not working!

 

Usually when I link a new unit I press the 'Start Linking' icon (from the admin console) and the box opens up waiting for the signal from the unit; then when I click on the Set button on the unit, I can see the address of the new unit behind the box; after I choose 1 of the 3 the Linking Options, the unit appears in the My Lighting section.

 

However, for this particular unit the address does not appear behind the box! Nor does the unit appear in the My Lighting section!

 

I ran the Event Viewer and below is what was recorded... The odd thing is that the ISY seems to communicate with the dimmer but there seems to be an error ([LNK-END ] 02 65 06 : : Unexpected, ignored (65))!

 

Any thoughts on what is going wrong??

 

 

Event Viewer:

 

Fri 08/17/2012 03:39:55 PM : [LNK-BGN ] 02 64 01 00 06

Fri 08/17/2012 03:40:40 PM : [iNST-SRX ] 02 50 1A.59.0D 01.19.40 87 01 00 (00)

Fri 08/17/2012 03:40:40 PM : [standard-Broadcast][1A.59.0D-->01.19.40] Max Hops=3, Hops Left=1

Fri 08/17/2012 03:40:41 PM : [LNK-STAT ] 02 53 M(01) gid=00 1A.59.0D 0119 40

Fri 08/17/2012 03:40:41 PM : Linked: Linked 1A.59.0D.00 type=01.19.40

Fri 08/17/2012 03:40:41 PM : [All ] Writing 0 bytes to devices

Fri 08/17/2012 03:40:41 PM : [LNK-BGN ] 02 64 01 00 06

Fri 08/17/2012 03:41:07 PM : [ IR] 00AA Press

Fri 08/17/2012 03:41:07 PM : [LNK-END ] 02 65 06 : : Unexpected, ignored (65)

Fri 08/17/2012 03:41:07 PM : ---- Initializing the linked devices ----

Fri 08/17/2012 03:41:07 PM : ---- All Linked Devices are now initialized ----

Fri 08/17/2012 03:41:07 PM : ---- Start: Generate Scenes from links ----

Fri 08/17/2012 03:41:07 PM : ---- End: Generate Scenes from links ----

Fri 08/17/2012 03:41:07 PM : ---- Initializing the linked devices ----

Fri 08/17/2012 03:41:07 PM : ---- All Linked Devices are now initialized ----

Fri 08/17/2012 03:41:07 PM : [VAR 2 11 ] 40

Fri 08/17/2012 03:41:08 PM : [All ] Writing 0 bytes to devices

Fri 08/17/2012 03:41:08 PM : [All ] Writing 0 bytes to devices

Fri 08/17/2012 03:42:08 PM : [VAR 2 11 ] 41

[LeeG]

The message is the result of the PLM timing out of linking mode. Not an error. The device did identify itself as Insteon address 1A.59.0D, type (cat/subcat) [01.19] which is not in the list of supported devices on 3.2.6. What is the specific device type number?

[GDavis01]

The device is a Switchlinc Dimmer (2476D)! I have many of these already setup!! I just tried to link another new device (also a Switchlinc Dimmer (2476D)) in another part of the house and I had the same message!!

[LeeG]

The [01.19] cat/subcat combination is not in the list of devices. Start Linking does not know what type of device a [01.19] is.

 

Suggest using New INSTEON Device and select one of the SwitchLinc Dimmers in the pulldown list. The PLM times out 4 minutes after clicking Start Linking which is what is generating that unexpected message. The assumption is the Finsish button would normally be clicked before the 4 minute timeout.

[Brian H]

01 19 Is a 2476D SwitchLinc Dimmer with beeper.

From what I can see in some of the stuff we get in the Developers Forums and it is not the latest Sub Cat.

It seems to be MIA in the drop down list of devices in mine also.

[GDavis01]

Isn't it a bit odd that the ISY will not recognize the type of device even though I have 10 other ones set up!

 

I just tried a few tests... I deleted one of the 2476D devices that was working previously and then pressed the Start Linking icon to relink it. It worked as it should. (I did this twice to make sure).

 

I then retried the other 2476D device and it still doesn't work. I also tried 2 other new 2476D devices and neither of them worked!

 

Below is part the Event Viewer log for the device that did work... it also shows [01.19] cat/subcat combination and yet it is recognized! It also has the [LNK-END ] 02 65 06 : : Unexpected, ignored (65) message and yet it works!!

 

I'm confused!

 

Event Viewer:

 

Fri 08/17/2012 05:10:39 PM : [1A 4B 41 1 ] Link 1 : 0FF0 [6201197437FF1F01] Saving [62..............]

Fri 08/17/2012 05:10:39 PM : [MNG-LNK-RSP ] 02 6F 80 E2 00 1A 4B 41 01 19 40 06

Fri 08/17/2012 05:10:39 PM : [1A 4B 41 1 ] Start : Removing device from ISY

Fri 08/17/2012 05:10:40 PM : [1A 4B 41 1 ] Finish : Removing from ISY was Successful

Fri 08/17/2012 05:10:40 PM : [All ] Writing 0 bytes to devices

Fri 08/17/2012 05:10:54 PM : [VAR 2 11 ] 10

Fri 08/17/2012 05:11:07 PM : [LNK-BGN ] 02 64 01 00 06

Fri 08/17/2012 05:11:35 PM : [LNK-STAT ] 02 53 M(01) gid=00 1A.4B.41 0119 40

Fri 08/17/2012 05:11:35 PM : Linked: Linked 1A.4B.41.00 type=01.19.40

Fri 08/17/2012 05:11:35 PM : [iNST-TX-I1 ] 02 62 1A 4B 41 0F 0D 00

Fri 08/17/2012 05:11:35 PM : [iNST-ACK ] 02 62 1A.4B.41 0F 0D 00 06 (00)

Fri 08/17/2012 05:11:35 PM : [iNST-SRX ] 02 50 1A.4B.41 19.74.37 27 0D 01 (01)

Fri 08/17/2012 05:11:35 PM : [standard-Direct Ack][1A.4B.41-->ISY/PLM Group=0] Max Hops=3, Hops Left=1

Fri 08/17/2012 05:11:35 PM : [1A 4B 41 0 ] Calibrating engine version

Fri 08/17/2012 05:11:35 PM : [1A 4B 41 0 ] May not fully support i2, reverting to i1

Fri 08/17/2012 05:11:35 PM : [1A 4B 41 1 ] Start : Adding device to ISY

Fri 08/17/2012 05:11:35 PM : [1A 4B 41 1 ] Finish : Adding device to ISY was Successful

Fri 08/17/2012 05:11:35 PM : [All ] Writing 0 bytes to devices

Fri 08/17/2012 05:11:35 PM : [LNK-BGN ] 02 64 01 00 06

Fri 08/17/2012 05:11:59 PM : ---- Initializing the linked devices ----

Fri 08/17/2012 05:11:59 PM : [1A 4B 41 1 ] Reading all links

Fri 08/17/2012 05:11:59 PM : [LNK-END ] 02 65 06 : : Unexpected, ignored (65)

Fri 08/17/2012 05:11:59 PM : [iNST-TX-I1 ] 02 62 1A 4B 41 0F 28 0F

Fri 08/17/2012 05:12:00 PM : [iNST-ACK ] 02 62 1A.4B.41 0F 28 0F 06 SET-MSB(0F)

Fri 08/17/2012 05:12:00 PM : [iNST-SRX ] 02 50 1A.4B.41 19.74.37 27 28 0F SET-MSB(0F)

Fri 08/17/2012 05:12:00 PM : [standard-Direct Ack][1A.4B.41-->ISY/PLM Group=0] Max Hops=3, Hops Left=1

Fri 08/17/2012 05:12:00 PM : [iNST-TX-I1 ] 02 62 1A 4B 41 0F 2B F8

Fri 08/17/2012 05:12:00 PM : [iNST-ACK ] 02 62 1A.4B.41 0F 2B F8 06 PEEK (F8)

Fri 08/17/2012 05:12:01 PM : [iNST-SRX ] 02 50 1A.4B.41 19.74.37 27 2B A2 PEEK (A2)

Fri 08/17/2012 05:12:01 PM : [standard-Direct Ack][1A.4B.41-->ISY/PLM Group=0] Max Hops=3, Hops Left=1

Fri 08/17/2012 05:12:01 PM : [iNST-TX-I1 ] 02 62 1A 4B 41 0F 28 0F

Fri 08/17/2012 05:12:01 PM : [iNST-ACK ] 02 62 1A.4B.41 0F 28 0F 06 SET-MSB(0F)

Fri 08/17/2012 05:12:01 PM : [iNST-SRX ] 02 50 1A.4B.41 19.74.37 23 28 0F SET-MSB(0F)

[LeeG]

When you click on the node for 1A.4B.41 what does the ISY display for the type of device in the right pane?

 

What ISY firmware level is being used? Run | Help About and confirm Firmware and UI lines both indicate the same level.

[GDavis01]

I clicked on the node (in My Lighting) and on the right panel it shows as:

 

1A.4B.41 - (2476D) Switchlinc Dimmer W/Beeper v.40

 

I'm at version v.3.2.6 for both firmware and UI

 

Interestingly, I brought up the PLM Links Table and I can see the device that didn't work in the table, as follows:

 

0031 : E2 00 1A.59.0D 01 19 40

0032 : A2 00 1A.59.0D 01 19 40

 

Neither the Device or ISY Links Tables show that device.

[LeeG]

When I click on Start Linking and press the Set button for a SwitchLinc Dimmer w/Beeper that is already defined to the ISY I get the same type of trace you originally post with a Writing 0 bytes message. This has always indicated the device is already defined.

 

 

Fri 08/17/2012 06:29:41 PM : [LNK-BGN ] 02 64 01 00 06

 

Fri 08/17/2012 06:29:50 PM : [LNK-STAT ] 02 53 M(01) gid=00 16.3F.93 0119 38

 

Fri 08/17/2012 06:29:50 PM : Linked: Linked 16.3F.93.00 type=01.19.38

 

Fri 08/17/2012 06:29:50 PM : [All ] Writing 0 bytes to devices

 

Fri 08/17/2012 06:29:50 PM : [LNK-BGN ] 02 64 01 00 06

 

Fri 08/17/2012 06:30:00 PM : ---- Initializing the linked devices ----

 

Fri 08/17/2012 06:30:00 PM : ---- All Linked Devices are now initialized ----

 

Fri 08/17/2012 06:30:00 PM : [LNK-END ] 02 65 06 : : Unexpected, ignored (65)

 

Fri 08/17/2012 06:30:01 PM : ---- Initializing the linked devices ----

 

Fri 08/17/2012 06:30:01 PM : ---- All Linked Devices are now initialized ----

 

Fri 08/17/2012 06:30:01 PM : [All ] Writing 0 bytes to devices

 

Fri 08/17/2012 06:30:01 PM : [All ] Writing 0 bytes to devices

 

Fri 08/17/2012 06:31:18 PM : [iNST-SRX ] 02 50 1D.6C.D6 19.70.06 01 6F 26 (26)

 

Fri 08/17/2012 06:31:18 PM : [standard-Direct][1D.6C.D6-->ISY/PLM Group=0] Max Hops=1, Hops Left=0

 

I will have to pass this one on to someone else as it presents as a device that already exists.

[Michel Kohanim]

Hello GMD99,

 

If these are new SWLs, I can tell you that they must report as i2cs but they are not.

 

Do all the devices that do not work are from the same batch?

 

With kind regards,

Michel

[GDavis01]

Michel,

 

Yes the ones that do not work were all bought together. However, there are also some other ones that do work that were (I think!) bought at the same time.

 

How do I know if a device reports as i2cs or that another doesn't? Is it evident from the 2 Event Viewer logs I posted? I see the line "Fri 08/17/2012 05:11:35 PM : [1A 4B 41 0 ] May not fully support i2, reverting to i1" but this is for the device that actually works!

 

Thanks

[LeeG]

For the device that works the trace indicates an I2 device (not I2CS). The 01 indicates I2, a value of 02 or FF would indicate I2CS.

 

For the device that does not work the ISY never talked to the device beyond getting the message from the device indicating Insteon address, device type and device firmware level. The Writing 0 bytes is what is normally traced when the Insteon address is already defined to the ISY. Everything looks like the ISY already has that device address so it never progressed to the point of querying the Insteon Engine.

 

This is the trace from the device that added successfully.

 

Fri 08/17/2012 05:11:35 PM : [iNST-TX-I1 ] 02 62 1A 4B 41 0F 0D 00

Fri 08/17/2012 05:11:35 PM : [iNST-ACK ] 02 62 1A.4B.41 0F 0D 00 06 (00)

Fri 08/17/2012 05:11:35 PM : [iNST-SRX ] 02 50 1A.4B.41 19.74.37 27 0D 01 (01)

[GDavis01]

Does all of this suggest that the devices that will not link are defective?

 

If so, what would you suggest I say is the reason for returning the devices for replacements?

[LeeG]

The ISY did not communicate with the device in any way so there is no indication the device is defective. The ISY would have had to send commands to the device and it fail to respond in the expected way. In this case nothing was ever sent to the device so it had no opportunity to fail.

[LeeG]

GMD99

 

To be sure we are not dealing with two different situations, post the event trace of the other devices that will not add successfully. The first post shows the device was never sent a command so the issue Michel discussed about the wrong Insteon Engine being indicated does not apply. That does not mean the other dimmers do not have what Michel discussed.

 

Also check for address 1A.59.0D already being defined again. Everything in the very first trace indicates the ISY thinks that address is already known. The other thing that can be tried with this dimmer is use New INSTEON Device to add the dimmer. Enter the address, name, and use Auto Discover. Have the event trace running for this test and post the trace if it does not add.

[GDavis01]

Sheepishly ( ) I have to admit that it finally dawned on me what you have been saying all along… “ISY thinks that address is already knownâ€!

 

The 3 devices, that I tried to link with the ISY and thought were unsuccessful, had been previously set up and were sitting there with a different name!!!!!! No wonder the ISY knew the address!!

 

Sorry for wasting your time on this!

 

I won't pretend to understand the issue Michel raised (I2 device vs. I2CS device), but should I be concerned?

 

Thanks again...

[Brian H]

I2 Is the Insteon Extended Messaging protocol.

I2CS added a Check Sum for added message integrity but also made some older commands not work.

Should not be a problem if added with the latest 3.2.6 firmware. Could be a problem if added with older firmware that didn't know about I2CS.

[LeeG]

GMD99

 

Thanks for posting back. Better that than some new unknown problem. Brian covered the I2/I2CS differences. Is not a concern, so long as the devices are working.