ST platform/hub/camera communication delay. If that delay is too long it’ll timeout and the picture wont’ show up. Reboot your camera and hub (unplug/replug) and it helps sometimes. If the platform is running slow you can’t do much about it.
I’ve been using the device type for a few weeks and starting the last couple of days the motion alarm and take picture commands are not working. I removed the device and changed the IP in case it was corrupted, but still no go.
Changing LED, Alarm Status etc… works. I just cannot take pictures and the motion alarm smart app is no longer working either.
I’m using Foscam IP Camera, v2.3.3. Snapshot quality was reduced to low to see if that would help, but didn’t change anything.
I am getting the motion alarms though the Foscam app, so I know the camera is working.
Any ideas?
Same happens for me with pictures taking. I reboot camera the first picture works. I then take another picture and it does not work.
I do not use the motion through this device type but through my diskstation device type.
What is diskstation? is that your NVR / DVR?
I was able to get it to take a few pics, but now nothing again. Motion still not working through the device type.
Go back to the V1 hub or keep rebooting the hub
Seriously report it to ST support that after a reboot it works fine then it stops after a while.
You platform instance scheduling is broken, contact ST support they have a tool to fix it.
What about the motion? That was working fine until the other day. Even after a reboot it doesn’t work.
See the posts above, the ST platform timers are broken and stop working after a while for some users. The timers are required for the motion detection to work. Put in a request to ST to allow custom apps to run locally. That way the users won’t be dependent on a slow/broken platform and can harness the full power of the v2 hubs. For some reason this broken timer impacts v2 hubs more than v1 hubs.
Yea, its my NVR.
I’ll test again and report my issue to ST.
I am having an issue… I have 2 Foscam IP cameras and have set everything up as instructed. When I go into the individual device configuration on the ST app, once I have entered all of the pertinent information (such as Name, Room, Camera’s IP address, Port, Username, and Password), when I click on next, I get an error that states “Please fill out all required fields”… any thoughts/suggestions?
Many thanks in advance for the assist.
If you’ve entered all the required fields and it’s still giving the error, take a snapshot and send it to support@smartthings.com
It may be a bug in their ST phone app specific to your phone (which phone BTW?). It’s working fine on the iPhone and Galaxy S.
See the posts above, the ST platform timers are broken and stop working after a while for some users. The timers are required for the motion detection to work. Put in a request to ST to allow custom apps to run locally. That way the users won’t be dependent on a slow/broken platform and can harness the full power of the v2 hubs. For some reason this broken timer impacts v2 hubs more than v1 hubs.
Excuse my ignorance (still new to ST), but would running the new UPDATE option in the IDE help fix it for me when it is broken?
Quick update. I changed my camera address to use a public IP (Forwarding through my router) and it works perfectly. The image shows up almost instantly and motion alerts are working.
My camera does support push notifications at least to the FOSCAM android app. Would this also be supported in this SmartApp? If I turn it on it doesn’t work. Turning it off works fine.
Another update. I changed the code in the DH to allow push on even the HD camera and also then enabled it through the settings on the smart app and I am now getting push notifications.
It would be nice if you included this as an option on the DH rather than using the HD option to set push / poll. For ref my camera is the FI9853EP.
Not sure what this means? What’s DH?
Sorry Device Handler. New here see a lot of people using that…
What change did you make to the DH? HD cameras don’t support push notifications by design (and specifications). This is a feature I’ve requested Foscam to integrate into their next release.
Are you sure? Mine has the option in the settings to enable push and it works for me. All I did was force the DH to use poll rather than decide based on HD vs SD.
There are two separate things. One in the API and according to the SDK HD camera’s dont’ have a push option, SD does. So I contacted foscam tech devs and they confirmed the same, hence my request to them to bring it to HD also.
There is however a push notification in their own Foscam phone app. That’s a private API that they don’t want to expose (yet).
Also you mentioned that you enabled poll. So assuming what you’re seeing is a poll result. If you open live logging it’ll tell you, If you’re in push mode it’ll talk about registering with the push service API otherwise if in poll mode you’ll notice the polling.
PM me with the details and I’ll be happy to take a look at it if I’m missing something.
Looks like the hub is running slower than the platform here. Routing it through the LAN is causing enough delays to cause the camera to timeout I think. Other folks have also noticed this before (see earlier posts), esp with the v2 hub.