search

blakeblackshear / frigate

NVR with realtime local object detection for IP cameras
https://frigate.video
MIT License
17.7k stars 1.62k forks source link

[Config Support]: Cannot playback clips on Android / Home Assistant or Frigate #4594

Closed inspired27 closed 1 year ago

inspired27 commented 1 year ago

Describe the problem you are having

All clips on Android Samsung Galaxy S21 Ultra or Galaxy S10 do not play in Home Assistant App, Home Assistant Frigate Proxy via Chrome or directly ip:5000 Frigate via Chrome on the device.

Message: "The media could not be loaded, either because the server or network failed or because the format is not supported"

Clips playback on PC Chrome, Edge etc fine

Version

0.11.1-2EADA21

Frigate config file

mqtt:
  host: 192.168.1.xxx
  port: 1883
  topic_prefix: frigate
  client_id: frigate
  user: frigate_mqtt
  password: xxxx
  stats_interval: 60

logger:
  default: info
  logs:
    frigate.event: debug  

detectors:
  coral:
    type: edgetpu
    device: usb

cameras:
  Front_Cam:
    ffmpeg:
      output_args:
        record: -f segment -segment_time 10 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c:v copy -c:a aac
        rtmp: -c:v copy -c:a aac -f flv
      inputs:
        - path: rtsp://user:pass@192.168.1.xxx:554/Streaming/Channels/1
          roles:
            - record
        - path: rtsp://user:pass@192.168.1.xxx:554/Streaming/Channels/2
          roles:
            - detect
            - rtmp
    detect:
      height: 536
      width: 1920
      fps: 20
      stationary:
        interval: 0
        threshold: 30
    objects:
      track:
        - car
        - person
        - bicycle
        - motorcycle
      filters:
        person:
          threshold: 0.69
        car:
          mask:
            - 1204,0,1220,203,604,205,596,0
            - 1452,68,1504,137,1419,118,1374,46
            - 185,143,235,112,256,143,216,168
    snapshots:
      enabled: true
      timestamp: true
      bounding_box: true
      crop: True
      height: 500
      retain:
        default: 3
    record:
      enabled: True
      retain:
        days: 0
      events:
        retain:
          default: 5
          mode: motion
        pre_capture: 10
        post_capture: 15
    motion:
      mask:
        - 620,207,624,183,612,157,592,134,592,96,565,69,533,75,508,85,511,118,545,134,545,173,555,209
        - 769,187,767,153,761,122,751,102,738,79,720,61,706,41,687,59,675,83,685,106,698,130,689,157,716,191
        - 911,191,934,159,932,128,930,98,929,77,919,49,909,26,881,0,862,33,850,71,826,100,852,134,856,165,873,195
        - 1078,193,1100,183,1106,163,1108,140,1094,112,1104,79,1096,51,1070,28,1054,57,1029,83,1007,108,1017,138,1029,161,1029,187
        - 1239,203,1267,183,1271,155,1279,89,1271,67,1243,67,1220,106,1198,155,1198,199
        - 1369,214,1389,203,1403,187,1418,155,1418,128,1409,106,1391,79,1359,98,1344,126,1328,161,1324,201
        - 0,536,110,536,222,453,168,321,0,384
        - 0,0,230,0,212,63,140,122,151,161,0,238
        - 1898,0,1898,39,1330,39,1344,0
        - 1326,43,1530,51,1578,142,1920,309,1920,90,1920,0,1334,0
        - 1891,388,1821,536,1920,536,1920,346
    zones:
      zone_0:
        coordinates: 108,536,0,321,439,0,1315,0,1874,409,1829,536    
birdseye:
  enabled: True
  width: 1920
  height: 1080
  quality: 1
  mode: continuous

Relevant log output

