dbwarner5

Can someone explain better how to connect to the Eisy to the Somfy URTSii serial interface so the that I can use this Plug in? Currently I am using an Somfy Dry Contact interface with a Insteon I/O that I control with EISY, along with an elk Open Close RF transmitter to determine if it's closed or not. Only control is on or off so would like better control.

If you are using the YoLink Notification, I dont know of any way in EISY or Yolk to turn them off "globally" However, if you are using EISY Notifications via programs triggered by the yo link device, you can easily add a variable (ie: Mouse traps armed=1, not armed 0) and then set up a toggle program in UDM that you can turn off all the notifications, by having the variable be a folder condition where all the notification programs reside.

@SMonk Yes, the power of the Eisy programing is ENORMOUS. Between state and integer variables, Nested IFs, ability to run other programs, if, then or else, from within a different program or even the same program, disabled programs on demand only, folders with conditions etc etc. I have yet to see any other "integrator" that is as powerful and yet "easy" to use, once you get the hang of it. One area people often get tripped up on are Waits and Repeats. These line will cause a retest of the IF upon completion which can often change the program from true to false, and therefore stopping it from completing. This forum is a great resource for help with programming. Best way to get help is to right click on a program in the AC and select copy to clipboard (at the bottom), and then paste into the forum. It preserves all the contextual elements of what is in the Eisy. This wiki explains a lot.. https://wiki.universal-devices.com/ISY-99i/ISY-26_INSTEON:Scope,_Precedence_and_Execution_Order Cheers!

Sounds like a great project.. if it works, ou will be busy! Voles are highly prolific mammals that can breed throughout the year, most actively in spring and summer. They typically produce 1 to 5 litters annually, with litter sizes ranging from 1 to 11 young, and an average of 3 to 6 young per litter. The gestation period for voles is about 21 days, and females reach sexual maturity within 35 to 40 days. This rapid maturation and frequent reproduction enable populations to expand quickly, often resulting in significant damage to lawns and gardens as voles seek food and shelter.

Start with simple.. status, and go from there?

I may have missed something in your description, but it seem like you are over thinking this? Wouldn't just one program that test the status of all the lights in the basement with ORs such that if on, turn on the keypad, if all off then turn keypad off? This would be your IF: Basement / RecRm / Devices / Rec_ByPat_Far I3' Status is not Off Or 'Basement / RecRm / Devices / Rec_ByPat_Mid I3' Status is not Off Or 'Basement / RecRm / Devices / Rec_ByPat_Near I3' Status is not Off Or 'Basement / RecRm / Devices / Rec_ByStrPad1_Near' Status is not Off Or 'Basement / RecRm / Devices / Rec_ByStr_Mid' Status is not Off Or 'Basement / RecRm / Devices / Rec_ByStr_Far' Status is not OfffTHEN: Turn on keypad ELSE turn off keypad.

Again, I dont have an i3, but for some ideas for you, the traditional Insteon paddle switch has lots of options, both built in and via programming. All of them can become triggers via control or state, depending on what you are trying to accomplish Built in: 1) On: single tap on top to turn to preset on level and ramp rate 2) On when on: ramps to 100% from preset level 3) Fast On: double tap on top to turn to 100% instantly 4) Off: single tap on bottom to turn off at preset ramp rate 5) Fast Off: double tap on bottom to turn off instantly. 6) Press and hold on: Ramps up slowly 7) Press and hold off: Ramps down slowly Via Programming 1) On when On at less than 100%: When light is not off, not at 100% and on is pressed 2) On when at 100%: When light is at 100% and on is pressed once 3) Fast On when On at less than 100%: Double tap on when light is not at zero and not at 100% 4) Fast On when at 100%: when light is at 100% and a double on is pressed 5) Off when off: Off press when light is at zero 6) Off when at on at less than 100%: when light is not at 100% and not zero, off is pressed 7) Off when light is at 100%: when light is at 100% and off is pressed 8) Fast Off when off: double tap off when light is at zero 9) Fast Off when on at less than 100% 10) Fast Off when at 100% These can get VERY CONVOLUTED, but they are all options. I have a simpler version of just on when at 100% in my basement game area, where each light changes the whole basement to a scene that corresponds to that switch / game (ie pingpong, pool, darts etc). Also the bottom switch at the stairs, I have an off when off that turns on the stair lights and then after a delay turns off all the basement lights. WARNING. we have guest bedrooms there as well so I needed to add a trigger variable to the folder that enables these programs as it really can confuse guests!

