LeeG

Sorry, thought you wanted to purchase them. The UDI web site has information on the various modules. Also the UDI Wiki has a section on the optional modules.

Bring up the Admin Console. Under Help | Purchase Modules.

The Local Ramp Rate was set to 3 minutes using the correct command. Does either the "load sensing" or Set button turning on the load connected to the OutletLinc cause the load to turn on over 3 minutes? If nether what is the approx ramp rate being used. Just to confirm the Local On Level was set to 100% based on the event trace. Update: the spec's on the web sales page for the OutletLInc does not list the ability to set a Ramp Rate. The User Manual does indicate that ability. Suggest trying the manual method of double tapping the Set button to see if a Local Ramp Rate can be set that way. The technique is described in the User Guide. With the correct command being issued but not having an effect there is the possibility the device does not support that ability. The ICON Dimmers are the same way, fixed Ramp Rate.

Thanks. Sometimes devices are added specifying the actual device type which results in a v.00 firmware indication which may prevent the correct method for updating the device. Lets see what is being stored in the device. Run Tools | Diagnostics | Event Viewer with Device communications events selected. Update the On Level (applied locally) and Ramp Rate (applied locally) sliders to something different so the new values will be written to the OutletLinc and post the Event log.

What does the Admin Console show for the firmware level of the OutletLinc?

cabbage How are you turning the I/O Linc Relay On? A Direct command (which it sounds like) or as a Responder of a Scene. The I/O Linc Relay is used in one of the Momentary modes to simulate a manual garage door button press. When using Direct commands the I/O Linc Relay always turns On with an ON command. Since the relay turns Off automatically in a few seconds the OFF command performs no function. To have the I/O Linc Relay respond to the ON/OFF commands as described in the various Momentary modes the I/O Linc Relay must be linked as a Responder to a Scene and turn the Scene On/Off. Lee

Use Tools | Diagnostics | PLM Info/Status which should show PLM address, PLM firmware, and Connected. What was done to "restore devices"? Was a Restore ISY run to transfer the 26 configuration into the 99? Runs Tools | Diagnostics | Shoe PLM Links Table to verify PLM has the expected link records.

This is what the 3.1.13 Help | About should look like if running the correct Admin Code.

Go to Help | About and see what it shows for the firmware in use. There are two lines now, one says Firmware which is the level of ISY firmware and the next line says UI which is the firmware level of the Admin Console. Both should indicate 3.1.13. I think you need to switch to the URL listed in the announcement post that brings up the Admin Console specific to the 3.1.13 beta. Also need to clear the Java cache.

Sure. The 2412S was the main stay until the 2413S came along.

TJF1960 The other RL problem was with a PLM that is very aged. Turns out it had nothing to do with a 2413 and associated firmware level. Have you counted the PLM links lately. Since it worked when the RL was the only thing defined the basic parts are working. I'm wondering if there is not a set of link records in the PLM that represented the RL at one time but got corrupted somehow and are not being erased when the RL is deleted. If you can send me the file produced from a Save of the Show PLM Link Database and the address of the RL I'll see if I can find anything that looks odd. That file is very hard to analyze as all the information is in decimal. Made it easy for the programmer who implemented it but it sure makes it very difficult to use as a diagnostic tool! I sent you my email address in a PM. Lee

There is nothing in the Insteon architecture that supports enable/disable of a Controller button. Once a Controller button/paddle and related Responders have been defined in a device the operation is independent of the ISY. Various Responders could be removed from some Scenes or the Controller button removed as a Controller of a particular Scene but this would have to be done through the Admin Console rather than an ISY Program. Performing all Scene actions with ISY Programs can be done but it adds some latency to the action. Particularly the dim/bright actions are slow to stop because of the delay in issuing the Fade Stop. Takes some practice as the Stop Manual Change (Fade Stop) has to be initiated prior to where the dim/bright ramp should stop. As the homeowner you can do it with practice. Not sure a guest will handle it well. How about dedicating a RemoteLinc2 specifically for guest use.

