Xathros

In this scenario, I like the first solution better. Low temp detected, adjust the Stat, notify and then delay further action. The goal is to prevent the pipes from freezing. The second solution waits for however long it takes for the sensor bounce to stop + 30 minutes + however long it takes for the attic temp to recover from the increased heating. I think it would be best to act first then wait. Just my personal preference. -Xathros

Probably an Avast update along the way changed the way it was handling the ISY. Glad you got it working. -Xathros

Here is how I would do it: Program: BasementMotion If Control Motion1 is Switched On or Control Motion2 is Switched On or Control Motion3 is Switched On Then Set BasementLight On Wait 5 minutes Set basement Light Off Else This way, the lights will com on with any motion and stay on for 5 minutes after the last motion was detected. Adjust the 5 minute delay to suit your needs. You could add a second program to disable the motion detect program when the lights are manually operated as follows: Program: BasementMotionDisable If ( Control BasementSwitchlinc1 is Switched On or Control Basement Switchlinc2 is Switched On ) And ( Control BasementSwitchlinc1 is Not Switched Off and Control BasementSwitchlinc2 is Not Switched Off ) Then Disable Program BasementMotion Else Enable Program BasementMotion Hope this helps -Xathros

This is certainly not normal. What are you using for Antivirus and Firewall solutions? When you turn on or off lights (at the light) does the status of the light change in the admin console? If not, try disabling your AV/firewall and test. -Xathros

Hi mbrossart- I am assuming this is a V.43 firmware KPL. These newer KPLs are coming with a multicolor LED behind the set button. From the User manual: Error Blink Default = on This setting is adjustable via software or a central controller only. Keypad Dimmer LED blinks red for a few seconds if one or more responders do not acknowledge a message. LED Behavior Keypad has a dual-color green and red LED which momentarily indicates if a button press was successfully communicated to all scene members. LED State Meaning Blinks green once - One or more scene members acknowledge the button press. Blinks red once - One or more scene members did not acknowledge the button press (note: scene members may still have heard the scene command and adjusted their settings) This doesn't explain a constant steady red condition. If this wasn't happening on 2 different KPL's I would have said device failure. Do they operate properly aside from the red glow? I have one of these newer KPL's and don't notice any red glow even when the room is dark. -Xathros

Anytime! Happy to help. -Xathros

Hi Mike- As long as you don't want to track levels of dim, you could use two programs to accomplish this. If Control MotionDetector is Switched On Then Run Blink (If Path) Program Blink: (Disabled) If Status Light is On Then Repeat 2 times Set light Off Wait 1 Set light On Wait 1 Else Repeat 2 times Set light On Wait 1 Set light Off Wait 1 -Xathros EDITED: To reduce the number of programs and provide proper operation. EDITED Again for same reason.

I suspect the problem is switch bounce from the reed switch door sensor causing multiple On commands as the magnet moves past the switch. I bet your event viewer shows multiple DON messages from the sensor when the door opens. Adding a wait should help. Try this: If Control 'Garage Door Sensor' is switched On Then Wait 3 seconds Send Notification to 'Default' content 'Garage Door Opened' Else - No Actions - (To add one, press 'Action') This will filter out the bounces and you should only receive one notification. If you still get multiple, try increasing the wait to 6 seconds but I bet the 3 will resolve it. -Xathros

The 2411T is an IRLinc TX. I just added one of these over the weekend on FW 4.1.3 I don't believe there is any reason for this to fail on 4.1.1 I suspect that you have a comm issue where you are trying to link the 2411T. As mentioned above - reset the 2411T again and move closer to the PLM and try again. If needed, you can use an extension cord to plus the 2411T in closer to the PLM while keeping the device located near the equipment you are trying to control with it. If that works, then you will need to figure out the comm problem in the desired location. You didn't plug it into a surge suppressor did you? If so, you might try plugging the 2411T directly into the wall and try again. Your AV equipment and any surge suppressors should be behind a filterlinc to prevent them from interfering with insteon signals. -Xathros

The Ubi- Welcome to the UDI forums! The ability to operate on the local network is most likely the most important feature to this community. I would test the http request from the Ubi but dont want to send my credentials in the clear outside of my LAN. The ability to have Ubi speak on command is a close second on the priority scale for me. Once again, welcome. I look forward to working with the the Ubi team and getting things working with out automation projects. -Xathros Sent from my iPhone using Tapatalk

Yes. You will contact support with the UUID of both the old 99 and the new 994 and they will transfer your purchased modules at no additional charge. Often within minutes of the request. -Xathros Sent from my iPhone using Tapatalk