I dont have an I3, but this two line condition should accomplish what you want (assume its available for an i3). If 'Garage Sink' is not switched Off Or 'Garage Sink' is switched Off

This only works with the old "doorbell" single contact switch type of door opener. The newer "coded" systems need to work with the code system to integrate and control the door. That's why RATDGO stands for Rage Against the Garage Door Opener. Simple left these devices long ago.

Here is a series of programs that I use for a powder room. Three different times / light settings, plus a way to "exit" the bathroom by turning the light off (guests always like to turn it off, but the Motions Sensor would turn it immediately back on). Pretty straightforward similar to @Geddy suggestions above. PROGRAM 1: Powder Rm Motion on Nightime - [ID 0076][Parent 00F5] If From 11:30:00PM To Sunrise (next day) And 'Elk Main House / MD Powder Room' Logical Status is Violated And 'Powder room' Status is Off Then Set 'Powder room' On 35% PROGRAM 2: Powder Rm Motion on Evening - [ID 0075][Parent 00F5] If From Sunset + 30 minutes To 11:30:00PM (same day) And 'Elk Main House / MD Powder Room' Logical Status is Violated And 'Powder room' Status is Off Then Set 'Powder room' On 50% PROGRAM 3: Powder Rm Motion on Daytime - [ID 00FC][Parent 00F5] If From Sunrise To Sunset + 29 minutes and 55 seconds (same day) And 'Elk Main House / MD Powder Room' Logical Status is Violated And 'Powder room' Status is Off Then Set 'Powder room' On PROGRAM 4 (Auto off if left on) Powder Rm Motion Off - [ID 0045][Parent 00F5] If 'Elk Main House / MD Powder Room' Logical Status is Normal And 'Powder room' Status is not Off Then Wait 7 minutes Set 'Powder room' Off PROGRAM 5 (Exit program, delays motion sensor triggering th lights when exiting) Powder RM Delay on - [ID 0115][Parent 00F5] If 'Powder room' is switched Off Then Disable Program 'Powder Rm Motion on Daytime' Disable Program 'Powder Rm Motion on Nightime' Disable Program 'Powder Rm Motion on Evening' Wait 5 seconds Enable Program 'Powder Rm Motion on Daytime' Enable Program 'Powder Rm Motion on Evening' Enable Program 'Powder Rm Motion on Nightime'

I've been using two Honeywell zwave since 2010 w/o any problems. Dont need a fancy programmable as the Eisy is the controller. Just connectivity.

Same here.

@aLf You are asking about a topic that has been a real pain. Many of the third party integrations take place through Plug-ins. These Plug-ins use the companies APIs to integrate their cloud data into the Eisy for seamless interactions / control and programming. However, many of the companies with large customer bases do not let third parties access their APIs. They do this to try and force hoemowerns to use only their technologies. MyQ is one of these companies. They want you to use their app, their cameras, their door openers, etc. So in the past they did share it, but as of about 2 years ago, they no longer allowed third party access. Therefore there is NO CURRENT WAY TO LINK A MyQ garage door controller to the Eisy via MyQ. The work arounds are numerous. The easiest one is to purchase a RATDGO (Rage against the Garage Door Opener!) device and use the RATDGO plugin. https://paulwieland.github.io/ratgdo/ I use this on two doors and have had good luck with it. Another way is to use a relay device, hardwired to a spare garage remote control and trigger it by emulating a button press. I use this on three doors and generally also works I have also been using a great product by Konnected called the Blaq. Uses the same technology as the RATDGO, but unfortunately there is not a plug in for it yet. (anyone want to write it? their api is available on their website and it uses the same technology as the RATDGO). I use this on a Smartthings installation (not EISY) on a second home but would love to convert all my other doors to it as it's a great product. https://konnected.io Hope this helps.. unfortunately its a PIA.

I hate when that happens!! When trouble shooting I often will use the Find/Replace function and search for the variable or device just to check to see if my failing memory forgot about some obscure program that may be using / adjusting it. With over 1000 programs, this happens.. lol

I would guess the biggest latency is going to be the BLE connection when in proximity. Wonder if you could put that further out than the gate to allow an earlier trigger point. Sounds like you are on the right path. Cant add anything more! Keep us posted. cheers.