LeeG

What application is issuing that message? The ISY does not have Macros so that will not be an ISY message.

Are you really suggesting changing to a completely different automation controller because the ISY does not support GH?

Some things that can be looked at. Check the Status LED on the OutletLinc before running the Query Scene. Does the Status LED on the OutletLinc change? If it does it cannot be the Query command itself. With the entire Insteon device list being queried by that Scene some device Current State is changing (not the device itself) which is driving a Program to produce the results. All the Programs can be Disabled but I would expect you know the Programs that can affect the OutletLinc. If the security system is affecting the OutletLinc I don’t know how to shut that off for diagnostic purposes.

Run Help | About, verify both Firmware and UI lines indicate 3.2.6.

I don't think a Query command is turning the OutletLinc Off. It may be physically Off, the ISY Current State shows On because of a communications problem or something the security system is doing the ISY is not aware of, so the status returned by the Query changes the Current State information to Off but a Query command does not change the physical state of the OutletLinc.

The Else runs whenever the If is False. Because the device Status is being checked in the If and changed in the Then the Program is triggered again when the Status changes to ON except now the If is False so the light immediately turns Off. Simple solution is to add a Set 'xxxx' Off in the Else and remove the device Status check. That way when the Program is triggered at the 5 minute mark the Else will run and turn the device Off.

What type of device is it? How are you turning it On? Through the ISY Admin Console or manually at the device? If at the device does the Admin Console show it as being On when turned On manually. Are programs triggered when the device is On?

A Query command by itself never changes the actual device status. If there are communications problems such that the ISY is not in sync with the actual status of the device, a Query can change the ISY Status (Current State) which will trigger Programs based on that Status. Also devices such as the I/O Linc Sensor have a Trigger Reverse option which reverses the commands issued by the I/O Linc Sensor. Sensor On sends an Off command, etc. A Query of the I/O Linc will return the actual Status of the Sensor, not the Trigger Reversed commands. Thus, when the I/O Linc is Queried the I/O Linc Sensor Status will change when Trigger Reverse is used.

There are almost always multiple ways of doing things with Insteon devices. You are relating Scene processing which is the only way an Off command in combination with the right Momentary mode will cause the I/O Linc Relay to turn On. The Relay must be turned On for the opener motor to move. The Program example I posted is using an Insteon Direct On command to turn the I/O Linc Relay On. This works independent of Momentary mode, independent of whether the Sensor is On when the door is open or On when the door is closed. To answer the specific question, NO, you cannot issue an Insteon Direct Off command and have the door move. If you want to use a Scene which has the I/O Linc Relay as the Responder, and you have the proper Momentary mode set, and the proper Sensor On/Off relative to door Open/Close, and the proper use of Trigger Reverse, you can issue a Scene Off.

Turning the I/O Linc Relay On is what causes the door opener to move, closing the door.

Something like this If From 11:00:00PM To 6:00:00AM (next day) And Status 'IOLinc-Sensor' is On Then Wait 5 minutes Set 'IOLinc-Relay' On Else - No Actions - (To add one, press 'Action') assumes the I/O Linc Sensor is On when he door is open.

I suspect when Smartlabs introduced the Garage Door Kit based on the I/O Linc user interest in Gareage Hawk fell off.

Could be an I2CS device which requires the latest Official release 3.2.6. Can you provide some additional information. What link method was used, what were the results (beyond cannot link), perhaps an Event Viewer with Level 3 covering the link attempt. Try moving the device closer to the ISY PLM for linking purposes. According to the Garage Hawk web site ISY support is "Comin Soon".

Both of those devices have load sense which does pass a small amount of current which is used to identify when the device is turned On. Load sense can be turned Off but the trickle current remains. It will require a Relay device without load sense powering a standard outlet.

That is normally some change in the AV. Is Avast or Kaspersky being using? Was it updated lately? If not what AV is being used?

