Jimbo.Automates

Have you tried that? It contains Javascript which has to be run on the client side, which in this case is the camera, so I don't see how that will work. Sent from my Nexus 7 using Tapatalk

Yes that is what I am saying. The webserver does not have a way to do it, and the Rest interface requires username and password which is the original problem. Sent from my Nexus 7 using Tapatalk

I am back from vacation and can try to look into this tomorrow. I just wanted to verify that this was your final status before I looked at it. Sent from my Nexus 7 using Tapatalk

Here is my point. First. Please remember that I have absolutely no idea of what you do or don't have access to. Whatever HTTP URL you use could be used to pass that information to the URL you would like to use. Meaning the HTTP URL launches some php/script URL that in fact actually does the formatting for the real URL. So, when you say proxy. I think of a proxy as being located on another system vs. calling a URL on the same system that uses a the real URL that is failing directly from the camera. I have no idea of what the ISY series supports. Don The ISY does not support what you suggest. It has to be done by a proxy as detailed in the other post. Sent from my Nexus 7 using Tapatalk

Yes, you were the one I was referring to that did a lot of testing on this subject viewtopic.php?p=111432#p111432 Sent from my Nexus 7 using Tapatalk

Don, Thanks for trying to help with this, but it was acknowledged on the foscam forum link, and through many tests by myself and others on the other udi forum link I listed that the foscam firmware does not allow having a username and password embedded in the URL, and that is the only way the ISY will do authorization with the rest interface. So we are stuck with using a proxy. Sent from my Nexus 7 using Tapatalk

Trying to have the camera alarm call the ISY rest interface with a username and password viewtopic.php?f=51&t=8666 Sent from my Nexus 5 using Tapatalk

Yes, I was able to do with Foscam on the URL and did not receive any error message. Checking the get_params.cgi, I got the results as per below. I am using FOSCAM with Device Firmware Version 11.37.2.56. However, my ISY variable is not changing. Are you having the same issue? I was never able to get this working either after trying many options... http://foscam.us/forum/post44644.html#p44644 Sent from my Nexus 7 using Tapatalk

Yes the new button status would need to be ORed with the current button inside parens , and added to the scene as a responder. I would try this, but I'm leaving on a vacation today... Sent from my Nexus 7 using Tapatalk

+1 for sure. Welcome Mike! Sent from my Nexus 7 using Tapatalk

I could not agree more. I have considered looking at other hardware just because I want a better interface on Android, but I love to many things about the ISY to switch. Mobilinc is okay on Android but could be a lot better. I would donate to a kickstarter project. I already pay for the mobilinc subscription even though I don't really need it, but will be canceling it this year if we don't see a new version that actually looks and behaves more like an android app. Sent from my Nexus 7 using Tapatalk

I'd be very interested in your programs as well. I had posted mine on here a while back which did everything yours do, but I really like the additional sensor. Sent from my Nexus 7 using Tapatalk

Oh yeah, I think you are correct, although I can't test it since mobilinc is very broken on the latest version of Android. Sent from my Nexus 7 using Tapatalk

Jonnyt, I did exactly the same thing with the X10 module just to see it in mobilinc. But now I just use a program as a favorite to toggle the variable. - Jim Sent from my Nexus 7 using Tapatalk

Great, glad to hear it is working for you. I should have added more notes in the op about the variable types... Sent from my Nexus 7 using Tapatalk

You're welcome. I'm not sure what would be wrong is the sensor status is not correct. Must be a communication issue? Sent from my SAMSUNG-SGH-I337 using Tapatalk 4

Tammy, That resource is using the network module to send me a notification using pushover. I you have not purchased the network module you can use email or text message, or just leave it out. The later post was a new program. You don't have to set the init value yourself, the first time the program runs it will set it for you. Glad you like the programs! Jim Sent from my SAMSUNG-SGH-I337 using Tapatalk 4

