MikeD

Hi Mike, This will send a text when your garage door closes. If Control 'Ashley_Garage_Door-Sensor' is switched On Then Send Notification to 'Text' content 'GarageClosed' Else - No Actions - (To add one, press 'Action') ~Mike

Hi Waketech, This will be somewhat lengthy however I hope it will be beneficial to others. I basically use two integer variables, $iSchlageLockedBy and $iSchlageUnlockedBy to track everything. The variables are change whenever an action is reported by the lock. Here is one of my user programs that sets the variables, turns on a Scene (button on a few KeypadLincs) and sends a Notification via Prowl. 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 $iSchlageLockedBy = 0 $iSchlageUnLockedBy = 1 Set Scene 'Scenes / SchlageButton-A' On Resource 'SchlageMary' Else - No Actions - (To add one, press 'Action') 'SchlageButtonA' program that controls the lock from a KeypadLinc button. If Control 'Living Room Wall / A-Schlage Lock' is switched On And Control 'Living Room Wall / A-Schlage Lock' is not switched Off Or ( Control 'Mike Bedside KPL / A-Schlage Lock' is switched On And Control 'Mike Bedside KPL / A-Schlage Lock' is not switched Off ) Then Set '.Z-Wave / ZW 006 Schlage Door Lock' Unlock $iSchlageLockedBy = 0 $iSchlageUnLockedBy = 55 Resource 'SchlageKPLUnLock' Else Set '.Z-Wave / ZW 006 Schlage Door Lock' Lock $iSchlageLockedBy = 3 Set Scene 'Scenes / SchlageUnlock' Off Stop program 'SchlageTimeout' Resource 'SchlageKPLLock' 'SchlageTimeout' (Disabled) program that locks the front door with exceptions noted. If Status '.Z-Wave / ZW 006 Schlage Door Lock' is Unlocked Then Wait 10 minutes Set '.Z-Wave / ZW 006 Schlage Door Lock' Lock $iSchlageLockedBy = 555 Set Scene 'Scenes / SchlageButton-A' Off Resource 'SchlageTimeout' Else - No Actions - (To add one, press 'Action') NOTES: *Must Remain DISABLED otherwise 10 minute time period starts as soon as door is unlocked.* Called by SchlageTimeoutEnable If LRWallKPL-B is Off. Stopped by FrontDoor program and resets upon every door closure. Stopped by SchlageLockedInside and SchlageLockedOutside programs. 'SchlageTimeoutEnable' program. I use a State variable called $sSchalgeTimeoutEnabled. (Another program is triggered when the state of this variable changes and Notifies me via Prowl.) If Status 'Living Room Wall / B-Disable Lock' is Off Then $sSchlageTimeoutEnabled = 1 Wait 5 seconds Run Program 'SchlageTimeout' (If) Else $sSchlageTimeoutEnabled = 0 Stop program 'SchlageTimeout' NOTES: Called by FrontDoor program. LRWallKPL-B Status: On: Prevents FrontDoor from locking after 10 minutes. Off: Calls SchlageTimeout(If) program, that will lock the FrontDoor unless reopened within 10 minutes. 'FrontDoor' program. If Status 'z-Door Sensors / Front Door' is 100% Then Resource 'FrontDrSensorOpen' Stop program 'SchlageTimeout' Else Resource 'FrontDrSensorClosed' Run Program 'SchlageTimeoutEnable' (If) NOTES: Stops SchlageTimeout when evaluated True and Runs SchlageTimeoutEnable when evaluated False. Front Door will automatically re-lock after closure when parameters if LRWallKPL-B is Off. LRWallKPL-B disables SchlageTimeout if On in SchlageTimeoutEnable program. 'SchlageLockedInside' program. If Control '.Z-Wave / ZW 006 Schlage Door Lock' is switched Key/Manually Locked Then $iSchlageLockedBy = 1 Set Scene 'Scenes / SchlageButton-A' Off Wait 1 second Set Scene 'Scenes / SchlageUnlock' Off Stop program 'SchlageTimeout' Resource 'SchlageLockedInside' Else - No Actions - (To add one, press 'Action') 'SchlageLockedOutside' program. If Control '.Z-Wave / ZW 006 Schlage Door Lock' is switched Locked by Keypad Then $iSchlageLockedBy = 2 Set Scene 'Scenes / SchlageButton-A' Off Wait 1 second Set Scene 'Scenes / SchlageUnlock' Off Stop program 'SchlageTimeout' Resource 'SchlageLockedOutside' Else - No Actions - (To add one, press 'Action') 'SchlageManualUnlocked' program. If Control '.Z-Wave / ZW 006 Schlage Door Lock' is switched Key/Manually Unlocked Then $iSchlageUnLockedBy = 0 $iSchlageLockedBy = 0 Set Scene 'Scenes / SchlageButton-A' On Resource 'SchlageManualUnLocked' Else - No Actions - (To add one, press 'Action') 'SchlageTamper' program. If Control '.Z-Wave / ZW 006 Schlage Door Lock' is switched Tamper Code Entry Limit Then $iSchlageLockedBy = 999 $iSchlageUnLockedBy = 999 Resource 'SchlageTamper' Send Notification to 'Michael' content 'SchlageTamper' Else - No Actions - (To add one, press 'Action') Here are my variable definitions. iSchlageUnLockedBy --------------------- 999 = Tamper Alarm 55 = Insteon Keypad 0 = Manually UNLOCKED 1 = Mary 2 = Michael 3 = Janet 4 = Tina 5 = Joe 6 = Alice iSchlageLockedBy ------------------------------------ 999 = Tamper Alarm 0 = Reset when UNLOCKed by Keypad or Manually UNLOCKED 1 = Manually LOCKED from inside 2 = LOCKED by Outside Schlage button 3 = LOCKED by Insteon Keypad 4 = LOCKED by KPLAllOffButton Program 555 = LOCKED by SchlageTimeout Program I also have two other programs to send a notification if the lock is Not Responding or Jammed. ~Mike

