LeeG

"I am trying to affirm that if I do the following that the device will be in fact empty and blank as if it came out of the box" It will NOT be as it came out of the box, assuming it came with no residual links. The ISY does not go through all the link records and set them to 00 which is what they should have looked like coming out of the box. It only sets the first link record flag to 00 which logically erases all active link records but does not physically erase them. Also the ISY device add process creates link records for ISY use which HL will have no knowledge of. They will look like broken links to HL. Half links are either links in the Controller device without matching links in the Responder or links in the Responder without matching links in the Controller. Either case is considered a broken or half link.

Yes. There must be something behind the question. What part are you questioning?

Insteon has no Scene status. The Status of each device in the Scene has to be checked for not Off. If Status 'ICON Dimmer 1' is not Off Or Status 'SwitchLinc Dimmer' is not Off Or Status 'ICON Relay 1' is not Off Then - No Actions - (To add one, press 'Action') Else - No Actions - (To add one, press 'Action')

It sets the first link record flag byte to 00 which is the End of List Marker. Nothing after that matters. The device firmware does not look past the End of List marker.

No. That is not possible.

aLf I run a generator when power goes down. Never damaged an Insteon device. However, as with many generators, the 60 cycle being generated is not accurate enough for reliable powerline communication. The local load control is fine but communication with linked devices is spotty. There are various other Insteon users with the same experience. Take a look at the Smarthome forum. The subject comes up whenever there is a wide spread power outage somewhere. Some generates, generally the more expensive but not always, do generate a very accurate 60 cycle sine wave. Insteon devices start sending before the zero crossing so accurate 60 cycle timing and wave shape are very important. Lee

"I do not need to have a computer running with software all the time to access it from my phone correct?" That is correct. The Admin Console is needed only when making changes/additions to ISY Programs and/or devices, etc. Otherwise the ISY is independent of any computer. Phone access is independent a computer. Sorry I do not have a mobile device. One of those old timers living in the past.

"What is everyones experience thus far with this device?" Great device in use for nearly 3 years. Never regretted the move. Have HouseLinc and Powerhome (software for PC). ISY does everything I want to do with automation. "Did you previously have a SmartLinc at all? How do they compare? " No. SmartLinc is a basic entry level Controller only device. No events, no tracking of device status. really a very different category of device. They are not in completion as the SmartLinc is not designed to do what the ISY or any full time PC/Mac based automation software "What are some things I'll be able to use the ISY for?" Device linking (Scenes) and device configuration. All done from PC web interface. Intelligent control of motion sensor controlled lights. Lower On Level with motion sensor, manual On/Off override, intelligent turn Off of lighting. Lived in look with random lighting pattern. With ISY Programs many things can be done that SmartLinc was not designed to do. "How close is the ISY to an Indigo set up?" Never used Indigo. No Mac. "Does the web interface work well? Or do you suggest the MobiLinc Pro for $20?" Admin Console on PC works well. MobiLinc provides portable wireless control of devices. It is not meant as an alternative to the Admin Console for the management of the installation (device linking and configuration, ISY Program development,etc).

Contact UDI. They will send you an adaptor. See the next to last post in this topic. viewtopic.php?f=27&t=6516&hilit=ISY+power+supply+connector

bocarob This link to the Variables section of the forum has some good information. The Summary topic describes what variables are and the difference between Integer and State variables regarding triggering (run) Programs. viewforum.php?f=68

You are very welcome. Post back anytime. Lots of really good folks on this forum. Best forum community I have found.

I have not found any Insteon device the cause of interference. There are devices such as some cell phone charges, PC and UPS (more signal attenuation than noise source) and other that can generate enough noise to cause powerline problems. I think the LampLinc may be defective. Could try doing a Factory reset before throwing in the towel. Some very short power interruptions have been known to hand up a device. If a Factory reset does restore operation remember to do a Restore Device to put any link records lost from the reset. Link records are not needed to manually control the device itself through the Admin Console. EDIT: the Device communications events option did not work for some reason. There are no commands in the trace. Might try it again but I'm pretty sure the device is not responding to anything.

Yes, that is correct. There are a few devices such as the ControLinc and RemoteLinc that are Controller only devices that cannot be added to a Scene as a Responder but for most single device situations either Controller or Responder works. Either will accept Scene commands.

Vince Thanks for that screen post. The FF ---FF is the problem. This link record (or what should be a link record) is what authorizes the ISY PLM to send commands to the MorningLinc. Once it is gone On/Off commands will no longer work. Another user is sending me an event trace of the scene creation. I'll post back with what that analysis shows. Lee