If your single program to toggle the variable was triggered off that same variable, and the variable is a state type, then the program will run continuously. You have to disable the program. Sent from my SAMSUNG-SGH-I337 using Tapatalk 4

Write a program to toggle or enable/disable the variable. Then you could use MobiLinc to run that program. Sent from my SAMSUNG-SGH-I337 using Tapatalk 4

Here's the fix for the power outage issue, read the comments for more info. Also, like I mention in the comments, I did change the '000 ButtonOn' to use '100%' instead of of 'not Off' which probably would fix it as well, but I didn't test it. If $i.GDM_DontWatch is -1 And ( Status 'ZZ-Buttons / Front House D (GDM)' is Off Or Status 'ZZ-Buttons / Front House D (GDM)' is 100% ) Then $s.GDM = 10 Function: Make sure everything is correct after a reboot. Details: Since I have to monitor the "status" of buttons and not "control", both of the 000 Button On or Off programs will be triggered on boot up of the ISY, and one of them should be true. On a normal reboot of just the ISY it all works properly because the button states are correct. But for some reason during a power outage the button status has not been correct. I think this is because the button is neither off nor on since the KPL is also rebotting, but I am not sure since I don't want to really force a power outage to the ISY & KPL at the exact same time. Originally the ButtonOn program used 'not Off' (because I don't like seeing 100%) so I think that was the root cause, but either way this program makes me feel better... So, the i.GDM_DontWatch has it's init value as -1, so when the ISY boots up, the 000 Button Off and On will not ever be true. This program runs the 010 Done, which resets the state. Hopefully the door was not in motion during the power outage, but I don't think I need to worry about that. Also, set the 'Init To' in '010 Done': If $s.GDM is 10 Then $i.GDM_DontWatch = 0 $s.GDM = 0 $i.GDM_DontWatch Init To -1 State machine is all done so start watching again.

Yes, lots of programming.. I did use the setup from the wiki for a while and it didn't meet both 1 & 2 from my OP, but I forget exactly why now since I tried a few different methods. My problem is not a run at startup issue, I don't have any of my programs run at startup. I'm pretty sure issue is that I have to use "status" instead of "control" for the KPL buttons. I know how to fix it, just need to work on it later today. Yes, the relay status never matters to me, especially since it's in momentary B mode. I have had a couple times where the IO Linc sensor input was not right, and still haven't figured out how that happens since it never happens when I have time to look at it. My sensors are normally closed, so that is not an issue for me. Thanks, Jim

Really glad you love them! I did discover an issue this week. We had a power outage and when everything rebooted, it decided to open the garage door while I was gone. Luckily it one of the 004 Failed programs was triggered which sent me a notification! That is on my list to debug this weekend... Sent from my SAMSUNG-SGH-I337 using Tapatalk 4

If it's a power outage, then you can also set the init value for the variable to make it stick. Sent from my SAMSUNG-SGH-I337 using Tapatalk 4

Awesome, glad to hear that someone else likes it and is trying it! Good to hear that you also figured out the problem. The only issue I have had with this since running it on one of my doors for the last couple weeks, is that originally the isy would somehow miss the Status changing from the Sensor occasionally. I changed the two wait commands in the '003 Loop' from 1 to 2 seconds and have not seen the issue since.... I'm not positive that was the issue because even if I queried the Sensor after that happened, it would not return the correct status, so may be my connections are flaky. I've not had time to play with it anymore since then... After thinking about that for a couple seconds, I think the easiest way is to create another Scene, and have these programs turn that scene on or off along with the current scene in the '003 DoorStatus*' programs, and maybe the '003 Loop' if you want them to flash as well. Then you will need another program that monitors one of the kpl's in that scene which sets the scene back to the correct state if a button is pressed.

The software that comes with the camera allows you program it to take pictures and email them when motion is detected. What you can't do is have it pan to where the motion is. I want to do that with mine, just haven't had time. -JIm Sent from my SAMSUNG-SGH-I337 using Tapatalk 4