search

blakeblackshear / frigate-hass-integration

Frigate integration for Home Assistant
MIT License
728 stars 114 forks source link

Birdseye Camera Entity switching unavailable after update for v5. #610

Closed k7franklin closed 6 months ago

k7franklin commented 8 months ago

Hi, my birdseye entity is unable to be viewed on home assistant because the integrations imagine that it was unavailable.

In frigate page, birdseye is fine.

Can i disable ther avaliability function on this version?

image

NickM-27 commented 8 months ago

Oh, this is an interesting issue I didn't think of

HarryCover78 commented 8 months ago

Hello, I had the same problem since the 31/01 update (V5.0.0).

The log HA displayed : Using a Frigate server (http://192.168.xx.xx:xxxx) with version 0.12.1-367d724 <= 0.12.1 which is not compatible

I ran the update on my docker: sudo docker pull ghcr.io/blakeblackshear/frigate:stable sudo docker stop frigate && sudo docker rm frigate cd ~/frigate-nvr docker compose up -d

Then click on reload in HA, and my problem is solved: Starting Frigate (0.13.1-34fb1c2)

Regards

NickM-27 commented 8 months ago

actually I was wrong, the birdseye camera is separate and I don't think this is a bug

calebvisage commented 8 months ago

well if it was working before (v0.12.1) and doesn't anymore after updating isn't that considered a bug?

k7franklin commented 8 months ago

I had double checked the frigate docker ports and opened the rtsp restream ports. Now is ok.

apparently the old integration used another way to display the camera, while the current one looked for the rtsp of the restream. But i'm not sure about this.

ChildApple commented 7 months ago

Hello, I had the same problem since the 31/01 update (V5.0.0).

The log HA displayed : Using a Frigate server (http://192.168.xx.xx:xxxx) with version 0.12.1-367d724 <= 0.12.1 which is not compatible

I ran the update on my docker: sudo docker pull ghcr.io/blakeblackshear/frigate:stable sudo docker stop frigate && sudo docker rm frigate cd ~/frigate-nvr docker compose up -d

Then click on reload in HA, and my problem is solved: Starting Frigate (0.13.1-34fb1c2)

Regards

this worked like a charm for me i was having the same problem, thanks!

github-actions[bot] commented 6 months ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

sudoxnym commented 4 months ago

Hmmm.. Having this issue on a HAOS Proxmox install. Have had it since setting up Frigate months ago, just now getting to research it. Don't think either options are available in OS? The entity works for a second, then craps the bed and goes unavailable. Using the HA Beta Addon.

zoechi commented 3 months ago

It worked for me for a few weeks after my initial Frigate setup, but now I run into this as well. When I show the device it shows "Streaming", when I click on it it switches to "Unavailable". A suspicion is that the machine running Frigate is too slow (no TPU). I should get the missing components any day to make the machine faster.

tombeynon commented 2 months ago

Same issue here on a new HAOS non-beta install. I don't have a TPU so don't have detect running currently. Frigate is at ~3% CPU but still seeing this behaviour with the birdseye cam showing 'Unavailable' when I try to view in HA. In Frigate the birdseye view works fine, so I don't think it's a performance issue.

Edit: tried a few variations - neither 'privileged mode' or enabling/disabling hardware acceleration helps.