Foscam Universal Internal Device Type (HD\Non-HD with Alarm\LED\PTZ Control)

Can anyone help, I think I’m doing something wrong with the IP syntax

MY device is at 192.168.1.102 and appears on the router host list as camera assigned by DHCP. I can access the foscam HTTP user interface at http:/192.168.1.102:88. The HTTPS port is 443. The ONVIF port is 888.

I have the following ST IDE settings

Device Network Id http://192.168.1.100:88

IP address/Hostname: camera
Port: 88
Preset 1: Kitchen1
Preset 2: LivingRoom1
Preset 3: Wall
Cruise Map 1: EdsCruise
Cruise Map 2:

User/Password is tested and confirmed correct.

Is this the correct syntax for the IP address/hostnames? Do they need http://? Is there a way to test the connection settings? For additional info currently the Preset names are not being transferred from the IDE to the ST App but the IP address and password are.

Thanks

I’d like to buy a Foscam HD. Does anyone have a recommendation for a model to get? I believe I’d be using this device type. Thanks all!

@eparkerjr - I have two Foscam cameras (one old one and one new HD one) both on 10.x.x.x n network.

What I find interesting is that I dont even get the option to input the IP address when I create the new device type using the above code and then create the device using it. I just get the option of entering username and password… that cannot be right ?

I have deleted the whole device setup and redone from scratch… without any luck. Thoughts ?

Make sure you are using the right Foscam device type. It will be down near the bottom of the list near any other of your own device types. There is also a ST Foscam device type (that’s not supported I assume) in the IDE that AFAIK does not work.

I am really new to this.
I am having the same problem as @zj4x4 … but my IP address is in the 192. format . It was not changing the IP address automatically so I tried to do it manually. When you first configure it what are you supposed to set the Device Network ID as ? Even though the logs are saying its changing when I go back to the device its still whatever ( I have tried random numbers or the IP:PORT format ) . I am able to connect to camera using the IP address just fine.

here are my logs … can anyone help please ?
Parsing 'index:01, mac:E8ABFA0C7E50, ip:C0A80198, port:0063, headers:SFRUUC8xLjEgNDA0IE5vdCBGb3VuZA0KQ29udGVudC1UeXBlOiB0ZXh0L2h0bWwNCkNvbnRlbnQtTGVuZ3RoOiAzNDUNCkRhdGU6IFNhdCwgMDggTm92IDIwMTQgMDM6MzI6MDMgR01UDQpTZXJ2ZXI6IGxpZ2h0dHBkLzEuNC4zMQ==, body:PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iaXNvLTg4NTktMSI/Pgo8IURPQ1RZUEUgaHRtbCBQVUJMSUMgIi0vL1czQy8vRFREIFhIVE1MIDEuMCBUcmFuc2l0aW9uYWwvL0VOIgogICAgICAgICAiaHR0cDovL3d3dy53My5vcmcvVFIveGh0bWwxL0RURC94aHRtbDEtdHJhbnNpdGlvbmFsLmR0ZCI+CjxodG1sIHhtbG5zPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hodG1sIiB4bWw6bGFuZz0iZW4iIGxhbmc9ImVuIj4KIDxoZWFkPgogIDx0aXRsZT40MDQgLSBOb3QgRm91bmQ8L3RpdGxlPgogPC9oZWFkPgogPGJvZHk+CiAgPGgxPjQwNCAtIE5vdCBGb3VuZDwvaDE+CiA8L2JvZHk+CjwvaHRtbD4K’
96e7fd9c-d617-40c9-9cfe-f3de7379e285 10:32:05 PM: debug /snapshot.cgi?user=admin&pwd=admin
96e7fd9c-d617-40c9-9cfe-f3de7379e285 10:32:05 PM: debug Executing hubaction on 192.168.1.152:99
96e7fd9c-d617-40c9-9cfe-f3de7379e285 10:32:05 PM: debug Device Network Id set to c0a80198:0063
96e7fd9c-d617-40c9-9cfe-f3de7379e285 10:32:05 PM: debug Taking Photo

My camera specs

Model: FI9821W V2
System Firmware Version : 1.4.1.8
Application Firmware Version : 2.11.1.116
Plugin Version : 3.1.0.5

So I took a look at the code and realized that I had set HD question to “True” instead of “true” which was causing it to use the old CGI rather than the new one so now my camera is connected . But I still have no picture , when I click take I dont get a picture my smartthings app does not display an image . Here are the logs . If I go to the URL directly in a browser I do get an image. Also if I go back to the Things page the “Take” is basically stuck on “Taking” and the tile next to it says “blank”. I am able to set the alarm to on and off and control the camera as well ( I can see the camera moving in my browser ) but I cant see anything on the smarthings app.

