MikeD

Now I can change the ringtone in v4 with a program. Thanks for the tip! ~Mike

Sounds like the PLM is bad. Many have had this problem and there is a fix if you are handy with a soldering iron. http://forum.universal-devices.com/topic/13866-repair-of-2413s-plm-when-the-power-supply-fails/ ~Mike

I found this answer from Michel in a search. http://forum.universal-devices.com/topic/14915-isy-program-scene-memory-limitations/?p=125848 ~Mike

Hi Tim, I think the best place to start with variables is the wiki. http://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Integer_Variables You have to define your variables before using them in programs. Don't forget to hit 'Save' when adding your variables. Since posting those programs two years ago I have slightly changed how they are named. A good practice is to preceed the chosen variable name with "i." for Integer and "s." for State variables. Using this labling method will help you identify the variable in your programs. A change in value will cause a program to run when a State variable is used in the 'If' clause, and Integer variables will not. Another thing that really helped me was to log all the changes I make to my ISY in a text document. Make a backup of your ISY before you start and another after you are done making making changes for the day. Log everything chronologically in the text document. If I add a variable or add/modify a program it goes into the log. This way you know where you are when making changes. Along with the Schlage BE469 I use an Insteon Hidden Door Sensor to detect if the door is open or closed. If unlocked it will automatically lock itself as long as the door is closed. I did not want a situation where the door is left open and my SchlageTimeout program extends the lock's bolt. That would be bad. I noticed that you want the KPL button lit when the BE469 is locked. I use the opposite indication, a lit button means unlocked. Just reverse the logic to get the result you are looking for. Try creating and modifying your programs to suite your requirements and let us know if you have further questions or need clarification. ~Mike

This set of programs have served me well. I am able to lock/unlock from KPL, have it lock after 10 minutes if unlocked. Two different KPLs have one button, as Controllers, in the 'SchlageButton-A' Scene. http://forum.universal-devices.com/topic/14677-schlage-be469/page-2?do=findComment&comment=123297 ~Mike

You can use one program per person and write the user to a variable in v4. http://forum.universal-devices.com/topic/14677-schlage-be469/page-2?do=findComment&comment=123297 ~Mike

Not in the way I wrote my programs. If unlocked my 'SchlageTimeout' program will automatically lock it unless it is stopped by another KPL button that runs my 'SchlageTimeoutEnable' program or the door is left open. ~Mike

- My Schlage lock is not in the Scene. The lock is always controlled by one of my programs. Only the KPL buttons are in this Scene and they are both Controllers. - Yes, my KPL buttons are in toggle mode. Hope this helps! ~Mike

1. Because I can. 2. So do not have to go to the door and physically unlock it. ~Mike

Hi Gary, I have been using this set of programs for well over a year to notify me with push notifications to my iPhone via Prowl. http://forum.universal-devices.com/topic/14677-schlage-be469/?p=123297

The BE-469 auto-lock feature is disabled (default setting.) It can be enabled through programming at the lock.

Wow, that looks amazing. Nice job! ~Mike

See the second screenshot in post #5. Individual programs call individual notifications added in the Network Module / Resource Editor. I consolidated all my Schlage lock programs in one folder. ~Mike

The variables are based on what the Schlage lock is sending and are set in programs. The first program (shown below) shows that when the Schlage Lock has a Status of 'Access Code 1' and is 'Unlocked by Keypad' then the integer variables $i.SchlageLockedBy is cleared to zero, $i.SchlageUnLockedBy is set to 1 (Mary), the Scene for my KPL buttons is turned On, and the Resource 'SchlageMary' (shown in above post) is called. SchlageMary - [ID 0073][Parent 0076] If Status '.Z-Wave / ZW 006 Schlage Door Lock' is Access Code 1 And Control '.Z-Wave / ZW 006 Schlage Door Lock' is switched Unlocked by Keypad Then $i.SchlageLockedBy = 0 $i.SchlageUnLockedBy = 1 Set Scene 'Scenes / SchlageButton-A' On Resource 'SchlageMary' Else - No Actions - (To add one, press 'Action') The same method is use throughout the programs. I added a period between '$i' and the variable name since posting those programs to define the type of variable. Hope this explanation helps. ~Mike

For logging you can use ISYLogger. http://forum.universal-devices.com/forum/61-isylogger/ If you have an iPhone you can use Prowl for notifications. For a history you can run the Prowl app. This is what it looks like on an iPhone. It requires the ISY Network Module. I have created a separate resource for every notification, each called by their respective program. I believe Tasker is the equivalent for android. ~Mike

Hi Scott, The portal profile will work both at home on your local wifi and externally, however the local wifi will be noticibly slower compared to directly accessing on wifi. I am not aware of a way to have MobiLinc automatically change profiles. ~Mike

Jon, Thank you for this info. Worked perfectly. ~Mike

You can use something like my 'SchlageTimeout' program and set whatever timeout period you like. I use a 10 minute timeout period. http://forum.universal-devices.com/topic/14677-schlage-be469/?p=123297 ~Mike

Hi oberkc, I misspelled your username in my first response. My apologies! You and many other forum members endeavor to be very precise in explaining the logic of ISY programming and it is very much appreciated. I know it can be frustrating to someone new. ~Mike

Hi obertec, I guess it is just how you look at it. True that as you stated 'triggers' themselves have no logical condition. I mentioned the 'trigger' as an evaluation for the TIME and CONTROL condition. Thus running the THEN or ELSE clause as appropriate. I was just trying to say the same thing as you did a different way. Hope that makes sense! ~Mike

Hi Amigo, If From Sunset To Sunrise + 30 minutes (next day) And Control 'Outside / Front Door Motion Sensor-Sens' is switched On The trigger for TIME conditions are only evaluated for those two specific moments in time and not for the whole time period in between. Therefore would evaluate FALSE unless a 'Control On' is sent from the Motion Sensor at those two moments in time. -- Which would be highly unlikely to occur. The trigger for the CONTROL condition is valid during the whole TIME period. A 'Control On' sent from the Motion Sensor evaluates TRUE during this period and FALSE outside this period. ~Mike

Thanks for the motivational information. I have been thinking about replacing the IOLinc that controls my garage door with a Z-Wave controller for a while. I just ordered this Z-Wave garage door controller http://products.z-wavealliance.org/products/1298 from Amazon and will be replacing the IOLinc. According to the documentation it has the 'Z-Wave Plus' or 'Gen 5' chipset. Should be here on Friday for installation this weekend. ~Mike

After converting from several X-10 devices around the house back in 2012 I can honestly say I am very happy with Insteon (and Z-Wave). All the helpful information on this forum allowed me to do things I did not think was even possible. I am sure that the guidance provided on this forum also has kept me out of trouble. For instance there are a half dozen FilterLincs around my house, all put in place based on comments made here. ~Mike

Hi Mitch, I am sure you will quickly get everything configured and running this weekend. Glad I could help. ~Mike

I record the values as soon as they change and do not use the variables as a condition to trigger any programs so I just decided to use Integer variables. That said, State variables could be used in these programs as written and everything would still work the same way. ~Mike