belias

+1 for getting a resolution to the heartbeat signal. I purchased 6 of these, and this is the only thing holding me back from installing them. Thanks to everyone troubleshooting this.

I have an almost identical setup. Here's a quick outline of what I've found works best after a year or so of trial-and-error: 1. Set the motion sensor to send ON only commands (these will be transmitted about every 10 seconds when motion is detected) 2. Put the motion sensor in a scene with the garage lights Now the garage lights will turn on almost immediately (no delay waiting for a program to run), however they won't turn off. For that you'll need a program. I use a variable to keep track of how long it's been since the last motion event, and then use this to determine when to switch off the lights. So, three more steps: 1. Create a state variable, lets say sGarageMotion 2. Create a program to control the variable: If Control 'Garage / Garage Motion - Sensor' is switched On Then $sGarageMotion = 3 Wait 15 seconds $sGarageMotion = 2 Wait 2 minutes and 45 seconds $sGarageMotion = 1 Else - No Actions - (To add one, press 'Action') Motion Variables: 1 = Normal state; no motion in the last 3 minutes 2 = Motion in the last 3 minutes, but not within the last 15 seconds 3 = Motion in the last 15 seconds 3. Create a program to shut off the garage lights: If Status 'Garage / Garage Lights' is On And $sGarageMotion is 1 Then Wait 5 minutes Set Scene 'Garage / Garage Lights' Off Else - No Actions - (To add one, press 'Action') Lights will switch off 5 minutes after being switched on manually (KPL, MobiLinc, etc.) or 8 minutes after the last motion is detected (because of the 3 minute delay in the sGarageMotion variable control program. Hope this helps. - Brian

LeeG: Thank you - makes perfect sense. This also explains why the Garage Motion Sensor would result in the program evaluating to TRUE (which was driving me nuts). I'll separate this into two separate programs and it should resolve things. Thanks again!

I've done some more troubleshooting with this (following the suggestions offered here), and I'm still at a loss. The program _IS_ triggered, however evaluates to FALSE when the "Kitchen Motion - Sensor" is switched ON. The ISY status is correct for all of the incorporated devices: Rear Entry Hall Lights [Gar] is OFF; and Kitchen Motion - Sensor going from OFF to ON as I walk in front of it, and the time is within the range specified. Also, the program correctly evaluates to TRUE for all of the other conditions (Garage Motion - Sensor switching ON, etc.). What's interesting is that splitting the program into four separate programs solves the issue. This works as expected: Entry On 1 If Status 'Entry Hall / Rear Entry Hall Lights [Gar]' is Off And From 4:30:00AM To 9:00:00PM (same day) And Control 'Kitchen / Kitchen Motion - Sensor' is switched On Then Wait 2 seconds Set Scene 'Entry Hall / Rear Entry Hall' On Send Notification to 'Brian E-Mail + Brian Push' Else - No Actions - (To add one, press 'Action') Entry On 2 If Status 'Entry Hall / Rear Entry Hall Lights [Gar]' is Off And From 4:30:00AM To 9:00:00PM (same day) And Control 'Garage / Garage Motion - Sensor' is switched On Then Wait 2 seconds Set Scene 'Entry Hall / Rear Entry Hall' On Send Notification to 'Brian E-Mail + Brian Push' Else - No Actions - (To add one, press 'Action') Entry On 3 If Status 'Entry Hall / Rear Entry Hall Lights [Gar]' is Off And From 4:30:00AM To 9:00:00PM (same day) And $sKitchenMotionPowerLoss is 0 Then Wait 2 seconds Set Scene 'Entry Hall / Rear Entry Hall' On Send Notification to 'Brian E-Mail + Brian Push' Else - No Actions - (To add one, press 'Action') Entry On 4 If Status 'Entry Hall / Rear Entry Hall Lights [Gar]' is Off And Time is 4:30:00AM And Status 'Kitchen / Kitchen Motion - Sensor' is On Then Wait 2 seconds Set Scene 'Entry Hall / Rear Entry Hall' On Send Notification to 'Brian E-Mail + Brian Push' Else - No Actions - (To add one, press 'Action') Any idea what might be going on here? Thanks.

