CoZ

From what I've read, the dedicated server stuff hasn't been optimized as yet by the DEVs

This still isn't listed in C.A.?? I had a work trip, figured I'd come back and install it, and it's still not listed? Yes, I know I can do the XML file thing but, I feel bad that it's not listed still after all this time you've put in.

@Nodiaquestill no results searching for "Enshrouded" in the CA Apps plug-in. That was really cool of @ich777to lend a hand !

There seems to be quite a few of them on Docker hub. However, I wouldn't even know which one would be "best" and not sure the level of trust would be the same as an ich777 docker container lol

Damn. That is disappointing - I came on here to ask for the same; Enshrouded Server. I do understand though, you've done a lot. Hopefully someone else makes one as rock solid as your Valheim server has been for me and, many others.

This helped me a great deal when setting up my notifcations https://community.home-assistant.io/t/frigate-mobile-app-notifications/311091

Ok, I took your advice and dropped it down to 4ps. I didn't see any noticeable difference either. Thank you for that suggestion.

Sorry. Absolutely nothing you just said made any sense to me. I'm waiting for the next version of Frigate, like you mentioned, that will have the NVIDIA detection stuff "built in". I can only guess that's what you meant by hwaccel card? I gave up on the TesnoRT stuff once I read your comment about that. I've offered cold-hard-Paypal funds to many people on many Frigate forums to just code my YML for me since I've been working on this for almost a year now and simply can't figure it out. No one has taken me up on my offer. So, I just keep plugging away at this in an act of frustration. Thanks anyway. I will continue to just lurk here and read and not post anything because I don't have the basic knowledge to even understand your reply. lol

Yes Sir, I believe I set it up properly – unless of course, like usual, I screwed something up. This is a lot to take in and one wrong indent along the way and POOF everything crashes. lol. go2rtc: streams: Rear_Deck: - rtsp://admin:[email protected]:554/h264Preview_01_main Rear_Deck_sub: - rtsp://admin:[email protected]:554/h264Preview_01_sub Garage_Camera: - rtsp://admin:[email protected]:554/cam/realmonitor?channel=1&subtype=0 Garage_Camera_sub: - rtsp://admin:[email protected]:554/cam/realmonitor?channel=1&subtype=1 ffmpeg: hwaccel_args: preset-nvidia-h265 rtmp: enabled: False cameras: ############## REAR DECK ################## Rear_Deck: ffmpeg: inputs: - path: rtsp://127.0.0.1:8554/Rear_Deck input_args: preset-rtsp-restream roles: - detect - path: rtsp://127.0.0.1:8554/Rear_Deck_sub input_args: preset-rtsp-restream roles: - record

Why if I use my camera's substream to detect, and set the detect: width: 640 height: 480 fps: 10 Frigate dashboard only displays that feed? Even though I have the 2k Resolution set up for “record” and the sub stream for detect, Frigate is only displaying the sub in live view. (or, I'm assuming it's the sub because of it's squished down view) If I change the above code to, for instance, 720p then my thumbnail of the video feeds and the video feed itself doesn't look as “squishy” as the 640x480. I thought perhaps I had gotten my sub and main streams reversed, but I have checked and re-checked them and they are correct. If my substream is only 640x480 but I set it to 720p just to get a clearer live view, am I now not upscaling my detect stream, using more resources than I need to be?

Trying to install that tensort model. Reading the instructions it says to place the tensorrt_models.sh script inside the /appdata/tensort directory. Disregard. Just saw yayitazale's post about the next version of Frigate coming out.

Went to C.A. and searched. It shows it installed . There is no option to update it, only remove it.

I was going to attempt to do just that but wasn't sure if I should. I just checked for updates on the docker page and nothing for your docker. Strange. It should automatically check C.A. when doing an update check, yes?

Well that is strange because I don't have that setting at all. The only thing is a setting to enable ValheimPlus. I even went into the show more settings and still it's not present.

