larryllix

Yup. There isn't much without v5. Sent using Tapatalk

Careful....CarPort-Sensor' is Switched On never runs Else so your Off command must be in your Then section. Most users disable the MS Off signal to save batteries.

For the CAO Tag I screwed one diagonally to the top panel of the metal door so that it sticks above the metal.This is for better RF transmission and faster motion activation as soon as the door moves from fully closed. The Tag online website includes a Kumoapp section where you can write javascript to send your output data to wherever you want. Mwareman wrote some script to stuff outputs into ISY variables and I made some improvements on that, posting them here each time. I use one of the XYZ axises that changed the most to determine the door was not fully closed. Another alternative would be to use a Polyglot nodeserver designed for this purpose. Here is a thread on setting the Tag code up. It can be cut and pasted into the webpage for your Tag manager setup, then the variable numbers and personalised Tag names you have assigned, can be modified in the code. It should be mostly obvious and help is always here.

While your explanations are much better and less "preachy" this time, I have to agree with most of what you last posted. However, the Leviton Whole House Surge Protector does not have a discharge circuit to ground as it utilizes the Faraday principle, not involving or requiring any discharge to ground. As @apostolakisl posted previously, It is the Faraday cage principle that is important for equipment and humans. If ground is included and connected into the "cage circuit", it can cause the transient damage to be more or less. In my lightning induction case, grounding made the damage worse and damaged my equipment inputs. https://www.amazon.com/gp/product/B00081K55Q/ref=as_li_tl?ie=UTF8&camp=1789&creative=390957&creativeASIN=B00081K55Q&linkCode=as2&tag=stejenblo-20&linkId=QG5BWIFQ3UOVTTBG

LOL! Sure! Think of the variable as a counter. The funny part is, I hear people tell me all the time they have never dealt with variables and run away from them, like we were talking advanced calculus on matrix arrays. I guess I spent a lifetime dealing with them since grade four (about 1960) when we studied unknown quantities in arithmetic, and computer wise in 1971 when the first 8 bit CPUs were launched. So I am very biased. People. You can't really break your ISY. It's a playground for experimentation and can be a favourite toy.. If you screw something up, spend about 2 minutes and restore your backup. I just showed my 9 year old granddaughter how to write programs on my ISY using a buzzLinc (thanx Stu), an MS, and three wall Switchlincs. She picked up compound logic using ANDs and ORs with parenthesis, in about 60 minutes and had a riot guessing if her dancing would pass the three wall switch logic to activate the beeper. ISY is an educational toy. Play with it!

I am not sure which one I would prefer. I like programs that don't use variables for this type of logic. (I use them profusely elsewhere) but the first one is more complex in understandable logic. For the variable think of them as a drawer. If one of the condition triggers happens, either sunset or 7:00 PM only open the drawer, look inside and if it is empty, drop a stone (1) into it. If the drawer already has a stone (1) inside it, then take the stone out for next time (=0) and then do whatever you want it to do. You are making sure both conditions have transpired by only marking the first condition when it happens.

I have the myQ system but I screwed a CAO wireless tag to the top of the door and now ISY notifies me via voice and flashes lights when the door us left open. It was the easiest path to install. My other garage door is monitored by an ioLinc and is much faster. I do not control my garage doors. Sent using Tapatalk

You're on the chopping block. Just keep it up.

If ( time is sunset <------- after 7:00 PM AND from 7:00 PM to 11:59 PM ) OR ( time is 7:00 PM <---- after sunset AND from sunset to sunset + 4 hours ) Then ------------- If ( Time is 7:00 PM or Time is sunset ) AND $Variable > 0 <----can't be State type variable or will retrigger program Then set $Variable = 0 do whatever Else set $Variable += 1 You may need a maintenance program for fringe cases If time = midnight Then set $Variable = 0

Forrest Gump comes to mind.

The last two LSs were a defective design were the case cover can never be closed. If you open them from one end instead of the side when you hinge the lid it breaks off the tuning coil and is a dead duck.

I have one LD under my dishwasher and the heartbeat misses about once per year, despite the five year old unit working just fine for years after. I decided to create a monitoring program that resets itself and continues to check the heartbeat and report it in another/every 48 hours. If I was away on a month long vacation I don't want notifications more frequently but I need a reminder for when I get back. Notifications that get sent once tend to be forgotten when I get back. Note: I write all my device monitoring in the positive context so if they show green (running Then) everything is fine. They also get labelled "XXX Ok". Also note the usage of constants so I don't have to guess what the codes are two years from now. A common program monitors the state variables and does the common things using ISY's event based logic engine design. Leak.Kitchen.OK - [ID 0164][Parent 00CD] If 'Kitchen / Kitchen Leak.dry / Kitchen Leak.heartbeat' is switched On Or 'Kitchen / Kitchen Leak.dry / Kitchen Leak.heartbeat' is switched Off <------some units do not use this Then $sLeak.Kitchen Init To $cLEAK.DRY $sLeak.Kitchen = $cLEAK.DRY Wait 25 hours Run Program 'Leak.Kitchen.OK' (Else Path) <-------- display a red icon Else $sLeak.LowBatt.room Init To $cROOM.KITCHEN <------where to look for lowBatt, log in ISY, power blink survivable $sLeak.LowBatt.room = $cROOM.KITCHEN $sLeak.Kitchen Init To $cLEAK.LOWBATT <------- trigger common alarm programs, power blink survivable $sLeak.Kitchen = $cLEAK.LOWBATT $sAlarm.level = 2 <------- ring some local beeper alarms Send Notification to 'Text Larry' content 'Leak Detector Heartbeat Missed' Send Notification to 'eMail Larry' content 'Leak Detector Heartbeat Missed' Wait 23 hours Run Program 'Leak.Kitchen.OK' (Then Path) <------- start over and retest

