Xathros

It will prompt you automatically when a new Official Release is available. Beyond that, not automated and no notifications for beta versions of which there are many between official releases. I have probably run nearly 50 beta ISY versions and never had a problem that made me roll back. -Xathros

Any Insteon dimmer or Zwave Dimmer will offer both local dimming capability and remote control. No need to add any additional devices with either one. Adding a micro relay to a manual dimmer switch will get remote on/off and local dimming only. Why not have on/off/dim local AND remote? -Xathros

http://www.smarthome.com/insteon-2443-222-micro-on-off-module.html -Xathros

From the specs section on the page linked above: Operating Temperature Range: Indoor / Outdoor, 0 to 120°F. Note: PIR reliability may vary with temperature -Xathros Not an IOLinc, A MicroOnOff module with Sense. -Xathros

In that case, you don't want the WiFi proximity solution either as that will tell you when his phone/device is on your network, not when he is in that room specifically. I think using your motion detector with a smart delays makes more sense. I do something very similar-ish in my basement laundry area which also leads to my basement exit. I want the light to come on when motion is detected in the area but turn off in 30 secs if no additional motion. This way if I just walk in the door to head upstairs, the light will shut off after 30 secs. If i'm working at the laundry in the evening, I can be still enough to be in the dark after the initial 30 seconds. If there is enough initial motion detected, it bumps the timeout up to 5 min with a reset the counter with continued motion. Very hard to stay in that location and not trigger motion at least once every 5 mins. In the below example, you will have to trigger motion in the boy's room 8 times within a 2 minute period for the stat to turn up. Once that happens it will stay up as long as there continues to be motion at least once in a 20 minute period. Thermostat will set back again 20 min after last motion detected. This way, as long as you don't have more than 7 random triggers in a 2 min period, the stat won't turn up. This example assumes that the motion sensor is using sensing mode. Define a state variable: s.BoyRmMotionCnt. Init value: -1 Program: BoyRmCntMotion If Control 'BoyRmMS_Sensor' is Switched On And $s.BoyRmMotionCnt < 8 (Will need to experiment for this value. Depends on MS sensing more and timeout config) Then $s.BoyRmMotionCnt += 1 Wait 2 minutes $s.BoyRmMotionCnt = 0 Ese Program: BoyRmTurnUpHeat If $s.BoyRmMotionCnt >=8 (Will need to experiment for this value. Depends on MS sensing more and timeout config) Then Set 'BoyRmTS_Heat Setpoint' to 70 s.BoyRmMotionCnt = 29 (This will be the number of minutes the heat will stay on without additional motion detected plus the Off count value in the last program. 20 min in this example.) Else Program: BoyRmHeatRun If $s.BoyRmMotionCnt > 9 (This value should be one greater than the minimum motion count used in the above 2 programs.) Then Wait 1 Minute $s.BoyRmMotionCnt -= 1 Else $s.BoyRmMotionCnt = 0 Set 'BoyRmTS_Heat_Setpoint' to 60 NOTE: You should place the following line in the then section of a program that runs at ISY startup. This will ensure that the heat does not stay turned up if the ISY were to restart during a heat run. $s.BoyRmMotionCnt = 0 This will change the value from the init value of -1 and force the last program to set back the heat. I hope this proves useful. -Xathros

Reboot the ISY then issue a File / Restore PLM from the admin console. -Xathros Sent from my iPhone using Tapatalk

Actually, now you've got me thinking about this, maybe all the OP needs is to insert a short delay between motion detection and ISY action preventing the need for proximity detection. -Xathros Sent from my iPhone using Tapatalk

Don't think that solution works here unfortunately. -Xathros Sent from my iPhone using Tapatalk

Many of us use WiFi proximity in ways like this. This long thread describes how I and some others do it: http://forum.universal-devices.com/topic/9172-howto-proximity-notification-wifi-phone-ipad-laptop/?hl=%2Bwifi+%2Bproximity Enjoy! It's a long read. -Xathros

The wireless stat also has to conserve energy to prolong battery life. The wired one need not worry about that. -Xathros

I certainly have no idea why your program folders have the blues. I have yet to see that on either of my ISYs. As for the socket errors - don't worry. I believe they are unrelated to the backup process. I see this as well. You and I both have l network connections to the ISY from external devices making frequent calls and these can suffer when the ISY is busy doing other things (like backing up). The console will throw up a notice about these failures. The backup should still be progressing underneath the error dialog. If you stop those external devices from connecting and backup again, you should see few to none of those errors. In no case have these messages resulted in a bad backup (or restore) for me. -Xathros

I believe the Ramp Rate is really what you want. Set on level and ramp rate in the scene and just use Scene On and Scene Off in the program. -Xathros

Thats more or less what I'm doing with my Venstar T1800 stat. It runs on 24v from my furnace. ISY monitors the temp as reported by the stat and uses that info to control my Pellet stove via a relay. -Xathros

Yep. Sure can. Here is how I would do this: (LeeG started down this road above) 2 Scenes: GarageOpen and GarageClosed. GarageOpen has 2 KPL Buttons (G & H) as responders only. Button H has it's OnLevel set to 0% Button G has It's OnLevel Set to 100% GarageClosed has 2 KPL Buttons (G & H) as responders only. Button H has it's OnLevel set to 100% Button G has It's OnLevel Set to 0% Then a program to deal with them: If Status 'GarageDoor IOLinc Sensor' is On Then Set Scene 'GarageOpen' On Else Set Scene 'GarageClosed' On Depending on the type of mag switch used, you may need to swap the contents of Then and Else above. Or swap your definition of G & H ): Added value here: You can use the True/False value of the above program in other programs that may need to know the status of the garage door. Hope that works for you. -Xathros

You are correct. You can use the same 12V supply that yu power the DinRelay with and simply switch it through one of the relays for the amp. I would use NC and Com and switch the positive side with the relay. I suspect the amp will want a certain polarity but without additional data cant say much more about that. -Xathros

He upgraded from a 99 to a 994. ZWave is not available for the 99. -Xathros

Simply setting a variable at the same time as I send a command to the relay. As far as I know, there is no way to query the relay state. You are welcome to quote me. -Xathros Sent from my iPhone using Tapatalk

I printed my own as well. I don't think they look quite as nice as the custom etched buttons can but at least all of mine are the same color. And, yes, you can still do it this way. -Xathros Sent from my iPhone using Tapatalk

Congrats! I thought I was there 4 years ago but these damn Black and Decker X10 weather proof relay modules keep finding their way back to my seasonal exterior lighting. Just can't bring myself to spend the $90+ to replace them with the outdoor appliance modules since they still work so well. -Xathros

I don't know for sure but I bet thats it. -Xathros

I should have caught that! -Xathros

You are missing more than just setpoint up/dn, also missing schedule and options buttons. Are you sure they just aren't off the screen? you screen shot does not include the very bottom of the interface where the buttons appear for me. -Xathros

If the button is a controller of a scene, you can't. Remove the button from the scene and use programs to activate the various scenes based on the type of button press instead. -Xathros

Anytime. Happy to help. -Xathros

Exactly What that does is any time the button is pushed, it checks the sensor state (variable value) and sets the button LED accordingly. Sensor on, LED on, sensor off, LED off. The program is triggers when the button is turned on or off and uses the value of the integer variable to decide the LED state. The variable is managed by the first program. NOTE: The variable in this case is an integer variable AND the button LED is also responder in a scene controlled by the sensor. Make sense? -Xathros