General Valheim question for anyone here; has anyone figured out how to install PlanBuild / Hook Gen Patcher / etc / etc on the server? I have a few mods installed locally (BepInExPack for instance) that will still allow me to connect to the dedicated server without issue. Once I enable the Planbuild and dependencies it won't allow me to connect since it isn't installed on the server. I tried digging through the folders on the appdata but they don't look remotely anything like what the directories are for the local server (was just going to drag and drop the BepInExPack into the same folder structure on the server and cross my fingers...

Your sarcasm was quicker than my ability to reply. Restarted a few times and it finally "kicked in"(?) Not sure what the hangup was. I only look at the logs when something isn't working. Your container has been rock solid for months so there wasn't a need to go looking.

There seems to be some issue with the newest Valheim update pushed out and the container. Restarted container to manually pull down the newest Valheim patch. Now getting an error message: Loading Steam API...dlmopen steamservice.so failed: steamservice.so: cannot open shared object file: No such file or directory Then, following that: Connecting anonymously to Steam Public...OK Waiting for client config...OK Waiting for user info...OK Success! App '896660' already up to date. ---Prepare Server--- ---Server ready--- ---Starting Backup daemon--- ---Update check deprecated!--- ---Start Server--- However it just hangs there. The server never actually starts - I can not connect to it. I've restarted the docker a few times. Same error message(s) over and over.

Sorry for the delay in replying. Some severe weather rolled through, and I was stuck at various airports forever. My friend, if I could UNDERSTAND the Docs and read them properly, I wouldn't be here asking for help. That is my main complaint with this. It's by no means 'user/idiot friendly'. There are too many variables listed in those docs. Hence, why I was looking for a “If you have this model of camera, your config file needs to look like this” type of website earlier. You have my gratitude for helping me get this far. You also have my sympathies for constantly trying to help others on here. Home Assistant has better docs / wiki and support forum. I didn't really have any issues setting all that up and the associated containers (NodeRed, MQTT, Zwave, etc) since it was easy to follow along. For some reason, I can't wrap my head around Frigate.

That was part of the initial docker pull - the got2rtc streaming you're speaking of? I deleted all those entries on the docker because (A) had no clue what it was for (B) it told me to remove them if they weren't going to be used. Putting in the output_args caused Frigate to crash with the following error: 2023-07-19 09:31:52.056562168 pydantic.error_wrappers.ValidationError: 1 validation error for FrigateConfig 2023-07-19 09:31:52.056566211 cameras -> Rear_Deck -> ffmpeg -> output_args -> output_args 2023-07-19 09:31:52.056569915 extra fields not permitted (type=value_error.extra)

As requested. I am sure you are going to have a field day with this one and just rip apart what I've done. I'm ready. Go for it. config.yml

I've expanded my docker.img a few times now. I am also partially to blame. Pulling down your container the first time and then going back in again and changing the repo (after actually digesting your instructions) to the newest Nvidia one and then pulling all that data again became far too much. I never did get it working. I saved your script and tried to place it in to the appdata/trt-models/tensorrt_models.sh folder. It would not let me because the folder is the same as the filename. So then I tried to change the name of the script and then change the whole chmod stuff to the new name of the script - still didn't work. I know you wren't judging. I was trying to bring some levity into the discussion. You want me to post my config.yml or, you want a screenshot of how I have your container setup with all the paths and etc...etc..? Remember, talk to me as if you were talking to a small child trying to explain how the universe was created. (again, levity)

