LeeG

andrew77 There is an entire Forum Category dedicated to ISY Variables. Initial posts in this Category have a description of the function of Variables viewforum.php?f=68

The Action | Insteon | Set pulldown does not show any Scene or does not list ISY as a Scene? If the OutletLinc Relay is turned Off locally, by OutletLinc button, by load sense; the ISY will not be aware of that change as the OutletLinc Relay has no Controller capability. Devices that are Responder Only can usually be identified by looking at the device User Guide. The User Guide will not have instructions for linking the device (OutletLinc Relay in this case) as a Controller of a Scene when it is a Responder Only. If the OutletLinc is controlled by an ISY Program, ISY Scene or the Admin Console the ISY should be aware of the OutletLinc Relay status.

lukeharrington An Insteon Dimmer chops off part of the AC Sine Wave even at 100% On. If there is anything in the fan light and/or circuit that are affected by this the load could be dimmer or flicker. It sounds like the fan light has some built in dimming capability or is dependent on a clean AC sine wave that is adversely affected by the operation of the Insteon Dimmer.

Is the OutletLinc a Relay or Dimmer? Only the Dimmer has Controller function. That is, it should notify the ISY if turned Off locally. The Relay version does not have Controller capability and as such does not notify the ISY if turned Off locally.

Look under the Main tab, below Network, it will either be My Lighting or ISY Lighting (from memory). Mine is labeled My Lighting but I think I renamed it many ISY images ago when it was changed to ISY Lighting, maybe when the 994i was first released. The QueryAll should be using whatever is below Network.

The ambient temperature being measured by the thermostat is available in the ISY. The specific temperature can be checked in the If section of an ISY Program. This value is available for an application to read if it chooses. Do not know what Homeseer does.

Variables do not yet support direct assignment of temperature.

You must do a Restore Device after the Factory Reset. As I mentioned before, when a device is added to the ISY link records are created. These must exist for the ISY to be aware of manaul device operation. A Restore Device will put them back.

1) Does that program make sense? To have a control variable that can be adjusted (set) by each remote, and just decrement it a minute at a time? Am I doing what I want in the proper manner (is that the right way to decrement the counter once a minute?) Not as coded. The Wait 1 minute at the end of the Then clause has nothing after it so the Wait is effectively a no-op. 2) What sort of devices should I have to control the ON signals? - Should I be using SwitchLincs (On/Off, not dimmer)? There is power in the walls at each location. - Should I use MiniRemotes? (These do not seem to come in Ivory, so that is a bit saddening, and thus I'd prefer not to use them) - Should I use KeypadLincs? Seems like overkill, but might work for one of the locations where I might have need for other control buttons, and isn't really all that much more expensive. I think this totally personal preference. Any Insteon device that can send On command (which is just about all of them) can drive the Program (not the one posted). 3) What sort of status/feedback will each switch show? Can I make them reflect the state of the OutletLic? I think this is the overriding question as it may well dictate the answer to number 2 as well. What kind of feedback do you want? Some newer devices have a Beep function that is not very loud but will be heard when at the device. It could beep for each time increment (10 minutes for example) that remains. A SwitchLinc Dimmer (not connected to any actual load) could be turned On to various % On Levels which is represented by the status LEDs to the left of the paddle. There are 8 or so LEDs that represent the % On Level of the SwitchLinc. With sufficient programming the status LEDs could show the amount of time remaining with an On button press incrementing and Off button decrementing the status LEDs and pump time remaining. The status LEDs may move to full On or full Off when the paddle is pressed but would be corrected by ISY programming. Something similar could be implemented with an 8 button KeypadLinc with each KPL button representing an increasing amount of pump run time. Decide on what if any feedback/control you want first. That should provide the answers to 2 and 3. You might also give some thought to the idea that too much thought is being put into this. Once the pump has moved hot water to the location there is no longer any need to have the pump running. A simple turn pump On for 5 minutes or 10 minutes may be all that is needed.

I would follow oberkc suggestion. The fact that no link records exist is an issue in and of itself. There are always link records created when a device is added to the ISY. Makes me wonder if there are not communication problems since no device links exist. Either they did not get created, were created and erased with a factory reset from the other forum activity, or there are link records now that cannot be read because of communication issues. After Deleting from the ISY, Factory Reset of device, add it back to the ISY, run another Show Device Links Table for the device. There should be link records present. If not post back that situation so it can be diagnosed and resolved before attempting anything further with the device(s).

Run a Show Device Links Table against both devices and post the results.

There are inline filters that may help. Smarthome use to sell them but apparently Smarthome dropped them from the inventory. I found a reference to an XPNR inline filter but I have no experience with any inline filter. All my filter needs are taken care of with FilterLincs. Anyone have information on currently available inline filters?

What type of load is being controlled? CFL, LED, Fluorescent, etc and what wattage.

When a device will turn On but not turn Off the first thing to look at is the load the device is controlling. The load may be creating enough interference to prevent the Off message from reaching the device. Disconnect the Red wire (and cap it) and see if the device will physically turn On and Off without the load.

