Jimbo.Automates

Just FYI, this works great if the sensor is in single scene mode, meaning the jumper is installed. But if you have the jumper removed like I do, then status is never sent, only control on for the open and closed node. I have mine configured without the jumper and the open node as the controller for a scene so the light comes on when the door is opened. So, I have to track the status in a separate variable. Sent from my Nexus 7 using Tapatalk

Open the log, or event viewer at level 3 to see what is happening. The only time this has happened to me is when I had an error in a program that caused it it continually rerun itself. Sent from my Nexus 7 using Tapatalk

Welcome to the UDI forums. This is probably the best forum I have ever been involved with, not to mention the great support from UDI. First verify the ISY is seeing the motion by opening the event viewer, set the level to 3, and activate the MS. Post the event trace if you need help understanding it. Post the MS options you have set, and the programs you are using to control the lights by right clicking on the program, or folder containing the programs and select copy to clipboard and paste them in the forum. And here is a good post to start with http://forum.universal-devices.com/index.php?/topic/15033-Motion-Senor-Disable&do=findComment&comment=127025 - Jim Sent from my Nexus 7 using Tapatalk

Yes, I was thinking the exact same thing. Now my to do list just got much longer! Thanks a lot. Sent from my Nexus 7 using Tapatalk

I didn't check the value, but I think it alternated on and off for the 2 I received. Sent from my Nexus 7 using Tapatalk

This can probably be done by putting the first switch in the scene for the second switch and setting the level to on or off. But I think we need a little more description of your requirements.

Yes, with mutually exclusive scenes you can leave the buttons in default toggle mode, and you don't have to have an off button. Some like having the explicit off, but I prefer to use the extra button for something else. I think the details are in the wiki. I learned this a few weeks ago when setting up my first fanlinc. Sent from my Nexus 7 using Tapatalk

I linked using Link Sensor -> Open close sensor, and it shows up as (2421) TriggerLinc v.40 with the 3 nodes.

I have had the issue as well, and resolved it by adding another query in the program that sends the alert. I need to have a level 3 event viewer running and send the log to support, but I haven't done that yet. The suspicion is that it's related to bad communication, but haven't been able to prove that... I do not have trigger reverse enabled, and I am monitoring the sensor, not the relay. Sent from my Nexus 7 using Tapatalk

Make another scene with just those kpl buttons, then a program that monitors all the devices in the other scenes and turns the button scene on or off. That is the only way since you can not check the status of the scene.

Yes, strange. I checked each node and do not get the options button at the bottom. The ISY window still shows them as a "(2421) TriggerLinc V.40" so may be that is why. I purchased them 3/26/14 as 2843-222's, and they are the newer 1.9 firmware based on the label inside. I'm just happy to have a heartbeat since there was no other way to check that they were responding besides opening/closing the door. I've copied and modified the leak sensor monitor to just monitor the hearbeat of these which was really simple.

Teken, I do not get the button for viewing the ISY options, so the heartbeat default is every 24 hours, that's all I know. I've submitted a ticket to support. Sent from my Nexus 7 using Tapatalk

I can confirm the heartbeat does work on these devices. I set up a simple program to notify me on a change: PoolRoomDoor - [ID 0167][Parent 0166] If Control 'Z-HeartBeat / PoolRoomDoor-Heartbeat' is switched On Or Control 'Z-HeartBeat / PoolRoomDoor-Heartbeat' is switched Off Then Send Notification to 'Pushover-Default' Else - No Actions - (To add one, press 'Action') And 24 hours after setting up deleting and re-adding the sensor, I received the notification. Now to modify the leak sensor programs to monitor these heartbeats Although I wish I didn't have to delete and re-add them to see that node

What is triggering the "Holiday reset" program? It has no conditions. Sent from my Nexus 7 using Tapatalk

