abuttino Posted October 18, 2013 Posted October 18, 2013 I have a 8918W and I try to direct it away from the house when I get home. There are presets that the ISY has pre-programmed into the Network Resources.. If I issue a HTTP REST statement to change the variable, all the rest of the network resources complete except for the camera turning back into position. It looks as if it gets interrupted midstream by something and stops it's movement immediately within about 1 second after it starts. I can't figure out why that would happen. The ISY is the ONLY way I've employed the camera to turn back to position 8. The HTTP Get command in the network resources is: http://myip:myport/decoder_control.cgi? ... d=password I might also add, it goes to position 1 perfectly fine.
Michel Kohanim Posted October 18, 2013 Posted October 18, 2013 Hello abuttino, So, the problem is only on one position. Have you tried running the program manually to see if it works at all? How about when you click on the Test button on the resource. Does that work? With kind regards, Michel
Xathros Posted October 18, 2013 Posted October 18, 2013 I have had 2 of my Foscams lose track of where the "home" position is after a few weeks of operation and as a result, all presets become wrong. A reboot of the camera fixes this. To avoid this, I have built a resource for each cam to reboot early morning daily. -Xathros
abuttino Posted October 18, 2013 Author Posted October 18, 2013 I fixed it... One of the other network resources was apparently interfering with the command.. I can't really tell if it was the ISY or just my network traffic. Amongst the weirdest of problems I've had with networking. The solution was to wait 10 seconds after my initial network commands went through, then initiate the turn sequence. To diagnose it, I went to a bare minimum to ONLY turn the camera. Then added Network resources; one by one, then started adding delays to get the end result of 10 seconds after everything else is finished. The way it's supposed to go is, the phone sends /rest/2/10/4, which initiates the program. The next to last step of the program it sets "10" to 1.. I was FORCED to put this AFTER the 10 second delay, otherwise the program would not finish and turn the camera back. I can only deduce that it may be a problem with concurrent Network Modules being addressed at once. Which still doesn't tell me if it's the ISY or not.
Recommended Posts