fitzpatri8

Random Timer Trigger: If On Mon, Wed, Fri Time is Sunset Then Run Program 'Random Timer' (Then Path) Else - No Actions - (To add one, press 'Action') And Random Timer: If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Wait 1 hour (Random) Set Scene 'Living Room Scene' On Wait 2 hours Wait 1 hour (Random) Set Scene 'Living Room Scene' Off Else - No Actions - (To add one, press 'Action') Notice how you can combine Wait statements, first with a set wait followed by a random wait. In this case, the scene always stays on for a random period between 2 and 3 hours.

Any touch-screen device that has an Internet browser can work directly with the ISY. If you use an IOS device--an iPad, iPhone or iPod Touch, you can also use 1Password or MobiLinc to automatically log in with your id and password. In the case of MobiLinc, you can also build a custom Favorites screen that lets you easily control your favorite devices, scenes and programs from one screen.

Like the OutletLinc, the Icon Dimmer Module, the Icon On/Off Module, and the larger LampLincs, the ApplianceLinc is a responder only, not a controller. Responder-only devices don't send a control message if you used the on-device button or Local Control to change its state. If you turn it on or off using a device linked through the ISY as a Controller to the outlet, then the ISY will update the status when it receives that control signal. If you are trying to track energy consumption and are concerned that users may try to 'cheat' the tracking by not using the linked controller, another option is to Query the outlet directly every few minutes for current status.

If you don't need the power of a full-blown ISY-99, you could track down a used/refurbished ISY 26 or you could use a SmartLinc.

I believe the MorningLinc is essentially an ApplianceLinc with a Morning Industries remote as a daughterboard. As such, it has similar limitations to a Morning Industries remote--you can associate it with multiple locks, but all associated locks within RF range lock/unlock in response to the same button press. While this means you don't have discreet control over each lock using a single MorningLinc, you ought to be able to add multiple MorningLincs to the ISY, then use programs to lock and unlock different sets of locks in response to different Insteon controls or timer triggers.

Step 3e of the 2.8.10 instructions installs it on your desktop: http://www.universal-devices.com/99i/2.8.9/admin.jnlp

You can have two Wait commands back-to-back--one can be a fixed minimum time, the second can be a random time.

Other oddities: I notice that if I expand a scene and select a controller within that scene, the control buttons on the bottom of the window (On, Fast On, Off, Fast Off) don't work. They work if I select the device in the My Lighting section, just not within scenes. Controls for devices that are responder-only members of scenes work, but not controllers. Also, when adjusting scenes, the status flag in the lower left doesn't always track with the status (status turns to busy but flag sometimes stays green.)

I just retested. If I run the Administrative Console, select a KeypadLinc dimmer, then quit the Administrative Console, then run the Administrative Console again from the desktop icon, after entering User ID and Password, it shows that KeypadLinc again without the Current State slider. (Actually, it shows up momentarily then disappears.) If I choose another device, then switch back to that KeypadLinc, from then on it displays the Current State slider correctly. It also appears that running the Admin Console using the desktop icon after installing the update and clearing the Java cache downloads the wrong version of the Admin Console code--it comes up without the new icons in front of Sunrise and Sunset. The progress bar appeared correctly on SwitchLincs. I'll retest the KeypadLinc Dimmers again later in the day when it won't wake people up.

After upgrading to RC 5, when I change the local dim level or the ramp rate on a KeypadLinc dimmer the System Busy notification is transparent--the progress bar is missing. Also, the Current Status slider appears intermittently, on screen sometimes and missing others.

This is where I wish the ISY would support other PLMs, the SmartLinc and the SeriaLinc similarly to how it currently supports the IRLinc Transmitter. If it only learned a group at a time, you wouldn't tie up 240 links per supported device and it would give the ISY a way to exchange messages with external hardware and software like HAL using a reliable two-way protocol.

What controller button or technique are you using to turn the light on or off when it gets out of sync?

Verizon may change your IP address occasionally, at which point you want the router to recognize the change and update the dyndns site with the new IP. Make sure the router is correctly configured to perform that update, or install an update application on a networked pc you leave running. (There are links to update apps on the dyndns site.)

Make sure you are using it with a compatible load (within wattage limits and dimmable).

Click on the Main tab in the Administrative Console. Create a new scene. (Click on the icon that looks like a painter's palette.) Add both the fan and the keypad button to the scene as responders. (Right click on each, Add to scene.) Change the program statement to turn off the scene you just created.

Makes sense. The big catch is, when you press the SwitchLinc ON a second time, the dimmer will immediately change to 100%. To deal with that, you'll have to have your program also adjust the dimmer back where you want it. (One modification I made, you'll need to press OFF twice quickly to turn the monitors on without turning on the lights.) Let us know how this set of programs works for you: Program Monitor Bank OutletLinc Toggle If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Set 'Monitor Bank OutletLinc' On Set 'Office SwitchLinc' 46% (Adjust to your desired %) Else Set 'Monitor Bank OutletLinc' Off Set 'Office SwitchLinc' 46% (Adjust to your desired %) Program Office SwitchLinc Off Pressed If Control 'Office SwitchLinc' is switched Off Then Set 'Monitor Bank OutletLinc' Off Else Program Office SwitchLinc FastOff Pressed If Control 'Office SwitchLinc' is switched FastOff Then Set 'Monitor Bank OutletLinc' On Else Program Office SwitchLinc On Pressed If Control 'Office SwitchLinc' is switched On And Status 'Monitor Bank OutletLinc' is Off Then Run Program 'Monitor Bank OutletLinc Toggle' (Then Path) Else Run Program 'Monitor Bank OutletLinc Toggle' (Else Path)

