Interesting, what camera firmware are you using?
[RELEASE] [Universal] Foscam Camera Device Handler with Discovery, Live Video Streaming, Motion Sensor/Alarm Integration (SD/HD/Ambarella/R2)
Is the new update on ST firmware for Monday going to fix that?
Software Ver. 188.8.131.52
I specifically reached out to Tenvis official company support to find out exactly which firmware is the latest for my specific camera (this was just about 3 days ago), and they said it’s the one I have now (which is 184.108.40.206).
One problem with Tenvis cameras (and with this one in particular) is that they are inconsistent (and at the same time, indiscriminate) with their naming conventions, etc (well, it appears they don’t actually have any conventions; they just name things whatever they feel at the moment).
Example 1 = This camera (the IPROBOT3 that I own) now goes by at least two different names.
When I go to THIS URL on Amazon, it tells me that I purchased this camera back in 2014 (so, this page IS where I bought my IPROBOT3). However, the one I bought was actually named IPROBOT3 then, whereas they have changed its name (both here on Amazon as well as on their own website) to TZ100. No big deal; one just needs to keep different product names in mind for exactly the same product.
Example 2 = This camera NAME (IPROBOT3) has been used by Tenvis for at least two completely different cameras.
There was another camera by them that uses a completely different firmware line (and different numbers), but has exactly the same name as mine. If I were to attempt to upload the firmware for the older IPROBOT3 camera to mine, it would most certainly break it.
Unless somebody else can somehow prove to me that they have exactly the same camera model as mine, there’s no way I will attempt putting firmware on it that Tenvis support tells me will brick it.
So, is there any chance that anybody that has a Tenvis IPROBOT3 working with this DH would be willing to help me out? In order to know for sure which actual camera model you have, I will need to see photographs of the device itself (from all angles), as well as screenshots (with appropriate blurring, etc, obviously) of all of the pages in the web admin control panel.
This way, I will be able to see for sure whether or not it’s actually the same product named IPROBOT3 (remember from above, Tenvis has at least two completely different cameras with this exact same name).
If you want to help out, please PM me.
UPDATE: Thanks to @kimmi for the assist.
They sent me some photos of their IPROBOT3 camera as well as screenshots of the admin pages.
Unfortunately, it was exactly what I needed to figure this out, but not what I wanted. lol
As it turns out, their IPROBOT3 that IS working with this Device Handler is the earlier product that Tenvis named IPROBOT3 (referred to sometimes as the 2013 version) and mine is the later one (sometimes referred to as the 2014 version). Two completely different products that look exactly the same in almost every way, but they are on a completely different firmware line.
So, I guess perhaps the wording for this Device Handler, where the Tenvis IPROBOT3 is concerned can still say that it supports the Tenvis IPROBOT3, but it should also include a mention of the fact that it supports the 2013 product with that name, and not the 2014 one.
Thanks a lot for helping out on this. I really appreciate it!
HI3510 IP Camera Device Type (Tenvis IPROBOT3, Instar, Wansview, others...)
I'm having issues connecting to the live stream. I can take photos, reboot, but can't seem to get the live stream to work. It says, "Camera cannot be found". I can view the live stream in a web browser, but not through Smartthings. I'm using Foscam F18921W V2, with the latest firmware installed.
I've rebooted it a few times, uninstalled the handler, and can't seem to figure it out. Any thoughts?
If it helps we've been playing with a variety if phones and connection types (from android tablets, phones, iPhones 4s to 6s), 3G, 4g LTE, wifi public wifi private, different cameras blink, foscam etc.
we've realized a couple of things:
- The video streaming ability depends upon the phone capabilities. It needs to support the codec and stream type parameters
- The video tile is very sensitive to errors in the stream. The slightest delay or dropped packets can cause streaming issues. It isn't very hardy yet hopefully ST could do something about it in future. Eg one camera works and another one only gives audio because it further away and has a low signal. Similarly connection of the Internet quality plays a role. When we have strong stable fast connection it works great but when the connection quality deteriorates (on either end) we start seeing streaming connection issues or only audio or stuff like that. Again very sensitive to streaming errors and delays.
Ah, I have six identical Foscam cameras and this explains why some streams work and others don’t at different times depending on your internet connection.
I got an issue where I wasn't able to connect to my SmartThing App, I got "could-not-parse-the-service-response" for the whole week end. Support first suspected my Ecobee, but that wasn't it.
Support came back to another user @Automatic00 having the same issue that the Foscam Device Handler was causing the issue.
After deleting it, I was also able to reconnect.
What do you think happened there?
No idea. ST architecture should isolate device handlers so this should never arise. Whatever it may be only support can get to the bottom of this. Though I am curious what's going on.
@slagle any thoughts why one DH can impact another DH
Hi RBoy, thanks for the code and tips. But one question, If I want to use ddns and I have a port forwarding. Would be enought to set the ddns name in the IP field and the port? I try with that but didn't work. So not sure how I should configure if I want to use DDNS+PortForwarding.
Thanks in advance!
I don't know if it was clear my question. Better said. I have configure DDNS+Port Forwarding and I'm able to access to my camera from outside of my lan. I use it with foscam application, foscam app let you configure a host or IP, in my case I have a host similar to "xxx.ddns.net" port 88. I try to configure this on the new device I add using your code, but didn't work. Instead of set the Camera IP address I set the hostname: "xxx.ddns.net" is that ok? If that so I'm not sure what I'm doing wrong becuase I don't see anything after that configuration.
Tahnks in advance!
Yes it should work fine. I'm using it the same way.
Check your configuration again maybe there's a typo somewhere. Does it work with the IP address? Possible that the DNS look ups failing since you're using ddns. Check the logs
Foscam Camera Universal Device Handler - version 3.2.4
- Workaround for an issue with the ST platform calling the updated() handler randomly causing random issues (wrong state of flip/mirror and other ST app issues)
Foscam Motion Alarm Monitor SmartApp - version 2.6.1
- (no change)
Looks like I got this working, but my camera image is under the "Take", "Auto", and "On" buttons with a large blank space at the very top. How can I get the video at the top where I assume it belongs (in the blank space)?
Depends on your ST app version and phone version. On the iPhone you get play button on Android you need to click on it and then click on the refresh button when it shows up.
Hi RBoy, thanks a lot for the answer.
Still get the issue but not figuring out which is the problem.
I try both configuration, using private IP address and using URL but nothing...
Device type seems to be fine...
This is what I see on log:
9f4e69d5-bd0a-4ad8-a5c3-be123c8691e9 10:33:22 PM GMT-3: error java.lang.NumberFormatException: For input string: "vazquezramirez"
Using internal IP:
9f4e69d5-bd0a-4ad8-a5c3-be123c8691e9 10:33:21 PM GMT-3: debug Taking Photo
ea3442e8-1609-48c6-a667-f62adf86dc75 10:33:20 PM GMT-3: trace getPhrases(), state.welcomeIssue = null
ea3442e8-1609-48c6-a667-f62adf86dc75 10:33:01 PM GMT-3: trace getPhrases(), state.welcomeIssue = null
ea3442e8-1609-48c6-a667-f62adf86dc75 10:32:55 PM GMT-3: trace getPhrases(), state.welcomeIssue = null
ea3442e8-1609-48c6-a667-f62adf86dc75 10:32:46 PM GMT-3: trace getPhrases(), state.welcomeIssue = null
9f4e69d5-bd0a-4ad8-a5c3-be123c8691e9 10:32:41 PM GMT-3: debug /decoder_control.cgi?command=0&onestep=1&user=admin&pwd=xxxxxxx
9f4e69d5-bd0a-4ad8-a5c3-be123c8691e9 10:32:41 PM GMT-3: debug Executing hubaction on 192.168.1.22:88
9f4e69d5-bd0a-4ad8-a5c3-be123c8691e9 10:32:41 PM GMT-3: debug Device Network Id set to c0a80116:0058
9f4e69d5-bd0a-4ad8-a5c3-be123c8691e9 10:32:40 PM GMT-3: debug /decoder_control.cgi?command=0&onestep=1&user=admin&pwd=xxxxx
9f4e69d5-bd0a-4ad8-a5c3-be123c8691e9 10:32:40 PM GMT-3: debug Executing hubaction on 192.168.1.22:88
9f4e69d5-bd0a-4ad8-a5c3-be123c8691e9 10:32:40 PM GMT-3: debug Device Network Id set to c0a80116:0058
9f4e69d5-bd0a-4ad8-a5c3-be123c8691e9 10:32:39 PM GMT-3: debug /decoder_control.cgi?command=0&onestep=1&user=admin&pwd=xxxxxxx
9f4e69d5-bd0a-4ad8-a5c3-be123c8691e9 10:32:39 PM GMT-3: debug Executing hubaction on 192.168.1.22:88
9f4e69d5-bd0a-4ad8-a5c3-be123c8691e9 10:32:39 PM GMT-3: debug Device Network Id set to c0a80116:0058
ea3442e8-1609-48c6-a667-f62adf86dc75 10:32:05 PM GMT-3: trace getPhrases(), state.welcomeIssue = null
9f4e69d5-bd0a-4ad8-a5c3-be123c8691e9 10:32:00 PM GMT-3: debug /snapshot.cgi?user=admin&pwd=xxxxxx
9f4e69d5-bd0a-4ad8-a5c3-be123c8691e9 10:32:00 PM GMT-3: debug Executing hubaction on 192.168.1.22:88
9f4e69d5-bd0a-4ad8-a5c3-be123c8691e9 10:32:00 PM GMT-3: debug Device Network Id set to c0a80116:0058
9f4e69d5-bd0a-4ad8-a5c3-be123c8691e9 10:32:00 PM GMT-3: debug Taking Photo
ea3442e8-1609-48c6-a667-f62adf86dc75 10:31:50 PM GMT-3: trace getPhrases(), state.welcomeIssue = null
9f4e69d5-bd0a-4ad8-a5c3-be123c8691e9 10:31:45 PM GMT-3: debug /snapshot.cgi?user=admin&pwd=xxxxxx
9f4e69d5-bd0a-4ad8-a5c3-be123c8691e9 10:31:45 PM GMT-3: debug Executing hubaction on 192.168.1.22:88
9f4e69d5-bd0a-4ad8-a5c3-be123c8691e9 10:31:45 PM GMT-3: debug Device Network Id set to c0a80116:0058
9f4e69d5-bd0a-4ad8-a5c3-be123c8691e9 10:31:45 PM GMT-3: debug Taking Photo
ea3442e8-1609-48c6-a667-f62adf86dc75 10:31:38 PM GMT-3: trace getPhrases(), state.welcomeIssue = null
10:30:36 PM GMT-3: info Waiting on events...
10:30:36 PM GMT-3: info For past logs for individual things go to the My Devices section, find the device and click on the Events link on the device information page.
10:30:36 PM GMT-3: info This console provides live logging of your SmartThings.
Are you sure you're entering this in the right box? Looks like you may be entering this where a number is expected (port?). Also filter your logs by the device, its' very hard to understand with everything mixed up. From the looks of it your camera isn't responding so either your configuration is wrong (port/ip/username/password) or your hub can't reach your camera. See the first post for troubleshooting.
Maybe that error is from when I try to set the url on the ip. But then I tried also with internal ip but still the same issue. Maybe that is more clear with the image I have attached.
Hi @RBoy, I've been using the Foscam 9821 with your device handler and smart app and it has been great. Recently I added a Foscam R2 (Full HD) and am having trouble. While I can create a device for the R2 using the device handler and have mostly everything working (e.g. live streaming), it was giving me problem with the motion detection. The web app for this camera appears to have slightly different UI on the motion detection where it can take 3 zones and the user can mark each zone and assign "Lowest, Lower, Low, Medium, High" on each zone. The problem I observed was that whenever the device handler activates the camera for motion detection, it will update/erase the motion detection settings such that zone 1 & 2 will be turned off (boxes unchecked), and zone 3 will be turned on with full frame set to whatever sensitivity level the user has set on the device handler. Unfortunately, the R2 camera will not activate the motion detection under these zone settings. It appears that the other zones (1 & 2) must be activated in the web app settings before it can detect motion. Would it be possible for you to update the device handler to support R2 with zone 1-3 sensitivity settings? Or just add an option in the device handler to avoid changing the zone sensitivity settings (i.e. just use whatever was setup in the web app)? The R2 is a great camera with 1080p resolution, and I would much appreciate if you can update the device handler/smart app to support it soon
UPDATE: I did some more testing and verify that at least zone 1 must be turned on in order to activate motion detection. It seems that the zone activation must be set in correct order, i.e. if only one zone is needed, then it must be zone 1.