[services.d] starting services
[services.d] done.
[2022-12-04 13:15:22] frigate.app                    INFO    : Starting Frigate (0.11.1-2eada21)
Starting migrations
[2022-12-04 13:15:22] peewee_migrate                 INFO    : Starting migrations
There is nothing to migrate
[2022-12-04 13:15:22] peewee_migrate                 INFO    : There is nothing to migrate
[2022-12-04 13:15:22] detector.coral                 INFO    : Starting detection process: 216
[2022-12-04 13:15:22] frigate.app                    INFO    : Output process started: 217
[2022-12-04 13:15:22] frigate.edgetpu                INFO    : Attempting to load TPU as usb
[2022-12-04 13:15:22] ws4py                          INFO    : Using epoll
[2022-12-04 13:15:22] frigate.app                    INFO    : Camera processor started for Front_Cam: 223
[2022-12-04 13:15:22] frigate.app                    INFO    : Capture process started for Front_Cam: 225
[2022-12-04 13:15:23] ws4py                          INFO    : Using epoll
[2022-12-04 13:15:25] frigate.edgetpu                INFO    : TPU found
[2022-12-04 13:15:28] frigate.record                 WARNING : Discarding a corrupt recording segment: Front_Cam-20221204131524.mp4
[2022-12-04 13:15:29] ws4py                          INFO    : Managing websocket [Local => 127.0.0.1:8082 | Remote => 127.0.0.1:41554]
[2022-12-04 13:15:37] ws4py                          INFO    : Terminating websocket [Local => 127.0.0.1:8082 | Remote => 127.0.0.1:41554]
[2022-12-04 13:15:40] frigate.http                   ERROR   : No recordings found for the requested time range
[2022-12-04 13:15:52] frigate.http                   ERROR   : Event does not have recordings: 1670159722.975261-9or1xk
[2022-12-04 13:15:56] frigate.http                   ERROR   : Event does not have recordings: 1670159722.975261-9or1xk
[2022-12-04 13:16:10] ws4py                          INFO    : Managing websocket [Local => 127.0.0.1:5002 | Remote => 127.0.0.1:49654]
[2022-12-04 13:16:29] ws4py                          INFO    : Terminating websocket [Local => 127.0.0.1:5002 | Remote => 127.0.0.1:49654]
[2022-12-04 13:16:29] ws4py                          INFO    : Managing websocket [Local => 127.0.0.1:5002 | Remote => 127.0.0.1:49656]
[2022-12-04 13:16:31] ws4py                          INFO    : Managing websocket [Local => 127.0.0.1:8082 | Remote => 127.0.0.1:41558]
[2022-12-04 13:16:34] ws4py                          INFO    : Terminating websocket [Local => 127.0.0.1:8082 | Remote => 127.0.0.1:41558]
[2022-12-04 13:16:54] ws4py                          INFO    : Managing websocket [Local => 127.0.0.1:8082 | Remote => 127.0.0.1:41560]
[2022-12-04 13:16:55] ws4py                          INFO    : Terminating websocket [Local => 127.0.0.1:8082 | Remote => 127.0.0.1:41560]
[2022-12-04 13:17:07] frigate.http                   ERROR   : Event does not have recordings: 1670159722.975261-9or1xk
[2022-12-04 13:17:10] ws4py                          INFO    : Managing websocket [Local => 127.0.0.1:5002 | Remote => 127.0.0.1:49658]
[2022-12-04 13:18:30] ws4py                          INFO    : Terminating websocket [Local => 127.0.0.1:5002 | Remote => 127.0.0.1:49658]
[2022-12-04 13:18:30] ws4py                          INFO    : Managing websocket [Local => 127.0.0.1:5002 | Remote => 127.0.0.1:49660]
[2022-12-04 13:20:03] ws4py                          INFO    : Terminating websocket [Local => 127.0.0.1:5002 | Remote => 127.0.0.1:49656]
[2022-12-04 13:20:04] ws4py                          INFO    : Managing websocket [Local => 127.0.0.1:5002 | Remote => 127.0.0.1:49662]
[2022-12-04 13:20:47] ws4py                          INFO    : Terminating websocket [Local => 127.0.0.1:5002 | Remote => 127.0.0.1:49662]
[2022-12-04 13:20:47] ws4py                          INFO    : Managing websocket [Local => 127.0.0.1:5002 | Remote => 127.0.0.1:49664]
[2022-12-04 13:24:42] ws4py                          INFO    : Managing websocket [Local => 127.0.0.1:5002 | Remote => 127.0.0.1:49666]
[2022-12-04 13:25:05] ws4py                          INFO    : Managing websocket [Local => 127.0.0.1:5002 | Remote => 127.0.0.1:49668]
[2022-12-04 13:25:28] ws4py                          INFO    : Terminating websocket [Local => 127.0.0.1:5002 | Remote => 127.0.0.1:49666]
[2022-12-04 13:26:31] ws4py                          INFO    : Terminating websocket [Local => 127.0.0.1:5002 | Remote => 127.0.0.1:49668]
[2022-12-04 13:27:00] ws4py                          INFO    : Terminating websocket [Local => 127.0.0.1:5002 | Remote => 127.0.0.1:49664]
[2022-12-04 13:27:19] ws4py                          INFO    : Managing websocket [Local => 127.0.0.1:5002 | Remote => 127.0.0.1:49670]
[2022-12-04 13:27:35] ws4py                          INFO    : Terminating websocket [Local => 127.0.0.1:5002 | Remote => 127.0.0.1:49670]
[2022-12-04 13:28:33] ws4py                          INFO    : Managing websocket [Local => 127.0.0.1:5002 | Remote => 127.0.0.1:49672]
[2022-12-04 13:28:34] ws4py                          INFO    : Managing websocket [Local => 127.0.0.1:8082 | Remote => 127.0.0.1:41562]
[2022-12-04 13:28:42] ws4py                          INFO    : Terminating websocket [Local => 127.0.0.1:8082 | Remote => 127.0.0.1:41562]
[2022-12-04 13:29:44] ws4py                          INFO    : Managing websocket [Local => 127.0.0.1:5002 | Remote => 127.0.0.1:49674]
[2022-12-04 13:36:08] ws4py                          INFO    : Terminating websocket [Local => 127.0.0.1:5002 | Remote => 127.0.0.1:49674]
[2022-12-04 13:36:08] ws4py                          INFO    : Terminating websocket [Local => 127.0.0.1:5002 | Remote => 127.0.0.1:49660]
[2022-12-04 13:36:08] ws4py                          INFO    : Terminating websocket [Local => 127.0.0.1:5002 | Remote => 127.0.0.1:49672]
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[2022-12-04 13:36:08] frigate.video                  ERROR   : Front_Cam: Unable to read frames from ffmpeg process.
[2022-12-04 13:36:08] frigate.video                  ERROR   : Front_Cam: ffmpeg process is not running. exiting capture thread...
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[2022-12-04 13:36:13] frigate.app                    INFO    : Starting Frigate (0.11.1-2eada21)
Starting migrations
[2022-12-04 13:36:13] peewee_migrate                 INFO    : Starting migrations
There is nothing to migrate
[2022-12-04 13:36:13] peewee_migrate                 INFO    : There is nothing to migrate
[2022-12-04 13:36:13] detector.coral                 INFO    : Starting detection process: 216
[2022-12-04 13:36:13] frigate.app                    INFO    : Output process started: 218
[2022-12-04 13:36:13] frigate.edgetpu                INFO    : Attempting to load TPU as usb
[2022-12-04 13:36:13] ws4py                          INFO    : Using epoll
[2022-12-04 13:36:13] frigate.app                    INFO    : Camera processor started for Front_Cam: 221
[2022-12-04 13:36:13] frigate.app                    INFO    : Capture process started for Front_Cam: 224
[2022-12-04 13:36:13] ws4py                          INFO    : Using epoll
[2022-12-04 13:36:15] frigate.edgetpu                INFO    : TPU found
[2022-12-04 13:36:18] frigate.record                 WARNING : Discarding a corrupt recording segment: {'cache_path': '/tmp/cache/Front_Cam-20221204133515.mp4', 'start_time': datetime.datetime(2022, 12, 4, 13, 35, 15)}
[2022-12-04 13:36:41] ws4py                          INFO    : Managing websocket [Local => 127.0.0.1:5002 | Remote => 127.0.0.1:49676]
[2022-12-04 13:36:45] frigate.http                   ERROR   : No recordings found for the requested time range