Excellent explanation, apostolakisl.

What do you mean by 'turn the outlet on remotely'? If you are using one Insteon SwitchLinc to control the outlet and you want another Insteon SwitchLinc to turn on at the same time, you only need to add the second SwitchLinc as either a controller or responder to the same scene. Insteon devices don't 'track' one another, they either control a scene or respond to a scene. If you mean you are turning the outlet on via the front set button or by toggling the device you plugged in off then back on (local control), then it gets a little complicated. As already mentioned, the OutletLinc cannot be a scene controller. You can, however, create an ISY program to query its status every so often then trigger a scene based on that query status. But you don't want to go to that trouble if you don't have to.

No, polexian wanted to have the control in non-toggle ON mode, and for the program to toggle the load each time he pressed it. To do that, use two programs and the Control trigger and the Status condition: Program KeypadLinc On Pressed If Control 'Keypad A' is switched On And Status 'OutletLinc 1' is Off Then Run Program 'OutletLinc 1 Toggle' (Then Path) Else Run Program 'OutletLinc 1 Toggle' (Else Path) Program OutletLinc 1 Toggle If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Set 'OutletLinc 1' On Else Set 'OutletLinc 1' Off

Excellent detail, Lee, thank you! I've got a Rev. 1.0B NC unit here, but I can't easily switch the load on and off independently for testing. When I get time this week, I'll try to temporarily relocate it to a different load to rerun your tests. I'll see if I can duplicate your load active results here.

Exactly, documentation, not marketing. Shouldn't there be another line in the chart that says Open with Load On, Solid Red? Clearly this is a niche product that goes above and beyond what your typical module can do. As such, it wouldn't floor me to hear that some of SH's retail staff didn't have a complete grasp of more unique features. I wonder how much training time new staff get on this product? If anything, my complaint would be that they offer a unit like this on their retail line at all. IMHO, this would be better sold and supported by senior folks on the commercial side of the business.

On reviewing the product specs, I do see where it says it is a controller for three separate scenes, not that scene 1 replaces the other scene 1. So I take back that question about the load demand scene 1 taking place of the controller scene 1, it looks like they are separate events. I don't see where operation deviates from marketing, but I do see where the documentation is vague enough that people are reading what they want into it. For instance, what does the Controller Group 1 scene do? As best I can tell, the Controller scene turns on and off when you press the front button. No other time. That doesn't sound terribly useful to my projects so far, but I suppose it does offer a way to track total run time in the event you activate the device manually. Kind of a virtual Hobbs meter, if you are tracking when you need to change a filter or service a pump. What about the Load Controller Sense scenes? First, they operate differently from other Insteon devices with Sense. On an InLineLinc or SwitchLinc with Sense, the device has only one controller scene and power on the Sense line causes the relay to turn on and off unless it is being ignored by the FAST ON or FAST OFF command. On the LC, Sense runs low current through the Load to see if the Load circuit is complete, i.e. that it would draw power if the LC offers it. If so, the LC turns the LOAD ACTIVE light ON. The documentation gets vague here. I see no mention of it, but I would expect that the Load Sense Scene 1 (i.e. Group 2) would send an ON to let your software know that the device was ready to use power when offered, yet not turn on the LC relay. (There's no way to disable the sense on the LC, so you wouldn't want heavy-duty equipment self-starting when your software says it should be off, and there's no mention of support for a Fast On/Fast Off kind of software disablement as with the ILL.) If I'm interpreting correctly, this would allow your software to make some intelligent decisions about when it should consider the load running (so it can track total run time, not just relay on/off time) and when it should consider turning the load on or off. This might be useful when you are running some kind of motor that requires rest periods after use--maybe a well or sump pump that also uses another switch to turn it on or off based on levels. If I've got this right, then it would be helpful for the ISY to support Group 2 on the LC, but you'd need the ISY to be attached to something that can keep count of run time (perhaps HomeSeer or one of the new web-based energy monitoring services) or a future ISY upgrade to include variables and counters to take full advantage.

According to the instructions for Creating a Load Sense Scene (Normally Closed Relay only): That sounds just like the TriggerLinc, where scene 2 disables the Off on scene 1. The way I read it, using a Load Controller Load Sense scene overrides a Load Controller scene, just as using a Load Sense Scene 2 overrides a Load Sense Scene 1 Off. Lee, can you verify that?

On devices that offer two controller groups vs. one, if you activate the second group you disable the 'off' to the first group. The TriggerLinc is like that. You can either send an On and and Off to group 1, or you can send an ON only to group 1 and and ON only to group 2. Perhaps I'm missing your point. What exactly are you trying to accomplish?

If you write your programs to trigger based on the 'Status' of the Load Controller, then the program will run any time the Load Controller turns on, no matter if it is because of an outside command or if it is the load triggering it. If you write your programs to trigger based on the 'Control' command, the program will only run if the Load Controller turns on as a result of the load demand turning on.