Not sure if I'm dealing with bad hardware or comm issues.

[manowell]

I updated to latest firmware and UI (4.5.4) with no change in effect.

 

I had a mini remote on my pack porch fail (likely got too damp too many times), so I replaced it.  Added device in console using device address and model, then dragged it into correct scenes.  Removed the old one.

 

Now programming on the controlled device :

(2477D) Dual Band SwitchLinc Dimmer v.41

fails.  The new mini remote DOES turn the device on an off, but I've lost ramp and on levels, and program access.

 

I've moved the PLC to four different places on the property with no change in symptom.  Did a full reset on the SwitchLinc with no change in symptoms.

 

Any ideas?  and, Thanks!

 

Event log:

Fri 02/03/2017 07:36:36 PM : [All         ] Writing 63 bytes to devices
Fri 02/03/2017 07:36:36 PM : [3F B 65 1   ] Link    0 : 0FF8 [E2013C499F010001] Writing [E2013C499F010001]
Fri 02/03/2017 07:36:36 PM : [iNST-TX-I2CS] 02 62 3F 0B 65 1F 2F 00 00 02 0F FF 08 E2 01 3C 49 9F 01 00 01 B0
Fri 02/03/2017 07:36:36 PM : [iNST-ACK    ] 02 62 3F.0B.65 1F 2F 00 00 02 0F FF 08 E2 01 3C 49 9F 01 00 01 B0 06        (00)
Fri 02/03/2017 07:36:45 PM : [iNST-TX-I2CS] 02 62 3F 0B 65 1F 2F 00 00 02 0F FF 08 E2 01 3C 49 9F 01 00 01 B0
Fri 02/03/2017 07:36:45 PM : [iNST-ACK    ] 02 62 3F.0B.65 1F 2F 00 00 02 0F FF 08 E2 01 3C 49 9F 01 00 01 B0 06        (00)
Fri 02/03/2017 07:36:54 PM : [iNST-TX-I2CS] 02 62 3F 0B 65 1F 2F 00 00 02 0F FF 08 E2 01 3C 49 9F 01 00 01 B0
Fri 02/03/2017 07:36:54 PM : [iNST-ACK    ] 02 62 3F.0B.65 1F 2F 00 00 02 0F FF 08 E2 01 3C 49 9F 01 00 01 B0 06        (00)
Fri 02/03/2017 07:36:58 PM : [3F B 65 1   ] Link    0 : 0FF8 [E2013C499F010001] *Failed Writing [E2013C499F010001]
Fri 02/03/2017 07:36:58 PM : [23 C2 9B 1  ] Link    3 : 0FE0 [A2013F0B65FF1F01] Writing [A2013F0B65FF1F01]
Fri 02/03/2017 07:36:58 PM : [iNST-TX-I2CS] 02 62 23 C2 9B 1F 2F 00 00 02 0F E7 08 A2 01 3F 0B 65 FF 1F 01 60
Fri 02/03/2017 07:36:58 PM : [iNST-ACK    ] 02 62 23.C2.9B 1F 2F 00 00 02 0F E7 08 A2 01 3F 0B 65 FF 1F 01 60 06        (00)
Fri 02/03/2017 07:36:59 PM : [iNST-SRX    ] 02 50 23.C2.9B 3C.49.9F AF 2F FF           (FF)
Fri 02/03/2017 07:36:59 PM : [std-Direct Nack] 23.C2.9B-->ISY/PLM Group=0, Max Hops=3, Hops Left=3
Fri 02/03/2017 07:37:04 PM : [iNST-TX-I2CS] 02 62 23 C2 9B 1F 2F 00 00 02 0F E7 08 A2 01 3F 0B 65 FF 1F 01 60
Fri 02/03/2017 07:37:04 PM : [iNST-ACK    ] 02 62 23.C2.9B 1F 2F 00 00 02 0F E7 08 A2 01 3F 0B 65 FF 1F 01 60 06        (00)
Fri 02/03/2017 07:37:04 PM : [iNST-SRX    ] 02 50 23.C2.9B 3C.49.9F AF 2F FF           (FF)
Fri 02/03/2017 07:37:04 PM : [std-Direct Nack] 23.C2.9B-->ISY/PLM Group=0, Max Hops=3, Hops Left=3
Fri 02/03/2017 07:37:09 PM : [iNST-TX-I2CS] 02 62 23 C2 9B 1F 2F 00 00 02 0F E7 08 A2 01 3F 0B 65 FF 1F 01 60
Fri 02/03/2017 07:37:09 PM : [iNST-ACK    ] 02 62 23.C2.9B 1F 2F 00 00 02 0F E7 08 A2 01 3F 0B 65 FF 1F 01 60 06        (00)
Fri 02/03/2017 07:37:10 PM : [iNST-SRX    ] 02 50 23.C2.9B 3C.49.9F AF 2F FF           (FF)
Fri 02/03/2017 07:37:10 PM : [std-Direct Nack] 23.C2.9B-->ISY/PLM Group=0, Max Hops=3, Hops Left=3
Fri 02/03/2017 07:37:10 PM : [23 C2 9B 1  ] Link    3 : 0FE0 [A2013F0B65FF1F01] *Failed Writing [A2013F0B65FF1F01]
 