I have a program that's set to turn on my entry hall lights under a variety of conditions (I know lots of parenthesis, but it keeps things clean and usually more reliable). For some reason, the program will not trigger for a "Kitchen Motion - Sensor, CONTROL ON" event even when it's between 4:30am and 9:00pm and the Entry Hall LIghts [Gar] is off. Yet, it DOES trigger for a "Garage Motion - Sensor, CONTROL ON" event. Can anybody see what I'm missing here? FYI, I have checked the log file and it clearly shows the "Kitchen Motion - Sensor" going to 100% but the program is not triggered. If I keep walking past the kitchen to the garage and trigger the garage motion sensor, the program triggers fine. Any help would be greatly appreciated. Thanks! If Status 'Entry Hall / Rear Entry Hall Lights [Gar]' is Off And ( ( From 4:30:00AM To 9:00:00PM (same day) And ( Control 'Kitchen / Kitchen Motion - Sensor' is switched On Or Control 'Garage / Garage Motion - Sensor' is switched On Or $sKitchenMotionPowerLoss is 0 ) ) Or ( Time is 4:30:00AM And Status 'Kitchen / Kitchen Motion - Sensor' is On ) ) Then Wait 2 seconds Set Scene 'Entry Hall / Rear Entry Hall' On Else - No Actions - (To add one, press 'Action')

LeeG, Thanks for taking the time to explain this. I always wondered why it was so much faster to remove a device from a scene than it was to add it, this makes sense now. The KPL device link table shows: 0F68 : 62 03 1F.C2.B7 FF 1F 03 The '1F.C2.B7' device is the IOLinc that I removed from the ISY, and indeed the flag byte is set as inactive (62). Thanks again. - Brian

I had an IOLinc that was set up as a controller (for a status button) on 3 KPL's. Over the weekend I decided to remove this device, and used the "Remove Device" command. I didn't, however, remove it from the associated scenes before-hand. Now, when I look at the "Device Links" for each of the KPL's the IOLinc's address is still there. So...a few questions: 1) In this case, if I choose to add the IOLinc back to the system at a later time, it would seem like this could cause a problem since the original links would still be present in the 3 KPLs. Is this correct? 2) If so, how come "remove device" doesn't also remove the associated links? It seems like this would be a more complete "removal" and would eliminate potential issues later on. 3) How can I remove these records from the 3 KPL's now? Any help would be great. Thanks! - Brian

Prior to 3.x, I hadn't experienced a single lock-up like the few I've seen recently. Also, no unusual Insteon activity was present when it occurred - only network resource usage. Maybe it would be worth it to consider some type of watchdog timer to auto-reset in cases like this? I suppose if it's just a few people experiencing it every once in a while, it's probably not worth it...just a thought.

Hi Michel, I have upgraded to FW 3.1.13, and attached the last few entries from the error log prior to the system lockup. Also - I do use network resources extensively and the -140008 errors are quite common. The resources work fine though. Any thoughts would be greatly appreciated. Thanks, - Brian ---- ERROR LOG ---- Tue 2011/12/06 07:23:24 AM System -140008 Net Module Rule: 33:204 Tue 2011/12/06 07:25:02 AM System -140008 Net Module Rule: 32:204 Tue 2011/12/06 08:01:03 AM System -140008 Net Module Rule: 33:204 Tue 2011/12/06 08:01:37 AM System -140008 Net Module Rule: 32:204 Tue 2011/12/06 08:04:06 AM System -140008 Net Module Rule: 33:204 Tue 2011/12/06 08:04:20 AM System -140008 Net Module Rule: 33:204 Tue 2011/12/06 08:13:48 AM System -140008 Net Module Rule: 33:204 Tue 2011/12/06 08:14:27 AM System -140008 Net Module Rule: 33:204 Tue 2011/12/06 10:17:36 AM System -170001 UDQ:Queue Full: LOG Tue 2011/12/06 10:17:09 AM System -5 Start Tue 2011/12/06 10:17:19 AM System -170001 [Network] Established

Hello, Every once in a while (maybe once a month or so) my ISY will experience a "lock-up" where it will stop running programs and is no longer accessible on the network until I do a power-cycle. It just happened a few minutes ago, and before power-cycling I checked the following: - Power LED is on; all others off - Network LEDs lit (at the RJ-45 connector) - Unable to ping the device After power-cycling, the ISY came back online and is running normally. Neither the regular log nor the error log show anything abnormal - however the last entry in both is at around 0845 (time of lock-up) and resume again at 1015 (time of power-cycle) with a start-up message. Any thoughts on what could cause this, or how to troubleshoot? P.S. FW is 3.1.11 Thanks! - Brian