State changes to the dusk.dawn node take 3.5 minutes to flip. Put the sensor in the dark for at least 3.5 mins to test. -Xathros Sent from my iPhone using Tapatalk

Many use RF wireless IR Repeaters like: http://www.amazon.com/X10-Powermid-PM5900-Control-Extender/dp/B00023KG40/ref=sr_1_4?ie=UTF8&qid=1390510686&sr=8-4&keywords=remote+extender Locate the IR receiver where you want to use your remote and the RF receiver/IR Emitter at the ISY. -Xathros

Just curious for future reference why use status? Will this also change the variable if a program turns "on" and "off" one of the lights? "Status" will trigger the program whenever the status of the device changes. From off to On or On to off or to any dim level in between. Status will trigger if the device is manually operated, changed by a scene or directly commanded by a program as long as the device's status actually changes. Status will NOT trigger if a device is already on and is switched on again or off and switched off again. "Control", in contrast, will only trigger when a device is locally operated with its paddle and only for the specified control. For instance: If Control Kitchen_Counter is Switched On Will trigger if you walk up to the switch and tap the On portion of the paddle regardless of whether its already on or not. It will not trigger if you press the Off portion or if you press and hold to fade up or down or fast on/fast off - all of those have their own control events that can be specified. It also will not trigger if the device is commanded on by a linked scene or by a program. A control event only exists for that brief moment when you activate the control whereas a device always has a status. Example: If Time is 3:30Pm and Control Kitchen_Light is Switched On Then Do something Is quite unlikely to ever do anything because the likelihood of someone turning on the kitchen light at the exact second that is 3:30pm is quite low. If, however, we used status instead: If Time is 3:30Pm and Status Kitchen_Light is On Then Do something Then something will happen at 3:30PM if the kitchen light is on. Hope this helps. -Xathros

Hi brain shocker- Program: If Status kitchen island is on or Status valencel is on or Status kitchen pots is on or Status kitchen dining is on Then s.lights_ON = 1 Else s.lights_ON = 0 Should do what you want. The point is: use the "Status: of the devices rather than "Control". -Xathros

Lee- My v.43 KPLD has a multi color set button. A green blink after a button press means ack received. Multiple red flashes means no ack from what I've been able to figure. I don't know of the actual button LED also shows extra blinks when no ack is received. I will have to do some additional testing to find out for sure. -Xathros

Device read/write to variables is not yet supported. The ver 5.x firmwares will contain those enhancements. -Xathros

This sure sounds like a bug in the v.43 KPL firmware to me. I have seen several reports of odd NonToggle behavior on the new KPL's. There may have even been an adjustment made for them in the latest 4.1.2 ISY firmware. -Xathros

This sure sounds to me like the location is unable to communicate with the PLM. Try placing the outletlinc on an appliance cord and plugging that in near the PLM. Do you have any access points bridging the phases of your electrical system? -Xathros

Possibly. The PLM is designed for 60Hz AC systems. It uses the AC waveform for timing. The RF transmissions are resynced to the AC timing on reception. I'm unsure if any of this will work on a 50Hz power system. Some Smarthome modules state 50/60Hz in their specs - the PLM says 60Hz. Also keep in mind that the 2413S PLM is only offered for US RF bands. It will not work with RF modules for the EU or other locales. -Xathros

Your VB script could call a /rest command to set a variable in the ISY. Something like: http://:@/rest/vars/set/2// -Xathros

Try this: If Control BedroomSwitch is switched On and Control BedroomSwitch is NOT switched FastOn Then Wait 30 minutes Set BedroomSwitch Off Else This way, the timer will run if the light is switched on normally and will reset if switched on again. If you FastOn, the timer will be avoided or aborted if already running. -Xathros

tkohler- I had edited my post after you saw it apparently. Absolutely no point in checking the status before changing the status. You can certainly move the On and Off into one program as follows: If Time is From 3:30:00PM to 9:30:00PM (Same Day) Then Set 'WH On-Off Module' On Else Set 'WH On-Off Module' Off Use a second program to check the status as I posted previously. -Xathros

The way this program is written (assuming that the notifications deliver) you will receive a notification every time the water heater turns on (not just at 3:30) or Off (except at 3:30). This is because the program is triggered every time the status of the water heater changes. The Else is evaluated and if it evaluates false, the else runs. This will evaluate False any time the WH turns Off except at 3:30 and every time it turns On. At 3:30, the Then clause runs, the WH turns on, the Status changes, the if re-evaluates and the else clause runs and you get notified. A separate program like: If Time is 3:30:01PM And Status 'WH On-Off Module' is Off Then Send Notification to 'Terry's All' content 'WH Status' Else Should do what you want. -Xathros