LeeG

What mode is the thermostat operating in? I don't think the set points can be changed in Auto mode.

The " Set Scene 'Kitchen Sensor On' On" is changing something the If is checking. When the Wait is encountered the If is reevaluated to False driving the Else clause. Common solution is to separate If from Then in two Programs. If section in first drives the Then clause which invokes the second Program. The second Program has nothing in the If and the Then logic from the current Program. When the Wait is encountered there is nothing in the second Program If to reevaluate so the statement after the Wait executes. Suggest looking at the UDI Wiki. There is a good explanation of the effects of Wait and Repeat statements.

I assume it is a RemoteLinc2, not a RemoteLinc. The RemoteLinc2 cannot function in a virtual 3-way cross-link the way other Insteon devices can. The RemoteLinc2 sleeps so there is no means of altering what a button press will do next. The entire RemoteLinc2 can be configured to non-toggle mode (cannot change a single button as can be done with a KeypadLinc). That way a Program could be triggered every time the RL2 button is pressed with the Program logically toggling the responder(s). The down side is all the RL2 buttons are non-toggle mode. EDIT: I found one can get use to having to do an extra RL2 button press rather than lose the toggle function for all the buttons. You can also remove the RL2 button from the Scene and trigger a toggle Program with either an On or Off command from the RL2 button.

With the objective of controlling from MobiLinc, create a Program that can be invoked by MobiLinc. The Program turns the Scene Off which insures all the involved buttons are Off, followed by an Insteon Direct command to the KeypadLinc Primary node to turn the KeypadLinc On.

The device link record updates were batched during the Replace test I just ran on 3.2.6. There are PLM changes and Program changes which are made as part of the Replace function. These are not part of the Batch function.

Apologies, my mistake. The ability to turn Off Secondary buttons from another explicit Controller of the Scene is in 3.2.6. That capability was not extended to the Scene name. I believe that function is a candidate for a future release. I am sure you have the latest KeypadLinc firmware.

What is the ISY firmware level?

When pressing physical KeypadLinc buttons the KeypadLinc is the Controller. When turning the Scene On from the Admin Console the ISY PLM is the Controller. Each Responder has a different setting based on which Controller is being used. Click on the Scene name and set the On Level for button C to 0% On Level. This only works on KeypadLincs with v.40 firmware and above. If the KeypadLinc is below v.40 a Secondary button cannot be turned Off with a Scene On. The older KeypadLincs require ISY Programs and separate Scenes for controlling Secondary button LEDs.

I'm still thinking powerline issue but note that my 900 MHz cordless phones works 1000' from the base. Could be a neighbor has something in the 900 MHz band but I think that possibility is low on the possibility list.

raderu That means you are not at 3.2.6 and that is the problem with the SwitchLinc Relays not working. These are I2CS devices (enhanced Insteon message protocol) which requires 3.2.6. Update to 3.2.6, being sure to clear the Java cache after the install. Detailed install instructions are contained in the 3.2.6 Availability post viewtopic.php?f=25&t=8643 Delete the SwitchLinc Relays and add them back to the ISY under 3.2.6.

Are you right clicking on the Scene name, selecting Diagnostics | Scene Test

With the Admin Console, click Help | About. What is listed for the ISY firmware being used. There are two lines, Firmware and UI. They will say something like 3.1.17 or 3.2.6. What is displayed for Firmware and UI

What ISY firmware is being used? Will the SwitchLinc Relay devices turn On and not turn Off? Try running a Scene Test. Does Scene Test produce failures?

Are all the devices in RF range of the ISY PLM? If not the powerline is used. Could be a baby monitor, cordless phone, anything in the 900 MHz range generating interference but I would start with the powerline unless you have a device (besides Insteon) that operates in the same frequency range. The more common powerline interference devices are noted in my earlier posts.

What ISY release is being used? Expanding on the Scene definition may help. How are the SwitchLincs defined to the Scene, Controller, Responder, the actual definition. Are the SwitchLincs controlling each other, does this work? Is it that turning the Scene On/Off through the Admin Console does not work. Is this new Insteon install? What is coupling the phases? Have they passed the 4 tap Set button test to confirm they are on opposite phases and in RF range of each other? Really need much more detail all around.

Having a SwitchLinc as a Controller and the KeypadLinc button H as a Responder should be fine. Do a Show Device Links Table and Compare for both the SwitchLinc and the KeypadLinc Primary node. Are any errors indicated by the Compare? Is the KeypadLinc on the same breaker as the SwitchLinc? Being in the same box does not mean they are on the same circuit. There could be a communications problem between the SwitchLinc and the KeypadLinc if using different circuits. EDIT: the ISY receives a message when the SwitchLinc paddle is pressed. It recognizes the SwitchLinc is a Controller of a Scene with the KeypadLinc button as Responder, marking the KeypadLinc button On assuming the SwitchLinc was able to communicate with the KeypadLinc.

It looked like a link record issue. I2CS devices are very restrictive about which PLM can issue commands to it and that authority rests with the link records in the device.

Run Tools | Diagnostics | Event Viewer with Level 3. Right click one of the LampLinc nodes, select Diagnostics | Query Insteon Engine. Then using the Admin Console turn the LampLinc On and Off. Post the trace containing the Query Insteon Engine and On/Off trace. I suspect these are I2CS devices. Was the Scene created under 3.2.6? Run Help | About and verify the UI line indicates 3.2.6.

Thanks for the trace. Most of the devices are sending a NAK response meaning they received the Scene command but would not react to it. What is the device type (number) and what load is connected to the failing devices. What ISY firmware is being used?

Something on the powerline is interfering with Insteon communication. With the Hops Left count changing as it is something is attenuating (signal sucker) the Insteon signal or generating noise. If there are no appliances On now that were not On before, if there is no other electronic equipment powered from the same circuit as the PLM, turn all the circuit breakers Off except the one that powers the ISY and PLM. If any of the other Insteon devices are also powered at this point see if communication is reliable to those devices. If no other Insteon device is powered turn On one breaker that has other Insteon device(s) installed and see if reliable communication is possible. By process of elimination the source of the problem may be identified. Unfortunately there is no magic bullet, no simple test that will find the source of the problem. I’ve covered the common sources in the previous posts.

Run Tools | Diagnostics | Event Viwer with Level 3, run the Scene test and post the results. Include in the posted trace a LampLinc On/Off with the Admin Console of one of the failing devices.

Look for a source of interference common to both 120v legs. Any PC/UPS/AV equipment on the same circuit as the PLM? Power supplies in these devices are common sources of signal attenuation or noise. CFLs, fluorescent lighting, are another source. Run Tools | Diagnostics | Event Viewer with Level 3 selected. Send some traffic to the various devices and look at the Hops Left Count compared to the Max Hops count. A differential of 1 between Max Hops and Hops Left count is good communication. A Hops Left of 1 or 0 when Max Hops is 3 indicates communication at the end of the reliability scale. Also a varying Hops Left count communicating with the same device indicates a communications problem.

Look for something that was turned On during that time frame. Or perhaps turned Off if phase coupling has not been implemented.

Never feel bad about asking a question!

No. LED Brightness controls the brightness of the LED status lights on the left side of the SwitchLinc.