Jimbo.Automates

Or a domain name from Google is $12 a year, and dynamic dns is included.

Completely agree. That is why I keep them as separate scenes, so they can be controlled easily from mobilinc. Sent from my Nexus 7 using Tapatalk

I have had strange things happen a couple times when playing around with different ways to control scenes. Try a a restore device for the KPLs that are acting weird. Also if you never factory reset them before installing, I would recommend that and then restore device. I have had a new device act weird before, presumably because it had bad links from factory testing. Sent from my Nexus 7 using Tapatalk

From the attached picture, button A is not in the cosy scene, and button B is not in the Reading scene. So add them as responders with on level at zero for the opposite controller. For mobilinc to work properly you have to also set the desired on level when the scene is selected since mobilinc controls the scene not the KPL button. Sent from my Nexus 7 using Tapatalk

Both buttons should be in both scenes, a controller of the scene, and a responder of the other scene. Then in the scene where they are a responder set their on level to zero. This is called a mutually exclusive scene. Sent from my Nexus 7 using Tapatalk

Yes, the closed node is only used in multi scene mode which is enabled when the jumper is removed. Sent from my Nexus 7 using Tapatalk

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