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

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

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 49 (1 by maintainers)

Most upvoted comments

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.

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

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 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

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.

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.

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.

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

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.

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.

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+.

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?