Frigate stats

No response

Operating system

Proxmox

Install method

Docker Compose

Coral version

USB

Any other information that may be helpful

No response

NickM-27 commented 1 year ago

Is your camera h.265?

Are the phone and computer on the same time zone / showing the same time?

What if you try to download the clip on the phone?

inspired27 commented 1 year ago

Is your camera h.265?

Are the phone and computer on the same time zone / showing the same time?

What if you try to download the clip on the phone?

The camera is set to h264 it is Hikvision 180 degree panoramic camera.

The phone and computer same time zone same time.

Yes downloading the clips onto the phone play via VLC player fine.

inspired27 commented 1 year ago

Are my issues related to this:

Frigate in LXC Container in Docker date and time is UTC Mon 05 Dec 02:11:48 see screenshot, is this correct? Proxmox is: Mon 05 Dec 2022 12:11:03 PM AEST (correct) HomeAssistant in Proxmox VM is - Mon 05 Dec 2022 12:11:03 PM AEST (correct)

image

inspired27 commented 1 year ago

Hi,

Don't know if it helps troubleshoot but I noticed that Frigate date and time on the Snapshot image below is 05/12/2022 08:05:11 which is not the same date and time as the Event Time 05/12/2022 18:05:01 as per image?

image

blakeblackshear commented 1 year ago