[larryllix]

In the admin console, device tree, right click and select to view the device links. After the upload completes, (you will see a 00 00 00 record) click on the compare button to check if the links installed in each device is the same as ISY thinks they should have will all the scenes and PLM connections.

 

If they disagree, try a right click and select restore on that device to correct the links.

 

Test again.

[oberkc]

When two devices are linked via scene, such as your remote and switchlinc, the PLM is not involved.  I would not expect moving it around would matter.

 

Besides the suggestion from Larryllix, it is worth double-checking the ramp rates and ON levels for the reponder device/miniremomote scene.  Within that scene, click on the mini remote button that is controller.  Do you still see the expected ramp rates and responder levels for the switch?

[manowell]

I have the little green "1011" flag next to things that need to be written.  When I choose to write the information, I get the green "Writing" flag in the same place.  When the writing completes, I have the "1011" flag again.  Does that mean the writing wasn't complete or successful?  Generally I would expect it to change to the little block of six green, blue, and red buttons.

[Techman]

I have the little green "1011" flag next to things that need to be written.  When I choose to write the information, I get the green "Writing" flag in the same place.  When the writing completes, I have the "1011" flag again.  Does that mean the writing wasn't complete or successful?  Generally I would expect it to change to the little block of six green, blue, and red buttons.

 

Put the mini remote into the linking mode then click on write updates to device.

[manowell]

And, I'm working on two different issues here.  The one I first described is my "porch kitchen dimmer" issue, I'll get back to it soon.

 