IMHO: "beta" and "alpha" are very bad labels UDI has assigned every version of v5 so far. It's a non-committal cop out for releases and causing UDI a very bad market reputation, hurting their sales.

Not that I know of. I wrote my own but basically I would copy the Belias programs verbatim and then use the mass change features in Admin Console to swap in sane name for variables, and programs, that mean something to a reader. Then I would create some Integer variable constants to identify codes with sane names. eg: set $sLD.dishwasher = $cLEAK.DRY

Time to bite the bullet and upgrade to the real ISY! This a basic setting that I think was included in v4 but then I haven't used v4 for about 5 years now. I don't use scenes unless I have to.

When you operate a device locally there is no scene involved. It is all internal between the switch contacts and the dimmer electronics. If it is a SwitcLinc then set the switchlinc On level, not an unrelated scene. Ensuite Lights Level.adjust Copy - [ID 001A][Parent 00FA] If From 8:00:05AM To 11:00:00PM (same day) Then Set 'Master Bedroom / Ensuite Lights' On Level 100% Set 'Master Bedroom / Ensuite Lights' Ramp Rate 0.5 seconds Else Set 'Master Bedroom / Ensuite Lights' On Level 20% Set 'Master Bedroom / Ensuite Lights' Ramp Rate 2.0 seconds

With google, they will never let any information go. It might be worth a few bucks someday. You can only unlink your hub account.

Yes. Vocal control is like having a keypad in every room with an infinite number of buttons. Although against my basic principles, I would have a hard time living without it now. The second largest usage for us, with vocal is asking how old some actor is, or what the name of the actor is, while watching movies. Third, is asking outside temperatures and weather. BTW: Alexa now has a skill that supports the CAO Tags now and will report temperatures for my 7 Tags. Recommended!

Voice control is like power windows in your car. You will never go back. I am with lilyoyo1. I believe in total automation but I am not there yet and will likely never be. Voice control allows so many more controls without dozens and dozens of pushbutton, every where in the house. Coloured lighting schemes would be next to impossible. Imagine the home wiring required to be able to turn on porch/deck lights outside from any room in the house? Lazy? You bet! Imagine doing this one manually! Alexa! Turn on security lights! Turns every light outside on and under porch and decks, around the house and turns ever light inside the house off, Straw Dogs style, (Dustin Hoffman movie) Alexa! Turn off security lights. Reverses it back to previous lighting setups.

This is an Insteon protocol phenomenon and not to be thought related to your PLM/ISY. It is believed to be a signal clash that may be repeated and cleaned up by Insteon units into a Scene On signal.. Since AC powered Insteon devices are supposed to play nicely in the protocol by watching for signal clash probabilities and avoiding them, it is believed to be from battery operated devices, that repeat their signal several times blindly. Examine your program looking for a battery operated device (typically MSes) that triggers a program and your program immediately puts out an Insteon response to activate a device and insert a Wait2-3 seconds as the first line before the Insteon device control. KPLs are bad for this as people like to get those LEDs to repond immediately and KPLs contain multiple devices that are all in the same device, protocol wise. For high speed operations from a MS to a lamp use a scene where ISY doesn't have to spit out a Lamp On right away. It is faster and ISY can just turn it off on it's own logic. Most of this is addressed in the UDI wiki website, with how to's to help you.

In the new PolISY I don't think there will be any SD card connections with it's built in SDD. Hopefully there will be no Molex pin connectors either. Mind you, the connector plating technology seems to have come a long way since the old 1 MHz CPU days when wiping and cleaning connectors was a weekly event.

Try one these I found for that expression. Maybe Google has taken java off it's "allowance" list https://www.bing.com/search?q=java+firewall+allowance&form=EDGNB3&mkt=en-ca&httpsmsn=1&plvar=0&refig=3dfbbf8dd65d407bf6ae7e1ea788a139&sp=-1&ghc=1&pq=java+firewall+a&sc=0-15&qs=n&sk=&cvid=3dfbbf8dd65d407bf6ae7e1ea788a139 Look into your java admin/control console, to find the firewall settings. It may require your ISY IP address added to the permissions list, it it will block requests coming from that IP address. I am not sure how iOS things look (and don't really want to) but surely Apple will let you make a setting inside your java firewall without their approval first.

The vocal device apps only link with your ISY Portal account, not your ISY, and are not related to the UI used in your ISY admin console. Perhaps you are referring to the GH UI?

Have you entered ISY IP address into the java firewall allowances?

We always had to spend 10's of thousands of dollars on special transformers to isolate our electrical grid station equipment from telco (Bell) stations. Bell would sent high voltages, right from their great grounding system, into our equipment every time we had a high current fault, and burn out our sensitive relays and electronics. Eventually things went away from DC signals and went to tone systems that could be insulated,and it eliminated some of the telco lineman idiots from disconnecting or reversing polarities on critical trip lines.