The time in the events list is the start time of the event. The snapshot could be from any point of time during the event. They are not expected to be the same.

inspired27 commented 1 year ago

The time in the events list is the start time of the event. The snapshot could be from any point of time during the event. They are not expected to be the same.

Hi,

Thanks for the reply, the difference seems to be 10 hours which is co-incidentally difference between my time zone Queensland Australia and UTC 10 hours. Should Frigate in LXC in Docker be running UTC or the host Proxmox time zone which is Queensland Australia? If so how do I set the timezone in Docker for Frigate?

Thanks

NickM-27 commented 1 year ago

With current versions you will want Frigate running the host timezone (not utc). In 0.12 it won't matter

inspired27 commented 1 year ago

With current versions you will want Frigate running the host timezone (not utc). In 0.12 it won't matter

Hey Nick,

Thanks, sounds good when do you think version 0.12 will be out?

NickM-27 commented 1 year ago

You can follow the progress here https://github.com/blakeblackshear/frigate/pull/4055

inspired27 commented 1 year ago

You can follow the progress here #4055

Great thanks, in the interim I update the portainer stack docker compose to the following:

volumes:

Also in the LXC set to Australia using dpkg-reconfigure tzdata

NickM-27 commented 1 year ago

yes you will want to add that 👍

inspired27 commented 1 year ago

yes you will want to add that 👍

Okay I have the timezones and times aligned showing correctly in snapshots, however I still cannot play clips on Android via HA or Frigate :5000 direct. "The media could not be loaded, either because the server or network failed or because the format is not supported"

Works when I download to device but not when I click event and clip.

Is there any logs anywhere that I could look at to find out more details I am not familiar where logs are for frigate in proxmox > docker.

NickM-27 commented 1 year ago

I would wait and try for a new recording and see if it has any issues

inspired27 commented 1 year ago

I would wait and try for a new recording and see if it has any issues

Yup I did that, and that is how I know snapshot date and time is aligned, works on PC okay.

Where do I find logs for this to get more details?

inspired27 commented 1 year ago

Config of my Hikvision Camera if it helps, are there any limitations with bitrate FPS etc for event clips to play on Android?

image

NickM-27 commented 1 year ago

I'm not sure on mobile, would need browser logs and docker logs.

as far as your camera config goes, if you set your I Frame interval to be the same as your fps. also maybe try turning the profile to base profile. What android device do you have?

inspired27 commented 1 year ago

I'm not sure on mobile, would need browser logs and docker logs.

Okay will check. I have a Galaxy S21 Ultra, I can confirm that the clips play fine with audio etc using Firefox browser on Android but not Chrome or Dolphin Browser. I have made the changes you mentioned for I frame and profile with not change for Chrome and Dolphin Browser both do not play clips.

inspired27 commented 1 year ago

Hi,

I have the Chrome Log with the error details:

image

Found some info of someone having similar with a different project:

The fix / suggestion was 'if you're playing HLS or DASH streams, consider including the overrideNative setting' not sure if this is relevant?

https://github.com/videojs/video.js/issues/6728

inspired27 commented 1 year ago

I'm not sure on mobile, would need browser logs and docker logs.

There seems to be a few scenarios where this issue comes up one more below:

https://github.com/videojs/video.js/issues/7623

I get the following image same as in the post above:

image

NickM-27 commented 1 year ago

Interesting, we did a lot of dependency updates in 0.12 so it is possible this has been fixed already there (if it is related to the linked issue)

inspired27 commented 1 year ago

Interesting, we did a lot of dependency updates in 0.12 so it is possible this has been fixed already there (if it is related to the linked issue)

