Closed dnestico closed 1 year ago
Do you have the standard or full access version of the addon installed?
@NickM-27 Sorry for late reply
I'm using standard not full access as that had problem's on my RPI4
you have the ingress enabled on the frigate addon config page correct?
What do the logs say on the addon logs?
I don't know what you mean by "ingress enabled" sorry, and here are the addon logs as of right now, most will probably be solved when I get my coral next week hopefully but the main problem is the notifications tbh.
[2022-08-24 19:05:18] frigate.video ERROR : driveway: Unable to read frames from ffmpeg process. [2022-08-24 19:05:18] frigate.video ERROR : driveway: ffmpeg process is not running. exiting capture thread... [2022-08-24 19:06:25] frigate.video ERROR : porch: Unable to read frames from ffmpeg process. [2022-08-24 19:06:25] frigate.video ERROR : porch: ffmpeg process is not running. exiting capture thread... [2022-08-24 19:08:23] frigate.video ERROR : driveway: Unable to read frames from ffmpeg process. [2022-08-24 19:08:23] frigate.video ERROR : driveway: Unable to read frames from ffmpeg process. [2022-08-24 19:08:23] frigate.video ERROR : driveway: ffmpeg process is not running. exiting capture thread... [2022-08-24 19:09:48] frigate.video ERROR : porch: Unable to read frames from ffmpeg process. [2022-08-24 19:09:48] frigate.video ERROR : porch: ffmpeg process is not running. exiting capture thread... [2022-08-24 19:09:50] frigate.video ERROR : driveway: Unable to read frames from ffmpeg process. [2022-08-24 19:09:50] frigate.video ERROR : driveway: ffmpeg process is not running. exiting capture thread... [2022-08-24 19:10:37] frigate.video ERROR : porch: Unable to read frames from ffmpeg process. [2022-08-24 19:10:37] frigate.video ERROR : porch: Unable to read frames from ffmpeg process. [2022-08-24 19:10:37] frigate.video ERROR : porch: Unable to read frames from ffmpeg process. [2022-08-24 19:10:37] frigate.video ERROR : porch: ffmpeg process is not running. exiting capture thread...
frigate.video ERROR : porch: Unable to read frames from ffmpeg process.
will not be solved by getting a coral, this is completely unrelated to the coral. We can try to address that after the notification issue though.
If you go to the frigate addon page there should be a switch called ingress along with other ones call Start On Boot
etc. You can just send a screenshot of that page (where you start / stop frigate) if that is easier.
How'r these?
Okay so I was wrong, it isn't a switch but looks as though it is working as expected. Really not sure why the integration is unable to connect unless you have something else also running on port 5000
Is there anyways to see that by the way? Cuz if it is something else on 5000 then I'd need to change that asap.
These are just my addons not the big integrations page lol:
I searched for you, docker wyze bridge hosts its web UI on port 5000 so they are likely conflicting. You'll need to change one of them (if you change frigate then you'll need to reconfigure the frigate integration)
Wow, you genius haha. I don't see anyway to change the port for the web UI on wyze docker.
I think ill have to change the frigate port once I read how to do so safely.
Yes, simply go to the page you screenshot before and change it to whatever and then go to the integrations page and delete the frigate integration then re-add it with the new port
So uh im getting a failed to connect error:
Changed the port on frigate then restarted but it's saying failed to connect.
I think that should do it
Im getting a failed to connect error when trying to re-add the integration as seen above, here are the logs:
[2022-08-24 19:44:11] ws4py INFO : Using epoll [2022-08-24 19:45:15] ws4py INFO : Managing websocket [Local => 127.0.0.1:5002 | Remote => 127.0.0.1:45648] [2022-08-24 19:45:19] ws4py INFO : Terminating websocket [Local => 127.0.0.1:5002 | Remote => 127.0.0.1:45648] [2022-08-24 19:47:16] frigate.video ERROR : driveway: Unable to read frames from ffmpeg process. [2022-08-24 19:47:16] frigate.video ERROR : driveway: ffmpeg process is not running. exiting capture thread... [2022-08-24 19:47:20] frigate.video ERROR : porch: Unable to read frames from ffmpeg process. [2022-08-24 19:47:20] frigate.video ERROR : porch: ffmpeg process is not running. exiting capture thread... [2022-08-24 19:47:21] watchdog.driveway ERROR : Ffmpeg process crashed unexpectedly for driveway. [2022-08-24 19:47:21] watchdog.driveway ERROR : The following ffmpeg logs include the last 100 lines prior to exit. [2022-08-24 19:47:21] ffmpeg.driveway.detect ERROR : Guessed Channel Layout for Input Stream #0.1 : mono [2022-08-24 19:47:21] ffmpeg.driveway.detect ERROR : [rtsp @ 0x55b4c996d0] CSeq 9 expected, 8 received. [2022-08-24 19:47:21] ffmpeg.driveway.detect ERROR : [rtsp @ 0x55b4c996d0] CSeq 10 expected, 9 received. [2022-08-24 19:47:21] ffmpeg.driveway.detect ERROR : [rtsp @ 0x55b4c996d0] CSeq 11 expected, 10 received. [2022-08-24 19:47:21] ffmpeg.driveway.detect ERROR : [rtsp @ 0x55b4c996d0] CSeq 12 expected, 11 received. [2022-08-24 19:47:21] ffmpeg.driveway.detect ERROR : [rtsp @ 0x55b4c996d0] CSeq 13 expected, 12 received. [2022-08-24 19:47:21] ffmpeg.driveway.detect ERROR : [rtsp @ 0x55b4c996d0] CSeq 14 expected, 13 received. [2022-08-24 19:47:21] ffmpeg.driveway.detect ERROR : [rtsp @ 0x55b4c996d0] CSeq 15 expected, 14 received. [2022-08-24 19:47:21] ffmpeg.driveway.detect ERROR : [rtsp @ 0x55b4c996d0] CSeq 21 expected, 20 received. [2022-08-24 19:47:21] ffmpeg.driveway.detect ERROR : [rtsp @ 0x55b4c996d0] CSeq 22 expected, 21 received. [2022-08-24 19:47:21] ffmpeg.driveway.detect ERROR : [rtsp @ 0x55b4c996d0] CSeq 23 expected, 22 received. [2022-08-24 19:47:21] ffmpeg.driveway.detect ERROR : [rtsp @ 0x55b4c996d0] CSeq 25 expected, 23 received. [2022-08-24 19:47:21] ffmpeg.driveway.detect ERROR : [rtsp @ 0x55b4c996d0] CSeq 26 expected, 24 received. [2022-08-24 19:47:21] ffmpeg.driveway.detect ERROR : [rtsp @ 0x55b4c996d0] CSeq 27 expected, 25 received. [2022-08-24 19:47:21] ffmpeg.driveway.detect ERROR : [rtsp @ 0x55b4c996d0] CSeq 28 expected, 26 received. [2022-08-24 19:47:21] ffmpeg.driveway.detect ERROR : [rtsp @ 0x55b4c996d0] CSeq 30 expected, 27 received. [2022-08-24 19:47:21] ffmpeg.driveway.detect ERROR : [rtsp @ 0x55b4c996d0] CSeq 33 expected, 28 received. [2022-08-24 19:47:21] ffmpeg.driveway.detect ERROR : [rtsp @ 0x55b4c996d0] CSeq 35 expected, 29 received. [2022-08-24 19:47:21] ffmpeg.driveway.detect ERROR : [rtsp @ 0x55b4c996d0] CSeq 36 expected, 33 received. [2022-08-24 19:47:21] ffmpeg.driveway.detect ERROR : [rtsp @ 0x55b4c996d0] CSeq 36 expected, 34 received. [2022-08-24 19:47:21] ffmpeg.driveway.detect ERROR : [rtsp @ 0x55b4c996d0] CSeq 36 expected, 35 received. [2022-08-24 19:47:21] ffmpeg.driveway.detect ERROR : [rtsp @ 0x55b4c996d0] CSeq 36 expected, 0 received. [2022-08-24 19:47:21] ffmpeg.driveway.detect ERROR : [h264 @ 0x55b4d86a40] error while decoding MB 118 25, bytestream -9 [2022-08-24 19:47:21] ffmpeg.driveway.detect ERROR : rtsp://admin:admin@192.168.2.30/live: corrupt decoded frame in stream 0 [2022-08-24 19:47:21] ffmpeg.driveway.detect ERROR : [flv @ 0x55b4cbd450] Failed to update header with correct duration. [2022-08-24 19:47:21] ffmpeg.driveway.detect ERROR : [flv @ 0x55b4cbd450] Failed to update header with correct filesize. [2022-08-24 19:47:21] watchdog.porch ERROR : Ffmpeg process crashed unexpectedly for porch. [2022-08-24 19:47:21] watchdog.porch ERROR : The following ffmpeg logs include the last 100 lines prior to exit. [2022-08-24 19:47:21] ffmpeg.porch.detect ERROR : Guessed Channel Layout for Input Stream #0.1 : mono [2022-08-24 19:47:21] ffmpeg.porch.detect ERROR : [rtsp @ 0x55c291d6d0] CSeq 8 expected, 7 received. [2022-08-24 19:47:21] ffmpeg.porch.detect ERROR : [rtsp @ 0x55c291d6d0] CSeq 9 expected, 8 received. [2022-08-24 19:47:21] ffmpeg.porch.detect ERROR : [rtsp @ 0x55c291d6d0] CSeq 10 expected, 9 received. [2022-08-24 19:47:21] ffmpeg.porch.detect ERROR : [rtsp @ 0x55c291d6d0] CSeq 11 expected, 10 received. [2022-08-24 19:47:21] ffmpeg.porch.detect ERROR : [rtsp @ 0x55c291d6d0] CSeq 32 expected, 31 received. [2022-08-24 19:47:21] ffmpeg.porch.detect ERROR : [rtsp @ 0x55c291d6d0] CSeq 35 expected, 32 received. [2022-08-24 19:47:21] ffmpeg.porch.detect ERROR : More than 1000 frames duplicated [2022-08-24 19:47:21] ffmpeg.porch.detect ERROR : [rtsp @ 0x55c291d6d0] CSeq 36 expected, 33 received. [2022-08-24 19:47:21] ffmpeg.porch.detect ERROR : rtsp://admin:admin@192.168.2.44/live: corrupt decoded frame in stream 0 [2022-08-24 19:47:21] ffmpeg.porch.detect ERROR : [flv @ 0x55c2958d10] Failed to update header with correct duration. [2022-08-24 19:47:21] ffmpeg.porch.detect ERROR : [flv @ 0x55c2958d10] Failed to update header with correct filesize. [2022-08-24 19:48:41] frigate.video ERROR : porch: Unable to read frames from ffmpeg process. [2022-08-24 19:48:41] frigate.video ERROR : porch: ffmpeg process is not running. exiting capture thread... [2022-08-24 19:48:41] watchdog.porch ERROR : Ffmpeg process crashed unexpectedly for porch. [2022-08-24 19:48:41] watchdog.porch ERROR : The following ffmpeg logs include the last 100 lines prior to exit. [2022-08-24 19:48:41] ffmpeg.porch.detect ERROR : Guessed Channel Layout for Input Stream #0.1 : mono [2022-08-24 19:48:41] ffmpeg.porch.detect ERROR : [rtsp @ 0x55a334e6d0] CSeq 8 expected, 7 received. [2022-08-24 19:48:41] ffmpeg.porch.detect ERROR : [rtsp @ 0x55a334e6d0] CSeq 9 expected, 8 received. [2022-08-24 19:48:41] ffmpeg.porch.detect ERROR : [rtsp @ 0x55a334e6d0] CSeq 11 expected, 9 received. [2022-08-24 19:48:41] ffmpeg.porch.detect ERROR : [rtsp @ 0x55a334e6d0] CSeq 13 expected, 10 received. [2022-08-24 19:48:41] ffmpeg.porch.detect ERROR : [rtsp @ 0x55a334e6d0] CSeq 14 expected, 11 received. [2022-08-24 19:48:41] ffmpeg.porch.detect ERROR : [flv @ 0x55a343ac80] Failed to update header with correct duration. [2022-08-24 19:48:41] ffmpeg.porch.detect ERROR : [flv @ 0x55a343ac80] Failed to update header with correct filesize. [2022-08-24 19:48:44] frigate.video ERROR : driveway: Unable to read frames from ffmpeg process. [2022-08-24 19:48:44] frigate.video ERROR : driveway: ffmpeg process is not running. exiting capture thread... [2022-08-24 19:48:51] watchdog.driveway ERROR : Ffmpeg process crashed unexpectedly for driveway. [2022-08-24 19:48:51] watchdog.driveway ERROR : The following ffmpeg logs include the last 100 lines prior to exit. [2022-08-24 19:48:51] ffmpeg.driveway.detect ERROR : Guessed Channel Layout for Input Stream #0.1 : mono [2022-08-24 19:48:51] ffmpeg.driveway.detect ERROR : [rtsp @ 0x5579e076d0] CSeq 10 expected, 8 received. [2022-08-24 19:48:51] ffmpeg.driveway.detect ERROR : [rtsp @ 0x5579e076d0] CSeq 12 expected, 9 received. [2022-08-24 19:48:51] ffmpeg.driveway.detect ERROR : [rtsp @ 0x5579e076d0] CSeq 14 expected, 10 received. [2022-08-24 19:48:51] ffmpeg.driveway.detect ERROR : [rtsp @ 0x5579e076d0] CSeq 15 expected, 11 received. [2022-08-24 19:48:51] ffmpeg.driveway.detect ERROR : [rtsp @ 0x5579e076d0] CSeq 15 expected, 12 received. [2022-08-24 19:48:51] ffmpeg.driveway.detect ERROR : [rtsp @ 0x5579e076d0] CSeq 16 expected, 0 received. [2022-08-24 19:48:51] ffmpeg.driveway.detect ERROR : Last message repeated 1 times [2022-08-24 19:48:51] ffmpeg.driveway.detect ERROR : rtsp://admin:admin@192.168.2.30/live: corrupt decoded frame in stream 0 [2022-08-24 19:48:51] ffmpeg.driveway.detect ERROR : [flv @ 0x5579e2a520] Failed to update header with correct duration. [2022-08-24 19:48:51] ffmpeg.driveway.detect ERROR : [flv @ 0x5579e2a520] Failed to update header with correct filesize. [2022-08-24 19:50:17] frigate.video ERROR : porch: Unable to read frames from ffmpeg process. [2022-08-24 19:50:17] frigate.video ERROR : porch: ffmpeg process is not running. exiting capture thread... [2022-08-24 19:50:21] watchdog.porch ERROR : Ffmpeg process crashed unexpectedly for porch. [2022-08-24 19:50:21] watchdog.porch ERROR : The following ffmpeg logs include the last 100 lines prior to exit. [2022-08-24 19:50:21] ffmpeg.porch.detect ERROR : Guessed Channel Layout for Input Stream #0.1 : mono [2022-08-24 19:50:21] ffmpeg.porch.detect ERROR : [rtsp @ 0x55830eb6d0] CSeq 17 expected, 16 received. [2022-08-24 19:50:21] ffmpeg.porch.detect ERROR : [rtsp @ 0x55830eb6d0] CSeq 18 expected, 17 received. [2022-08-24 19:50:21] ffmpeg.porch.detect ERROR : [h264 @ 0x5583195090] error while decoding MB 15 46, bytestream -5 [2022-08-24 19:50:21] ffmpeg.porch.detect ERROR : rtsp://admin:admin@192.168.2.44/live: corrupt decoded frame in stream 0 [2022-08-24 19:50:21] ffmpeg.porch.detect ERROR : [flv @ 0x55831d7a10] Failed to update header with correct duration. [2022-08-24 19:50:21] ffmpeg.porch.detect ERROR : [flv @ 0x55831d7a10] Failed to update header with correct filesize. [2022-08-24 19:50:23] frigate.video ERROR : driveway: Unable to read frames from ffmpeg process. [2022-08-24 19:50:23] frigate.video ERROR : driveway: ffmpeg process is not running. exiting capture thread... [2022-08-24 19:50:31] watchdog.driveway ERROR : Ffmpeg process crashed unexpectedly for driveway. [2022-08-24 19:50:31] watchdog.driveway ERROR : The following ffmpeg logs include the last 100 lines prior to exit. [2022-08-24 19:50:31] ffmpeg.driveway.detect ERROR : Guessed Channel Layout for Input Stream #0.1 : mono [2022-08-24 19:50:31] ffmpeg.driveway.detect ERROR : [rtsp @ 0x5568f0d6d0] CSeq 9 expected, 8 received. [2022-08-24 19:50:31] ffmpeg.driveway.detect ERROR : [rtsp @ 0x5568f0d6d0] CSeq 10 expected, 9 received. [2022-08-24 19:50:31] ffmpeg.driveway.detect ERROR : [rtsp @ 0x5568f0d6d0] CSeq 12 expected, 10 received. [2022-08-24 19:50:31] ffmpeg.driveway.detect ERROR : [rtsp @ 0x5568f0d6d0] CSeq 14 expected, 11 received. [2022-08-24 19:50:31] ffmpeg.driveway.detect ERROR : [rtsp @ 0x5568f0d6d0] CSeq 15 expected, 12 received. [2022-08-24 19:50:31] ffmpeg.driveway.detect ERROR : [rtsp @ 0x5568f0d6d0] CSeq 17 expected, 13 received. [2022-08-24 19:50:31] ffmpeg.driveway.detect ERROR : [flv @ 0x5568f31450] Failed to update header with correct duration. [2022-08-24 19:50:31] ffmpeg.driveway.detect ERROR : [flv @ 0x5568f31450] Failed to update header with correct filesize.
Interesting, instead of the ingress host name (ccab4aaf-frigate) can you do it with the pis ip address instead (still include the :5001?)
Success! I think I should either leave this open or make a new issue though for the notification bug which'll let you know if this fixes that soon unless you wanna try and debug that now.
Well, the notifications require the integration to be working so that makes sense that it was failing.
Btw, if you disable RTMP your cameras should stop crashing
rtmp:
enabled: false
I think ill let you know soon if the notifications come back cuz right now they're currently "in progress" since my dad's outside so not really a good time to test it.
And that seems about right hopefully all notifications restored because all day it says its been sending them but like less then half of them actually went out to the devices.
And sure just added that to the config!
And sure just added that to the config!
did you restart? are the errors still occurring in the frigate addon logs?
Yes just restarted again because I was editing the masks and here are the logs, also notifications seem to be working so far...
Here are the logs after my restart just now:
[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-08-24 20:30:37] frigate.app INFO : Starting Frigate (0.10.1-83481af) [2022-08-24 20:30:37] frigate.app INFO : Creating directory: /tmp/cache Starting migrations [2022-08-24 20:30:37] peewee_migrate INFO : Starting migrations There is nothing to migrate [2022-08-24 20:30:37] peewee_migrate INFO : There is nothing to migrate [2022-08-24 20:30:37] frigate.app INFO : Output process started: 218 [2022-08-24 20:30:37] detector.cpu INFO : Starting detection process: 217 [2022-08-24 20:30:37] frigate.edgetpu WARNING : CPU detectors are not recommended and should only be used for testing or for trial purposes. [2022-08-24 20:30:37] frigate.app INFO : Camera processor started for porch: 221 [2022-08-24 20:30:37] frigate.app INFO : Camera processor started for driveway: 222 [2022-08-24 20:30:37] frigate.app INFO : Capture process started for porch: 223 [2022-08-24 20:30:37] ws4py INFO : Using epoll [2022-08-24 20:30:37] frigate.app INFO : Capture process started for driveway: 227 [2022-08-24 20:30:38] ws4py INFO : Using epoll [2022-08-24 20:30:47] ws4py INFO : Managing websocket [Local => 127.0.0.1:5002 | Remote => 127.0.0.1:45690] [2022-08-24 20:30:55] ws4py INFO : Terminating websocket [Local => 127.0.0.1:5002 | Remote => 127.0.0.1:45690] [2022-08-24 20:30:56] ws4py INFO : Managing websocket [Local => 127.0.0.1:5002 | Remote => 127.0.0.1:45692] [2022-08-24 20:31:24] frigate.video ERROR : porch: Unable to read frames from ffmpeg process. [2022-08-24 20:31:24] frigate.video ERROR : porch: ffmpeg process is not running. exiting capture thread...
What kind of cameras do you have? Seems that the porch camera is still having issues.
Ahhh the porch camera is the one that I am trying to make faster when detecting people walking by, hence why I tried putting it at 15fps and hoping coral's faster detection stuff can fix it.
Also, I am using a Wyze V2 on the porch and probably will upgrade to a v3 in the future like I have with some of my other cams, and all the cameras are running Wyze's official RTSP software.
frigate.yml config for my porch cam just in case helpful:
porch:
ffmpeg:
inputs:
- path: rtsp://admin:admin@192.168.2.44/live
roles:
- detect
- record
detect:
width: 1280
height: 720
fps: 15
objects:
track:
- person
- dog
filters:
dog:
threshold: 0.8
person:
threshold: 0.7
# min_area: 0
# min_score: 0.5
# max_area: 100000
motion:
improve_contrast: true
mask:
- 955,339,1001,0,1280,0,1280,720,886,720
zones:
porch_deck:
coordinates: 249,720,370,487,233,0,1010,0,966,371,901,720
objects:
- person
- dog
filters:
person:
threshold: 0.7
porch_stairs:
coordinates: 297,720,348,641,178,620,58,720
objects:
- person
filters:
person:
threshold: 0.7
# min_area: 0
# min_score: 0.5
# max_area: 100000
record:
enabled: false
retain:
days: 2
mode: motion
events:
retain:
default: 2
pre_capture: 5
post_capture: 5
max_seconds: 10
required_zones:
- porch_deck
snapshots:
enabled: true
bounding_box: true
crop: false
timestamp: false
retain:
default: 2
required_zones:
- porch_deck
@NickM-27 Yea so it's been a day and can confirm the notification issue isn't solved, it says it's firing but only like half the time it actually gets sent to phones.
This is the blueprint, want to make my own more customizable notifications soon but for now using that. https://community.home-assistant.io/t/frigate-mobile-app-notifications/311091/225?u=davidnestico
Okay, at that point with the integration working I don't think this is frigate related anymore. Might be a Firebase not delivering issue or an HA not sending issue
Damn I hope they drop and update soon to hopefully fix this, never had an issue like this before.
Damn I hope they drop and update soon to hopefully fix this, never had an issue like this before.
To be clear, I'm saying you should look into a bug or issue on that. Or enable persistent connection and see if that fixes it
I have persistent connection already enabled this whole time, this only happens with these automations now, all my other notification automations work great and quickly.
I have persistent connection already enabled this whole time, this only happens with these automations now, all my other notification automations work great and quickly.
Might want to ask the question on the home assistant forum post for the blueprint. I don't use the blueprint and it isn't associated with or maintained by this repo.
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.
Describe the problem you are having
I am using the blueprint for notifications, it says its firing, but only half the time do notifications actually show up on our devices via the notification group.
So I am going through the logs to try and clean it up and there's a lot related to frigate so here are the names:
Triggered but not sent to phones:
Version
0.10.1-83481AF
Frigate config file
Relevant log output
Frigate stats
Operating system
HassOS
Install method
HassOS Addon
Coral version
CPU (no coral)
Any other information that may be helpful
I don't have a coral yet, it should arrive in the next 2 weeks, but it seems to be working ok with 2 cameras 1 at 10fps the other at 15fps to test faster detection.