larryllix

Just for interest sake....here is another programming trick to incorporate the two programs into one. (makes vocals easier sometimes, but may make it complex to figure out a year from now) Den Ceiling Fan WRUN - [ID 011C][Parent 011B] If Control '_Den Fireplace Fan RUNNING' is switched On AND Control '_Den Fireplace Fan RUNNING' is NOT switched Off <------NOT makes Else run when 'switched Off' becomes True Then Set 'Den-Ceiling Fan' On Else Wait 10 minutes Set 'Den-Ceiling Fan' Off AND Logic explanation If - 'is switched On' is true then 'is Not switched Off' must also be True = both can never happen at the same time If - 'is NOT switched Off' is False then 'is switched On' must also be False = both can never happen at the same time Have fun!!

Look in the program summary tab. You should find a column titled "Enable at startup". If you click on any of these headers the "spreadsheet" will be sorted by this field and you can find all the programs involved at the top or bottom, depending on last click selection. Now you can r.click on any program and enable this for that program. Note: If there is a condition in the "If" section of the program it will run whichever claus (2 more months ) depending the outcome of the If section logic. Many of us have created one common "Run at Startup" program that dispatches to all the other little nuance programs that initialise all the hardware monitoring programs, etc. I have requested the ability to "Enable at Startup (if/Then/Else) from UDI and it may be installed in a new ISY version someday. We have also requested this be more visible on the programming pages along with an indicator.

65 Sussex Drive?

Along with what oberkc posted, the program summary page is sortable by any parameter field desired by clicking on the field title at the top.

In the admin console if you right click on any program in the program tree (tab), you should find a "Find/replace" menu / option. Using this you can enter any program name, variable name, device, raw text etc... to search for parameters in your programs. This makes it easier to find some old program you experimented with but may have forgotten. Also, did you ever create a direct link between the lights in question and another device, like an MS etc..? Did you factory reset all your devices before linking them to ISY?

The usual way most conclude in the end is. - Create a State variable called $sVacation. (note: I find vacation and away to be two different scenarios needed.) - Create ways to control the variable accurately when you are away from home. I use my $sAway variable with a 16 hour delay to automatically set the house into Vacation mode, as well as a few manual methods. - Use the variable to control key programs, disallowing them to run in the "If" section, or control Then / Else with a different routine based on $sVacation = $cTRUE or $cFALSE

Then you have set the re-alert time to 15 minutes and notifications will be as frequent as 15 minutes + time for the next degree change to happen. I think this could all be simplified by just setting a smart thermostat to the temperature you want and changing it when you want it changed.

Yes. You would be dumping the new owners into a technology way over their heads. Sure they a fascinated by it and they want it but look how long it takes others to get to that point. It is asking for a world of hurt. The new owner should start into the advanced level that you leave them but I would eliminate every fancy feature you can for them to start with. If the new owner ever comes up to speed, he/she can buy their own fancy peripherals and you will be free of training and retraining that is about to happen. Cripes! I left a security system in my last home I sold and with all the default setups and passwords restored back to the manuals I left for the new homeowners, and written instructions what to do, I still heard threats of suing for a system they could make use of. It finally went away after I informed the real-estate agent where the info was, again. People just want things to work magically and they may step on anybody they can blame for their own incompetence.

It's usually pretty easy to decide when to notify the human and cause alarms. The difficult part is deciding when to reset them, so they can activate again. You will have to decide when that should occur. immediately - that was your complaint. after a time after the temperature returns to a defined tempearure (hysteresis) never a combination

Please paste your programs here so we can have a look without guessing too much. You can copy to clipboard with a right click on the program in the program tree. Off the cuff. Have you forgotten to use From 12:00 AM to 7:00 AM (next day) ?

Welcome to the forum!!! Program1 If temperature <= 80F Then turn A/C off notify my owner run (If) program 'Reset' disable This.Program Else ---- Reset (enabled to run at startup) <--- need to always cock this baby or it may not fire. if ---- Then Wait x hours turn A/C On? enable Program1 Else ----

The main clue there is "New". Every Insteon device should be factory reset before installing into ISY. The factory leaves these things with unbelievable qualities that you may never see again. I had one MS send the opposite status. Alas! It is easy now. Just factory reset the device, and then use Restore (right click on the device in the device tree) in the admin console. It will restore the settings ISY "believes" should be inside the device. Takes about 2 minutes. Be sure to only do one battery device at a time and put it into "Linking mode" before trying to write to any battery device. Start with the odd unit and proceed to the rest as time permits.

