stusviews

With separate programs, you can determine if all or only one thermostat is going out of heat mode. BTW, which thermostats are you using?

A problem is that the scene would turn the device off before the program has an opportunity to change the ramp rate.

A device can be a controller of only one scene. A solution is to use a program to turn the device on--setting the ramp rate appropriately. The program will, unfortunately, add a small delay. No program is needed for off.

When you convert from 6-button to 8-button, the designation of the buttons change. The On-button splits int o A & B, A becomes C, B becomes D., C & D become E & F, respectfully and the Off-button becomes G & H. You need to check each and every former scene involving each button. The easiest way to do that is to select each button and review the Membership panel located on the right side of the screen.

The easiest solution is to create a scene with the button as a controller and the light as a responder. Set the ramp rate to any duration up to 8 min. The ramp rate, BTW, is the time from full on (or off) to off (or full on). For example, if the ramp rate is set to 4 min. and the light On-level is at 50%, then it will take 2 min. to turn completely off. A 9 min. ramp rate is available to accommodate older devices. When used with current devices, the effective ramp rate is 0.1 sec.

http://forum.universal-devices.com/topic/18027-isy-portal-with-moblinc-and-http-while-within-home-wifi/

Although I haven't tested it, the latest portal update seems to allow up to five aliases for the same device.

Who gets the discount for the first three? The installer or the client?

If From xx:yy:zzPM To xx:yy:zzPM (next day) plus a trigger will repeat after you start it. Note that From and To are idential times.

Most Insteon devices including SwitchLincs and KeypadLincs can be responders for hundreds of controllers. But a device can be a controller of only one scene. If you can't add the SwitchLinc as a controller, then it must be a controller of a different scene. Select the SwitchLinc. View the a Membership panel on the right.

The current performance is not as fast as my Downey-Atlanta supercharged (DASC) BMW, but W W, I'm impressed. Thanks, Benoit.

Create a scene with both the main SwitchLinc and the button as a controller. In your program, control the scene. BTW, responses to scenes are immediate, programs may take a second or two.

Then statement(s) will turn on, wait a second, then turn on again and repeat unless you stop it. Then Repeat Every 1 second do what you want to do A BuzzLinc can be used as an audible alert.

What is the result if, under the same conditions, you view the thermostat from the Admin Console? Does the humidity value agree with the display? If not, does a query correct it? You actually don't have anything to trigger the program. A Status statement won't unless the state of the device changes or something triggers the program. A query can do that. BTW, if you want to streamline your program, then you can place "And Status 'Main Floor Thermostat - Main' is Mode Heat" as the first condition outside an all inclusive And ( ). instead of repeating that statement. Also, if the thermostat is in Heat mode, then the fan will be on, so that statement is unneeded. That won't change the way the program runs, so it's purely aesthetic

I accomplish something similar that with two programs for each possible mode, Cool, Heat, Auto and Program Auto plus a trigger program. The extra program is needed because setting the mode off ends the first program. The delay is to prevent all mode programs from running concurrently. Since you just want a hold you don't need a delay. Just add restart programs to Else. Dine Out HVAC If Place your trigger here Then Run Program 'LR Dine Out Cool 1' (If) Run Program 'LR Dine Out Heat 1' (If) Run Program 'BR Dine Out Auto 1' (If) Run Program 'BR Dine Out Prog 1' (If) Else - No Actions - (To add one, press 'Action') BR Dine Out Cool 1 [Not Enabled] If Status 'BR / Devices / BR Thermostat Main' is Mode Cool Then Wait 4 seconds Run Program 'BR Dine Out Cool 2' (Then Path) Else - No Actions - (To add one, press 'Action') BR Dine Out Cool 2 If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Set 'BR / Devices / BR Thermostat Main' Synchronize Clock Set 'BR / Devices / BR Thermostat Main' Mode Off Wait 1 hour Set 'BR / Devices / BR Thermostat Main' Mode Cool Else - No Actions - (To add one, press 'Action')

You are correct. The KeypadLinc is not wired to anything, so either the On/Off or the dimmer can be used. The On/Off clicks with each on or off button push, the dimmer doesn't.

I've never experienced a KPL secondary button change state due to an ALL ON.

Any post about anything abnormal is helpful

Do you mean that nothing in the log showed as being fully on or nothing seemed to trigger the event? Or both?

All of my All On events were visible in the log. Although I couldn't pinpoint the source, the devices being on at 100% was clearly recorded. Also, I added a 2 second delay to programs that involved MSs. Over time, I've not had a full All On, so I deleted the delays, also over time. I haven't had a repetition of the All On for several months.

Don't forget the set the Leak Sensor to dry. The method (mentioned in an earlier post) depends on the version of the sensor.

http://www.universal-devices.com/docs/production/ISY994%20Series%20Network%20Security%20Guide.pdf

A wet paper towel should be adequate to initiate a wet condition.

Does that mean that each time I add or change something in the portal that I need to forget devices before doing a discovery?