image

It is pretty hard to get the benefits of Frigate if you cannot play clips on an android mobile device in native chrome

Which month do you think version 0.12 will be released?

NickM-27 commented 1 year ago

It is pretty hard to get the benefits of Frigate if you cannot play clips on an android mobile device in native chrome

I agree but it is difficult to say why this is happening, chrome on my android device is working just fine. Chrome has done a lot of updates lately, it is possible that they broke something. Might be worth trying the beta version of chrome to see if it behaves any differently.

inspired27 commented 1 year ago

I agree but it is difficult to say why this is happening, chrome on my android device is working just fine. Chrome has done a lot of updates lately, it is possible that they broke something. Might be worth trying the beta version of chrome to see if it behaves any differently.

Thanks, just installed Chrome Beta and the same issue, the above two articles point to code changes to fix.

image

NickM-27 commented 1 year ago

The error "Media could not be loaded" is a very generic error that occurs in MANY different cases.

It can happen because your stream is h.265 and your browser doesn't support that, it can happen because there is a timezone mismatch and the requested files don't exist, it can happen if one of the segments saved is corrupted, etc.

So while it fixed it for the users that asked the question, it is not as though one code change will fix all instances of this error. Also, the fact that this isn't a widespread issue for all users with Chrome on Android means it is likely something more specific.

We are also using videojs 7.20.2 in frigate 0.11.1 which would contain the default behaviors that the linked issues suggested https://github.com/blakeblackshear/frigate/blob/a46c37018f3cd1ed15dc15ed47e91999fe1920c2/web/package.json#L22

github-actions[bot] commented 1 year 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.

DerT0bi commented 1 year ago

Hi, did you still encounter the problem? I am using frigate 0.12.1 and i have exactly the same error. I'm also using a Galaxy S21 Ultra. The error also occurs on my Galaxy Tab S8+.

Caddyman68 commented 1 year ago

Hi, did you still encounter the problem? I am using frigate 0.12.1 and i have exactly the same error. I'm also using a Galaxy S21 Ultra. The error also occurs on my Galaxy Tab S8+.

I'm not sure but I think 0.12.1 caused my problem. In any case the problem is exactly what they closed out here with no fix (other than to say 0.12.1 will fix it). I am still testing Frigate since I can't get a Coral. I only have one camera currently but a few weeks ago had 3 and if I recall correctly I could watch the clips on my phone (Moto G5) with the app and the HA card. Now I can't with HA or Chrome - can download and watch with VLC fine. I guess I'll have to live with it but I wish I wasn't so sure that it worked before and is now broken. I thought I had found a reason when I saw that they no longer opened port 5000 automatically, but when I opened it in the addon there was no effect. And to answer the "usual" questions: not H.265, time on PC (Home Assistant) matches phone, and files are NOT corrupted - if they were how could I watch them on the PC?

NickM-27 commented 1 year ago

I'm not sure but I think 0.12.1 caused my problem.

there were no changes in 0.12.1 related to this as it was a small update that only fixed a few specific bugs

In any case the problem is exactly what they closed out here with no fix (other than to say 0.12.1 will fix it).

that is not what happened, the issue was closed due to no continued response from OP and the issue was never identified so 0.12.1 was never claimed to fix anything.

in the vast majority of cases this issue is due to bad camera / camera settings or something on the device that is watching the stream. If it plays on one device but not another then that further points to an issue with the device since the code to playback is transparent from frigate's POV.

Especially in the case that it worked on a device and then stopped some time later, would point to a browser update that could have broken things.

Caddyman68 commented 1 year ago

I'm not sure but I think 0.12.1 caused my problem.

there were no changes in 0.12.1 related to this as it was a small update that only fixed a few specific bugs

In any case the problem is exactly what they closed out here with no fix (other than to say 0.12.1 will fix it).

that is not what happened, the issue was closed due to no continued response from OP and the issue was never identified so 0.12.1 was never claimed to fix anything.

in the vast majority of cases this issue is due to bad camera / camera settings or something on the device that is watching the stream. If it plays on one device but not another then that further points to an issue with the device since the code to playback is transparent from frigate's POV.

Especially in the case that it worked on a device and then stopped some time later, would point to a browser update that could have broken things.

