Xathros

Hi jjm2958- You can accomplish what you want but it would require that you use a program to sit between you and the garage door kit. You would use the program as your Mobilink favorite rather than the IOLinc or a Scene to activate the garage door. Here is what I envision: Define a state variable: s.ButtonPressCounter and set its value to 0 Program: GarageDoorIsolation If Then s.ButtonPressCounter =+1 Else Program: TriggerGarageDoor If s.ButtonPressCounter < 2 Then Wait 4 seconds s.ButtonPressCounter = 0 Else Set GarageDoorRelay On Wait 2 seconds Set Garage Door Relay Off You would make the RunThen portion of GarageDoorIsolation your favorite. You will have to run this twice within 4 seconds to activate the door. Hope this helps. -Xathros

Try: https:/rest/programs/My%20Programs %20 is the http placeholder for a space. -Xathros

Most I have purchased direct from Smarthome. I could be wrong, but I remember the relays being on the order of $10 cheaper than the dimmers. I haven't bought any in a while however. I have been buying SLDs recently and replacing older TLRs where I wanted dimmers then re-purposing the older TLRs. -Xathros

Is the HUB X10 capable? If so, you could have the HUB issue X10 commands and the ISY react to them. Just a thought. -Xathros

I do something very similar to this with my fanlinc's. I have one KPL or RL2 button that cycles through low, med, high and off with each press. A FastOn will always turn the fan off. -Xathros

You could also use the somewhat cheaper relay versions as your controllers and only place the dimmer where your load is. -Xathros

Excellent. Thanks for posting back with your results. -Xathros

Don't worry, some of these things still trip me up on occasion too. You will get the hang of it. -Xathros

Any time. Happy to help. -Xathros

Can the other end be configured to require a username? Then you could pass both user and pass in the auth header. -Xathros

I'm not sure that is the right answer either. I think you want to monitor the STATUS of all devices in the scene and manage the KPL button based on that. The above will work if a specific control is used to turn a scene member off but what if another scene changes a member in this scene? Try this: If Status SceneMember1 is Off or Status SceneMember2 is Off or Status SceneMember3 is Off or Status SceneMember4 is Off Then Set KPLButtonScene Off Else This way, no matter how a scene member is turned off, the KPL button will be affected. -Xathros

I think you need to take the password out of the body and place it in an authentication header instead. -Xathros

Use the Motion node as the controller rather than the Dusk node. -Xathros

Some of us send beep commands to a switch that is nearing the end of a timer to alert anyone in the area that the lights are going to turn off is no action is taken. Another method (if on a dimmer) is to use a scene with a long ramp rate for the timer program to use when turning off the light. This way the light starts to slowly dim giving someone the opportunity to hit the switch again before being left in the dark. -Xathros

A common point of failure for notification emails and texts is when either the subject or the body of the notification is blank, the ISY will not send. Make sure there is something in both the subject and the body. -Xathros

Anytime. Happy to help. Happy holidays to you too! -Xathros

Define an integer variable: i.notificationDelay and set it's value to 0 Create a second program as follows: Program:NotificationDelay If i.notificationDelay=0 Then Send notification to 'email notification' Content 'Garage Outside Motion' i.notificationDelay=1 Run Program NotificationDelay (Else Path) Else wait 2 minutes i.notificationDelay = 0 Modify your original program by changing the line with the notification From: Send notification to 'email notification' Content 'Garage Outside Motion' to: Run Program NotificationDelay (If Path) This will notify you then prevent additional notifications until there has been no motion activity for 2 minutes. -Xathros

It starts at 2 representing "Unknown status" when you set it up and will change to 1 or 0 once the phone crosses a boundary. -Xathros

Sort of - you are now talking about controlling the door with a scene rather than a scene with the door. There are 2 parts to this - sensor and relay. While both are part of the one IOLinc, you might as well consider them 2 separate devices. Thinking about that for a moment: IOLinc relay is in momentary mode. Turn on a scene in which the relay is a responder, the relay will close for the preset momentary delay (2 seconds) and the door will move. Turn off the scene and nothing will happen. Turn the scene on again, the door will move to the opposite of what it is now. To run the whole show with scenes, a KPL button would be configured as a scene controller with the relay as a responder. The KPL button would be configured for "non-toggle On only". Then you would add the KPL LED as a responder to a scene with the door sensor as controller. This way the door responds to every button press and the LED follows the door state. Only in this case the LED will be on when the door is closed and off when open (Until you change the sensor switch). -Xathros

If the program ID from the summary does not work for you - try converting the ID from HEX to decimal and test the decimal version of the ID with roomie. -Xathros

oberkc is correct above. When the sensor changes state it sends either an on or off command. When you make the sensor a scene controller, the scene will respond to the on or off sent by the sensor. With the current mac switch installed, the sensor will turn the scene on when the door closes and off when it opens. Using the program, we watch for the on and off commands from the sensor and instruct the scene to do the opposite. -Xathros

No. The ISY is event driven. Anytime an event occurs, the ISY checks the program list to see if anything needs to be done. It is not constantly polling devices looking for changes. There are 2 ways to do what you want. With scenes and with programs. For now, since you have th wrong mag switch, program is the way to go. Once you get the right switch in there, then you could drive a scene with the sensor. Here is an example program: If Control GarageDoorSensor is Switched Off and Control GarageDoorSensor is NOT switched On Then Set Scene KeypadButtonG On Else Set Scene KeyPadButtonG Off This program will trigger when the garage door sensor turns on (Door closed) or off (Door Open). When it turns On, the Else path will run and turn off the scene with a keypad button light in it. When it turns off, the then path will run and the scene is turned on. We need the program to reverse the meaning of the sensor. Once you change out the sensor, you could simply make the GarageDoorSensor a controller of the KeyPadButtonG scene and the program won't be required. -Xathros

This depends on the garage door opener. Many (like mine) only require a short press of a momentary button (1 to 2 secs) and the door will move to the opposite of what it was before the press. On systems like these, keeping the button held can prevent other control methods from functioning. -Xathros

I use the Pi for things that the ISY does not do natively. The Pi itself does not do insteon. Using the optional netowrking module for the ISY to talk to the Pi and the Pi talks to the ISY using the ISYs /rest interface. A very powerful combination and soon to become more powerful as the ISY gains bi-directional networking and improved variable support in a future update. I have no worries about support for the ISY going away anytime soon. I'm sure somewhere down the road, the ISY will move to a different CPU or platform but I suspect that is a long way off. -Xathros

This is what the kit used to come with: http://www.smarthome.com/7455B/SECO-LARM-SM-226L-3-Magnetic-Garage-Door-Contact-Switch/p.aspx and is what many of us are using. Wire the red and black in place of what you have now. -Xathros