larryllix

I have been told that the battLow reset when ISY does a MS query via a program. I am not sure if this is true (haven't proven it to myself) but I have a separate query only program for each MS. Again, many of us have given up on the lowBatt actually working. Some of my 12 units work sometime, some never work, and some may work all the time, some work while the battery has a few more months of energy left. Mant techniques have been tried only to leave users with... ...."just replace the battery when the light stops working". See many other previous threads for the same result. I have written logging software to record the last four LowBatt signals in a variable. Interesting as it remebers who sent me a lowBatt signal while on holidays. Partially a waste of time. Here are some MS quirks: tap the link button to send a MS motion detected On/Off alternately tap the link button once to reset the lowBatt signal tap the link button 7 times quickly to force the send of Dark On/Off signal without 5 minutes of delay. (testing sensing levels?)

Saves the latest state to the "init to" portion of the variable, that ISY transfers into the variable when booting up. When ISY boots up the variable will look as if nothing happened.

I have never seen one. I use the trial and error method. I always hope for one more trial than error though. Sent from my SM-G930W8 using Tapatalk

Yes. That is exactly the way to do it. Most don't find the lowbatt signal always reliable. When batteries get low you should see a multiple flash for every motion detected. Sent from my SM-G930W8 using Tapatalk

I have to concur with Apostolakisl's ideas and reports. I have read a few cases where people have connected an out building 500' away before but not 600'. If the circuit is fairly noise free, I don't see why the powerline signals would not do it. OTOH, signal extenders may work off RF only and not work at this distance. Try a couple of plug-in modules at receptacles very close to each panel, to get a feel if it will work. Make sure they are both on the same phase of the grid.

Another technique you may consider is creating a program to run about 4:00 AM each day that turns off every device that shouldn't be left on permanently. This can help if all-else-fails, on vacation etc.. You can rest assured that things will get turned off while you are gone.\ and is in addition to what you are doing here. Luckily with the LED bulbs now, most of this is not so critical as it was with a few hundred watts of incandescent burning away.

I try very hard to avoid using google account access for any other devices / software. After years of experience with that process, google has changed their security about three times and I had to basically start over with all google apps and android phone workings. Sounds like a great idea but when your password changes, almost every app you enabled with google security stops working and it can be very difficult to get them back without a complete factory reset of everything you own.. Google never forgets. Switching to www.duckduckgo.com for a search engine has resulted in a lot less intelligent google spy pop-ups on my android devices and now I have also discovered my router was using a default google DNS. That has been changed and some web accesses are actually faster, now. I am slowly starting to feel I am getting some privacy back.

CAO Wireless Tags Sent from my SM-G930W8 using Tapatalk

If you are using a logic element that has a Status then only one If logic line is needed, as On will run True, and Off will run Else. On a SwitchLinc, control switched On/Off is from the paddle presses, and status is from the bulb dimmer position. rograms watching control/switched watch paddle operations only, while status watches for anything that modifies the dimmer position. OK. no nightmares....K?

I was thinking opposite that it would not run but..... "Not Enabled" only affect the trigger elements in the "If" section, and since there are no lines of code (at all) in the "If"...... ....thus you have it and you have proven it again. You're good! It must be the name! Side Note: About ten years ago I built a new house and moved to a small town area where much to my dismay it seems about a third of the males are named "Larry". Geeesh! True story... Just this morning, on our usual Sunday morning breakfast in one of the local watering holes, we take my next door neighbour with us for breakfast. (His name is "Larry", also). While having breakfast, who shows up but the local small time, fresh egg dealer, along with his helper. (His name is "Larry", also). Next my neighbour claims Larry is his cousin, and introduces him as well, to his helper named....... "Larry"! Here we are in one restaurant, with a total of 7 people (not counting cook and waitress) , including the vendor and helper, and four of us are named...Larry! I didn't have the nerve to ask the stranger at another table.

Only since you have such a great and powerful name... and nationality like the majority of us here. We don't know what the program "AtStartupTime" contains in it but as a guess (It is enabled to run at startup) Depending on the result of the If section logic in that program the above program may run Then or Else. The program status (true/False) is dependent on what logically conclusion was determined in it's last run. ISY remembers that. It is a bit of a cloaked method to determine whether the 'AtStartupTime' program has ever run but not to determine if it is currently running so I avoid using the program testing logic and use variables for my program logic. It is more easily understood and less obscure to find later. hmmmmm... 'garage entry'? are you having troubles with the reverse status of an IOLink monitoring your garage door?

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.