These are exactly the Insteon messages expected from an On button/paddle press. Once the correct link records were created the rest just had to work. Basic Insteon hardware has worked this way since 2005/2006. Fri 12/02/2011 09:48:22 PM : [iNST-SRX ] 02 50 0E.58.77 00.00.01 CB 11 00 LTONRR (00) Fri 12/02/2011 09:48:22 PM : [standard-Group][0E.58.77-->Group=1] Max Hops=3, Hops Left=2 Fri 12/02/2011 09:48:22 PM : [ E 58 77 1] DON 0 Fri 12/02/2011 09:48:22 PM : [iNST-SRX ] 02 50 0E.58.77 19.75.B9 41 11 01 LTONRR (01) Fri 12/02/2011 09:48:22 PM : [standard-Cleanup][0E.58.77-->ISY/PLM Group=1] Max Hops=1, Hops Left=0 Yes, I would delete and readd each device. It is the only way I know of to be sure there is a clean environment. Once that has been done take a backup. Then create your Scenes and anything else that needs to be done and take another backup. Note the names of both files in case they are needed in the future.

TJF1960 There is another post with a similar RemoteLinc problem. Not sure about the PLM firmware level yet. Although the New INSTEON Device ran with no errors the link records were not present or not functional in the PLM. Required a PLM factory reset before the RemoteLinc would work. For whatever it may be worth. Lee

Thanks for the feedback. Glad it is working. If you have the time can you do a Tools | Diagnostics | PLM Info/Status and post the firmware of the PLM. The Insteon address of the PLM will be followed a v??/ Connected. Would like to know the v?? value. Thanks

It may be Remove at 2.8.16. UDI changed the name but I thought it was before 2.8.16. Right clicking on other than the primary node may not show Remove/Delete.

Smarthome does not reflash devices. I added a RemoteLinc to my ISY this morning and see all the status updates as each button is pressed so I don't think 3.1.13 has an issue. There is nothing to lose by doing a factory reset of the PLM ONLY. I suspect the link records are not in the PLM. That is why no state changes are noted. Now that I am under post I cannot see the beginning of the topic. Were there other devices added to the ISY that are not RF devices such that the I1 Peek/Poke would have been used for those.

I am afraid none of the Restore options are correcting the missing links. Delete and readd the SwitchLinc that triggers the Program. That should get the state changes back for that device. You can do Show Device and Show PLM after adding the SwitchLinc back and confirm the links I described before are there. These links records are Insteon hardware requirements.

Do a Show Device Links Table for the SwitchLinc that should trigger the Program. You are looking for a link record E2 01 aa bb cc xx xx xx where aa bb cc is the PLM Insteon address Then do a Show PLM Links Table and look for a link record A2 01 aa bb cc xx xx xx where aa bb cc is the SwitchLinc Insteon address If both are there run Tools | Diagnostics | Event Viewer with Device communication events select. Press the SwithLinc On paddle and post the event log. There are still missing links in the PLM if you have 29 separate devices, some of which are KeypadLincs, and there are only 29 link records in the PLM. A KeypadLinc in 6 button mode must have 5 link records for the KeypadLinc with an 8 button KeypadLinc having 8 link records for the KeypadLinc EDIT: when restoring a KeypadLinc all buttons are restored, not just one button at a time.

Are there any KeypadLincs installed? They should have a link record for each button. Deleting a Scene should remove links associated with that Scene so duplicates in individual devices should not occur. The links that should be in the PLM will be deleted but since they do not exist anyway no harm.

Michel Have not been using the v98 long enough to establish long term reliability. I switched to the v98 a few days ago when a different OP reported not being able to link a RemoteLinc2 which works fine with my v98. Also I just added a RemoteLinc using the v98 and do not see the problem Tim is having with what I think is his RemoteLinc (not RL2). Of course not everyone saw the tstat dongle problems even though several clearly existed. Lee

I believe that is a RemoteLinc, not a RemoteLinc2. The trace is showing I1 Peek/Poke to setup the RemoteLinc which is fine but would not work on a RemoteLinc2.

The variable should be an Integer variable, not a State variable. Changing a State variable in the Program causes the Program to be reevaluated when the Wait is executed.

Sorry about the cryptic question on ISY level. What ISY firmware level is currently being used and did you install 3.1.10 or 3.1.12 if running 3.1.13? EDIT: I know the initial post indicated 2.8.16 but sometimes changes are made in evolution of a problem

The Admin Console is seeing device responses from the Restore Device this time so that is good. Do a Restore Device on each device and see if that gets things back to normal. What ISY image is running and what images have been used in the past to get where you are now?