Hello, I have a program set up to send out an email notification at 9:00am each day if any motion sensor has a low battery. In the email notification, I'd like to see which motion sensor is reporting a low battery. However, since the program is activated by time and not by the device status change, the typical "${alert.node.name}" doesn't work. Is it possible to specifically list the status of a few nodes, as we can with variables? For example, something like "${node.XX.YY.ZZ.#}. Thanks! - Brian

Hi Michel, Sorry for the late reply... I tried your suggestion a few days ago (re-installing the self signed certificate), and I am still getting similar errors. I've also tried the normal steps of clearing the Java cache, trying from a different machine, power cycling the ISY, etc. Here's the message I see now: "Socket Open Failed javax.net.ssl.SSLException: server 'finished' message doesn't verify" Also - I'm not sure it's related but I had an issue accessing programs the other day as well. Whenever I would go into Program Summary or Program Details, the list would be blank. The only way I could get it back was to Reboot the ISY (from the admin console). Thanks for the excellent support as always. - Brian

I upgraded to 2.8.16 a few days ago and I'm seeing the following error pop up every once in a while while in the Console: "Socket Open Failed javax.net.sll.SSLException: Server selected improper ciphersuite SSL_NULL_WITH_NULL_NULL" Any ideas? Thanks!

Same findings here on 2.8.15. Thanks for checking to it though! - Brian

Hi Michel, I'm also having a problem setting the LED brightness on a 2477D SWL. It does support beep, so I was expecting this to work... Any ideas? (Using 2.8.12) Thanks, - Brian

Recently I've been getting a notification from MobiLinc that the ISY cannot communicate with a device - specifically a button on my RemoteLinc. When I open the admin console, the specific button ("All Outside") shows up with a red exclamation point. Any idea what causes this? (Running 2.8.12) Thanks, - Brian

I believe this one has been mentioned before - just throwing it out there: Many times when creating a new program it will default to 'Disabled' as soon as it is saved (even if the checkbox on the lower right is checked). It requires toggling the checkbox and then re-saving in order to enable the program. Thanks and have a good New Year. - Brian

I have a few of the 2477D working fine with my ISY (2.8.7). I did have to choose the model from the list rather than use "Auto Detect". - Brian

Hi Larry, I have two garage doors and a few KPL's around the house with an "OHD" button. The button lights up when one of the doors is open, and goes out when both doors are closed. Pushing the button will close any OHD that is open - but it will have no effect on a door that is closed (i.e. it will never open a door). Everything is accomplished with direct linking (i.e. no programs) EXCEPT the status of the indicator light. In other words, even if I unplug my ISY the KPL button will still only close whatever door is open. Here's what I did: * Note: My sensors are installed such that when the sensor reports "ON" the door is CLOSED. It really should be installed the other way around, but I've been too lazy to change it. All instructions below follow my installation... 1. Open the garage door (the position of the door when you perform Step 2 affects how Momentary C functions; if it's closed when you program Momentary C then an OFF command will open the door). 2. In the ISY, choose your I/O Linc and click "Set Options". For the hold time, I'm using one second (so 10 10ths of a second); on the left only "LED on TX"; on the right choose Momentary C. 3. In the ISY, choose your KPL and click "Buttons Toggle Mode". Set the OHD button to "Non-Toggle [Off]". 4. Create a scene to link the KPL button to the IO Linc's: Scene - "Garage Doors (IO Lincs + KPL)" KPL 1 - OHD Button (Controller) OHD 1 - Relay (Responder) OHD 2 - Relay (Responder) 5. Create a scene for the KPL OHD button indicator light (since it must be in a scene to be controlled by a program): Scene - "OHD Buttons (KPL Indicators)" KPL 1 - OHD Button (Responder) 6. Create programs to update the KPL indicator light as below: OHD Closed If Status 'Garage / OHD 1-Sensor' is On And Status 'Garage / OHD 2-Sensor' is On Then Set Scene 'Garage / OHD Buttons (KPL Indicators)' Off OHD Open If Status 'Garage / OHD 1-Sensor' is Off Or Status 'Garage / OHD 2-Sensor' is Off Then Set Scene 'Garage / OHD Buttons (KPL Indicators)' On OHD Query (This shouldn't be needed; I think it's a relic from when I was having Insteon comm. issues) If Control 'KPL 1 - OHD' is Switched Off Then Wait 5 seconds Set 'Garage / OHD 1-Sensor' Query Set 'Garage / OHD 2-Sensor' Query Hope this helps. - Brian

