dbwarner5

@Brian H Yes, am aware that battery items go to sleep. It seems as if though it takes a “cycle” to get it to work. AFter that first cyc.e, i get 100% communications and consistency, but am not sure. How to test it vs a communications issue. How would i check the RF signal at a dual band device nearby? And if its not there, is it a communications issue or the device not broadcasting, the first cycle which is more what i seem to be seeing. Thanks,

I have two of the above on a two separate pole barn overhead doors such that when closed they are in contact with the magnet, open they are not. It seems that when I first open one of the doors, after a period of time has elapsed, ie 1 day or more, I get about a 90% reliability of it registering open. Then a few hours later, when I close the door, I get NO registration of it being closed. However, if I immediately open the door and reclose it any number of times, or manually move the magnet, I get 100% reliable readings. It seems as if the triggerlinc is "going to sleep" and takes a cycle to wake it up enough to properly register. And this "sleep" seems to happen every time when its open, and just randomly when in the closed position. Has anyone else seen this behavior? I can reliably repeat this behavior. Thanks.

@GQuack Glenn! doing well.... always balancing the line between loving my HA and dealing with updates / systems / failures etc! I'll touch base offline from here.... By the way , if items are changing and programs running, the count will differ. I am not sure why, but I went through this a while ago because I had over 900 links and things were acting strange and that is one of the things I learned. So to get an accurate count, you should stop any programs and try to get the system to be static while doing the count.

@Michel Kohanim As you have heard before, wish UDI would develop their own PLM that had capacity corresponding to the isy and was reliable. This is the weakest link by a magnitude of 10 to using ISY / Polisy and all the great things UDI has done.

In regards to the following: Please Note: Due to reported issues, if you are not using a 500 Series Z-Wave board in your ISY then we do not recommend you upgrade to 5.1.0 What is the recommended process to upgrade both z-wave and the isy? Ie: I am on 5.016c with the 300 series.. should I first upgrade the zwave board and then migrate to 5.1? Is there a thread on how to do this? thanks.

you could set a variable for each scene you want, then the variable gets controlled either by time of day or whatever button is pushed on keypad. so Morning may be 1, day 2, etc, party 5, etc.. then based on the variable whenever the motion detector triggers, you run a series of programs, each testing for the varilabe state and then turns the lights on accordingly... So a series of programs that set the variable based on time of day..... a series of programs that set it b tased on the keypad settings, then a series of programs that get run whenever the motion detector triggers. you can then build in resets etc. prog1: if var =1, then morning light settings prog 2; if var =2, then set lights for day e let me know if you need more details along this thought process, but it is pretty straight forward and would work well. etc.

Have been using fanlincs since they came out.. Have replaced ~30% of them through the years. When recently building a new house, with this replacement history, I had the electricians place boxes in convenient places for the fanlincs, like in a closet or in a bathroom cabinet, so that I dont have to access the fan itself in two 10 foot ceiling rooms and one 20 ft room etc. in replacing them. So far in four years, I have had to replace 3 of 5...... Failure seems to follow power surges / outages. I also have temp sensors in the fans or in the rooms and have the fan speed correlated to the temps / season etc.

@JSchumann If you sole purpose is to turn on your interior motion sensors AFTEr you have left the house and the Elk is fully armed, why not just simply put a wait of 2 minutes or so after any elk arming condition? IE: If elk is armed away or armed vacation or armed..etct....then wait 2 minutes, activate interior sensors.. You could even make the timer 10 minutes, unless you think you will miss someone entering your house that soon after you leave?

Perfect summary.....

@TheWabit no problem.. good luck. The ISY is an extremely powerful device and only limited by your imagination and determination to figure it out the nuances of "state" based programming. Even after ~20 years of doing this beginning with X10 telephone responders at a second home, I still learn something or a new trick all the time from folks here. Cheers.

@TheWabit Think of it this way..,. the MS can be in the scene but doesn't have to be. For any scene, you can have multiple ways to "trigger" them. In a scene, any of the devices (depends on kind), can either be a responder or a controller., If its a controller, then its a "trigger" for that scene. For example, if. you have three switches that control three different lights in a room and you want to have a "mood" setting, you could set up a scene to do so, with each light set at the level you want. Now how do you "trigger" that scene? Some possibilities could be: -a Program that calls it on or off, dependant on its IF statement -a controller in the scene itself.. ie, it could be whenever you turn one of the three switches on or off, all three go to the scene setting - could be two of the three switches, it could be all three of the switches etc -Alexa. -keypad button in the scene or keypad that calls a program that turns it on -etc. Glad you got it working the way you want it to! Also remember, that with Waits and Repeats, the IF statement gets re-evaluated, so in your program, the MS turns on, and if its in the time period, the program turns true and turns on the scene and starts the WAIT. At that point it re-evaluates the IF. In your case the MS will still be on as it probably has a 30 or 60 second delay. So the program is still true and continues to the end of the Wait clause. However for example, if you had a second Wait after the first 10 minutes, followed by action xyzzy, the program would never get to xyzzy because the MS would be off, and the program would turn false and stop running. Here is the description from the wiki attached below on this. Its easy to get tripped up by this as your programs grow in complexity. A series of statements within a Then clause (or within an Else clause), up to the next Wait or Repeat statement, are atomic. In other words, all such statements are executed before the conditions of the program are retested. The program's conditions are reevaluated each time a Wait or Repeat statement is encountered, and at the end of each iteration of a Repeat loop. https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Scope,_Precedence_and_Execution_Order Cheers.