Controlling a KeypadLinc Primary load control button from a Secondary button on the same KeypadLinc is done with special definitions within the KeypadLinc itself. Not all KeypadLincs will handle this correctly. Can you provide the KeypadLinc firmware level. The numbers in the previous post are hardware revision numbers. The KeypadLinc firmware level is displayed on the second line of the Admin Console detail node display (right pane). Controlling the Primary load control button from a different device, be it another KeypadLinc or a SwitchLinc (single paddle) is done very differently and would be expected to work regardless of KeypadLinc firmware level. The reason it works when controlling the Scene is the ISY PLM is the controller, a separate device, which always works when defined properly. Again, it is controlling the primary button from a secondary button on the same KPL that is problematic on some KPLs

What is the 6 button KeypadLinc firmware level? Controlling the Main load button from a Secondary button on the same KeypadLinc has been a problem with some KPLs. When you click on button D listed below the Scene name are both the Main and other Dimmer set to 60%?

Tests on the latest KPL firmware does not result in the KPL button turning Off with a Fade Down. Tried it both as commands from the ISY and from another KPL as Controller. Fade Up turns the button On, Fade Down does not turn the button Off. After using the Fade Down/Fade Stop, issue a Scene Off. The other responders will be Off so the only visual effect will be to turn the KPL button LED Off.

I'll have to run a test using Fade on an older KPL Secondary button but there is a problem with the Program. Fade is to a two command sequence. When a button/paddle is pressed and held, either a Start Manual Change Up or Start Manual Change Down is sent to the Responders. This first part is the equivalent to issuing a Fade Up or Fade Down. When the button/paddle is released a Stop Manual Change command is sent to the Responder to complete the Fade operation. The last part is equivalent to Fade Stop which is missing from the Program. Without that Fade Stop the device firmware is left in an incomplete Fade operation. Add a Fade Stop and see what happens. It may not change anything but the Fade Stop is required.

The inherent differences between If Control and If Status exist regardless of the type of device. If the device can send On, On, On then there is much difference between If Control and If Status. You need to be specific about what event is being discussed when comparing the possible differences between If Control and If Status results. Also If Control triggers only on command flow from the device. If Status can trigger on command flow from the device as well as a Scene initiated change.

kevinvw Smarthome does not upgrade Insteon devices. Must purchase the newer devices to get the newest features. The older KeypadLinc buttons need to be handled with a separate Scene. Scene X is turned On to set various responders to low On Levels or even Off (except Secondary KPL buttons). Scene Y contains the Secondary KeypadLinc button(s) so Scene Y can be turned Off.

kevinvw "I thought I could add the kpl button to the go to bed scene as a responder so that when the scene is set to off in the program, the button would also be set to off. doesnt work. can somebody explain why that shouldnt work? makes sense in my logic, but I am pretty new to the ISY." It should which means something is not as described. A Scene On to set some of the Responders to various low levels cannot turn a Secondary KeypadLinc button Off until KPL firmware v.40. A Scene Off should turn the Secondary button Off. Post the Scene and the Program.

Sounds like the Program is triggered with an “If Control†which is looking for a command flowing from the specific device. If you want turning the KPL button Off with a Scene Off then “If Status†is needed as that triggers the Program both when the KPL button is pressed Off and when the button is turned Off with a Scene.

tunaman No luck. The ISY recognized the KPL as 8 button, defined the 8 nodes, and I was able to add Secondary buttons as Responders and add Secondary button H as Controller.

Thanks, that explains the difference in PLM response. I'm running v.99. I’m working on changing a KPL from 6 to 8. Thought I had a spare 8 button kit, turns out I don't. Temporarily taking the buttons off one of the 8 button KPLs so I can move the frame and buttons to an existing 6 button. From the trace it looks like your KPL is v.40 so I will use one the v.40 6 button KPLs as the test vehicle. That last trace showed no Insteon errors once I got past the PLM difference.