The "On" level is changed twice per day. The On times are the same and use the exact same method...MS ---->Scene On--->Dimming Device. The On level from the MS is immediate no matter what level of brightness is used.

Read down about four posts.

Alexa announcements operate from NRs and not programs (like this one) directly. You need to set up a set of NRs, each with a text and then use them from your program.

Sorry! Skills are just for Alexa. My google Home stopped communicating with the ISY Portal for a few months and google support told me on several occasions they never heard of UDI or the ISY Portal. The ISY Portal started complaining with a similar error about 4-5 months ago and some here thought it wasn't required anymore. My GH HA started working again by itself, months later after destroying my googel account and starting over with another one, and I just gave up on it being reliable. Since I have many Amazon units here, only 3 GH minis, and Amazon trusts people to set their own parameters I have been avoiding GH for HA lately. Great games and quick wikipedia connections though.

Google Home asks you to link to your UDI account the only first time you install the skill. After that, google makes an assumption you want the same account. If it is incorrect, starting over may help, or google may never let go of that account address and you may have to contact google support to modify it. Have you built. saved, and downloaded your google home device spoken translation table in ISY Portal yet? This appears to be a good account connection but bad data table linking.

Amazon by far. I have had lots of problems with google that I didn't have with Alexa. Main problem is google wants to apply their artificial intelligence technique to home automation. That means guessing at what it thinks you said and grouping all devices by any common word...like 'lamp' so that a command with a common word in it may affect all devices containing that name. This makes very frustrating HA operation. Google doesn't seem to allow any calendar account except your google one. Try using that on two mobile phones without sharing email. Alexa allows other brands of calendars without complaining. Most of the time you just guess with google as they don't think users should know anything that 'they will handle better than you can' or should I say 'you are allowed to handle'. 'Total control...end to end' was nothing compared to what google controls while hiding it.

The details given are not always enough to troubleshoot a wiring as complex as I believe this is becoming. I also recommend an electrician to sort you out. Sent from my SM-G930W8 using Tapatalk

I think you would really appreciate the difference between a constantly on guard device that listens to your every whim vs a cell phone that you have to get out of your pocket, turn it on, run an app, wait for the app to connect and then talk to it, maybe after pushing a button to activate it. We accumulate shopping items by voice, stuff calendar event into our mobile phone calendars, ask it for jokes, games, language translations, etc.. etc.. and the list goes on as we find more for it everyday. Now we use our multiple Alexas'a as a PA system to call the grandchildren up for meals. Get one when they go on sale. You won't regret it.

Insteon scenes were designed before ISY existed.

Another set of switches is not based on anything 4 way. It is based on the idea that nobody would wire two sets of 3 way circuits all in the same two boxes. It would serve no purpose having two switches beside each other with the same function. I suspect there are two more 3way switches elsewhere involved, and three 3 way circuits involved. Each box shown contains one end of a 3way circuit as well as a common 3way circuit shared between the boxes shown. The usage of 4 way switches in the bottom photo shows somebody used irregular practices.

I have never heard of a California 3 way. I don;t think these are old timers but rather old 4 way switches 4 way switches will work the same as 3way switches if you don't mind paying $30 a switch instead of $4. @trevorst: if you are not a good electrical troubleshooter you may consider getting an electrician with a good reputation. At this point (assuming all wires are disconnected and hot) I would find the breaker for the circuit. Turn it off and tape it over so it doesn't get flipped by accident. Get your meter out and prove all wires to be dead. Test to the metal boxes. Prove your meter still works, elsewhere. Hook your ohmmeter/buzzer from each wire to it's metal box. Touch each other end of wires to the metal box at their end until you can locate the one buzzes/shows continuity. Mark both end s of the wire with a cable number eg: A, B, C, or C1 etc... You may need to find the cable that feeds the lamp fixture by checking for voltage first and then using a continuity tester across the black and white of a cable (probably 14/2). Turn out all the bulbs to see if the continuity stops when the last bulbs is loosened. Mark that cable or wires say...."L" for lamps. Once you have done all that you should make yourself a diagram on paper of what you found and post it here. Perhaps somebody can make sense out of it and we can continue.

At one time I had posted a suggestion to have a small square debug area in the admin console under the program Tab, that we could place 2 or 3 variables and their current values for debug purposes. The idea was pooh-poohed at the time, and I cannot find the posting now. You could start a new thread in the suggestions thread, and see if more support will happen this time around. It would be nice to debug while watching programs and variable results (even a pseudo flag) on the same screen.

It should be noted that in the Admin Console, Programs must be loaded first before the variables Tab will show up. Variables are part of the program grouping in the ISY.