Right now I'm also chasing an issue with my mom's (Penny's) items.  I have a structure of:

 

{scene} Penny's table lamp

  {Controller} Penny's Black Chairside - A (This is a Remotelinc 2440)

  {Device} Penny's Table (this is a LampLinc BiPhyv.3A

 

Using oberkc's instructions above, when I do a [right click][diagnostics][show device link table] on the DEVICE, I get:

 

when I do a [right click][diagnostics][show device link table] on the CONTROLLER button, I get:

 

Some writing activity, then,

then no activity until I clock on the box again, then

A LOT of activity in the event viewer and progress bar, then a link table.  When I compare,

 

There is a mismatch.  When I do a RESTORE DEVICE to that same item, I follow the directions to put the batter=powered device in setup mode, hit OK, get nine items in the event viewer (level 3 messages), and it completes.  But nothing has changed.  If I compare the links again, I see the same mistmatch.

[manowell]

Put the mini remote into the linking mode then click on write updates to device.

 

To those reading and helping, this is my "Porch Kitchen" item, which was the start of the thread.

 

Techman, I swear on my [fill in valuable item] that I did that three times yesterday, and it failed.  Just now it worked perfectly.  I have no idea why, but thanks.

 

Do the mini remotes always need to be in linking mode to write with them?  The gui prompts don't call that out like it does for other remotes.

[Techman]

To those reading and helping, this is my "Porch Kitchen" item, which was the start of the thread.

 

Techman, I swear on my [fill in valuable item] that I did that three times yesterday, and it failed.  Just now it worked perfectly.  I have no idea why, but thanks.

 

Do the mini remotes always need to be in linking mode to write with them?  The gui prompts don't call that out like it does for other remotes.

 

Take a look at this thread  http://forum.universal-devices.com/topic/20511-remotelinc-2440-problems/?hl=2440

 

All battery operated devices need to be put into the linking mode in order to write updates to them. When not in the linking mode they are in the sleep mode in order to preserve the battery life. If you have more than one battery operated device then only one battery operated device should be in the linking mode at any one time.

 

If the lamplinc is still giving you problems then you might want to try doing a factory reset on it, then do a restore device.

[manowell]

Take a look at this thread  http://forum.universal-devices.com/topic/20511-remotelinc-2440-problems/?hl=2440

 

All battery operated devices need to be put into the linking mode in order to write updates to them. When not in the linking mode they are in the sleep mode in order to preserve the battery life. If you have more than one battery operated device then only one battery operated device should be in the linking mode at any one time.

 

If the lamplinc is still giving you problems then you might want to try doing a factory reset on it, then do a restore device.

 

Thanks, that helped me remember just how far out I have to move the RemoteLinc to communicate happily:  Outside, on the far side of the driveway in back.  This is caused by RF from the PLM?  At any rate, moving out there let me write changes and clear the 1011 flags.

 

I feel that the LampLinc isn't the issue, it controls fine from the console perfectly, and responds to "all on" and "all off" from the RemoteLinc just fine.  Just not the assigned button on the same RemoteLinc.

 

I've been able to read the device links a could of times and compare, there is one link mismatch.  I've still not been able to complete a successful device restore on that button.

 

This is concerning this configuration, from above:

 

{scene} Penny's table lamp

  {Controller} Penny's Black Chairside - A (This is a Remotelinc 2440)

  {Device} Penny's Table (this is a LampLinc BiPhyv.3A

[manowell]

So what causes "-200000/-5" errors, or any other -200000 error?  I did a search and there are a few thread about communications issues, but most of them seem to treand towards seeing if you have a general PLM failure, which is not what I seem to be having.

 

Can it be a failure in a node device as well?

[Techman]

So what causes "-200000/-5" errors, or any other -200000 error?  I did a search and there are a few thread about communications issues, but most of them seem to treand towards seeing if you have a general PLM failure, which is not what I seem to be having.

 

Can it be a failure in a node device as well?

 

 

What's the firmware version and date code on your PLM?

 

Do a scene test on the "Penny's table lamp" scene. That will give you a level 3 report with details.

[oberkc]

When the writing completes, I have the "1011" flag again.  Does that mean the writing wasn't complete or successful?

Yes

So what causes "-200000/-5" errors, or any other -200000 error?

The only place I can recall that defined error numbers is:

 

http://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Errors_And_Error_Messages

 

I never found it to be overly helpful.

 

Can it be a failure in a node device as well?

I never discount a device failures.  But, I have had very few.  I would tend to look elsewhere.

[manowell]

What's the firmware version and date code on your PLM?

Console says v9E, stickers on PLM say 2413S, V2.1, 1534.

 

Do a scene test on the "Penny's table lamp" scene. That will give you a level 3 report with details.

 

Sun 02/05/2017 11:59:51 AM : [GRP-RX      ] 02 61 19 13 00 15

----- Penny's table lamp Test Results -----

[Failed] Penny's table (14 3B 46 1)

[ignore] Penny's Black Chairside - A (11 C5 18 1)

----- Penny's table lamp Test Results -----

[manowell]

Yes

The only place I can recall that defined error numbers is:

 

http://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Errors_And_Error_Messages

 

I never found it to be overly helpful.

 

Well, it's something at least.  Glad I'm only seeing a couple of those.

 

When I'm having issue with a device, I'm now running the Device Links Table to compare.  I often get a -200000/-5 error while doing that.  Once I see that, am I failed for that operation?  I'm getting dialog box with two of those errors, one from a device that I'm not even working on that appears to be OK.  Once I click "OK" to close the box, nothing else seems to happen,

 

Just did a factory reset (pull button out for ten seconds, then press in until beep) on an in-wall SwitchLinc Dimmer w/Beeper, was getting the -200000/-5 error before and still am after resetting it.  Would PLM location be a factor?  It's two rooms away.  Is PLM distance a factor for ANYTHING that isn't wireless?

[oberkc]

Once I see that, am I failed for that operation?

 

 

I really don't know.  If the device responds normally, then I tend not to worry about things.  If it does not, then I start troubleshooting.  I have never found the error messages to be of much use in the troubleshooting process. 

 

The big thing, I believe, is that I don't think one can query device, perform a link check, write updates, etc.. on battery devices without first activating those devices (puts them into programming mode). 

 

Would PLM location be a factor?

 

 

My perceptions are that funny things can happen when the PLM is in a bad mood.  First, however, I would ensure that your PLM is on a good, clean circuit.  Are there lots of other electronics on that circuit?  Have you ever tried the plm on the end of a long extension cord, plugged into another circuit, to see if that helps?

[Techman]

Console says v9E, stickers on PLM say 2413S, V2.1, 1534.

 

 

Sun 02/05/2017 11:59:51 AM : [GRP-RX      ] 02 61 19 13 00 15

----- Penny's table lamp Test Results -----

[Failed] Penny's table (14 3B 46 1)

[ignore] Penny's Black Chairside - A (11 C5 18 1)

----- Penny's table lamp Test Results -----

 

The PLM was manufactured in the 34th week of 2015, it's probably OK.

 

Take the device, "Penny's table", and plug it into a circuit close to the PLM then try to query it.  If you're able to do a successful query and a restore device then  you most likely have a communications issue, if not then you might have a defective device.

 

When you do a factory restore on a device be sure to wait until the long beep stops before releasing the set button.

 

You can also try removing power from the PLM and the ISY then power up the PLM, wait about 10 seconds then power up the ISY