LeeG

easytim The same difference between base and Pro without the IR feature. 256 versus 1024 devices, 300 versus 1000 Scenes. The Pro version allows updates to be held and done as a batch. Suggest looking at the UDI web site which covers the capabilities of each variant. http://www.universal-devices.com/99i.htm Lee

ELA There are a few posts about the latest update to AVAST blocking Current State information. See the following topic for one of the threads. There are others. Perhaps one of the systems has the latest AVAST update and one does not. A Search on Avast will yield some other hits viewtopic.php?f=3&t=6911&hilit=Avast Lee

Dodger Just saw that you are a New user. To add an device to the ISY use Link Management | New INSTEON Device. Enter the Insteon Address and Name that you chose. Click Ok. The ISY will proceed to add the device to the ISY devices in the My Lighting tree and create the necessary link records. To create a Scene use Link Management | New Scene. Enter a Scene name of your choice. Add the OutletLinc to the Scene as described in my previous post. If another Insteon device will control the OutletLinc add that device/button as a Controller of the Scene using the same method as the OutletLinc. Lee

Dodger Add the OutletLinc to the ISY in the same way other Insteon devices were added. Once added right click on the OutletLinc node and select “Add to Scene …â€. I popup will appear with a list of Scene names to pick from. Once the Scene has been selected another popup will display showing the OutletLinc as a Responder to the Scene. When the Scene update process is complete the OutletLinc will respond to the Scene. Lee

rlebel The PLM commands to read the PLM link database do go through the serial interface. The Get Next PLM command is dependent on a NEXT record field internal to the PLM. Each Get Next command sets the NEXT field to the next available PLM link record. Unfortunately if the PLM receives an inbound Insteon message the link database is searched looking for a match. This search changes the NEXT field to point to the PLM link record following the matching link record to the inbound message. The Get Next issued to read the next record related to the Replace is no longer the correct record. This symptom is most often seen when running a Show PLM Links Table command. Any inbound Insteon traffic changes the NEXT field and leads to impossibly high link record counts because link records are being accessed multiple times or too low as link records are skipped. EDIT: the ISY does not access PLM link records directly. That would require tracking were each link record is located in the PLM. I don't know the implications of rebooting during the Replace operations. I would not expect it to cause intermittant powerline problems. Lee

Moshe Right click on KeypadLinc primary node and select Delete. That will remove the device from the ISY and delete any link references to the deleted device. Lee

tech_dog "Is there a way to use the ISY to link the OPEN scene to the on-mode for the keypadlinc button, and the CLOSE scene to the off-mode for the same keypadlinc button?" Sorry, no. Insteon hardware does not support the KeypadLinc On button press controlling Scene X and the KeypadLinc Off button press controlling Scene Y. ISY Programs can perform an Action when the On command is received and a different Action when the Off command is received but it sounds like that is what is in use today. Lee

Matapan Mutually Exclusive buttons may control the same responder(s) or different responder(s). That depends on how the Scene each button controls is defined. ON ON is not a possible combination for a pair of Mutually Exclusive buttons. The other 3 combinations are possible. There is no best approach. Mutually Exclusive buttons work well so long as only one KeypadLinc is involved. If multiple KeypadLincs are to be cross-linked Mutually Exclusive button relationship applies only where the button is being pressed. It does not carry over to other linked KeypadLincs Lee

rlebel Be sure NO Insteon traffic other than that associated with the Replace reaches the PLM. The process of reading PLM link records will be disturbed possibly repeating large portions of the link database if Insteon messages are received because other Insteon devices are being turned On and Off. Lee

rlebel Those commands are reading through the PLM link database looking for entries that have the old device address. The first part of Replace with took some 7 minutes to get to the point where the PLM link database is being processed. Let it run to completion. Lee

Yes. See the latest User Guide in the WSDK link http://www.universal-devices.com/develo ... Manual.pdf

Michel Sorry for the confusion. I issued the Clear Log under 3.1.8 to see if that would resolve the errors being encountered when accessing the Log file. It did not. When I installed 3.1.9 and displayed the Log file I found it in tact (except for the missing entries from 3.1.8 that Tim noted) indicating the Clear Log issued under 3.1.8 had no effect. Everything under 3.1.9 is running fine. I add my thanks for such a quick resolution. Lee

