Xathros

Not sure I understand the request. Which motion sensor? Scenes don't run true or false, programs do. Your All Lights program can call a second program to look at the other sensor and turn on the LED's but if the other sensor is already controlling the LED's, it seems to me like you've already accomplished the stated goal. I must be missing something. -Xathros

I too see delays when sending notifications via SMS/MMS to my AT&T cell. I have tested sending to both my MMS and Email simultaneously and find that the email arrives in the usual 5-15 seconds and the MMS can at times be just as quick but can often be delayed for many minutes. I have moved all critical notifications to Prowl and have been much happier with the performance there. -Xathros

Is this a Gas or Electric dryer? If Gas, then I think a Synchrolinc may be the best solution for detecting the states of the dryer as you should be able to tell the various draws, Running, idle, door open with light on etc. If Electric another solution may need to be found. I'm not a fan of your Triggerlinc solution as implemented. While the dryer is running, this will be flooding the Insteon network with On/Off messages from the Triggerlinc. This seems like a bad idea to me. Can't imagine the battery in the Triggerlinc will last long with that kind of usage either. If you have Zwave on your ISY, one of these energy meters would be a good solution to this problem: http://www.amazon.com/Aeon-Labs-DSB09104-ZWUS-Z-Wave-Energy/dp/B00DIBSKFU Like the Synchrolinc, you should be able to detect run, idle and door open with this. If done right, you could use one sensor for the dryer and one for the washer. Hope this helps. -Xathros

Reboot the ISY. -Xathros

Excellent! Thanks for posting back with the result. -Xathros

Or as the op suggested, simply not use the light output of the fanlinc and wire the bulbs hot always. -Xathros Sent from my iPhone using Tapatalk

To take that a bit further, create a scene with the ramp rate you desire for the turn off ramp speed and set the controllers to that ramp rate. Then create a program as follows: If 'Control_A' is swiatched On or 'Control_B' is switched On Then Set Scene 'MyScene' FastOn When you turn the lights on with either control, thety will start to ramp up but the program will see the control on and issue a FastOn to get them on full. When you turn them off, the scene will just ramp off at the rate you set. Hope this helps. -Xathros

Glad you got it going. I have never run into a situation with any of my ISY's like this and I really don't believe this to be a common issue. If this happens again, I think it would be worth doing some additional testing to narrow down the root cause. -Xathros

Very nice! Welcome aboard and thanks for the post. -Xathros

The program runs once when the status changes to Off. The summary says the program has not run since startup. Cycle the Fan On/Off and see if the program status changes. -Xathros

How many scenes do you have already? Is your ISY a standard or Pro? Have you rebooted the ISY and tried again? -Xathros

This does sound like a failing PLM to me. -Xathros

Possibilities: 1) The program is in a folder with conditions that are preventing it from triggering 2) The value of the state variable maybe non-zero but unless the value changes, it won't trigger. If the value is 1 and another program sets the value to 1 again, the program will not trigger as the value didn't change. 3) The initial program is set Disabled. Hope this helps -Xathros

Well, yes. The IdeaScale site is fairly new. The product requests forum predates that by many years. I think the IdeaScale format works better for tracking feature requests and the associated demand for each request and I suspect thats why UDI decided to go that route. For what it's worth, it is somewhat integrated with the forums. You will see it in the upper right of the forums home screen: http://forum.universal-devices.com/index.php -Xathros

While I do have quite a few Insteon nodes and a small but growing number of ZWave nodes, the large majority of my programs and variables relate to communication with other devices on my LAN and many do nothing with Insteon or ZWave nodes at all. -Xathros

I think they call rain at -45C with wind howling "light snow" up there in Canada. -Xathros

There is an idea posted in the IdeaScale site for a feature like this. Have a look there and add your vote if you think it has merit. http://udi.ideascale.com/a/dtd/Program-edit-GUI-Show-programs-that-call-this-program/83984-32911 -Xathros

Anytime! Always happy to help. -Xathros

Not sure whether or not to take that as a compliment... I also agree that simplicity is better and usually try to find the simplest answer to a problem. The current limitations however often dictate multiple programs to solve seemingly simple problems. I'm quite hopeful that the 5.X features will allow me to drastically simplify things and reduce the overall number of programs that I have now. Many of them are used to integrate with external devices (Din relay, Ubi, Hue etc) and when I can use one program and network resource combined with variables in many cases 10+ programs could easily become 1. -Xathros

Pull the Airgap switch on the KPL, wait 10 seconds, push the airgap all the way in and hold it in until the KPL beeps. Then go to the admin console, right click the KPL and select Restore Device. -Xathros

Instead of using a Scene or the IOLink directly in ML, you would set up a program like: Program: GarageOpenClose (Make sure you set this program as DISABLED) If 2Car.sensor is On (Assuming sensor is on when door is closed - otherwise change this to Off) Then Set '2Car.relay' On Wait 2 seconds Set Scene 'Mudroom_Lights' On Wait 5 minutes Set Scene 'Mudroom Lights' Off Else Set '2Car.relay' On Wait 5 minutes Set Scene 'Mudroom Lights' Off Set the program to RunIf on the ML Dashboard. Pressing the Icon on the ML dashboard will open the door and turn on the mudroom lights for 5 minutes if the door was closed. If the door was open, it will simply close the door, wait 5 mins and turn the light off just in case you forgot. Hope this works for you. -Xathros

You will want to make sure that the IOLinc Relay Options are set for "Latching Continuous" rather than any of the momentary modes. If Time is Sunset Or Time is 10pm Or Time is 2am Or Time is Sunrise Then Set 'IOLinc Relay' On Wait 35 seconds Set 'IOLinc Relay' Off Else That should do it. -Xathros

Hi Jeff- The system cannot distinguish between the remote or the GDO keypad. You could tell when the GDO is activated by Mobilinc if using a program. You could easily trigger a lighting routine based on the door opening by using the IOLinc sensor but you would need other criteria to decide if you are coming or going. Geofence may not help as you will still be in the region regardless of direction. If you have a sensor on the door between the mudroom and garage, you could turn on the light in the mudroom when the mudroom door is opened and the garage door is already open and not turn on the light if mudroom door is open while the garage door is closed. This probably depends on where your GDO buttons are located in relation to the mudroom door. Hope this helps. -Xathros

I have: 552 Programs 7 Folders with conditions 93 State Mvars 136 Integer Mvars 381 Network resources. Like MWareman above, I expect to drop many resources and a number of programs once 5.x allows wider usage of variables. At that time I expect to increase the number of both state and integer variables in use. -Xathros

Anytime! Happy to help. -Xathros