Hi Teken, I installed this lock on my front door back in April and am very happy with it's operation. I did change the batteries after 6 months. The battery level reported was at 86% as I recall. At 86% the internal motor does 'sound' just a bit slower as it moves the bolt. I was leaving for a week and did not want any issues since my family did not accompany me on the trip. With new batteries installed on October 16 and an average of 15 motorized lock/unlock actions per day the battery level is 99% today. I use ISYLogger to record the date/time/user-number that unlocks via keypad. Other actions such as manually locking/unlocking from inside, locking from outside with the Schlage button, locking/unlocking from a KeypadLinc button, and locking after a timeout via program are also logged. I also use Prowl via the Network Module to notify me in real time of the above actions. The only negative I can think of is the number pad is a little difficult to read in direct sunlight but other than that it is perfect! ~Mike

It can be controlled by the iOS version of MobiLinc, do not know about android version.

Hi Brian, I have their 3801HGV Gateway and it serves as the DSL interface with built-in router and 802.11g wifi. I had my own ASUS router with operational dual-band 802.11n wifi networks when I switched over from Comcast in August 2013 and just placed the ASUS behind the AT&T Gateway. I always usd 8.8.8.8 and 8.8.4.4 for primary and secondary DNS server addresses in the ASUS so maybe that is why I did not experience any downtime during this transition to Frontier. I just checked the 3801 and they have primary DNS set to 99.99.99.53 and secondary at 99.99.99.153. Don't know if they are valid and they are not changable by the user. My suggestion would be to place your own router behind their equipment. In the 3801 they have a setting to add a 'Cascaded Router' however I did not enable that and used what they called 'pinholes' to port-forward the ports I needed. ~Mike

Hi smokegub, To write updates to the door sensor it has to be in linking mode. Here is the Hidden Door Sensor linking procedure I follow. When you press and hold the Set button the first time the LED starts flashing. While in this mode you can link it to your ISY, write changes to the Door Sensor, include it in Scenes and Programs, and Query it. To exit linking mode you do not have to wait for the LED to stop flashing, it is a two step process. 1. Press the Set button again and the LED will continue to flash but at a different rate. I believe this is referred to as the unlinking mode, this mode is not used in the setup with your ISY and can be ignored. 2. Press the Set button one more time to exit. The LED should be completely off at this point. Once the Door Sensor is out of linking mode it is a one way communicating device, sending Open/Close, Heartbeat, and Battery Status information to your ISY. It cannot receive any changes until it is placed in linking mode again. Hope this helps clarify linking mode for you. ~Mike

Hi Michel, Email sent with Query results and Topology attachments. Thank you, ~Mike

Hi Eric, Try If Control 'Sitting Room / Sitting KPL (DB) Lights' is switched Off Then Set Scene 'Sitting Room / Sitting Room Dim KPL' Off Else - No Actions - (To add one, press 'Action') ~Mike

That is the way it should be. Bug? ~Mike

