errors after upgrading to mini pc with new Intel n100 cpu #7320
Answered
by
NickM-27
Cold-Lemonade
asked this question in
Question
-
|
I suspect I have messed something up in my config.yml file. Here's the quick story. I had everything working great on the Minisforum GK41 (Intel J4125) running Ubuntu Server 22.04 LTS . But I bought a new Beeklink EQ12 (Intel N100) and installed Ubuntu Server 23.04. I installed Frigate 0.12.1 through docker-compose but not I am getting errors. For example: and Then the errors repeat. All of my cameras have the following ffmpeg section in the I changed the hwaccel_args in the ffmpeg section from how I had it set up before because the Intel n100 cpu is 12th generation. Any suggestions? Your help would be much appreciated. |
Beta Was this translation helpful? Give feedback.
Answered by
NickM-27
Jul 29, 2023
Replies: 5 comments 24 replies
-
|
Here's an excerpt from my config.yml file. I have 8 cameras so I just focused on the first one. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I'd still suggest using preset-vaapi |
Beta Was this translation helpful? Give feedback.
16 replies
-
|
Where can I find the log that docker keeps? Because the frigate:5000/log screen gets refreshed when the frigate automatically restarts. |
Beta Was this translation helpful? Give feedback.
-
|
Need to get the coral sorted out first |
Beta Was this translation helpful? Give feedback.
-
|
It is weird because both devices are attached, but when I run |
Beta Was this translation helpful? Give feedback.
-
|
They aren't being initialized, try with just 1 for now and see if it works |
Beta Was this translation helpful? Give feedback.
-
|
Crazy. Just as @NickM-27--the very amazing @NickM-27--suggested trying, it is working now... I removed one of the coral USBs but it still wasn't working. Now I was feeling quite readying to throw in the towel and hook everything back up to my Minisforum GK41. BUT I decided that I should at least try unplugging the one coral USB and plugging it into the other open port. And suddenly everything seems to be working. Now how do I get the other coral USB working? What should I try next? In case anyone else runs into this problem, to be clear, this is my set up:
Here is the log. NB, the mqtt isn't publishing because my mqtt server is down. |
Beta Was this translation helpful? Give feedback.
Answer selected by
Cold-Lemonade
-
|
After fiddling with this some more, I think something is wrong with the front-left USB-A port on the Beelink EQ12. This might be a manufacturing defect because I see others on the Beelink forum complaining of the same thing. Anyways, lots of thanks to @NickM-27! |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I spoke too soon! I am still getting errors... While the frigate:5000 page shows the snap shots, there are no recordings in the recordings pages. Nothing. They are just blank. Also, I think Frigate keeps restarting because my log seems to show that it restarts every few minutes and purges the prior log. I have not changed my config.yml or frigate.yaml file from my earlier set up, except for deleting the "i965" environment variable. Any thoughts? I think what may be happening is that the computer drops the coral USB and then Frigate starts experiencing problems. I say this because Iive been checking my usb devices with Here's the log: |
Beta Was this translation helpful? Give feedback.
4 replies
-
|
Something is wrong with the device, most likely its usb ports are not able to power the coral correctly. You may want to try a powered usb hub |
Beta Was this translation helpful? Give feedback.
-
|
Will most powered usb hubs work with linux or do I need to look for one that's explicitly compatible? |
Beta Was this translation helpful? Give feedback.
-
|
there are no drivers so it will work regardless of the OS |
Beta Was this translation helpful? Give feedback.
-
|
Thank you. |
Beta Was this translation helpful? Give feedback.
-
|
There's good news and bad news... First, the good news, a powered USB hub brought both coral USBs online. I could see both identified as "Google" using Now, the bad news. I am still getting ffmpeg errors. I can see the camera snap shots in the frigate webpage port 5000. But it is not making any recordings. I have not touched the recording sections of the config.yml file. And the storage device is showing as mounted to the appropriate mount point (/media/frigate) which corresponds to the frigate.yaml file. There seems to be a problem with ffmpeg. Here's the log: |
Beta Was this translation helpful? Give feedback.
4 replies
-
|
you should be using |
Beta Was this translation helpful? Give feedback.
-
|
That fixed it. Thanks @NickM-27. I get recordings now, but another problem emerges. Now Home Assistant isn't appending the snapshot in notifications triggered by Frigate. Home Assistant sends me a notification that, for example, someone is on my back deck. But it does not append the snapshot as it did on my earlier set up. I get this error message: "Failed to load attachment: Response status code was unacceptable: 502". For anyone who experiences similar trouble in terms of not being able to record, here is a short explanation of what I did following the advice from @NickM-27. Specifically, here's an excerpt from my config.yml file showing how I set it up for my "front_south" camera. Note that the mini pc that's running Frigate in a docker container has ip address 192.168.1.25 on my local network. I used the loop back ip address 127.0.0.1 as instructed by @NickM-27 inside each camera's configuration: |
Beta Was this translation helpful? Give feedback.
-
|
I think the 502 problem requires me to change the URL for the Frigate instance in the Frigate Add-On in Home Assistant. The name of the computer changed so the Frigate add-on is listed as, for example, frigate.home:5000, but now it should be frigate-nvr.home:5000. I've renamed it but this doesn't seem to change where the add-on thinks Frigate is located. The only has places where I can input a URL are for a RTSP URL and a RTMP URL. Those are blank and I think they should stay blank. Any thoughts? |
Beta Was this translation helpful? Give feedback.
-
|
@NickM-27 explained in a different thread that the solution is to delete the integration and then reinstall it. It worked. Much appreciated Nick! |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'd still suggest using preset-vaapi