That sucks… Maybe a good update to LazyNVR would let grab the RTSP stream…

Good! I was probably doing something wrong, but in any case seems more logical to leverage the cameras internal detection.

Feels like nextcloud…

Have you read the readme? There is literally a text config file to fill with the camera info (url of image).

Feel free to open a ticket on codeberg or DM/PM me for any additional detail.

Indeed documentation could be better…

In my experience frigate is quite CPU intensive. I have 10 cameras and my old I7-8700 would die trying to have frigate process them all.

I opted for a different approach with LazyNVR (https://codeberg.org/LazyNVR/lazynvr-sources) leveraging the capability of the camera to perform motion detection and video recording directly. This offloaded my CPU and now I can record all 10 cameras on a OPi3.

There are rules and whoever post, must add the ai tags. But more than that, I find low effort posts like this one do not contribute to the community and are frankly human slop.

At least take the time to write a few lines on what this is and why we should bother click the link.

That will go long way toward a useful post.

You missed my point?

why can’t you just use a wireguard connection between your device and the server, or network?

I don’t get the need for those tunnels.

Wouldn’t a simple wireguard setup be enough un less you are behind CG-NAT?

Wireguard it’s there, free, open source, doesn’t rely on any external server or company…

What does these “tunnels” actually add?

This won’t work for Android windows and such devices. And it’s a pain to setup, won’t work 100% and some scanners are ven worse .

Scanservejs is the final solution for all platforms.

Op want to upload a file to a web GUI and print it from there, not share printers with other computer/ devices.

Also, scanservejs is the the sane web GUI to actually do the same with scanner.

For scanning it make sense as there are no shared scanning solutions across platforms. For printing, it’s of little use as other pointed out you can print to cups from anything basically.

But o get the need for a web printing page, as uploading a file and hit print button is a zero setup, and while simple even remote cups printing is not 0% extra setup, you have at the very least to select a printer or hit “share as” and select a print service (android). YMMV

48 disks seems a nightmare in power consumption, failure rate, and overall cabling management…

What was the total capacity?

I use e self made wood cabinet in the attic where also the PV inverter is located. I used Velcro to strip on the wall (brick wall) stuff like switch firewall etc, only to find those collapsed on the server itself every time. No matter which glue or adhesive i used.

At the end, a strong unbranded Chinese double sided tape was better and still strong after all big western brand failed over time.

Maybe a mix of heat and uneven surface was the culprit, who knows.

Uptime for home users is useless. More important is recovery, reboot and resume (the 3’Rs)

You server should reboot automatically, storage should restore itself from unsafe shutdown and your services should resume operations like nothing happened.

This means test your reboot, ensure stuff doesn’t break, and so on.

Failing storage after an hard reboot is the hardest.

For network, i have two ISP connections and a an auto switch script Incase one goes down. But honestly it’s overkill and not needed for 99% of home hosters.

Buying some kind of UPS like a battery powered power strip is also nice but keep in mind that require maintenance to replace batteries once every few years (long enough to forget) and so be useless. The ups shall only last enough to perform a controlled server shutdown using NUTS.

I use scanservejs since at least one year and can confirm it’s the best.

As for printing, I went down the same rabbit hole and had zero luck. Seems such a stupid thing yet nobody created such a service, except for a couple of commercial ones.

So yeah, if you find something …

By the way, probably creating a simple web interface that accepts uploads and pipe to lpr is pretty easy to do, but I didn’t got around to do it. Printing feels… Outdated. And printing from computer or android is so easy anyway that probably useless.

Llama CPP can run models offloading with CPU (es MoE models), you have much more control over how you run your models, and overall it’s very much actively developed.

For starters and people without too much willingness to mess up with stuff, ollama is a great choice. Llama.cpp gives you that extra power and flexibility that is so much worth for people who like to tweak and do more.

My personal opinion, of course. But based on having used both and ditched ollama for llama.cpp, so I am also biased, keep in mind.

But I will hardly go back to ollama now :)

Every use case is different and there is when you can customize it being Linux.

So good, sladapt your swappines and/or ditch swap completely or try zram, according to your needs. Standard use case works fine for most people tough.

Here is my experience https://wiki.gardiol.org/7-services/llamacpp

No ads no monetization just a wiki I keep for my future reference.

Never been happier than moving to llamacpp from ollama.

As a suggestion, ditch ollama and setup llama.cpp. it will work fine with openwebui and it’s much more efficient. (Unrelated to the ram/swap issue)

You can enable zram and remove your on disk swap file if you prefer to spare the SSD write cycles…

That is expected and a good thing.

Free ram is wasted ram, so every file touched by any service will be cached and cache will stay there until ram is needed. This means that over time cache and buffers will always grow, because any subsequent access to those will be faster. The moment more ram is needed by programs, those buffers and cache will be freed immediately.

This is also the reason why some swap will be used even if there is free ram. Some stuff and pages can be swapped out without impact on performance.

Look at it this way: free ram is a wasted opportunity to increase performance by caching some file from disk.