Hello, My suggestion would be: If Control 'Entry Light Switch' is Switched On Then Disable [all programs that automatically turn the lights off] and then one to re-enable them again: If Control 'Entry Light Switch' is Switched off Then Enable [all the programs you disabled above] This is what I use for my garage lights (same applications) and it works great. - Brian

Good thought. If I can catch it soon after it occurs, I'll check the table. Thanks.

Good catch. I looked through my programs both manually and with the Find command looking for any references to 'Nighttime All-Off" but I can't find a single program that calls this one. I also don't remember programming this anywhere (although I've learned that's not always the most reliable). Anyway - thanks again for the help. - Brian

Agreed - reading through the forum and seeing the great support is what convinced me to buy an ISY in the first place. UDI is the company I point to as an example of what support should be like.

Unfortunately it doesn't follow a pattern (i.e. 5 seconds after the garage motion sensor). But here's the contents of the program that ran at 07:25:59 (in response to the Garage Motion Sensor): If Status 'Kitchen / Kitchen Motion - Sensor' is On Or Status ' Garage / Garage Motion - Sensor' is On Then Set Scene 'Entry Hall / Rear Entry Hall' On Else Set Scene 'Entry Hall / Rear Entry Hall' Off Just to make sure I'm reading the log right...it looks like the 'Nightly All Off' scene was called at 07:25:59 by a program. If the only program that has this scene is the "Nighttime All-Off" program, then this is the one that must have run. But - this program has only two triggers: (1) Time is 10:30:00 PM; and (2) Control 'MBR KPL - Night Off' is Switched On. But the log shows that neither are true... Maybe I've been staring at this too long Thanks again for the help - Brian

I've been having a weird issue over the past month or so where my outside lights turn off before the scheduled time. I finally had time to pull the log file tonight, and now I'm even more confused.... I have a program called "Nighttime All-Off" that looks like this: If Time is 10:30:00PM Or Control 'MBR / MBR KPL - Night Off' is Switched Off Then Set Scene 'Daily Maintenance / Nightly All-Off' Off Wait 10 seconds Run Program 'X-10 Cupola Chandelier' (Else Path) Wait 5 seconds Run Program 'X-10 Mom's Office Light' (Else Path) Else - No Actions - This is the ONLY program that references this scene (confirmed with a Find). And now for the log entries: Garage / Garage Motion - Sensor Status 0 Tue 2010/11/30 07:25:58 PM System Log Scene:Entry Hall / Rear Entry Hall On 255 Tue 2010/11/30 07:25:59 PM Program Log Scene:Daily Maintenance / Nightly All-Off Off 0 Tue 2010/11/30 07:26:04 PM Program Log Entry Hall / Rear Entry Hall Lights [Gar] Status 0 Tue 2010/11/30 07:26:04 PM System Log Entry Hall / Rear Entry Hall Lights2 [Kit] Status 0 Tue 2010/11/30 07:26:04 PM System Log Outside / Walkway Lights Status 0 Tue 2010/11/30 07:26:04 PM System Log Garage / Garage Lights Status 0 Tue 2010/11/30 07:26:04 PM System Log Entry Hall / Entry Hall KPL - Garage Lts Status 0 Tue 2010/11/30 07:26:04 PM System Log Entry Hall / Entry Hall KPL - Walkway Status 0 Tue 2010/11/30 07:26:04 PM System Log MBR / MBR KPL - Walkway Status 0 Tue 2010/11/30 07:26:04 PM System Log 2nd Floor LR / Upstrs Hall KPL - Walkway Status 0 Tue 2010/11/30 07:26:04 PM System Log Scene:KPL Button Scenes / All Outside Buttons Off 0 Tue 2010/11/30 07:26:05 PM Program Log X10 D4 Tue 2010/11/30 07:26:13 PM Program Log X10 D4 Off (11) Tue 2010/11/30 07:26:13 PM Program Log X10 K1 Tue 2010/11/30 07:26:19 PM Program Log X10 K1 Off (11) Tue 2010/11/30 07:26:19 PM Program Log So...here's the question: Any ideas on what's causing 'Scene:Daily Maintenance / Nightly All-Off' to be triggered?? Thanks! - Brian