@TheWabit One more question for clarification. Do you have the Motion Sensor as a controller of the scene? If you do, that is why your light is coming on. You have now have two triggers for the scene, the MS and the program. And that is why your program is not running the then, as it IS false based on the time, but the MS as controller of the scene is turning it on 24hours a day. If not, then as my earlier post, please copy to clipboard and paste the actual program for review. thanks.

@TheWabit can you post the actual program? In the Admin console, right click on the program and at the bottom choose, Copy to clipboard. then paste it in this forum? Also try to explain in 1-2 sentences EXACTLY what you are trying to achieve. This is not a complex problem, but can sometimes be confusing for those trying to help w./o these two things, which then leads to even more confusion for you!! thanks

Am using 2 Honeywell z-wave thermostats. Integrates well with isy. havent had any problems with them for 4 years now. No latency as everything is local. All programming is done in isy vs at the thermostats. Can also control easily with Alexa. Also relatively easy to read and use. Have an ecobee at a second home. Also z-wave, to a Samsung smartphone hub.. using polyisy node server. Also works really well. A bit easier to walk up and adjust / read.

to add to lilyoyo1, your program is "adjusting" the scene. You still need to turn it on or off. In your case, there is no need to adjust the scene, just turn it on or turn it off. Adjusting the scene will affect the properties of that light for the NEXT time you turn it on, and in of itself, does NOT turn the light on.

You can set up a program in the isy and then give it a voice command in the portal and then simple say to Alex to turn it on, which runs the THEN, or turn it off which runs the ELSE. Many times, I use a very simple program to tie to Alexa, then have it initiate much more complex multiple program events, that previously might have been tied to keypads etc.

also assumes that the xbox is plugged into an isy controlled outlet and that the child cant unplug it and plug it in elsewhere. Router would be a safer way to go. But to build on Mr Bills thoughts, you can easily have the timer program when it ends, disable the program / switch until the next morning.

also look at this wiki https://wiki.universal-devices.com/index.php?title=ISY_Portal_Amazon_Echo_Integration_V3#State_Variables Two sections: State Variables and ISY can talk to you. Holler back if you continue to have trouble

@RichTJ99 For me the most strait forward method is to have Alexa trigger an ISY program either directly, "turn on xyz", or through a simple routine that turns on a variable". I have a ton of Alexa routines, but after a while they get hard to track / read/ edit etc. so I am slowly migrating everything I can to the ISY where editing is easier etc. For example, at night, I simply say to Alexa. "goodnight" and that triggers a variable which triggers ISY to run a whole series of integrated programs, arming security, slowly changing lights that mesh with my nighttime routine etc and step up automatic morning routines such as alarm clocks, coffee lighting, master bedroom fireplace etc. Much easier in ISY.

Great.. for programming, since you only have 8 buttons and 8 zones, you can write a set of programs that if button A is pressed, and the zone is off, then turn it on, otherwise, turn it off. That way the landscaper can turn them on and off easily.

yes, you would need an X10 transiever to receive the x10 signal from the remote and then propagate it into your house wiring system, of which then the EZFLORA would pick it up just like any Insteon type signal. You would need to set up the x10 codes appropriately. It wasn't clear what 8 button remote control you were referring to above, but if its an Insteon 8 button Remote Linc device, you can easily program any of those buttons to turn on each zone for x minutes and then turn it off..... In this manner you could get 8 zones directly. An alternative programing technique if you have more zones is to have certain buttons cycle through a few zones.. with one button as a dedicated all off. If you have 7 or less, then you could still have a dedicated off button and each other button would turn on zones 1-7. The landscaper would just have to be using the remote, somewhat close enough to the house to ensure the signal gets picked up. I do something similar with one where I use the buttons to control the garage doors., So in the winter when out snowblowing, I can easily open and close the garage doors and that works from quite a distance out.