kevinkaz Use the 2420M device type for any Insteon motion sensor purchased from Smarthome. The -SP is the Pro product line available only to professional installers. Lee

TJF1960 Looks like Log was not functional during time 3.1.8 was installed. I even tried a Clear Log to see if I could get rid of the errors on 3.1.8 and that did not clear the log. Looks like all Log activity of any kind was not functional on 3.1.8. Lee

Install of 3.1.9 was successful. Log file was not lost. It is now accessible under 3.1.9

I also see error when accessing Log. File is empty under Excel and as .txt file. Tried Clear Log but that did not resolve. Now get "Request Failed" popup and empty Log file.

The 3.1.8 install was good. The Batch and RF Icons are back on Admin Console The Motion Sensor now has the Replace xxxx with option

The 3.1.8 install was good. The Batch and RF Icons are back on Admin Console The Motion Sensor now has the Replace xxxx with option

Michel I do not have a Replace xxx with option for my 2420M V2 Motion Sensors on 3.1.7. Lee

Thanks for the Wiki link. That sure makes it look like the Status check should be predictable.

Jpoje The UPS was likely a source of Insteon signal attenuation. They are well known for that. Using a FilterLinc between the UPS and the powerline usually resolves that problem. Adding a device using the “keep existing links†option should have defined Scenes with names such as Scene xxx which correspond to the link records found in the RemoteLincs. Linking with the Set button is not a good idea as it creates link records the ISY is not aware of which will eventually result in unpredictable operation due to link record issues. To link devices define an ISY Scene and add the corresponding devices to the Scene. For example, adding a KeypadLinc button as a Controller and a SwitchLinc as a Controller will result in the devices being cross-linked. The ISY assumes a Controller is also a Responder (if the Controller has Responder capability). Right click on the respective device node in the My Lighting tree and select Add to Scene. The Scene popup will have a button on the bottom of the window to select Controller or Responder if the initial choice by the ISY is not the desired choice. The RemoteLinc is one of the few devices that are Controller only. The RemoteLinc button is added as a Controller of a Scene with some other device either added as a Responder (such as an ApplianceLinc) or as a Controller such as a SwitchLinc. In the later case the RemoteLinc button will control the SwitchLinc but the SwitchLinc is not cross-linked back to the RemoteLinc as it is not a Responder. Lee

So it has never been a totally reliable technique. That is interesting and should be helpful information to UDI. Where did you find the example? I would like to see the context of the example.

jpoje That is good to hear. As an FYI, Access Points do not have to added to the ISY. There is no linking associated with Access Points and no configuration. The 4 tap Set button process verifies the Access Points are talking to each other on opposite 120V legs but performs no permanent linking or configuration. Something has happened on the circuit where the PLM was orginally receiving power. Problems with new devices on that same circuit may appear in the future. Lee

"I liked the way it used to work and would like it to still work that way." It is normal not to want to recode something that was "working" in the past. That may not be possible in this case. It will require Status updates happen before a Program is triggered when triggered with an If Status and after a Program is triggered and the If evaluated when the Program is triggered with an If Status and If Control for the same device. Not very logical but that may be what the intent has been all along and the latest image introduced a timing difference. Or the latest image introduced a timing difference and something that was never intended to work no longer works. Will be interesting to see what UDI comes up with.

So the expectation is all initial Program If evaluation will be based on device Status before the effect of the current inbound command is posted. That pesky old multi tasking. The ISY will have to delay posting a device Status change until all Program Ifs have been evaluated except it cannot be that simple. The Status change itself causes Programs to trigger. Will be interesting to see how the ISY solves that dilemma. EDIT: need something like If Status xxxxx was Off to indicate the Program is looking to check the prior status of the device, not the status as a result of the If Control command. EDIT2: a Program with an If Status xxxxx is Off expects the Status to be Off when an Off command is received so this check normally wants to look at the device status after the inbound command has posted the resulting Status. Otherwise the Status is Off does not produce the expected results. Where in the If Status combined with If Control case the desire is to have the Status checked be before the inbound command has posted the resulting Status. Tricky logic to sometimes use the before value and sometimes use the after value.