LeeG

Add the responder device to the ISY Scene as a Responder.

Yes, to restoring any device that has been linked outside of the ISY. RemoteLinc2 buttons are linked to ISY Scenes the same way KeypadLinc buttons, SwitchLincs, and so on. There is nothing special about a RemoteLinc2 except it goes to sleep to save battery life. As with all battery RF devices the RemoteLinc2 must be manually put into linking mode with the Set button before any link records can be written into the RemoteLinc2. A battery device will timeout of linking mode in 4 minutes.

You have one screwed up Insteon network!!

The RemoteLinc2 is added to the ISY using New INSTEON Device, Enter the Insteon address, Name of your choice, Device Type as default Auto Discover. Be sure to manually put the Remoteinc2 into linking mode with the RemoteLinc2 Set button as required with all battery RF devices. You now have at least one link record in the responder device the ISY is not aware of. It will eventually be overlaid or deleted. Strongly recommend doing a Restore Device on the responder device to clean up the link database before adding the RemoteLinc2 button(s) as Controllers of ISY Scenes. Are there other Insteon devices being used that are not defined to the ISY?

Does the RemoteLinc2 button in the Admin Console change state when the button is pressed?

Things do not make sense. A RemoteLinc2 cannot be queried as it is asleep. Where are you seeing a Hops Left=2 if the Admin Console is not changing state? The RemoteLinc2 is restored as other Insteon devices are. Right click on the Primary node, select Restore Device. As with any RF only device it must be manually put into linking mode.

Press a RemoteLinc2 button. Same as pressing a KeypadLinc button. If state changes are not being seen either the RemoteLinc2 is not in range of a Dual Band device or there is a link record problem either in the RemoteLinc2 or the PLM.

Using the Set button with Start Linking to identify the device to the ISY is fine. That is how it is done when using Start Linking. The Set button press is not actually creating a link. The ISY creates the links as part of the Start Linking process. My comment about not using the Set button for linking is following the device Quick Start Guide and User Guide which describes using the Set button on the Controller device and Responder device to link the two devices together. That should not be done as the ISY is not aware of those links and will eventually overlay or delete them. Sorry for the confusion, I should have more explicit. Yes, add each device separately. Then Drag/Drop the device to the ISY Scene definition or right click the device node selecting Add to Scene .... Each device is added to the Scene as a Controller. There is no advantage to linking the two devices together before adding the devices to the ISY. There is additional work when done that way. The ISY will define an ISY Scene, giving a name of Scene xxx where xxx is number. The Scene name has to be renamed to be meaningful. Also if there are other links in the devices other devices can be added to the ISY or broken links can exist. Best to never Set button link outside of the ISY.

First, do not use the Set button to do linking when using an ISY. The Group Devices function has nothing to do with linking devices. When used with a KeypadLinc for example, the Secondary nodes are grouped under the Primary node regardless of the node names assigned. There will be a plus or minus sign to the left of the KPL Primary node which will expand or compress the display of the KPL nodes. To link the devices in a 3-way configuration, define one ISY Scene. Add both the switches as Controllers of the one ISY Scene. The ISY wlll cross-link the devices.

Was the PLM changed with the Pro update?

That is an unknown message type from the PLM. What type PLM (2412 or 2413) and what is the firmware level of the PLM (Tools | Diagnostics | PLM Info/Status).

I suspect there is something in the device definition that has gotten corrupted. The Replace xxx with... changes the Insteon address in the old definition which is why the new KPL worked until the old configuration was used with the new address. The only thing I can think to try is to delete the KPL definition altogether. That will be a pain getting the links back for sure being a KPL. Could open a Ticket with UDI Tech Support to see if they have information about the Platform error message and this symptom. We are coming up on the 4 month mark since a new ISY image has been released. Could be this issue is known. Note that when the Hops Left count is moving around, sometimes 2, sometimes 1 or 0, there is some comm issue. It is not causing the current issue but is something to look into as time allows.

There were no commands issued in the posted event trace so not the case of the command failing. EDIT: the command in one of the earlier event traces is the Query Insteon Engine. The toggle mode change did not initiate a command. A single Extended command is used to alter toggle mode

Turn the Scene On/Off rather than an individual device. Sending Insteon Direct commands to control an individual device does not involve the Scene at all which is why only the specific device responds. EDIT: using MobiLinc tapping the device button normally turns the Scene On/Off when MobiLinc is aware that the device is a Controller of a Scene. This feature does not exist in the Admin Console. With the Admin Console scroll down to the Scenes. Then turn the Scene On/Off.

Is there anything pending/queued for the KeypadLinc or any chance it is marked Disabled. When I mark my v36 KPL disabled and change the toggle mode all I get is the 0 bytes message.

For some reason the change is not being written to the KeypadLinc. What ISY firmware level is being used? Run Help | About, verify Firmware and UI lines show same level.

My apologies. The Wait has no affect when there are no functional statements following the Wait. Program 1 no change Program 2 If Then Disable Program '1' Send notification to 'email' content 'Watch the wind' Wait 1 hour Enable Program '1'

Right click the KeypadLinc Primary node, select Diagnostics | Query Insteon Engine. With the Event viewer running Level 3 change the KPL button to something different as the ISY will not write an option to the KPL it thinks has already been set. Then change the button toggle mode to the desired setting. See if button works after the Query Insteon Engine. If not please post the event trace.

Copy/Paste the two Programs. Right click a Program, select Copy to Clipboard (last option at bottom of list). They past into forum. Make sure the Program changes have been saved by clicking Save Changes.

Program 1 If From 9:00:00AM To 6:00:00PM And Module 'Climate' Wind Speed >= 16 mph Then Run Program ‘2’ (if) Program 2 If Then Send notification to 'email' content 'Watch the wind' Wait 1 hour

The Wait (and Repeat) statement allows the If to be reevaluated. Every time the wind speed exceeds the checked value the Program is triggered from the beginning and issues another email. One solution is split the logic into two Programs. The second Program has a null If so that the Wait cannot cause the Program to be reevaluated.

It may be related to the confg file not being deleted. However, the ISY did try to communicate with the RemoteLinc2 and failed to get any response from the device. Be sure it is in linking mode and near a Dual Band Device. Post the trace with these two requirements satisfied.

The router has to support uPnP for the File | Enable Internet Access to work. Not all routers do. Also if the router is rebooted the uPnP setup is lost. UDI recommends setting the router definition manually so they are permanent. EDIT: I checked the Wiki which does list that router as supporting uPnP. Is that feature enabled in the router? Does not change the recommendation that port forwarding be done manually

Define an ISY Scene. Add the MorningLinc On node as a Responder the MorningLinc Off node as a Responder the KeypadLinc button as a Controller click the KeypadLinc button entry below the ISY Scene name set the MorningLinc On node to unlock set the MorningLinc Off node to lock click the ISY Scene name and set the same values for the MorningLinc On and Off nodes

Have the buttons that stay On been added to the All Off Scene as Responders?