There are different ways to do this, but here is how i do it http://forum.universal-devices.com/index.php?/topic/14947-My-programs-to-control-a-light-from-motion-and-door-sensor Sent from my Nexus 7 using Tapatalk

Yes I do the same, but don't need programs, I just use mutually exclusive scenes which works great

I just removed, reset, and relinked one of my 2843-222 Rev. 1.9 open/close sensors and I do get a Heartbeat node which I previously did not have, but I do not see the ability to check options. I'll submit a ticket for this if you haven't already.

Thanks for taking the time to respond! I will be changing how I do this based on your suggestions. Does anyone think that having an option for a program to check the status of a scene is a good solution for the future? Seems that having the option to say "if in scene allfront any responder is not off" or "all responders are not off"? Sent from my Nexus 7 using Tapatalk

Some of your questions are answered in my post from yesterday http://forum.universal-devices.com/index.php?/topic/15001-KPL-monitoring-multiple-light-status and to have the button only turn on certain devices in the scene you can set the on level to zero for the responder of that controller in the scene. Sent from my Nexus 7 using Tapatalk

Thanks. Yes, that is what I was going to change to, but tedious to add all the lights to the scene and the program. Especially for the whole house off.

Yes, for that is the part I don't like about option 1.

Eric, yes I was just pointing out another way to handle it. Each way has its advantages and disadvantages. Sent from my Nexus 7 using Tapatalk

I have a KPL button that I use to show the status of a bunch of lights which is used turn them all of at once when any of them are on. I know others do this as well, but they are tedious to setup and I'm wondering if there is a better way that I am not aware of, or possibly an enhancement to the ISY to make this easier. I've long wanted to do this better and another post from last night was asking a similar, but slightly different thing. To simplify this, let's say I have 3 switchlinc's and I want a button on one my KPL's to be lit when ANY of those switches are on, then when the button is turned off, all switches turned off. It can also be used to turn them all on at once as well, but for my use, it's mostly just to turn off any light around the house, or a group of rooms. Based on what I know, there are 2 ways to do this: 1. Create a scene for each switch, switch1, switch2, switch3 with the switches as controllers, and the KPL.A button as a responder in each of them. Then another scene switchall that has the KPL.A as the controller, and all 3 switch scenes as responders. This works great so whenever one or all of the swtiches are turned on, the KPL.A is also turned on, then when the KPL.A is turned off, all switches turn off. The problem is, if you turn on switch1, then turn on switch2, then turn off switch2, the KPL.A turns off. This makes complete sense because of how insteon works, but isn't ideal. 2. Create a scene switchall that has the KPL.A has the controller, and all 3 switches as responders. Then have a program that turns on the KPL.A if any of those switches are on. As my insteon system has grown, this has become tedious to add the device to the scene, and the program. Is there a better way of doing this with Inteon/ISY? If not, I would like to make a proposal for an ISY enhancement to make this easier. Have the ability to check the "status" of a scene, basically "if in scene switchall any device is not off". This would allow us to have a simple program to monitor the scene since all those switches have to be in the scene anyway. Mobilinc kind of does this when showing the status of the scene, by showing a percentage of lights in the scene that are turned on. This is probably not a new idea, and has possibly been discussed before, but in all my searching I haven't found it with a better way to handle this. - Jim

I'm not exactly sure of what you want, but for the KPL button that is the controller of the "all outside lights" scene, if you make it a responder to all 3 of the individual lights scene then it will turn on when any or all of those 3 are on. Then you can press it once to turn them off no matter if 1, 2, or all 3 are on. This advantage of this is that it's all controlled by insteon, no need for a program. The disadvantage is that it tracks the last status, so if 1 is turned on, then 2 is turned on, then off, the all KPL will show off. Sent from my Nexus 7 using Tapatalk

I don't have an ELK, yet, but is is probably stopping the program once the zones are not violated. Put the wait and off's in a separate program and run that program from this one. And make sure to disable the second program so it can't run on its own.