Foscam camera works, but claims to be "unavailable"

Configuration
1

I have a Foscam R4 camera connected via the Foscam integration. My problem is that the camera shows as “unavailable”, even though the image is updating.

Reloading the integration sets the status correctly, but after about 20 minutes or so, the status changes back to “unavailable”.

Accessing the camera through the Foscam iOS app works fine.

I don’t have any Foscam cloud services set up, just RTSP.

Any ideas about what might be happening?

2

Did you ever find out why this is happening? I have the same issue.

3

Unfortunately, no. I wanted more than a basic camera, anyway, so I removed the integration & devices and connected the camera via Frigate.

4

I’m having the same issue. Any ideas how to solve it?
What would be the best/easiest alternative to integrate my Foscam R2 and use the PTZ presets?

Thanks!

5

Since a few days my foscam image in a home assistant Lovelace card turned black and the entity shows ‘unavailable’.
The camera works fine through the foscam app.

6

I just updated from 2021.3.4 where my foscam camera’s configured via yaml worked fine.
The current version rejects the yaml configuration and requires I use the UI to configure.
I had to enter the same data several times before it was accepted, when it fails to connect it blanks out the data which is annoying.

Now I have the camera’s configured via the UI and I am getting the same issue. It displays 1 static image same as in 2021.3.4 but it places “Unavailable” on the image and clicking on the image used to open a popup window with live video, now it opens with no image at all.

Has anyone figured out how to make these camera’s work so we can get live video and not just 1 screen shot?

7

Just added a G4 camera, and I have the same problem. However, I have several Insteon cameras that work just fine. The cameras were supposedly made by Foscam, and the Insteon cameras work with the Foscam VMS. The only difference is the port setting and the fact that the Insteon cameras go through the Insteon hub.

8

For me this was caused by using the default RTSP port of 554, and not RTSP port 88. With these settings it worked properly. I had to delete the old device and re-create.
image