LeeG

Take a look at this old topic. It has Program examples viewtopic.php?f=26&t=9132&hilit=count+variable

The ApplianceLinc is a Responder Only device. It does have the Controller function to notify the ISY when it is turned On or Off manually at the ApplianceLinc. Same with an OutletLinc Relay so that will not be an alternative. Could control the standard outlet with something like a SwitchLinc Relay. The SwitchLinc Relay does notify the ISY when the SwitchLinc paddle is operated locally.

"To me, it makes more sense for the condition of a folder to evaluated whenever one its programs is triggered by a state change." That may make more sense to you but that is NOT the way it works. If the Folder condition does not allow Programs to run/trigger (Folder is False) the Programs do no trigger on their own. The Programs do not trigger even if the Program has an 'If State Variable' and the State variable value is changed because a Folder with a False state prevents Programs below it from running. That is one of the functions of a Folder, establish a set of conditions that control whether the underlying Programs can or cannot be triggered. I don't know what happens at reboot with a Folder testing an Integer variable. Since the If condition makes no sense I've not tested what happens with that scenario. It is pretty easy, simply look at the Folder condition after the ISY reboots. EDIT: take a look at this Wiki link. It covers Folder conditions in detail http://wiki.universal-devices.com/index ... tion_Order

Teken Is the sensor with the low battery the one that is linked to the Smoke Bridge?

There should be 7 nodes for the Smoke Bridge. What ISY level are you running? It was one of the 4.0.x images that added all the nodes and set up the correct link records.

A Folder has to be triggered to have the If section execute just as a Program does. Using 'If integer variable' does not cause the Folder to be triggered when the Integer variable value is changed. The Folder condition (true or false) does not change when the Integer variable value is changed because changing an Integer variable value does not trigger a Folder or Program. That is what differentiates an Integer variable from a State variable. Changing the value of a State variable will cause a Folder or Program trigger (run) and the If evaluated. Changing the value of an Integer DOES NOT cause a Folder or Program to trigger. There is an entire forum category dedicated to Variables. The first topic describes Variables and explains the only difference between State and Integer Variables is State variable change triggers Folder/Program, Integer does not.

Unfortunately not. Although it would take up more buttons using On to start the Repeat loop (rather than Fade Up) and Off to stop the loop (rather than Fade Stop) would allow as much time as needed to adjust volume.

If checking the Integer variable is the only thing in the Folder (or Program) If section changing the value of an Integer variable does not cause a Folder or Program to trigger. Has to be a State variable or something else in the IF must be coded to cause the Folder or Program to trigger. Once triggered the Integer variable value can affect the True/False state but does not cause a trigger by itself.

Use some number in the Repeat that will bring it out of the Repeat loop in case there is a comm problem and the Fade Stop is not received. When the Fade Stop occurs the If is reevaluated to False running the Else clause and ending the Repeat loop. Be careful not to hold the button too long as the device will enter linking mode in about 10 seconds. If Control 'RermoteLinc2 - 4 Scene - C' is switched Fade Up And Control 'RermoteLinc2 - 4 Scene - C' is not switched Fade Stop Then Repeat 50 times Send X10 'A1/All Lights Off (1)' Else - No Actions - (To add one, press 'Action')

The top information is for 4.0.4. The release date and list of changes applies to 4.0.4. Only the line that says 4.0.3 was missed.

My understanding of wired Dual Band operation is exactly what Xathros described. If Dual Band devices all but eliminate Insteon Mesh network issues, the KPLs would be working. Certainly if the RF power levels allowed each Dual Band device to talk to all other Dual Band devices it might be but the RF power is low. There are too many network issues posted on various forums to think Dual Band technology is the solution to Insteon communication issues. Even the Access Point which has the best RF range says 200’ clear line of sight. Stick the RF inside a box (I won’t even talk about inside a metal box) with lots of wires, blocked by walls, floors, metal things, etc and that range drops off significantly.

Sorry, I have those. I thought these were 8 button KPLs.

How did you get Dual Band KPLs?

These are low power RF devices. Many things affect range, how much does the wiring in the box block the signal, what else is between the device and a receiving dual band device. It sounds like the KPLs are on different floors. That is a significant difference in what the RF signal has to pass through to get to the receiver. Easy to test the device in question, connect to an appliance cord and change the plug point. Just getting it out of the box in open air may improve RF communication.

