Foscam component not working (Foscam FI8905W)

Configuration
1

I have the Foscam FI8905W. Running latest verison of HA on CentOS. I configured it:

camera:
  - platform: foscam
    ip: 192.168.1.xxx
    username: xxxx
    password: xxxx
    port: xx
    name: BackCamera

The credentials are correct. The card shows up, but it looks to be a broken image icon.
foscam

I can access the camera through its own web interface to confirm it’s running.

Checking the browser console, I do see:

foscam_error
foscam_error1917×63 8.22 KB

I assume one of these is related, likely the 500 error. But that URL is HA’s address, so that means HA is getting an error?

2

Do you have any errors in the actual home-assistant.log file?

3

I see no errors. Only normal stuff:

2019-09-21 18:27:17 INFO (SyncWorker_8) [homeassistant.loader] Loaded foscam from homeassistant.components.foscam
2019-09-21 18:27:17 INFO (MainThread) [homeassistant.components.camera] Setting up camera.foscam
...
2019-09-21 18:27:05 INFO (SyncWorker_0) [homeassistant.loader] Loaded camera from homeassistant.components.camera
2019-09-21 18:27:17 INFO (MainThread) [homeassistant.setup] Setting up camera
2019-09-21 18:27:17 INFO (MainThread) [homeassistant.components.camera] Setting up camera.foscam
2019-09-21 18:27:17 INFO (MainThread) [homeassistant.components.camera] Setting up camera.ring
2019-09-21 18:27:20 INFO (MainThread) [homeassistant.setup] Setup of domain camera took 2.6 seconds.
4

try clearing the cache. I get those gray boxes occasionally and a reload of the browser window or maybe even a restart of HA usually fixes it.

I have had a few times where rebooting the camera was necessary tho.

5

I still get the same issue after trying that.

Attempting the API URL that’s listed in the error presents a 500 error, it looks to be coming from camera_proxy in HA.

6

I’m on the latest version of HA (v0.99.1) and use the foscam integration for 5 cameras and I’m not having any issues.

are you sure you are inputting the correct IP address and Port for the camera’s in the config?

And make sure the camera is set up correctly. for example, I don’t use https to access my cameras. I use just http. I don’t know if that makes any difference but it could be a similar camera set up issue.

7

Yes, correct IP and port. It doesn’t offer HTTPS, so it is indeed HTTP.

I worked around it, had to define it as mjpeg and point to the raw URL. I get the feeling the component doesn’t support my model.

8

I just looked at what I use for my cameras and realized that I use a custom component for my one SD foscam (FI8910W). You could probably use it too.

However, the component hasn’t been updated in a while (but it still works perfectly fine) so the instructions still have the old way of installing things before “the great migration”.

It’s easy enough to change how you install it tho. If you want to try it just let me know and I can post the updated install instructions here.

1 Like
9

THE FIX:

Old topic but I needed to specify that the RTSP port is ALSO 88 on these cameras when adding via the the Foscam integration.

1 Like
10

I had a lot of problems recently with my two Foscam camera’s, one a C2, the other one a FI9961EP camera, using the standard Foscam integration. I tried many different solutions, including using the Synology Surveillance one.
But the best solution is to use the ONVIF integration.
First check whether your camera supports ONVIF (using the Foscam VMS software, under setup), then note the relevant port, my ports were 888.
Then go to HA Integrations and search for the ONVIF integration.
To set it up enter the camera name, the local IP address and the ONVIF port number. On the next screen fill in the Username and Password (you need it). Hit enter and you have created two new entities, one for each camera profile:

camera.camera_name_prof0_name
camera.camera_name_prof1_name

For me only profile 0 works. But it works like a charm. Use one of the picture entity Lovelace front end cards to present a live stream from the camera.

2 Likes