Jimbo.Automates

Do any of you know if all functionality is available thru Mobilinc for Android?

Thanks for all this info. This is making me think I should return my 6 2441TH's that I haven't had time to install yet. Sent from my Nexus 7 using Tapatalk

Yes, when you put B in scene 1 with on level of zero it will turn off B when scene 1 is active. that is how mutually exclusive scenes work. But I don't think you can do that for A in scene 2,since a has the load. I've avoided this since I usually want the ability to control the load on its own when needed.

And if you put KPL.B in scene 1 as a responder with level 0, then B will turn off when A is enabled.

Thanks, I'm very familiar with curl and xml, so could do it from a web server, or hopefully with V5.

Thanks for that endorsement! I'm in the market for a good outdoor camera like that so will check that one out! Does it have an api to receive from and send to the ISY network module like we can do with the foscams?

Yes, Mobilinc support of Android does lag behind iOS. But, it's the best/only choice. The camera part integrated in isn't a big deal for me, there are plenty of good android apps like TinyCam or IP Cam Viewer.

What does that program do? It looks like the then runs itself? To run the program in mobilinc just browse to it and run it, and you can favorite a program in mobilinc. Sent from my Nexus 7 using Tapatalk

Sorry I contributed to the confusion, it seems that most people call 6 and 8 button Keypad Dimmer and Keypad Switch KPL's... My confusion came from SWL which to me, means a single paddle switch link... There are many ways to do it, but personally I would create a scene with the main button as the controller and the D button as a responder, set to off.

Yes, create a scene with the SWL as the controller and add the KPL.D to the scene. If you want the D to be off when the SWL is on, the select the SWL inside the scene and adjust the level of the D. I may be confused on exactly what you want, so if this doesn't make sense, describe your requirement in more detail.

Add the D button to the other scene as a responder and set the on level to zero for the D for the controller of the other scene. Sent from my Nexus 7 using Tapatalk

Haha, I'm the furthest from college party towns or wild resorts! Neither were big names, Surf and Sand in Laguna, and I can't remember the name of the other one, but it was a nice place in Pismo Beach, not Santa Barbara. Sent from my Nexus 7 using Tapatalk

Most Internet isn't blocked at work, just some sites, and any site coming from any of the Dyndns type services. It was actually 2 places one in Laguna Beach, and one in Santa Barbara.

Yes, I was using Dyndns but it's blocked from being used from my work wifi and a one hotel I just stayed at recently

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