I am almost there can someone please help me?

96e7fd9c-d617-40c9-9cfe-f3de7379e285 11:23:47 PM: debug Parsing 'index:01, mac:E8ABFA0C7E50, ip:C0A80198, port:0063, headers:SFRUUC8xLjEgMjAwIE9LDQpDb250ZW50LXR5cGU6IGltYWdlL2pwZWcNCkNvbnRlbnQtTGVuZ3RoOiA0MDk0MQ0KRGF0ZTogU2F0LCAwOCBOb3YgMjAxNCAwNDoyMzo0NCBHTVQNClNlcnZlcjogbGlnaHR0cGQvMS40LjMx’
96e7fd9c-d617-40c9-9cfe-f3de7379e285 11:23:46 PM: debug /cgi-bin/CGIProxy.fcgi?usr=admin&pwd=admin&cmd=snapPicture2
96e7fd9c-d617-40c9-9cfe-f3de7379e285 11:23:46 PM: debug Executing hubaction on 192.168.1.152:99
96e7fd9c-d617-40c9-9cfe-f3de7379e285 11:23:46 PM: debug Device Network Id set to c0a80198:0063
96e7fd9c-d617-40c9-9cfe-f3de7379e285 11:23:46 PM: debug Taking Photo

Need help with my Foscam, SKP19 Universal device, it will control my camera but will not display a picture, I’m a new to this and not sure if there is something else I need to do.
Thanks,
Dolphusk

If you can control it (turn on/off IR, make it move, etc) but can’t get a picture it sounds like the configuration is correct. I had the same issue and after much trial and error I ended up deleting the device and adding it back. It worked for me after this. Not the device type just the actual camera.

I also just added a Foscam 8910. Used the device type, added the camera and I can control PTZ, but not seeing any images?

Can anyone give any advice? Tried removing the camera and re-adding.

Yea I am having that same problem :frowning:

I had this code up and running for several weeks and about Halloween in stopped working and I’m getting the same errors everyone else is talking about.

Has anyone figured out the root cause? I’ve tried deleting and recreating the device with no joy.

Turns out I am having similar issues. I can get it to work with the HD device type and a firewall hole but not the universal one with local access. :expressionless:

Hi,
first of all, thanks for the great effort to write a driver for foscam.
I just tried to get the driver working with partial success: I can call the camera (e.g., set the alarm) but no values are returned (e.g., the status of the alarm when I pull). Looking at the logs revealed that parse is never called. Instead, whenever I pull I see shortly after a message about Sonos:

8:28:40 PM: trace SONOS REPONSE TYPE: Content-Type: text/plain
8:28:40 PM: trace SONOS REPONSE TYPE: Content-Type: text/plain
8:28:39 PM: debug Sending hup action
8:28:39 PM: debug /get_params.cgi?user=XX&pwd=YYY
8:28:39 PM: debug Executing hubaction on 192.168.1.189:80
8:28:39 PM: debug Device Network Id set to c0a801bd:0050

Any idea why it happens/what I am doing wrong?

Thanks,

Tim

I just got a 9821w set up last night and noticed this same alarm issue. I was not having the problem with the 8910w. I may try this code alteration at some point this week, but would love to hear if anyone else that lacks programming skills like me got this to work.

Lacbra, I’ll let you know if I’m successful. Thanks for posting!

I am having the same problem as some others – I can’t pull a picture from the cameras - you click take and it gets sick in “taking”; not sure why, same with all my cameras and I have tried uninstalling and reinstalling cameras (all NON-HD cameras by the way).

Using the latest “Foscam Universal” app you guys have up.

Everything else works (at least from what I can tell – I can PTZ the camera fine and change the other settings but it can’t for the life of me get it to pull a picture from the cams (this just randomly started one day)

Add me to the same club… stuck at taking a picture, but everything else works with PTZ and such… I’d love to get it fully working!

Yup. I am having the same issue with a foscam 8910W. I can control it but now picture. Also seems to freeze the smartthings app as well.

Same problem here… Cannot take a pic with 8910

Same problem here. Does anyone have the date we lost image capture? My poor memory seems to think it was around thanksgiving. Which is close to when Cassandra was implemented for persistent data (sticky post at top of announcements).

Back up and working for me (taking pictures) as of the last few days.

Have a feeling it was an issue saving the picture to the ST cloud that was resolved.

Makes it much more useful; glad to have the feature back – just wish they would integrate live cam into ST.