Sorry to seem unappreciative. I missed the post from the OP that said it worked with Firefox (and indeed it does) which points to a problem with my phone also. They may have snuck in an update recently. I'm still confused that it doesn't work with the Home Assistant app, but there have definitely been updates there in the past month. Then again it's possible that I'm mistaken about it ever working since I lost interest in it when I searched for a Coral USB. I am still using Blue Iris for the majority of my cameras and might use Frigate to trigger/analyze and BI to view as I see other users doing, so the difficulty I'm having with the viewer is probably moot. I guess this will add to my inference time but my main reason for wanting to get away from BI is related to it's CPU usage which the elusive Coral would solve if they would allow it to be used (I hope). I tried an NVIDIA GPU but didn't see an improvement, although that was probably my fault / wasn't set up properly. Then I read about Frigate and Google Coral USB... Thanks for taking the time to help. I wish the OP had just taken the time to report on his situation (ie did the update to 0.12.1 solve his issue or what did?).

DerT0bi commented 1 year ago

I'm not sure but I think 0.12.1 caused my problem.

there were no changes in 0.12.1 related to this as it was a small update that only fixed a few specific bugs

In any case the problem is exactly what they closed out here with no fix (other than to say 0.12.1 will fix it).

that is not what happened, the issue was closed due to no continued response from OP and the issue was never identified so 0.12.1 was never claimed to fix anything. in the vast majority of cases this issue is due to bad camera / camera settings or something on the device that is watching the stream. If it plays on one device but not another then that further points to an issue with the device since the code to playback is transparent from frigate's POV. Especially in the case that it worked on a device and then stopped some time later, would point to a browser update that could have broken things.

Sorry to seem unappreciative. I missed the post from the OP that said it worked with Firefox (and indeed it does) which points to a problem with my phone also. They may have snuck in an update recently. I'm still confused that it doesn't work with the Home Assistant app, but there have definitely been updates there in the past month. Then again it's possible that I'm mistaken about it ever working since I lost interest in it when I searched for a Coral USB. I am still using Blue Iris for the majority of my cameras and might use Frigate to trigger/analyze and BI to view as I see other users doing, so the difficulty I'm having with the viewer is probably moot. I guess this will add to my inference time but my main reason for wanting to get away from BI is related to it's CPU usage which the elusive Coral would solve if they would allow it to be used (I hope). I tried an NVIDIA GPU but didn't see an improvement, although that was probably my fault / wasn't set up properly. Then I read about Frigate and Google Coral USB... Thanks for taking the time to help. I wish the OP had just taken the time to report on his situation (ie did the update to 0.12.1 solve his issue or what did?).

Hmm, then I think it has something to do with an update of the chromium engine. After your comments I tried a few different Browsers and it's working fine on Firefox and the Samsung browser. Every chromium based browser is not working (tested with Chrome, Chrome beta, Opera, Edge and Brave). I also guess that the HA app is using chromium(?). Maybe they change something there.

I'm pretty sure that it was working a few weeks ago. At that time I was on 0.12.0. After it stopped working I found this issue and thought that maybe an update to 0.12.1 would help, but it didn't. I mainly asked, because I thought it was specific to Samsung devices.

For now I'm just using the Samsung browser and installed the HA App as a PWA via the Samsung browser. I will check in Chrome periodically.

NickM-27 commented 1 year ago

it seems it is still going to be specific to a certain camera codec or profile, my android device with chrome has no problem with my cameras; though my cameras are mostly h.265 main and I have one h.264 high 5.1

Caddyman68 commented 1 year ago

Thanks for the info. I was thinking (as is the case a lot of the time) that it was just me and my luck. I tried Edge before I read (re-read?) your post and would probably have downloaded Dolphin before Firefox - so you saved me a little time. I have a home screen link to Frigate in Firefox that I'm sure takes a bit longer than the app to view a clip but it's quicker than downloading and viewing in VLC

Serhioromano commented 1 year ago

@inspired27 do you have FIREWALL turned on? How do you access from phone CLOUDFLARED OR ELSE?

Caddyman68 commented 1 year ago

@inspired27 do you have FIREWALL turned on? How do you access from phone CLOUDFLARED OR ELSE?

I use Cloudflare. Not sure why that would affect the app or Chrome browser, but not Firefox. Same with a firewall but I don't have that either on Android

Serhioromano commented 1 year ago