1. Eventually – I guess? I have one camera and I only use it to detect when my family of wild raccoons show up at night so I can go out and feed them and hang with them. Please, don't judge. lol I know I have to download another docker image Tensor (something or other) to utilize it. I'm just concentrating on getting this back up and running. 2. Done. They didn't specify if it should be before or after. Again, the DOCS leave a lot to be desired for amateurs such as I. 3. 2023-07-17 14:28:52.680503315 [2023-07-17 14:28:52] frigate.video ERROR : Rear_Deck: Unable to read frames from ffmpeg process. 2023-07-17 14:28:52.680790112 [2023-07-17 14:28:52] frigate.video ERROR : Rear_Deck: ffmpeg process is not running. exiting capture thread... 2023-07-17 14:28:55.961193412 [2023-07-17 14:28:55] watchdog.Rear_Deck ERROR : Ffmpeg process crashed unexpectedly for Rear_Deck. 2023-07-17 14:28:55.961446594 [2023-07-17 14:28:55] watchdog.Rear_Deck ERROR : The following ffmpeg logs include the last 100 lines prior to exit. 2023-07-17 14:28:55.961725123 [2023-07-17 14:28:55] ffmpeg.Rear_Deck.detect ERROR : [segment @ 0x55dfd77aff40] Timestamps are unset in a packet for stream 0. This is deprecated and will stop working in the future. Fix your code to set the timestamps properly 2023-07-17 14:28:55.961920823 [2023-07-17 14:28:55] ffmpeg.Rear_Deck.detect ERROR : [rtsp @ 0x55dfd7793200] CSeq 6 expected, 0 received. 2023-07-17 14:28:55.962207303 [2023-07-17 14:28:55] ffmpeg.Rear_Deck.detect ERROR : Last message repeated 4 times 2023-07-17 14:28:55.962494096 [2023-07-17 14:28:55] ffmpeg.Rear_Deck.detect ERROR : rtsp://*:*@192.168.1.18:554/h264Preview_01_main: Connection timed out 2023-07-17 14:28:55.962704420 [2023-07-17 14:28:55] ffmpeg.Rear_Deck.detect ERROR : Last message repeated 1 times 4. I know enough to run it from the CLI in UInraid (Plex and Jellyfin and Unimanic user). Otherwise, that piece of information would have been useful. New information: After switching the runtime=nvidia to the front of the extra parameter line and placing back in the hwaccel_args: preset-nvidia-h264 back into my config.yml. Even though it explodes and I get all those FFMPEG error messages I can now actually VIEW the camera stream and typing in nvidia-smi into the CLI shows that a FFMPEG running process is ... running. So, no idea why or how? I leave that up to you good Sir. Update 19:46HRS: Tried messing with the Tensor docker. It filled my docker memory usage to 90% once it extracted almost 4GB worth of files. Almost crashed my entire system. Not good.

So, I've been messing with it because I am too stubborn to call it quits. I seem to have it up and running. However, picking the Nvidia Branch when selecting which version to install from CA and then trying to enter into the config.yml: hwaccel_args: preset-nvidia-h264 Which, causes an error about FFMPEG crashing. If I remove the hwaccel_args: preset-nvidia-h264 and restart frigate docker, I can see the stream. I did enter my GPUID and clicked advancded tab and entered the --runtime=nvidia at the end of all the other text that was already pre-populated. --shm-size=256mb --mount type=tmpfs,target=/tmp/cache,tmpfs-size=100000000 --restart unless-stopped --runtime=nvidia Running the command nvidia-smi without the hwaccel_args tells me that there are no running processes. I'm using a Geforce GTX 1050 on a Reolink RLC-410W You DID tell me to ask for help. So, this is pretty much your fault now

Is there an “idiots guide” to setting this up? It took me about a month of troubleshooting and reading the docs on the older version and, I eventually got it up and running. I saw that an upgrade was available and there was no way I was going to attempt it after reading the docs as far as what was required to get the new version running. So, I left it alone. Unfortunately for me, I had to stop my Docker service to do some maintenance and the old version of Frigate, for whatever reason, would no longer launch. I made a backup of my config.yml file and attempted to install the new version to no avail. The docs aren't exactly idiot/user-friendly. There has got to be a better “how to” video/webpage out there that I can't find to assist in getting this new version back up and running?

Yes. Like I said, the only way to get it to stop bootlooping was to change the server's previous password to something new.