"Replace with" instructions for ToggleLinc

[yardman 49]

Hello everyone:

 

I managed to smoke one of my ToggleLinc dimmers yesterday evening. So I got the chance to use the "Replace....with" function in firmware version 2.6 on my ISY-26. If you want to read the gory details, you can visit this thread at the SH forums: http://www.techmall.com/topic.asp?TOPIC_ID=2455

 

So after wiring in the replacement TGL, I then added the it to "My Lighting". I then selected the bad device, right clicked, chose "Replace....with", and chose the replacement TGL.

 

After several minutes, the operation completed with no errors. And everything was 99% back to normal.

 

The only issues were with the Remotelinc that is a co-controller for many of the scenes of which that damaged TGL had been a part.

 

Everytime I would press a scene button on the RTL, about 5 seconds later the RTL status light would blink once. Then it would flash several times in a row, as though it were receiving collisions. This would happen repeatedly.

 

I was able to fix this by doing a "Restore Device" function on the RTL. But even this took about seven minutes, so I had to put it into linking mode twice.

 

So here are my questions/observations:

 

________________________________________

 

1) When I initially performed the "Replace....with" on the TGL, I noticed that it didn't ask me to put the RTL in linking mode. I thought this was odd, since if I was removing or adding a responder device to a scene of which the RTL was a controller, I think that it usually requires that I put the RTL in linking mode.

 

2) Is having to perform a "Restore Device" for a RTL "normal" after performing the "Replace.....with" function on one of its responder devices? Maybe the RTL is a special case. Or maybe this was an oversight?

 

3) My RTL is not only linked to Insteon devices, but also triggers my "KPL secondary cleanup programs", to turn off unwanted secondary status lights. I don't know if this played into this issue at all.

 

4) Since the RTL was never put into linking mode during the "Replace....with" function, could it still have been using the address from the old TGL in some of its links? This was my hypothesis, which is what led me to do the subsequent "Restore Device" on the RTL.

_________________________________________

 

 

Anyway, it seems that everything is back to normal now after performing those two funtions. So thanks, Michel & Chris! This was waaay less painful than having to do everything manually. The damaged TGL was part of many different scenes, so rebuilding all those scenes manually would have taken me hours.

 

Best wishes,

[Sub-Routine]

I noticed the lack of notice about the RemoteLinc when I removed a LampLinc. I did have the RemoteLinc ready so I kicked it in anyway.

 

I know if I removed the device from a scene the requester would have opened so I'm guessing the programmers missed a routine that should have called the RTL requester sub-routine.

 

I think I also missed the RTL requester when I deleted a scene that an RTL was involved in.

 

I imagine that yes, #4 is true. The RTL was looking for the dead device.

 

You may have avoided Restore Device by deleting the RTL from scenes involving the TGL and re-adding it, if that was feasable.

 

Anyway, it's pretty freakin' good how the ISY works with some of these errors, like the timeout on the RemoteLinc, isn't it?

 

Rand

[yardman 49]

 

You may have avoided Restore Device by deleting the RTL from scenes involving the TGL and re-adding it, if that was feasable.

 

Anyway, it's pretty freakin' good how the ISY works with some of these errors, like the timeout on the RemoteLinc, isn't it?

 

Rand

 

Hello Rand:

 

Actually, Restore Device on the RTL was much easier to use than removing the ToggleLinc and re-adding it. That ToggleLinc was in many of the scenes on the RTL.

 

Come to think of it, I couldn't even have removed and re-added the old TGL after doing the "Replace....with", as the old TGL appears to have had its address completely removed from the ISY. It got "vaporized" by the Replace procedure.

 

You are right about how the RTL can time-out in the middle of an ISY function, but you can put it back in link mode and the ISY never seems to miss a beat. Thanks Michel and Chris!

 

Best wishes,

[Sub-Routine]

No, no. Don't remove the ToggleLinc, R&R the RemoteLinc. Wouldn't that be easier than a Restore?

 

Anyway, I'm glad you got it fixed

 

Rand

[yardman 49]

No, no. Don't remove the ToggleLinc, R&R the RemoteLinc. Wouldn't that be easier than a Restore?

 

Anyway, I'm glad you got it fixed

 

Rand

 

Hello Rand:

 

Sorry, too many posts for me today! I misread your message. My bad!

 

No, "Removing & Re-adding" the RTL wouldn't have been easier. It and that TGL were part of many scenes together. For each scene, the RTL would be calling out different dim levels for all the members of those scenes. So going this route would have been a lot of extra work to get all the levels reprogrammed.

 

All I had to do was run the "Restore Device" command on the RTL, which took about 7 minutes and also required putting the RTL into link mode twice. But that was it.

 

My point in mentioning my need to do this is that I think the "Replace.....with" function is not yet including the RTL when it's part of the scenes in the device being replaced.

 

Come to think of it (as I recently showed n another post), you can't even find a right-menu option for doing a "Replace....with" for an RTL yet. Michel acknowledges that this is a bug. So maybe both issues are related.

 

Best wishes,

[Sub-Routine]

Hello Rand:

 

...

 

Come to think of it (as I recently showed n another post), you can't even find a right-menu option for doing a "Replace....with" for an RTL yet. Michel acknowledges that this is a bug. So maybe both issues are related.

 

Best wishes,

 

Not really a bug, only an omission with the RemoteLinc.

 

Nothing to do with ToggleLincs though.

 

Rand

[Michel Kohanim]

Hello Frank,

 

Apologies for a tardy reply and thanks so very much for finding yet another bug! Yes, indeed we forgot to put a prompt in the replace function to warn the user when the replaced node is in any scene which also has an RL. This has already been rectified and is part of the next code drop ( http://forum.universal-devices.com/viewtopic.php?p=5399 ).

 

My comments below.

 

Thanks again and with kind regards,

Michel

 

 

 

 

So here are my questions/observations:

 

1) When I initially performed the "Replace....with" on the TGL, I noticed that it didn't ask me to put the RTL in linking mode. I thought this was odd, since if I was removing or adding a responder device to a scene of which the RTL was a controller, I think that it usually requires that I put the RTL in linking mode.

Apologies ... this was an oversight on our part which has already been rectified

 

2) Is having to perform a "Restore Device" for a RTL "normal" after performing the "Replace.....with" function on one of its responder devices? Maybe the RTL is a special case. Or maybe this was an oversight?

Not normal and definitely and oversight on our part

 

3) My RTL is not only linked to Insteon devices, but also triggers my "KPL secondary cleanup programs", to turn off unwanted secondary status lights. I don't know if this played into this issue at all.

No

 

4) Since the RTL was never put into linking mode during the "Replace....with" function, could it still have been using the address from the old TGL in some of its links? This was my hypothesis, which is what led me to do the subsequent "Restore Device" on the RTL.

Yes, absolutely correct!

[yardman 49]

Hello Michel:

 

Thank you for the response and for already having the fix ready for the next drop!

 

Best wishes,