I have read somewhere a suggestion. I selected 1080 for my main stream that is recorded and now I can play it on all my android devices.

DerT0bi commented 1 year ago

I have read somewhere a suggestion. I selected 1080 for my main stream that is recorded and now I can play it on all my android devices.

I can confirm, that it is also working for me now. But I didn't change anything in my setup. Maybe there Was an update for Chrome.

Caddyman68 commented 1 year ago

I have read somewhere a suggestion. I selected 1080 for my main stream that is recorded and now I can play it on all my android devices.

I have Reolink RLC -410 camera and it does 2304x1296 or above for main stream or 640x480 for substream. I will try to change role-record to the substream to see if that works

Caddyman68 commented 1 year ago

I have read somewhere a suggestion. I selected 1080 for my main stream that is recorded and now I can play it on all my android devices.

I can confirm, that it is also working for me now. But I didn't change anything in my setup. Maybe there Was an update for Chrome.

Thanks. I hope mine starts to work again - currently only have one cam for testing, but it won't work on Blue Iris anymore (for some reason) and I have another that I can't configure to BI either after a power outage and hard reset. Hoping to get a Coral USB soon. Also one is Reolink and the other is Hikvision so will see if the camera has anything to do with it (doubt it though)

Caddyman68 commented 1 year ago

I have read somewhere a suggestion. I selected 1080 for my main stream that is recorded and now I can play it on all my android devices.

Update: got both cameras to work with Blue Iris again - not sure what I did differently and again they are different brands. Now back to HA app/ Frigate view. It does work when I use the substream in mode-record (Frigate.Yaml), but 640x480 is my only option. It would be okay for the app but I'd like to have full resolution recorded on the computer. I can't read a license plate even on full screen in the low resolution. Wish I could lower the high res to 1080p. Or record both streams and tell the app to play the substream - seems like a desirable option anyway for bandwidth/speed/data limits. I just looked again at the Frigate configuration page and was wondering if I change the Birdseye resolution (width, height and/or quality) will that take the recorded video and send it to the app with a lower resolution? It looks like the app/card uses birdseye - definitely different than the UI screen. Looks like I'm going to find out - another sleepless night

Serhioromano commented 1 year ago

I have read somewhere a suggestion. I selected 1080 for my main stream that is recorded and now I can play it on all my android devices.

Update: got both cameras to work with Blue Iris again - not sure what I did differently and again they are different brands. Now back to HA app/ Frigate view. It does work when I use the substream in mode-record (Frigate.Yaml), but 640x480 is my only option. It would be okay for the app but I'd like to have full resolution recorded on the computer. I can't read a license plate even on full screen in the low resolution. Wish I could lower the high res to 1080p. Or record both streams and tell the app to play the substream - seems like a desirable option anyway for bandwidth/speed/data limits. I just looked again at the Frigate configuration page and was wondering if I change the Birdseye resolution (width, height and/or quality) will that take the recorded video and send it to the app with a lower resolution? It looks like the app/card uses birdseye - definitely different than the UI screen. Looks like I'm going to find out - another sleepless night

I am not sure about birdseye. I have never used it.

NickM-27 commented 1 year ago

I just looked again at the Frigate configuration page and was wondering if I change the Birdseye resolution (width, height and/or quality) will that take the recorded video and send it to the app with a lower resolution? It looks like the app/card uses birdseye - definitely different than the UI screen. Looks like I'm going to find out - another sleepless night

birdseye uses the detect stream as the input

Caddyman68 commented 1 year ago

I just looked again at the Frigate configuration page and was wondering if I change the Birdseye resolution (width, height and/or quality) will that take the recorded video and send it to the app with a lower resolution? It looks like the app/card uses birdseye - definitely different than the UI screen. Looks like I'm going to find out - another sleepless night

birdseye uses the detect stream as the input

That's what I thought, but I may have my frigate.yaml setup wrong. I have included birdseye:/ enabled: True and my substream (640x480) has roles:/ - detect. I must have something wrong since the card shows the birdseye view but if I open the UI and choose Birdseye it is just a black screen with a large bird. Maybe that's because I'm only using one camera? That will change soon as I have ordered a Google Coral USB. When I set my substream to roles: - detect AND - record I can view the clips on Android Rather than keep this thread going, I may open another for help on my yaml if I can't figure it out for myself. Thanks again for the help

