Xathros

Right click on your notification program, select Copy to Clipboard, and paste here for us to review. -Xathros

Thats what this thread is about actually. Right click a DEVICE and select disable. It will prevent it from being queried and complained about while it is not present on the network. -Xathros

chrishick- I am following this thread wit great interest. I use iRule to control some of my AV gear right now and do plan to expand to the ISY. This has got me very interested. -Xathros

I don't know what is complex about that at all. If your looking for a plug and play solution, I believe the wireless Insteon stat is the best solution. I have one that I use simply for monitoring the temp upstairs. It's a simple thing to send a notification if the temp is above/below predetermined values. You won't be using any of the stats internal programming. Simply link it to the ISY and use an ISY program to notify if temp drops below your threshold. Of course, if the power and internet are out, then there is no notify. There are some other solutions that just connect to your phone line and have internal battery backup. When triggered, they call out to a few preconfigured phone numbers and play a recorded message to alert you to the situation. These work as long as the phone line does not go down. -Xathros

Hi Jeff- There is a fairly low tech solution to this problem that works well for me: A square (1/2" by 1/2" of white electrical tape placed on the MS lens such that it obscures the bed area. I can toss and turn all I want but the sensor does not trigger till I stand up getting out of the bed or walk into the room through the door. I have the sensor mounted across the room from the bed centered with the bed. The tape is affixed to the lower center of the MS lens. I used a square cut out of a post-it note to experiment with placement before placing the electrical tape. Since the door to my master bath is normally open when it's not in use, instead of bringing the MBR lights on dim, I bring the LED backlight of the Master Bath Switchlinc Dimmer on to 100% for 5 minutes. Normally the backlights are off during our sleep hours. This provides enough light to navigate to and inside the bathroom without lighting up the bedroom and waking the boss. I also set the onlevel for the vanity light to 20% so that if we do turn on the light once in the bathroom with the door closed, it's not a blinding light. Normally, the backlight is all we need though. Hope this helps. -Xathros

Nice! Clean and simple. Why didn't I think of this... -Xathros

Thank you. Order placed. -Xathros

I have one KPLD that failed in this way. Does anyone have a Mouser or Digikey PN for the preferred Low ESR cap to replace with? -Xathros

Possibly but in my mind it is: DDT ("dichlorodiphenyltrichloroethane") is a colorless, crystalline, tasteless and almost odorless organochloride known for its insecticidal properties. -Xathros

Dunno what I'm gonna do if SH releases a dual outlet dimmer. Guess I'll have to use DDT! -Xathros

I do something similar with mine: SLD - Switchlinc Dimmer SLR - Switchlinc Relay TLD - Toggleinc Dimmer TLR - Toggleinc Relay KD8 - Keypadlinc Dimmer (8 button) KR6 - Keypadlinc Relay (6 Button) OLR - Outletlinc Relay OLD - Outletlinc Dimmer DOT - Dual Outletlinc Relay (Top) DOB - Dual Outletlinc Relay (Bottom) ILD - Inlinelinc Dimmer ILR - Inlinelinc Relay MDM - Micro Dimmer Module MS - Motion Sensor TL - Triggerlinc HDS - Hidden Door Sensor BLB - Bulblinc And so on... -Xathros

In addition to the suggestions above, I have taken to adding a suffix to my scene names: MBR / MBR_Light.scn as in many cases I have a device and a scene with the same or very similar name. Having the .scn extension makes it easy to tell a device from a scene. When setting up variables, it helps to prefix them with s. or i. for State or Integer variables. -Xathros

Jim- Try this: Define an integer variable: i.Daylight Program: Daylight If From Sunrise To Sunset (same day) Then $i.Daylight = 1 Else $i.Daylight = 0 Program: Wakeup If Time is 6:00:00AM And $i.Daylight is 0 Then Set Scene 'MBR Lights' On Else - No Actions - (To add one, press 'Action') Hope this helps. -Xathros

That long silver one looks to me like a Quartz Crystal. Is there a component label near it on the board? -Xathros

Additionally, you can add a program to resolve this for you: If Status 'Switchlinc-W/Load' Is Not Off And Control 'Secondary-Switchlinc' is switched On Then Set 'Switchlinc-W/Load' 100% Else Hope this helps. -Xathros

What? I have to disagree. I believe this will trigger and run then at sunset and trigger and run else at sunrise. -Xathros

Because his error was: /conf/net/6.res -Xathros Sent from my iPhone using Tapatalk

Excellent. Thanks for posting back. -Xathros Sent from my iPhone using Tapatalk

Problems like this often turn out to be a corrupted file on the SD card. Do you have the network module? If so, delete and recreate resource #6 and then try to backup again. -Xathros

The only one that I can think of is eKeypad. -Xathros EDIT: Nevermind. Thats not it. It's Home Automation Pro. Sent from my iPhone using Tapatalk

I see a problem with this. Let's say it's just after sunset and you arrive home, open the door, pull in and close the door. I bet the lights stay on rather than turn off in 5 minutes. This is because the status of the sensor changes to Off when the door closes, re-triggering the program and running Else before the 5 minute wait can timeout. Change 'Status' to 'Control' and then it should work as intended. Additionally, you may want to add "Set Scene 'Garage' Off" to the Else section to force the lights off in the case where sunrise might occur during the 5 minute wait. Hope this helps. -Xathros

I think I understand what you mean but let me make sure- When you say devices A,B,C and D you are referring to thinks other than KPL buttons such as Switchlincs or Outletlincs correct? In addition, for each of those devices, you have assigned a KPL button to display they're individual status. Correct? If both of my questions above are correct then all you need to do is include the additional KPL buttons in the scene that the initial Non-Toggle Off KPL Button is controlling. Add them as responders. -Xathros

In this case, the one sample trace shows good comms between the IOLinc and PLM though that one brief trace is not really enough to says all is good there without question. If the relay was off then and given Lee's response above, I find a false status message to be unlikely. Not sure where else to go with this now. Keep an eye on it and lets see if there is any pattern to the problem if it happens again. -Xathros

Can you clarify this a bit for me? When you press a button to turn the devices off, is it the button that you presses that remains On? If so, then the button is NOT in non-toggle Off mode. A button in non-toggle Off will blink twice then go off after being pressed. If the button(s) that is/are staying on are on a different KPL, then you will need to include them in the scene that you are turning off as responders. -Xathros

Another thought and maybe @LeeG can chime in on this, some multi-node devices when queried report the status for the multiple nodes and a duplicate message from one node can be mistaken as status for a a defferent node by the ISY. If your IOLinc relay was on when it was queried, it may be possible that the ISY mistook a duplicate on status message from the relay as the sensor status. I have heard of this happening with the EZIO devices and I vaguely remember a thread where this happened with an IOLinc in a garage door application. Do you know what the relay status should have been with the false sensor On occurred? -Xathros