Yes I don’t see why not, same code just different tiles.
[RELEASE] Foscam Camera Device Handler Universal DTH with Motion Detection - SD (FI89xx), HD Ambarella FI98xx, FI99xx, Cx, Gx, Rx, Ex, Zx, Fosbaby
I seem to be having the excessive logging (every 5 seconds) saying there is motion detected. I’ve updated to 2.3.4 for the device handler.
Of note- motion detect sensitivity level is set to medium. One thing I notice, I set the Motion Detect Take picture option to active and enable the HD model option as well, but when I tap done and return to the settings, they are no longer checked. I can never get them to stay set. I have a 9821W v2
Ah, I see the settings thing is a bug. Got it.
What about the excessive motion? I currently have it facing a wall, so there is zero motion.
If you’re seeing it check for a motion alarm that’s normal, ignore the logging that’s just for debugging. . Don’t confuse checking for an alarm with an alarm. WHen there is an alarm it will notify you and screen icon will change
I’m trying to get the Motion Sensor in the Foscam C1 to be used to turn on Lights.
So far I was able to make this work by setting Up Turning on the Light via the Foscam Alarm Monitor, but I guess this is not how it is supposed to work.
I setup my Light Motion App to turn ON the Lights when there is motion on the regular ST motion sensor and the Foscam C1 motion detector (every works when motion is detected from the regular ST Motion)
Anyway if I turn ON the motion detection, when motion happens it also triggers the Intruder Alarm from the App.
If I turn it OFF, then nothing is detected.
I think I’m missing something, is there a way to have the motion detector up and working without triggering an Intruder Alarm when the system is Disarmed (or even Stay)?
Also there is a delay between Movement / Detection and Light ON, I believe it’s because the App polls the Camera every x seconds about the Motion status, is it planned to support a more Push like model where the Camera will push the notification to the Hub? (I can see the AlarmNotifyType: Pull, maybe Push is next? lol)
So you want to use the camera just like a regular motion sensor to turn on lights?
The app should be able to do that just don’t select any routines or disarm etc. only turn on lights options. You can also write your own custom app or use any smart app from the marketplace / community which turns on lights when there is a motion event. Many apps do that or you can use rules machine or trigger happy to do it.
As for push notifications you should ask Foscam. I’ve requested them add that feature to their HD cameras. Currently only their SD cameras support push notifications. Interesting this something they can re add with just a firmware update.
The ideal would be to have the Camera’s Motion sensor used for Light (or whatever trigger) when the system is disarmed and of course for Alarm when the system is armed.
I used to do that with my old Iris platform and their Cameras, was kinda handy and save the expense of a Motion sensor where the Camera is installed.
I’ll give a try with the Rule Machine.
About Push motion notification, I sent an email to Foscam, wait and see…
I am getting this sequence in the event log when trying to “Take” . Pulling the URl out and running it standalone I get the image back in a browser. Any ideas?
f2581f8e-e1f1-4f88-8ff2-bd32944096cd 1:26:13 PM: debug Falling back to hubAction and retrying command
f2581f8e-e1f1-4f88-8ff2-bd32944096cd 1:26:13 PM: warn Unable to connect to host 220.127.116.11:88, Error: groovy.lang.MissingMethodException: No signature of method: groovy.util.slurpersupport.NodeChild.getText() is applicable for argument types: () values: 
Possible solutions: text(), text(), getAt(groovy.lang.IntRange), getAt(int), getAt(int), getAt(java.lang.String)
f2581f8e-e1f1-4f88-8ff2-bd32944096cd 1:26:13 PM: trace Received response from camera to httpGet, headers=text/html, status=200
f2581f8e-e1f1-4f88-8ff2-bd32944096cd 1:26:13 PM: trace IPAddress 18.104.22.168 is a public IP Address
f2581f8e-e1f1-4f88-8ff2-bd32944096cd 1:26:13 PM: trace Sending command -> http://22.214.171.124:88/cgi-bin/CGIProxy.fcgi?usr=admin&pwd=Txxxxxxxx&cmd=snapPicture2
f2581f8e-e1f1-4f88-8ff2-bd32944096cd 1:26:13 PM: trace Request was successful, data=[[[host:ht1533.myfoscam.org, class:IN, ttl:12, type:A, ip:126.96.36.199]]], status=200
f2581f8e-e1f1-4f88-8ff2-bd32944096cd 1:26:13 PM: debug Taking Photo
The ST cloud can’t reach your camera one possible issue is port forwarding, another could be a firewall.
When you do it yourself in a browser is loops back at the router so it is an incorrect result
What’s before this? This is the fallback mechanism, why did the primary one fail? Reason’s would be the same, port forward / firewall etc. The cloud can’t reach your camera. Use an Internal IP address instead.
I get this:
f2581f8e-e1f1-4f88-8ff2-bd32944096cd 4:58:04 PM: trace Received response from Camera to hubAction
but still no image visible in the App on iOS or Android.
I will test now with an internal IP address. I started there and it did not work. As an aside, all the other interactions with the device (polling, etc) appear to be working via the public address.
Here is the result with a private address
f2581f8e-e1f1-4f88-8ff2-bd32944096cd 4:59:39 PM: trace Received response from Camera to hubAction f2581f8e-e1f1-4f88-8ff2-bd32944096cd 4:59:38 PM: trace IPAddress 192.168.2.226 is a private IP Address f2581f8e-e1f1-4f88-8ff2-bd32944096cd 4:59:38 PM: trace Sending command -> http://192.168.2.226:88/cgi-bin/CGIProxy.fcgi?usr=admin&pwd=XXXXXXX&cmd=snapPicture2 f2581f8e-e1f1-4f88-8ff2-bd32944096cd 4:59:38 PM: debug Taking Photo f2581f8e-e1f1-4f88-8ff2-bd32944096cd 4:59:38 PM: trace IPAddress 192.168.2.226 is a private IP Address
Just bought a license but I can’t get the take picture to work. Clicking it just have a blue cricle and stay there forever. If I use a browser and use the link: http://192.168.15.30:88/cgi-bin/CGIProxy.fcgi?usr=admin&pwd=mypw&cmd=snapPicture2 it load right away.
Looking at the logs, I can see it’s receiving the response but that’s about it, the picture is not showing up:
e252dfda-2add-4daa-93e2-ae06a6de55e6 5:58:24 PM: trace Received response from Camera to hubAction
9965f885-ffa3-425c-9f7c-575a5a57c9f1 5:58:21 PM: trace IPAddress 192.168.15.30 is a private IP Address
9965f885-ffa3-425c-9f7c-575a5a57c9f1 5:58:21 PM: trace Sending command -> http://192.168.15.30:88/cgi-bin/CGIProxy.fcgi?usr=admin&pwd=lmeucp93&cmd=snapPicture2
9965f885-ffa3-425c-9f7c-575a5a57c9f1 5:58:21 PM: debug Taking Photo
I have a Foscam FI9826P. You mention that a slow connection might be the issue here and to use the external url. However, this didn’t work either as you don’t seem to be supporting reverseProxy url. I can’t load my webcam through the ip directly, I need to use the name when trying to connect to the server. Seems like you should be using the url as it instead of the ip…
I’m looking for solution here…
Try entering your external/WAN IP address. I made the change from device IP to WAN IP and it loads much faster.
Also, make sure to setup port forwarding on the router.
Thanks for the suggestion, as I said in my earlier post, I’ve tried to use the WAN URL but it transform the url to my ip, which is a problem since the cam is behind a proxy.
Unfortunately the picture is very sensitive to time and a slow anything can disrupt it. Try rebooting your camera and hub and that helps speed things up.
Yeah, Already did and didn’t have much luck. Where exactly is the timeout happening ? from where to where ? I don’t see any timeout error in the logs at all. Look like it has received the response from Camera to the hubAction and died after.
The timeout would then be from the hub to the cloud ? I’m trying to pin-point where is the problem and see if we can do anything about it. In my opinion, at least logging something in the logs would help identifiy where is the timeout happening ?
As far as the wan URL, would it be possible to use the provided name in the url to connect instead of the ip ?
Looks like Jonathan and I have very similar problems. What happens after the “hubAction” call? I also get pictures back immediately from a direct URL call via a public IP or via the local address. I have tried both ways within the Device with no luck. I also tested the App from on Lan and from outside just in case it was a problem with retrieving the picture to display but still no luck. Maybe this is an App problem - is there any other way to confirm the image is being captured and stored by the Hub into S3?
If it’s an app problem it won’t work for others but if you scroll up you’ll see that’s others were able to resolve it by fixing their setup.
The issue is between the camera and the ST platform. The app just connects them together. If either runs slow the picture isn’t uploaded to the Amazon S3 cloud (no errors are thrown). If it doesn’t upload it won’t show up on the device. It’s working fine for most folks with local and public IP. However you need to configure your router properly with port forwarding. Using local IP introduces another layer in between the camera and the cloud, IE the hub. This slows it down further. Especially with the v2 hub, it adds a lot of latency. Hence the recommendation to use public IP with port forwarding.
Spend some time and scroll through the last 6 months of posts and see how people have gotten their cameras to work and reduce latency issues with the network. It’s a latency issue, so I would suggest focus the efforts on finding out why your network has latency and how to reduce it.
Here are some reasons I’ve seen on this forum which folks have identified fixed and then got it to work eventually
- Reboot your router, hub and camera (50% of issues)
- Use public IP with port forwarding
- Get off WiFi and try it. Some folks have noted their wifi networks were congested and introduce latency. One disabled all devices on his network temporarily and found that it started working. Then one by one isolated the errant device causing network latency when connected to wifi.
- Move back to the v1 hub (if you have it)
- Your platform instance is running slow. If this is the cause then there is nothing you can do about it. This would cause the picture transfer from the camera to the cloud to slow down and then the cloud will drop the picture. As This is instance specific it doesn’t affect all users. Just wait for a while and hope your instance fixes itself through load balancing.
The app works fine when configured and use in the right environment.
I had the no picture problem with one of mine and had to change the port number, fwd the new port and reboot it.