NickM-27 commented 1 year ago

I open the UI and choose Birdseye it is just a black screen with a large bird

by default birdseye only shows a camera when that camera is detecting an object

Caddyman68 commented 1 year ago

I open the UI and choose Birdseye it is just a black screen with a large bird

by default birdseye only shows a camera when that camera is detecting an object

I read that - too bad I didn't comprehend or retain that information LOL

dallibab commented 6 months ago

I'm getting the exact same problems.

I can watch clips or recordings fine on any pc, any browser. . But not on my phone, android using the home assistant app chrome or brave, Firefox does work though. Have not tried until the last few days and getting the exact same errors as the post above.

Caddyman68 commented 6 months ago

I'm getting the exact same problems.

I can watch clips or recordings fine on any pc, any browser. . But not on my phone, android using the home assistant app chrome or brave, Firefox does work though. Have not tried until the last few days and getting the exact same errors as the post above.

I have recently discovered (?) this blueprint: "https://github.com/SgtBatten/HA_blueprints". It notifies you and sends a thumbnail that you click on to start a clip. So far I have a slight problem with false trigger events, but the playback seems more dependable than the card in Android. Haven't tested extensively on 5G and sometimes the clip won't come up but I think that's on the false events so if I solve that problem it's a 2fer. Even so, the thumbnail is sufficient to see what triggered the camera

dallibab commented 6 months ago

ill have a look at that link thanks, i havnt set up a card yet for alerts, just getting all working, it all was good until i tried to watch a clip on my phone. (AT LEAST FIREFOX WORKS)

On Fri, 23 Feb 2024 at 19:34, Caddyman68 @.***> wrote:

I'm getting the exact same problems.

I can watch clips or recordings fine on any pc, any browser. . But not on my phone, android using the home assistant app chrome or brave, Firefox does work though. Have not tried until the last few days and getting the exact same errors as the post above.

I have recently discovered (?) this blueprint: " https://github.com/SgtBatten/HA_blueprints". It notifies you and sends a thumbnail that you click on to start a clip. So far I have a slight problem with false trigger events, but the playback seems more dependable than the card in Android. Haven't tested extensively on 5G and sometimes the clip won't come up but I think that's on the false events so if I solve that problem it's a 2fer. Even so, the thumbnail is sufficient to see what triggered the camera

— Reply to this email directly, view it on GitHub https://github.com/blakeblackshear/frigate/issues/4594#issuecomment-1961881978, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADIJIWUWDII5SJ5IBSIZLA3YVDVNHAVCNFSM6AAAAAASTLVKKSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRRHA4DCOJXHA . You are receiving this because you commented.Message ID: @.***>

-- John Spencer

Caddyman68 commented 6 months ago

I fiddled around with the thumbnails Frigate notification sent me through that blueprint. Seems like 2 of my cameras don't let me see clips or snapshots at all (or send me to the video window and can't play) so it has to be something with them or their setup in configuration. 3 work, but not all thumbnails sent me to a clip that played - about 80% did. They are 2 Reolink Lumus and 1 Reolink RLC-410-W; all 3 are wireless but the 410-w is connected via POE although the app says it's connected to wifi. Don't know why these would work and the other 2 (Reolink RLC-410-5mp and Amcrest IP5M-T1277EW-AI) don't. Especially the Reolink. I have a RLC-410 that I can't figure out how to get into Frigate for recording at all, only viewing/streaming. Pretty sure it's a firmware problem but it won't let me upgrade and their support wasn't helpful. I just looked at my Frigate.yml and 1 working plus 1 not are setup in Go2RTC with their HTTP address and the path is RTSP. Thought I was onto something. Maybe the w likes that and the 5mp doesn't - again WHY? Good luck. The blueprint is the way to go. I have it setup to give a different alert sound on Android for each camera and it does so much more too.

Caddyman68 commented 6 months ago

Great news. For the camera thumbnails in the notifications that don't stream the clip, there is a select (3 dots) to download it. It worked for me on wifi and 5G. Pretty quick although not as fast as the ones that just played especially since I already clicked the thumbnail expecting it to just play. 47 second clip took about a minute to download but that was on 5G. Using the default playe (Photos) on my Android phone I could zoom in too; zoom is available on the clips that stream directly also