Hi Michel, Unfortunately if I clicked the + button you would not be able to see all my devices on one screen. I did check on my last ISY restart and there were no devices with green 1011 icons. Can you explain why my Hidden Door Sensors are queried during the '3 AM Query All' given the information in the last few posts? Are they so different than a Leak Sensor that is not included in the Query All? Thank you, ~Mike

Hi Xathros, Query at startup produces the same System Busy and Event Viewer results. I have a Hidden Door Sensor startup program configured to run at ISY startup. It is very similar to the Leak Sensor startup program that many here are running. If $iDoorSensorStartup is 0 Then Run Program 'FrontDoorHeartbeat' (Then Path) Run Program 'InsideGarageDrHeartbeat' (Then Path) Run Program 'UpperPatioDrHeartbeat' (Then Path) Run Program 'LowerPatioDrHeartbeat' (Then Path) Wait 2 seconds $iDoorSensorStartup = 1 Else - No Actions - (To add one, press 'Action') Each Heartbeat program is similar to this one below and is a status of 'Running Then' after ISY restart. If Control 'z-Door Sensors / Front Door / Front Door - Heartbeat' is switched On Or Control 'z-Door Sensors / Front Door / Front Door - Heartbeat' is switched Off Then $iFrontDoorMissedHB = 0 Wait 48 hours Resource 'FrontDrSensorNotResponding' $iFrontDoorMissedHB = 1 Else - No Actions - (To add one, press 'Action') None of the programs associated with my Hidden Door Sensors, including the one that checks the Status (Post #6) changed the time displayed in the 'Last Run Time' column on the Programs / Summary tab when I ran Query All (Then Path) a few minutes ago. ~Mike

Hi Xathros, Thanks for the suggestions. Query at Restart and Wait while busy reading were the only ones that were checked. I first unchecked Wait while busy reading and rebooted - that did not help. Unchecking Query at Restart did solve the System Busy problem on boot up however I think that is a questionable solution. My next question I have (for Michel) is why don't the Leak Sensors exhibit the same symptoms on ISY restart, since I also check the Status of their Wet node in an If statement? ~Mike

Yes, and that must be why the Query at Restart? If Status 'z-Door Sensors / Front Door' is On Then Resource 'FrontDrSensorOpen' Else Resource 'FrontDrSensorClosed' ~Mike

Hi Michel, I rebooted the ISY again just to make sure, no green icons. 2B.0D.E1 is the Inside Garage Door sensor 2B.0F.03 is the Front Door sensor Attached is a screen shot of the System Busy in progress. ~Mike

Hi all, For some unknown reason my Z-Wave dongle was not responding this morning. I was getting updates from my devices if queried but just had a "! Z-Wave dongle not responding" selection from the pull-down in the admin console. I rebooted the ISY and everything is back to normal. However this bothered me... Every time I cold-boot the ISY it takes about 5 minutes to completely come back up with System Busy in the lower left corner of the admin console (where you normally see Ready) and a System Busy dialog box with a progress bar continually going from left to right over and over. I thought to bring up the Event Viewer at level 3 to try and see what was happening. Below is a portion of the capture that indicates communications with my Hidden Door Sensors. I have 4 of these sensors installed and looking at the log it appears they are the cause of my LONG boot-up time. Can anyone explain what is going on and why this is happening? Is anyone else that has (2845-222) Insteon Hidden Door Sensors experiencing this? Thanks ~Mike --- ISY Boot-up --- --- Did not catch preceding ISY log events from start of boot process --- --- These are all (2845-222) Insteon Hidden Door Sensors v.43 --- Mon 09/29/2014 02:00:04 PM : [INST-TX-I2CS] 02 62 2B 0B 70 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 Mon 09/29/2014 02:00:04 PM : [INST-ACK ] 02 62 2B.0B.70 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 06 (00) Mon 09/29/2014 02:00:13 PM : [INST-TX-I2CS] 02 62 2B 0B 70 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 Mon 09/29/2014 02:00:13 PM : [INST-ACK ] 02 62 2B.0B.70 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 06 (00) Mon 09/29/2014 02:00:22 PM : [INST-TX-I2CS] 02 62 2B 0B 70 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 Mon 09/29/2014 02:00:22 PM : [INST-ACK ] 02 62 2B.0B.70 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 06 (00) Mon 09/29/2014 02:00:26 PM : [INST-TX-I2CS] 02 62 2B 0B 70 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 Mon 09/29/2014 02:00:26 PM : [INST-ACK ] 02 62 2B.0B.70 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 06 (00) Mon 09/29/2014 02:00:35 PM : [INST-TX-I2CS] 02 62 2B 0B 70 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 Mon 09/29/2014 02:00:35 PM : [INST-ACK ] 02 62 2B.0B.70 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 06 (00) Mon 09/29/2014 02:00:44 PM : [INST-TX-I2CS] 02 62 2B 0B 70 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 Mon 09/29/2014 02:00:44 PM : [INST-ACK ] 02 62 2B.0B.70 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 06 (00) Mon 09/29/2014 02:00:48 PM : [INST-TX-I2CS] 02 62 2B 0D E1 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 Mon 09/29/2014 02:00:48 PM : [INST-ACK ] 02 62 2B.0D.E1 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 06 (00) Mon 09/29/2014 02:00:57 PM : [INST-TX-I2CS] 02 62 2B 0D E1 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 Mon 09/29/2014 02:00:57 PM : [INST-ACK ] 02 62 2B.0D.E1 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 06 (00) Mon 09/29/2014 02:01:06 PM : [INST-TX-I2CS] 02 62 2B 0D E1 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 Mon 09/29/2014 02:01:06 PM : [INST-ACK ] 02 62 2B.0D.E1 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 06 (00) Mon 09/29/2014 02:01:10 PM : [INST-TX-I2CS] 02 62 2B 0D E1 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 Mon 09/29/2014 02:01:10 PM : [INST-ACK ] 02 62 2B.0D.E1 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 06 (00) Mon 09/29/2014 02:01:19 PM : [INST-TX-I2CS] 02 62 2B 0D E1 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 Mon 09/29/2014 02:01:19 PM : [INST-ACK ] 02 62 2B.0D.E1 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 06 (00) Mon 09/29/2014 02:01:28 PM : [INST-TX-I2CS] 02 62 2B 0D E1 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 Mon 09/29/2014 02:01:28 PM : [INST-ACK ] 02 62 2B.0D.E1 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 06 (00) Mon 09/29/2014 02:01:32 PM : [INST-TX-I2CS] 02 62 2B 0D E1 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 Mon 09/29/2014 02:01:32 PM : [INST-ACK ] 02 62 2B.0D.E1 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 06 (00) Mon 09/29/2014 02:01:41 PM : [INST-TX-I2CS] 02 62 2B 0D E1 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 Mon 09/29/2014 02:01:41 PM : [INST-ACK ] 02 62 2B.0D.E1 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 06 (00) Mon 09/29/2014 02:01:50 PM : [INST-TX-I2CS] 02 62 2B 0D E1 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 Mon 09/29/2014 02:01:50 PM : [INST-ACK ] 02 62 2B.0D.E1 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 06 (00) Mon 09/29/2014 02:01:54 PM : [INST-TX-I2CS] 02 62 2B 0F 03 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 Mon 09/29/2014 02:01:54 PM : [INST-ACK ] 02 62 2B.0F.03 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 06 (00) Mon 09/29/2014 02:02:03 PM : [INST-TX-I2CS] 02 62 2B 0F 03 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 Mon 09/29/2014 02:02:03 PM : [INST-ACK ] 02 62 2B.0F.03 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 06 (00) --- Some Z-Wave comms were here (Removed) --- Mon 09/29/2014 02:02:12 PM : [INST-TX-I2CS] 02 62 2B 0F 03 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 Mon 09/29/2014 02:02:12 PM : [INST-ACK ] 02 62 2B.0F.03 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 06 (00) Mon 09/29/2014 02:02:16 PM : [INST-TX-I2CS] 02 62 2B 0F 03 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 Mon 09/29/2014 02:02:16 PM : [INST-ACK ] 02 62 2B.0F.03 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 06 (00) Mon 09/29/2014 02:02:25 PM : [INST-TX-I2CS] 02 62 2B 0F 03 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 Mon 09/29/2014 02:02:25 PM : [INST-ACK ] 02 62 2B.0F.03 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 06 (00) Mon 09/29/2014 02:02:34 PM : [INST-TX-I2CS] 02 62 2B 0F 03 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 Mon 09/29/2014 02:02:34 PM : [INST-ACK ] 02 62 2B.0F.03 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 06 (00) Mon 09/29/2014 02:02:38 PM : [INST-TX-I2CS] 02 62 2B 0F 03 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 Mon 09/29/2014 02:02:38 PM : [INST-ACK ] 02 62 2B.0F.03 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 06 (00) Mon 09/29/2014 02:02:47 PM : [INST-TX-I2CS] 02 62 2B 0F 03 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 Mon 09/29/2014 02:02:47 PM : [INST-ACK ] 02 62 2B.0F.03 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 06 (00) Mon 09/29/2014 02:02:56 PM : [INST-TX-I2CS] 02 62 2B 0F 03 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 Mon 09/29/2014 02:02:56 PM : [INST-ACK ] 02 62 2B.0F.03 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 06 (00) --- More Z-Wave / Insteon comms were here (Removed) --- Mon 09/29/2014 02:03:21 PM : [ Time] 14:03:21 0(0) --- ISY completed boot process ---

That is exactly how I handled it for use with MobiLinc except I just use a 1 second Wait. ~Mike

I have this thermostat also and it has performed flawlessly since installed back in April. Cannot comment on the range, it is only 6 feet away from my ISY through one interior wall. ~Mike

Hi Eric, Yes, unfortunately that is the only way to get it to show an Off status. If you reboot the ISY the status will remain blank until the battery runs low again and it sends an On condition. ~Mike

Hi Xathros, No, it does not clear after an open/close but still indicates On for a Low Battery condition. I do not believe it will clear evey after 24 hours since the Low Battery node is normally blank, after ISY boot, until a Low Battery condition. It never shows a status of Off. ~Mike

Hi Eric, You could use set an integer variable to 1 (initialized to 0) when "Control 'Basement Door.3 - Low Battery' is switched On" is detected. A second program could check the value of the variable at a specific time of day you choose, then notify you if the variable=1. You would have to reset the variable to 0 after replacing the battery. Use a separate variable for each Door Sensor, this way you can identify the one sending the notification. I just replaced the battery in one of my Door Sensors and tried to clear the 'On' state of the Low Battery node with a Query however that bug has not been fixed. See http://forum.universal-devices.com/topic/11480-2845-222-hidden-door-sensor/?p=111876 posts 104 - 108. Therefore I still use Control rather than Status to detect a Low Battery condition. The solution from Xathros above can also work as long as you put the sensor in linking mode and Query the device so it responds with the correct state after replacing the battery. ~Mike

You will need to be at firmware v4.2.3 or higher, recommend you just go right to v4.2.10. The Heartbeat and Low Battery nodes will appear after you re-add them. For the low battery notification can use something like this: If Control 'Door Sensor - Low Battery' is switched On Then Send Notification to 'Email' content 'LowBattery' Else - No Actions - (To add one, press 'Action') With the above program the Hidden Door Sensor will notify you daily of a Low Battery condition until the battery is replaced. I modeled my heartbeat detection similar to the ones belias created for the Leak Sensor heartbeat in this post here: http://forum.universal-devices.com/topic/11566-leak-sensors-a-suggested-complete-program-package/?p=93722 ~Mike

I have my ISY and PLM powered by a UPS and the UPS is powered through a FilterLinc. Been configured this way for over 1-1/2 years without issues. Another limitation to this configuration not mentioned is that the PLM can only send X-10 signaling over the power line, so you will loose X-10 capability if you presently have X-10 modules. ~Mike

Hi Waketech, As far as I know no one has published a table as you described. Once loaded in the ISY those options are available as detectable programming options. I'm not sure what you are trying to accomplish. For custom notification formatting there is guidance on the wiki. http://wiki.universal-devices.com/index.php?title=ISY-99i_Series_INSTEON:Custom_Email_Substitution_Variables ~Mike

Hi Waketech, Here is the post I believe you are looking for: http://forum.universal-devices.com/topic/13081-custom-notifications/?p=113716 ~Mike

Stusview, Am I really giving up the dual-mesh distribution? It is a single point of distribution via RF until it hits a dual-band device. At that point Insteon signals will probagate over the house wiring in addition to RF. I have been operating this way for over 1-1/2 years without any Insteon communication issues except for the one described below. *The only drawback is placing the PLM behind a UPS will not work if you still wish to control X10 devices around the home. I still have one X10 device, the chime module, that is also behind the UPS on the same power strip as my PLM so it still functions. Teken, I chose to configure this way for the reason stated earlier. After configuring this way early on everything ran great until I used an I/O-Linc to control my garage-door opener. Occasionally I had an issue with syncronizing my KeypadLinc buttons to show the correct door status. It was discussion on this forum that pointed me towards the possibility that the opener could be a signal-sucker. This was also eliminated by running the garage-door opener through a FilterLinc. I do not have a spare PLM right now but will be one of the first to order the (still in development) UDI PLM when released! ~Mike