The FF -- FF for the first link record indicates the ISY PLM has lost authority to communicate with the MorningLinc. The MorningLinc has a special security feature that other Insteon devices do not have. Suggest a Factory reset of the MorningLinc. Verify the MorningLinc Set button press will continue to cycle the lockset. It should, mine does after a Factory reset. Add the MorningLinc to the ISY again. Sorry about that. It is the only way to establish the ISY PLM as an authorized user of the MorningLinc. Run Tools | Diagnostics | Event Viewer with Level: Device communications events selected and define the RemoteLinc Scene again. That should show what is happening to the MorningLinc link database that is causing authorization to be lost. If the Event Log is too big to post send it to lwgwork@embarqmail.com.

No, a Scene is not necessary. The devices are listed and commands can be issued directly to the device. A single device can be a Responder or Controller (controller assumed to also be responder) in the Scene and control the Scene through the mobile app but that is not necessary. Direct device control is normal.

I’ve got some doubts about this being what you want because the conditions to Trigger the Program are the conditions to do nothing but here goes. These are State variables. Any time one of the three State variable value changes the Program is triggered. That is the way ISY Programs work. When triggered, if any of the State variables are greater than 0 run the Then clause. The Then clause has the function to be executed. If none of the State variables are greater than 0 the Else clause is run. The Else clause contains no function so the effect is to do nothing. If $SVar4 > 0 Or $SVar2 > 0 Or $SVar3 > 0 Then - Add functional statements here Else - No Actions - (To add one, press 'Action') If as I fear this is not what you are looking for please try again to explain the conditions to run the Then clause.

When running the Event Viewer set the Level to Device communications events. The posted trace does not show the command detail. It looks like the device is not responding to commands but that is a conclusion based on the results rather than being able to see the actual command responses. EDIT: it may be this device has just failed. Would explain why it stopped working before and now will not communicate at all. Things like was the device moved to a surge suppressor power strip would also block Insteon communication. A new trace with Device communications events selected will show if it is responding to any commands.

The part about the multi-way switches as Controllers of the Scene and Motion Sensors and TriggerLincs as Controllers is correct. Defining the devices in a multi-way configuration as Controllers causes the ISY to cross link the devices such that any device can control the load and they will all stay in sync. Do not understand the last part about the remaining switches which are single function. If the switch is only controlling its local load there is no need to have the switch in a Scene at all. Making it a Responder in a unique Scene provides no additional function and it adds to the link record count in the PLM.

bsobel Check Help | About and be sure the Firmware line and the UI line both say 3.1.16. If the UI line does not say 3.1.16 or the UI line is not there at all (should be line immediately below Firmware line) check the URL being used to invoke the Admin Console and clear Java cache again. Sounds like the wrong level Admin Console is being used. Lee

Even using the KeypadLinc Button Grouping function it is legal to toggle the current On button to Off such that they are all Off. Turning the button Off presumably turned the Scene Off so leaving the button LED On would be misleading. It would look like the Scene was On when it was Off. That said the Program can be set up to turn the button LED back On when an Off is received.

If the device is Insteon there is no need to use X10 commands. To the question I think it would.

ahwman When a device is added to the ISY its Device Type indicates whether it is a Responder Only device (blue), a Controller only device (red) or both (also red). This is determined by what hardware/firmware capability the device has. Only when the device is added to a Scene can a choice be made about whether the device should be added to the Scene as a Responder Only or as a Controller. This choice can be made only for devices that have both Controller and Responder capability. When added as a Controller is also functions as a Responder. For Controller only devices and Responder only devices they are added to the Scene as what they are as a Responder only device cannot function as a Controller and a Controller only device cannot function as a Responder. Lee

"if I specify only "Run program If" under "Then,": The Program referenced in the Run Program If will evaluate the If and either run the Then clause or the Else clause based on the True/False of the IF. One possible issue with the second posted Program is the Wait 5 minutes. If the garage door is closed before the 5 minutes elapses the Program If will be reevaluated as False with the result that the Run Program is never executed. The Program Summary showing Last Run Time for the Program with the Set 45% will indicate if the Program is every executed and whether the Then or Else ran by looking at the True/False state.

Vince What ISY firmware is being used? Run Tools | Diagnostics | Show Device Links Table for the MorningLinc. When the display completes click Compare. If you can screen capture the results and post the screen image of the Show and Compare.