larryllix

Thanks! That doesn't look easy to interface to a GDO and I can't see any pricing. Actually, my original drive was having a side opening back door on a RAV4 and the garage door coming down on the edge would have demolished that door. It becomes very protruding when they open sideways. Other than that, completely useless format. I raised my GDO beams up to the level of the lower tip of the vehicle door in an attempt to avoid that accident. I realised it helped endanger the very child problem we have been discussing. However I live in the rural and have no small children in the area. Worst is coyotes, skunks, and cats, but I would be proud to squish one of them.

I bent a side door by backing into the GDO track. I bent the track back with my hands and it's been fine, not showing any dents for last few years. It was minor. The Rav4 door had the corner metal rolled over but bent it structurally, slightly. That one cost me almost $3K to replace the door with a junkyard, lower model (no coatings) door. Mind you the bodyshop people all told me the window tracks are welded in and cannot be made to not bind, on a scrollable door window. Then there is all the power gadget switches. While I was at the bodyshops I saw several bans with the awning type doors with dents in them. I was told by different shops the door were write-offs, as the painting of half the vehicle was the larger part of the costing, anyway. Insurance coverage (big deductibles) was part of the solutions, I am sure.

The one that bothered me was: now having a hatchback style opening back door on a CR-V, I have seen several rear vehicle doors at body shops, last time I was there. They become a very expensive repair into several thousands of dollars to replace. I have several laser pointer type parking guides on the garage ceiling, and the first spot that falls off the dash gives a tested clearance, including the hinge hardware, clear of the vehicle by a few inches, while the door is open and during any part of the opening arc.. Just another consideration for blindly closing garage doors. OTOH: That could also happen while you are closing it from the wall PB,.

I am a big variable advocate where they make things easier or more complex algorithms available but.... Try something like this. If door open is switched on (not status) AND Light is Off (this is status) Then turn light on WAIT x hour ( all else fails clause) turn light off (anyway) Else turn light Off Framing this with a time of day logic will complicate things and require at least two programs with interlocking enable/disables

Not too much of that Guinness! I was looking for a multiple beam sensor originally. Do you have any links to one of those?

All my cameras have a few seconds of delay. If I saw a child entering under the door, it would a few seconds later and then the remote control command would likely take a few seconds more to stop the door travel. That doesn't even account for the human delay to find the dongle or click spot..

That would be nice but like all the other high-tech industry, they would ave to produce a new video every week or two.

...and if they addressed by Insteon ID, they will definitely be different. I know the nice names are only converted at human read times. ISY uses all indexed references.

Insteon protocol is supposed to include an anti-colision algorithm mechanism in every Insteon device. Either way enough packet stacking would likely cause problems for battery devices, that are blind to it. I think.

I think the PLM and devices have limited stacking facilities to create a polite transmission order but with a lot of Insteon traffic, that feature can potentially make it worse for battery operated devices that cannot detect powerline collisions. It seems Insteon battery devices just do a dumb algorithm by just banging the RF signal out a few times at random. This could make things even worse yet.

I use a lot of variable for lighting moods. Increasing the variable by one can brighten the lighting scenes (not Insteon, but combinations of Insteon, WiFi bulbs and strips with colours). When "borrowing" a lamp for flashing or other temporary uses, it is easy to restore the lighting in effect before the "Borrow" by replacing the variable value. It's not usually your children. It would be the neighbour's baby carriage pushed by the older sibling under your garage door. The existing safety mechanisms in GDO could still break a child's. neck or back. They are not designed for that kind of protection. Paying law suit would not help you live in the neighbourhood, or sleep, if something like that happened.

You may encounter people here telling you not to close a garage door without visual confirmation there isn't a toy, or a young child under the door. I don't control my garage doors. I do notify the humans if they are open though. While any door is open I continuously flash one lamp in the corner of my Gathering Room, with red flashing. If the Gathering Room lights are off and the bedroom lamp is turned on (automatically) I flash that lamp at full brilliance. I normally run that 100W equiv. lamp about 10% at nights. The bedroom lamp is flashed by an ISY program loop, while the Gathering Room lamp is flashed by a self-contained bulb code, so ISY doesn't have to do it. Programs can just go down a list of items to fix. There is no need to detect whether they are on or off, just set them to the position you want. With garage doors that is usually different, as the control toggles them open/close but there should be programs already in place that you would just call as subroutines, and those programs would decide what to do. So it could look something like this. If bedtime detected Then set lamp1 to Off Wait 2 seconds set lamp2 to Off Wait 2 seconds Run GDO1 close program (if) Wait 15 seconds Run GDO2 close program (if) Wait 15 seconds $sSayGoodNight = 1 <---- trigger alexa routine Wait 5 seconds $sSayGoodNight = 0 Else -----

