Which model is it? As far as I’m aware all the Unifi APs need the controller for config. It doesn’t need to stay running unless you want a couple features for large deployments but you do need to run it to set things up initially. The Air Max / uisp lines are the ones with web based config.
Do you have a continuously running unifi controller or is it only running when you do the config? Does it do the same thing with the controller opposite to how it is now (ie if you aren’t running it does it do it when you leave the controller on)?
Are you running the 2.4 and 5 as separate SSIDs or the same one?
Are you on the latest controller and firmware?
We use a few Schlage connect zwave deadbolts, and they have been basically rock solid. We’re using them through Smartthings, but home assistant should work just as well. We have hardwired zwave light switches next to all of them, apparently that can help with the reliability since they will act as zwave repeaters in case the lock doesn’t pick up the signal first time - especially for changing the codes.
Are they a perfect lock that no one will be able to pick? Probably not, but it’s a lot faster to just put a brick through your window no matter how good your locks are.
Propaganda from who? Big newspaper? Big book publisher? Big stick and wheel?
To be fair there’s a Linux version of the bedrock server. But yeah not having it on the steam deck is pretty annoying.
To be fair I’d call it a wash. Bedrock fixes a lot of weird stuff like quasi connectivity and being able to push things like chests with pistons but also introduces it’s own bugs like weird timing things and randomly taking fall damage. There’s also weird differences like being able to do things with cauldrons or just like minor texture differences that they are slowly bringing into sync.
Because Bedrock runs on phones, tablets, consoles, and a host of other random crap, and does so relatively well. Because of that the install base and playtime especially among younger players is actually massively skewed toward Bedrock being the more used. Add to that rumors that the Java codebase at least was a terrible mess, and the performance issues Java edition still has to this day and it’s no wonder they wanted to do a full rewrite, especially after having to make things like the console editions and even one for the 3DS.
The windows launcher is annoying though.
Tldw: it’s boring and grindy. Honestly the video isn’t great.
Since I played it when it was free from epic too:
Its a game whose tediousness outstrips its interesting ideas way too quickly. There’s a loop that starts blank that the hero goes around, and the player builds the loop up over the course of a “mission” by placing things like mountains and plains and swamps. Some of these tiles spawn monsters, some help the hero, and some do both. It’s the most interesting thing in the game and also the most underdeveloped. Eventually after placing enough tiles a boss spawns and your “mission” is over and the hero goes back to camp. Technically you can keep going through loops but there’s really no point.
Camp is made up of buildings that you build out of resources collected during the loop and serves as a sort of meta progression for the game. You build things and get new cards, classes, equipment and whatnot. They’re made of tiles but much larger and less visually distinct than the loop tiles - which is super annoying because much like the loop tiles layout is important but unlike the loop that you will place a million times, you only get one camp, so any mistakes are forever. Camp Tiles are built from resources gathered doing loops, so they feed into each other in a kind of rougelite way.
The main problem with the game is that the systems are interesting but they have so much tedious stuff attached that the entire experience is bogged down. Take for instance equipment: the game gives you a stream of equipment that functionally can be different, it might buff attack speed, defense, all kinds of things. But the game gives you like hundreds of pieces of equipment per loop, and it’s all random so you wind up babysitting the equipment section of the screen all the time so that the hero doesn’t become underpowered and die, but you also can’t try for a “build” because any equipment you don’t use is slowly deleted. If you want attack speed the only thing you can do is pray to rngsus that it pops up consistently (spoiler, it won’t). Or the camp itself - eventually you unlock furniture for each house, there are a million different ones, and they’re all things like +1%hp Regen.
But by far the grind gets the most real when you start looking at how many resources you need. Certain tiles grant certain resources that are given during the loop, which is a really good way to incentive players to not get stuck in a rut when building the loop - but the math is way off, and when failing to defeat the boss means that you lose 70% of anything gathered it just adds insult to injury. It’s supposed to be a push your luck thing, but you’re only allowed to leave once a loop and loops can be fairly long and … well like everything else in this game - random.
It kinda feels like I’m just crapping on the game, but I actually think under the tedium there’s an interesting game here. The first time you find a tile interaction (of which there are far too few) is a little magical, and the plot is kind of interesting even though it’s the most overwrought sequel to the neverending story you’ll ever read. Like an annoying amount of Devolver games, this kinda feels like it would be a really good mobile game if it was somewhat streamlined.
Basically, it’s “why not both?”
So first, kubernetes is a different ball of wax than containers, and if you want to run it on one machine you can, but it’s really for running containers across a cluster of machines. I’m guessing you just generally mean containers so I’ll go with that.
Containers are essentially just apps running on a virtual os. Virtual machines are an OS running on virtual hardware. You can abstract both layers and have virtual hardware running an os that runs a virtual os for your containers, and nothing will really mind - in fact that’s kind of the way to do it if you have one big machine you need to run a bunch of services on. You might cut up a server into a Linux VM, a Windows VM, and a BSD VM, and run containers on each one. Or you might run 3 Linux VMs and have the containers for 3 different services split between them.
It really depends on what you’re hosting and trying to do for how exactly to go about it. Take for instance a pretty common self hosted stack:
Plex Radarr Prowlarr Deluge TrueNAS
Now you could install TrueNAS scale and run all of those as containers on it, and it would work ok, but TrueNAS scale isn’t really meant for managing a ton of containers right now. You could make a vm on it for each service and have them all talk to each other but then you’re probably wasting resources by duplicating the OS 5 times. Also, what if you want to run TrueNAS core instead of scale? Can you get everything else working in jails – maybe? – but it’ll probably be a pain.
Instead, you might install proxmox and pass through the drive controller, and set up one VM for TrueNAS core. Then you might make another VM for the arrs containers, and a third for Plex itself.
It gets you the best of both worlds. TrueNAS can run on BSD instead of Linux, your arrs are easy to deploy and update in containers that keep everything separated, and Plex is sequestered in a hardened os with read only access to everything else since it gets a port forwarded and is more of a security risk. Again that’s just one option though.
VMs get you a ton of really handy things like snapshots and for simple VMs, very easy portability between relatively similar hardware. I’ll probably get ruined for saying this but they’re also a security tool that you should probably keep in your belt. If someone manages to break out of a container and your files are just sitting there for the taking that’s not great. If someone manages to break into your VM and “the good stuff” is on another VM that’s another layer of security they have to break through.
Containers on the other hand use way fewer resources, especially ram - and are much easier to wrangle than many OSes for updates and config.
There’s really a lot of self hosted stuff that assumes you’re running docker and treats regular install as a kind of weird edge case, so you’ll probably run docker even if you don’t want to.
Kubernetes on the other hand I would argue isn’t really meant for self hosting where you probably have a one or two servers that you own. Its meant to deploy containers across various cloud servers in a way that’s more automated to manage. If you need storage in a kubernetes cluster you’ll probably use something like s3 buckets, not a hard drive.
If you want to learn it you can totally deploy it on a computer running a few VMs as nodes or with a few laptops / SBCs as a cluster, but if you just want the services to run on your server in the closet it’s a bit like using a sledgehammer to nail a chair back together. That’s why you don’t tend to see it talked about as much - it’s a bit of a different rabbit hole.
Ah, ok. The Unifi stuff is a bit weird like that. I recommend installing the controller on a computer if you continue to have issues. You don’t have to run it all the time, just use it for config and then turning it off is fine. It’ll give you way more information and control over exactly how the AP is set up.