Jump to content

Jimbo.Automates

Members
  • Posts

    4650
  • Joined

  • Last visited

Everything posted by Jimbo.Automates

  1. Oberck, if you say yours solve both 1 and 2 from the op, that would make this simpler Sent from my Nexus 5 using Tapatalk
  2. oberck, the difference between this setup and the one on the wiki is detailed in the op. I will try to find time later this week or this weekend to add a second button to one of my doors and test it. Jim Sent from my Nexus 5 using Tapatalk
  3. I totally agree with everything you said. Sent from my Nexus 5 using Tapatalk
  4. You should be able to configure the new routers base ip address to what you had before. Was the ISY configured to use dhcp or a hard address? Sent from my Nexus 7 using Tapatalk
  5. Those are instructions to create a client to talk with the ISY. There may be a way to create a ISY module to accomplish this, but that is a lot of work for a simple fix. I've asked UDI to chime in on this subject... Sent from my Nexus 5 using Tapatalk
  6. We know that using a proxy like you mentioned with Google works, examples using a web server on a nas device were posted. To do it with Google opens a lot of security issues that I don't want to get into. I have requested a change for the ISY firmware, of course it is possible, but it was given low priority by UDI. Sent from my Nexus 5 using Tapatalk
  7. An understanding of your intentions you mentioned above would have been helpful. Both MWareman and myself are seasoned ISY user/programmer types along with others in the posts I mentioned above. It was confirmed by UDI that there didn't seem to be a way to do this without a proxy. The easiest fix for this is for the foscam set_alarm to allow the URL with embedded username/password, or have the ISY REST interface allow passing the username/password as parameters. It would be awesome to have a cleaner interface between foscam and ISY so any help you can provide would be appreciated. Sent from my Nexus 7 using Tapatalk
  8. Sorry if I offended you, it was not meant that way. I only a have a few decades of programming experience so you obviously know more than me. But I do have a few years of ISY experience.. I will leave this discussion now. Sent from my Nexus 7 using Tapatalk
  9. My point is. That even using Java, please see the link I provided in my prior post. You should be able to launch something that can go to the "Real" URL without any need to included the User Id and Password in the HTTP URL in the camera. I know absolutely "Nothing" about ISY hardware. That said. Even the Java example shown in my last link seems capable to do this. Without the need of a proxy. Maybe some other ISY users with programming experience using the web/java interfaces has better suggestions on what methods should be used. But most likely there are methods that can be used. Without the need of a proxy. Don It's not Java. It's Javascript, which is very different... Neither the camera or ISY support Javascript so it's not possible the way you suggest. I appreciate you trying to help, but if you don't know the hardware/software supported by the ISY then it's not really helpful. Sent from my Nexus 7 using Tapatalk
  10. That is correct. If we could send username and password as parameters that would also solve the original problem. I think I requested UDI to support that... Sent from my Nexus 7 using Tapatalk
  11. 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
  12. 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
  13. 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
  14. 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
  15. 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
  16. 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
  17. 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
  18. 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
  19. 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
  20. +1 for sure. Welcome Mike! Sent from my Nexus 7 using Tapatalk
  21. 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
  22. 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
  23. 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
  24. 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
  25. 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
×
×
  • Create New...