I’m really struggling to understand the SIM side, the page talks about 5G while tethered to a phone?
I think these models can act as router while leveraging RNDIS tethering if you don't have a separate sim card...
Readit Newsvsviridov commented on Unifi Travel Router blog.ui.com/article/trave... · Posted by u/flurdy
vsviridov commented on Penpot: The Open-Source Figma github.com/penpot/penpot... · Posted by u/selvan
Have been self-hosting this on Docker/Portainer for several weeks for a few people. Works fine so far.
vsviridov commented on Adventures in upgrading Proxmox blog.vasi.li/adventures-i... · Posted by u/speckx
My Thingino camera seems to have some RTSP issues, which is a shame because I’d like to use it on more devices.
2.4 GHz sucks though. Wish my mesh allowed me to use multiple 2.4 GHz channels concurrently or per node.
I might just succumb and do the prudynt restart by cron every once in a while as this does seemingly fix it.
vsviridov commented on Adventures in upgrading Proxmox blog.vasi.li/adventures-i... · Posted by u/speckx
I have around 6 cameras, mostly 1080p, and about 8 GB RAM and 3 cores on the VM (plus Coral USB and Intel VAAPI). CPU usage is about 30 - 70% depending on how much activity there is. I also have other VMs on the machine running container services and misc stuff.
There are some camera stability issues which are probably WiFi related (2.4 GHz is overloaded) and Frigate also has its own issues (e.g. with detecting static objects as moving) but generally I’m happy with it. If I optimize my setup some more I could probably get it to a < 50% utilization.
I'm running thingino cameras off wifi and the stability is kinda meh... Want to try a wired setup with a PoE USB Ethernet adapter...
vsviridov commented on Adventures in upgrading Proxmox blog.vasi.li/adventures-i... · Posted by u/speckx
It seems like a lot of the pain comes from the fact that hardware passthrough behaves so differently under LXC vs VMs.
Has anyone here found a stable way to handle USB / PCIe device identity changes across updates or reboots?
That part always feels like the weak point in otherwise solid Proxmox setups
For most part it's okay to pass through by I'd, unless it's some chinese device, which reminds me of the scene from Life Aquatic with Steve Zissou:
"- do interns get Glocks? - no, they all share one"
vsviridov commented on Adventures in upgrading Proxmox blog.vasi.li/adventures-i... · Posted by u/speckx
Lesson 1: clusters should have an odd number of nodes.
Originally I was planning on building the NAS with just the Minisforum MS-01, but truenas and USB enclosures do not play well together.
So I went for the AOOSTAR NAS mini-pc as a "proper" solution. Ended up with two machines, so why not join them into the cluster!
Probably can chuck proxmox on a RasPi somewhere, just for quorum purposes :)
vsviridov commented on Adventures in upgrading Proxmox blog.vasi.li/adventures-i... · Posted by u/speckx
> As an aside... Because one node didn't start, and my Proxmox cluster has only two nodes, it can't reach quorum, meaning I can't really make any changes to my other node, and I can't start any containers that are stopped.
I've recently added another Zigbee dongle, that supports Thread, and it happens to share same VID:PID combo as the old dongle, so due to how these were mapped into guest OS, all my light switches stopped working. I had to fix the issue fast.
Lesson in here somewhere. Something about about a toaster representing the local intelligence maxima?
At least I was laughing at the Cloudflare oopsie, since all my light switches (et al) are all local. Unlike those people with a fancy smart bed that went into a W shape because it couldn't talk to AWS.
vsviridov commented on Adventures in upgrading Proxmox blog.vasi.li/adventures-i... · Posted by u/speckx
I can't speak for the author, but they said they have a Coral TPU passed into the LXC & container, which I also have on my Proxmox setup for Frigate NVR.
Depending on your hardware platform, there could be valid reasons why you wouldn't want to run Frigate NVR in a VM. Frigate NVR it works best when it can leverage the GPU for video transcoding and TPU for object detection. If you pass the GPU to the VM, then the Proxmox host no longer has video output (without a secondary GPU).
Unless you have an Intel Arc iGPU, Intel Arc B50/B60, or fancy server GPU, you won't have SR-IOV on your system, and that means you have to pass the entire GPU into the VM. This is a non-starter for systems where there is no extra PCIe slot for a graphics card, such as the many power-efficient Intel N100 systems that do a good job running Frigate.
The reason why you'd put Docker into LXC is that's the best supported way to get docker engine working on Proxmox without a VM. You'd want to do it on Proxmox because it brings other benefits like a familiar interface, clustering, Proxmox Backup Server, and a great community. You'd want to run Frigate NVR within Docker because it is the best supported way to run it.
At least, this was the case in Proxmox 8. I haven't checked what advancements in Proxmox 9 may have changed this.
At first I had the unholy abomination that is Frigate LXC container, but since it's not trivially updatable and breaks other subtle things, I ended up going with Docker. Was debating getting it into a VM, but for most part, docker on LXC only gave me solvable problems.
vsviridov commented on Adventures in upgrading Proxmox blog.vasi.li/adventures-i... · Posted by u/speckx
Look ma, I'm on the TV.
The merch is in the back, sub to the YouTube channel...
Interesting! Are you familiar with tommysense.com? I think it doing something similar? Did not yet have time to try it.
It's neat that Tommysense works on top of esphome... I'm currently using Bermuda BLE trilateration, but it doesn't quite work, especially in a multy-story living space (e.g. a townhouse). So I already have a bunch of esphome Bluetooth proxies all over the building.
But no source and "lifetime license if you join our discord" is kinda not my jam.