Good luck! I used 5 MSIs for driveway detection for many years w/o any problems. Life span was typically about 3-5 years. I have had to replace now 3 of them with MSII.One is protected, two are not. I tried putting clear nail polish across all joints etc. So far, I have had 3 fail. Likewise, I have replaced some very old X10 motion sensors inside the house is certain rooms / closets with MSII's. What a disaster that has been. Like you, I have had to write / re-write programs to get them to all to work consistently and reliably. and even then I really am never sure if they will work. Some work fine, some dont. Go figure. For the driveway, I have decided to move away from MS and go to two photoelectric beams (https://www.homedepot.com/p/SPT-Wired-Indoor-Outdoor-Photoelectric-Dual-Beam-Motion-Sensor-up-to-550-ft-Indoor-180-ft-Outdoor-15-946A/308004053?MERCH=REC-_-rv_categorypages_rr-_-NA-_-308004053-_-N) and connect them to two I/O lincs that I used to use to control garage doors (before garage door openers went to encrypted signals). May also use Insteon wireless open/close sensors for linking to ISY of which I have two that I havent installed yet as planned on two pole barn doors, but generally want to get away from batteries.

As mentioned above, you can connect any constant power line to the motion sensor shown above and micro switch, along with the micro switch sense wire to the motion sensor load wire. Then use the ISY either via programs to have the micro switch turn on the lights you want, when you want, based on schedules, sunrises, sunsets etc. I think from memory, it would be: incoming white to both Motion Sensor white and to the micro switch white. Same with black. Then the red load from the motion sensor to the sense 1 of the micro switch. The load of the micro switch would not be used. In this manner, the motion sensor should trigger the micro switch on and off, which the ISY can read and react to, however you want or need, such as turning on the other switches you want on via a program.

I bought a 100' ethernet cable for <$10 and just move my ISY around the house, plugging into wherever I have an ethernet connection. Works well for locks that are already installed and need attention etc. Just dont trip and additional advice; do this when your wife is out as they typically dont like blue cables snaking all around the house

I have three of the above. All work adequately. Having gotten the Notification Nodeserver working well on my Polyisy, I am trying to set up some programs to notify me if at anytime a lock is locked and it jams (typically when a door doesn't get closed fully), I will get a high priority notification from the Nodeserver. Notification end is all working fine. The issue is that if the lock jams, for some reason, the ISY programs will not run. There are settings for status = jammed, but they dont do anything either. Lock status is never reported to isy as jammed, so there is no way to determine it that way. Instead, I have two programs, the first one simply tells me it is locked or unlocked. And in the Then (locked response), it calls a second, disabled program that tests if the lock is actually locked and if it isn't, then it runs the high priority notification telling me that the lock is jammed. Seems simple enough. The problem is that the first program won't run if the lock jams. It only runs if the lock completes it cycle, which is stranger since the trigger is based on the lock getting a lock command not completing it. One option as a workaround is to have each of my locking programs (there are many), call the jammed lock program. This would work fine, as the first program always runs if the lock is successfully locked or unlocked. The trick is calling the jam test program consistently. While I can add that to many programs, it will not pick up a remote locking ie from Mobilinc. Again a simple workaround is to put a program into mobilinc that locks etc. vs manipulating the lock directly as a device. Anyone else have any experiences with this? Havent looked at the event viewer yet to see what is happening and why the isy isn't picking up that the lock was told to lock. Here are the programs. Lock Front Door Notification [ID 0225][Parent 020B] If ( 'Lock - Front Door' is switched Alarm Remotely Locked Or 'Lock - Front Door' is switched Alarm Key/Manually Locked Or 'Lock - Front Door' is switched Alarm Locked by Touch Or 'Lock - Front Door' is switched Alarm Locked by Keypad ) And ( 'Lock - Front Door' is not switched Alarm Key/Manually Unlocked Or 'Lock - Front Door' is not switched Alarm Remotely Unlocked Or 'Lock - Front Door' is not switched Alarm Unlocked by Keypad ) Then Set 'Notification Controller / Notify Front Door Lock' Priority Normal Set 'Notification Controller / Notify Front Door Lock' On Run Program 'Lock Front Door Jammed LD' (If). ** this is the line that would call for the jam test program, but this program doesn't trigger if the lock jams even though the if has "switched remotely locked", which I would think would trigger it regardless of the lock's completion status but doesnt, If the lock completes unlocking or locking, the program runs fine. Else Set 'Notification Controller / Notify Front Door Lock' Priority Normal Set 'Notification Controller / Notify Front Door Lock' Set Device Off Message Unlocked Set 'Notification Controller / Notify Front Door Lock' Off Lock Front Door Jammed LD - [ID 0222][Parent 020B][Not Enabled] If 'Lock - Front Door' Status is not Locked Then Set 'Notification Controller / Notify Front Door Lock' Priority High Set 'Notification Controller / Notify Front Door Lock' Set Device Off Message Jammed Set 'Notification Controller / Notify Front Door Lock' Off Wait 2 seconds Set 'Notification Controller / Notify Front Door Lock' Set Device Off Message Unlocked