Wait and Repeat statements ALLOW the system engine to re-evaluate all program triggers, if any condition has changed. This includes the same program's If section as the one containing the Wait or Repeat. Think of them like a surrender of their time slice in a multitasking system. If any condition changes in a program containing that same condition the program will stop what it is doing (if running) and run Then or Else, depending on the outcome of the If section. Disabling does not disable the program, only the triggers in the If section. This affords subroutine style usage. Calling a program as a subroutine does NOT wait for it to return but the second program will launch simultaneously. There is no guarantee of running order. Simple in-line if-then constructs can be done with the ISY Repeat-while construct. Clumsy and ugly but it can be done. It takes the involvement of another variable. In many past threads users have wanted to change the program structure into a When-If-Then-Else sectionalised structure. Some want the same but each If line can be enabled/disabled individually. UDI is slow to respond to these requests as the bit off Zwave with it's constant updates, and dumping the java for HTML5/CSS/js admin console. Lastly, Integer variables do not cause event triggers. State variables do.

I have one of those I bought under a different name in a surplus store here. I don't detect any Insteon signal problems with it for Insteon devices connected beside it. I have never used Insteon devices plugged into it, though. Nice bars, with a little more space between each socket. I use a FilterLinc on each GDO and an I/OLinc plugged into each unfiltered receptacle on them. One Chamberlain MyQ GDO had crippled my whole Insteon system, so I know the FilterLincs must block Insteon interference very well.

Nahh. UDI doesn't believe in home automation. Today is Saturday. Michel's day to replenish his food supplies. Sent using Tapatalk

Yes, but it was an example of @apostolakisl's posted logic where the "To" time is before the "from" time. Let me post the whole thing again so it doesn't get it's meaning misconstrued. Program Logic Test From 11:59 PM To 12:00 PM (same day) <-------- 11 hours 59 minutes earlier Then Will Never Run Else -------

UDI did some real head scratching for some of that logic. Program Logic Test From 11:59 PM To 12:00 PM (same day) <-------- 11 hours, 59 minutes earlier Then Will Never Run Else -------

After clicking on the link sent to me by UDI in email, I went to my ISY Portal. A popup with payment options was automatic. I think somebody was secretly listening here.

I thought I was wrong once but it was just an error. Sent using Tapatalk

On that note I just received my notice for renewal of my ISY Portal subscription. All links were very obvious they were from my account with clear URL domain names. On a link I was transferred to my ISY portal login, where the option to renew was easy, clear and safe as URLs were easily identified. Links were verified each step of the way before entering any credentials. The pulldown options were easy to select from the $500 or $750 amounts. JUST KIDDING ABOUT THIS LAST PARAGRAPH!!! Sent using Tapatalk

Put a link to the wiki on the top of every forum page inside the huge blank UDI logo banner. In the wiki create a list with a few handy quick links including one to pay bills on the top of the entrance page. Linking people to a login page does not solve the security problem. Years back, I received one like that from my bank. Just as I was about to commit my credentials with the final click I noticed the corner logo icture aspect ratio was odd. Checking the url links I noticed wrong domain names. Linking people to a login page only makes it worse and is the exact technique credential thieves use. Sent using Tapatalk

My ISY came with one program installed. The 3:00 AM containing Query All. When people delete it they have no Query All. I have added a series of device off clean ups and delayed the query until 4:00 AM. Gotta' love those alarms in the middle of the night.? I mostly set flags and check them in the morning for lower urgency alarms like low batteries.

When a program containing a wait or repeat line, is interrupted by it's own If logic triggers, the program knows i,t and terminating action can be taken in the Else section. This is not possible for a folder condition. When a folder condition becomes false the programs inside are not aware of the change, and cannot take any alternative action. Lights and devices can be left in undesirable states.

LOL. That's not a Then or Else. That is a True and False. No programs are enabled during False times and no programs will be run to clean up the mess of programs stopping abruptly.

You came to the right place! I use this technique to determine Home/Away. Each and every device that can be used injects a value (number of minutes delay) into a variable. Each MS or other device injects a different number of minutes to delay. Typically the closer you get to the exit door, the lower the delay number. The security (built into ISY for me) system injects only a 1 minute delay. Motion.EveBR - [ID 0015][Parent 000B] If 'Evening Bedroom / Motion.EveBR' is switched On Or 'Rec Room / RecRm stat / RecRm stat cribroom' Occupancy is Yes Then $sMS.Motion.room = $cROOM.EVEBR Wait 2 seconds $sHouse.occupied.timer = 120 Else - No Actions - (To add one, press 'Action') A countdown program self-retriggers every 1 minute or whatever clock click you desire. Note my implementation allows people to sleep without timing out and resumes in the morning again. Occupied.countdowner - [ID 0167][Parent 000B][Run At Startup] If $sHouse.occupied.timer > 0 And From 7:00:00AM To 11:00:00PM (same day) Then Wait 1 minute $sHouse.occupied.timer -= 1 Else - No Actions - (To add one, press 'Action') Self retriggering timer. Enabled to run at startup! -If startup occurs ouside wake timeframe, will self start at beginning of timeframe. -If timeframe commences while .timer is 0, first new occupied.timer value will start again. A third program monitors the countdown vairable and does the dirty deed desired. Occupied.flagger - [ID 0168][Parent 000B] If $sHouse.occupied.timer > 0 Then $sHouse.occupied = $cTRUE Else $sHouse.occupied = $cFALSE Power up assumes home unoccupied! Shouldn't be long to correct that. Program cannot be combined into "Occupied countdowner" program as it's timeframe end would zero occupied.timer