"The scene B button on the primary keypadlinc works most of the time. The scene B button on the secondary keypadlinc works only about 10% of the time." There will always be some variation in transmission levels between devices. When nothing shows in the event viewer when a button is pressed it means 4 attempts by the device to notify the PLM have failed to arrive. This means comm with that circuit (with multiple devices on that circuit) is very poor at least at times. Depending on the Max Hops and Hops Left counts on the inbound messages when they do arrive, it will show if the problem is general with that circuit or intermittent which would suggest something that runs intermittently is interfering.

"get event viewer activity without the "Can't Comm" error, but the thermostat/scene does not change state...is this still a comm error?" If the event trace shows the Scene was executed it would likely be a comm problem. A Scene command in ISY does not have ACKs and no retries so they are normally first to see problems when comm is not reliable. "Cannot communicate" errors are usually on outbound direct commands that have ACKs and retries so the application knows when something is not ACKed. With intermittent missing inbound messages, problems with Responders in a Scene, and "cannot communicate" errors it sounds like comm issues.

MWareman This is a known problem. From the earlier post it looks like the calculator is lost. viewtopic.php?f=27&t=11350&p=86789&hilit=Calculator#p86789

"is there a way to program the keypad to not change a button's LED state based on the physical pushing of the button" No.

I have more sensors coming the end of the week (I hope) so I can test. I don't think multiple Smoke Bridge devices are needed. Based on the User Guide information I think any one sensor that trips will trip them all and the Smoke Bridge will receive the alarm indication. If it does not work that way I would hope the User Guide would specifically state that all sensors have to be linked to the Smoke Bridge. Is easy to test, link one sensor to the Smoke Bridge and trip another sensor.

I ran the same test on the latest 4.0.4 with the same results. I thought perhaps 3.3.10 was using a different command sequence to set the Local Ramp Rate but your trace and mine shows the ISY using the latest Extended command to change the Local Ramp Rate. Some older devices required the internal memory of the device to be updated with new Local values. The device did not pick up the change until a power cycle was done. To the question, just one of those things one learns over time. However, the new Extended command is being used to change the Local Ramp Rate of the FanLinc. It looks like the FanLinc was designed that way. Very odd as it is the only device using Extended commands that does not pick up the Local change immediately.

"What does it mean if I press the button and no activity shows on the event viewer?" There is likely a comm problem. There will be no ISY cannot communicate message. How would the ISY know if a button is pressed and the message does not make it to the PLM. Comm fail messages come from outbound messages that do not get a response. Hops Left=0 on inbound messages can be okay. Depends on the Max Hops=x count of the inbound message. Post the event trace.

Do not worry about the Show Device Links Table. The "Ramp Rate (applied locally)" slider is setting values internal to the FanLinc. Link records are not being used in the way the FanLinc Light is being tested. Do need to see the event trace of the commands that are executed when the "Ramp Rate (applied locally)" slider is moved to a new setting. There have been devices in the past that required a power cycle for the "Local" values to take effect. I'm pretty sure that when the FanLinc Light is being controlled with an external controller such as a KeypadLinc button or RemoteLinc2 button the FanLinc Light will be affected be the Ramp Rate changes without a power cycle as link records are controlling the Ramp Rate.

The ISY Replace xxxx With function requires the old and new device be the same basic type. A Dimmer cannot be replaced with a Relay and a Relay cannot be replaced with a Dimmer. There is no easy process available. Delete the old device and add the new device. Then add the new device to Scenes and Programs as necessary.

What Controller is being used to turn the FanLinc Light On (where Ramp Rate should have an effect)? Suggest running Tools | Diagnostics | Event Viewer at LEVEL 3. Use the Admin Console to change the Ramp Rate for the Controller being used to turn the FanLinc Light On. The value must be changed for the ISY to write a new value to the FanLinc. Post the event trace. Right click the FanLinc Light node, select Diagnostics | Show Device Links Table. Post the Show results.

Each Controller has a unique set of Responder values. If the Scene name was selected the Responder values that were set are associated with the PLM (when the Scene is used in a Program or from Admin Console). Select the KeypadLinc button node name below the Scene name (should be a Controller in Red) and set those Responder values. Then select the RL button node name below the Scene name (should also be a Controller in Red) and set those Responder values.