Placing the PLM near the central panel is usually a good place. It is necessary to couple the two 120v legs. Otherwise signals have to travel out to the utility transformer and back to get to the opposite 120v leg. For most homes this makes it impossible for signals to get to the opposite 120v leg reliably. For coupling purposes I would place the Access Points near the central power panel. The advantage of Access Points over the passive coupler is signals are rebroadcast on the opposite 120v leg at full amplitude. With a passive coupler the signal is coupled to the other 120v leg at what is likely a lower amplitude because the signal has traveled some distance to get to the passive coupler. Placing the Access Points near the central power panel is not the best location for them to send/receive signals from RF devices such as Motion Sensors, RemoteLincs2, etc that are positioned at the other end of the house. It may require additional Dual Band devices at other locations in the house to cover RF only devices. This is becoming less of an issue with so many Insteon devices being Dual Band. However, wired Dual Band devices stuck inside a junction box generally do not have the range of an Access Point. Placed inside a metal junction box greatly reduces the RF coverage.

Lighting circuits that the SwitchLinc is powered from are often on different circuit breakers then outlets in the same room. Some rooms may have outlets on more than one circuit which sounds like your case where some outlets in the same room work and some do not. The ApplianceLinc is powerline only so Dual Band devices may not have the expected benefit particularly if the SwitchLinc is on a different circuit. Get a pair of Access Points to couple the two 120v legs.

For Button C and Button D to act as exclusive/radio buttons, define two ISY Scenes. Scene 1 KeypadLinc Button C Controller KeypadLinc Button D Responder - 0% On Level Scene 2 KeypadLinc Button D Controller KeypadLinc Button C Responder - 0% On Level Remember that every Scene Controller has its own set of Responder values. When clicking Scene 1 name set Button D to 0% On Level. Then click Red Button C node name just below Scene 1 name. Also set Button D to 0% On Level Do the same thing for Scene 2. Set Button C to 0% On Level for both the Scene 2 name and the Red Button D node name below Scene 2. EDIT: if button C and D are already Controllers in ISY Scenes it is only necessary to add the opposite button to the Scene as a Responder with 0% On Level. The Scene button C is already a Controller of, add button D as a Responder with 0% On Level The Scene button D is already a Controller of, add button C as a Responder with 0% On Level

The passive coupler is not added to the ISY. It has no Insteon address. The Finish button was not clicked on the Start Linking function. Unplug the PLM for 30 seconds. Plug it back in and let it fully boot up. Then reboot the ISY. It may be necessary to do this twice. Update the ISY to 3.3.10. Then run Tools | Diagnostics | Event Viewer at LEVEL 3. Use New INSTEON Device, enter Insteon address of Load Controller, Name of choice, and Device Type at default Auto Discover. Post the event trace. A failure to communicate with the Load Controller will not leave the ISY/PLM in linking mode when using New INSTEON Device.

Spitfire1493 The ISY-99i last firmware update is 3.3.10. There will be no further updates that apply to the 99i. See the link below as this update offer expires the end of March I think viewtopic.php?f=44&t=10771

rrogers Try a factory reset of the MorningLinc. Unplug for 30 seconds, press Set button and hold in, plug in MorningLinc while holding Set button in for 10 seconds after plugged in. This will not reset the link between the MorningLinc and the lockset as that information is in the lockset. If that restores the MorningLinc LED, run Tools | Diagnostics | Event Viewer at LEVEL 3. Click Start Linking, press MorningLinc Set button for 3-5 seconds. Select third Start Linking option, keep existing links, click Finish. Post the event trace.

The ISY Log indicates there are 7 Responders in the Scene (some or all of which could be Controllers). The devices do not directly ACK the Scene On so the ISY marks the Controllers/Responders of the Scene as the ISY thinks the devices should have reacted. The one thing that does stand out is the event is started by a Motion Sensor. Being an RF device it sends multiple messages when motion is detected which might be conflicting with the Scene On the Program initiated. I suggest one of two things, either add a 2 second wait at the beginning of the Program before it issues the Scene On or make the Motion Sensor a Controller of the Scene so the Motion Sensor turns the Scene devices On directly. The later approach could involve more than just making the Motion Sensor a Controller as the Motion Sensor may be sending Off commands which might not be desirable. Perhaps adding the Wait first and see if the resolves the problem. Would also like to see an event trace at LEVEL 3 if you happen to collect a trace of another All On.

Had not considered an Irrigation Requirement value would be held internally that did not match the displayed value.

When every device reacts it is likely a Scene containing all the devices was directed to turn On. The QueryAll Program that runs a 3AM uses a Scene the ISY generated internally to Query all the devices. This Scene should not be used for anything other than the 3AM Query. Was the event trace at LEVEL 3 saved that shows all the devices reacting? It should have the command issued that initiated the process. EDIT: Insteon does not have an All On command that every device is programmed to react to. The only way to get mass device reaction is to send an On command to a Scene that has those devices. The RemoteLinc has an All On button but that controls only those devices that have been linked to the RemoteLinc buttons.

JMC Michel indicated in another topic he would be gone until Thursday. A few pages back was it not established that "You cannot have a negative number for the amount of water" so a calculation that drives Irrigation Requirement to a negative value would not exist. The "0.2973 - 0.5" results in a negative number for Irrigation Requirement which would seem to reset it to 0. To that add "+ 0.1547" and the Irrigation Requirement would be 0.1547. Obviously I don't have access to the internal code used to calculate the value so this may be junk science requiring Michel's return to clarify.

timster No difference in the Insteon commands executed whether one Program or two in this example. Coding one Program that uses both Then and Else keeps related logic in the same Program and uses the least number of Programs. I prefer the single Program because it keeps related logic in one Program. There are times where two Programs (or more) are needed to avoid If reevaluation problems so having multiple Programs is fine when needed. There is a 300 Max Programs limits for the non-Pro ISY versus a 1000 Max Programs for the Pro ISY.