I really like KDE. As a long time Windows user, it feels so much more natural than Gnome.
I really like KDE. As a long time Windows user, it feels so much more natural than Gnome.
I just installed Bazzite over the weekend on my main computer. It’s definitely not the smooth experience that Windows is, but I’m hoping I can get used to it and keep using it.
What is the reference I’m not getting here?
Not enough to be a problem. I think things can get unstable around 100-150 devices.
I’m curious how many devices are on your Zigbee network.
Same here. My only issue is sometimes I mix up some card suits due to the lower resolution and smaller screen size, and because I’m not paying close enough attention, end up playing a high card hand instead a flush.
Might help to turn off the scanline effect.
Otherwise it’s a perfect Deck game.
I bought an N100 mini PC (not POE) as my new server a couple months ago. I really like it. That processor is great for power efficiency.
I attempted to do that once. I got a couple hours into calculating exactly what all I needed before giving up. Especially after figuring out it’s not even the best way to make money in the game. But I’ve also spent hours and hours designing and building bases just for fun, so I get it.
people will shit on me about replacing Proxmox with LXD
From reading your comments I understand why. It’s in your delivery. You’re abrasive and you don’t explain why. You’re also telling people not to use something they know, to use something they don’t know, and not explaining how that would be beneficial. As far as I can see, you’ve only explained how LXD, when setup correctly, can do what Proxmox does.
You’re essentially telling people to use something that is at best a side grade for reasons, and being salty about it.
My x86 Proxmox consumes about 0.3 kwh a day at around 15% average load. I’ve only had the Kill A Watt on it for a day, so I don’t know how accurate that is, but it shouldn’t be too far off.
I don’t know personally. But I’d assume it would be from ease of use and reliability.
You could probably get something close to a networked zigbee dongle by running zigbee2mqtt on a pi with a USB dongle and run nothing else on it. It would potentially make restoring it in a failure easier.
From everything I’ve seen, the networked ones are never recommended over USB dongles.
I definitely recommend zigbee2mqtt over ZHA. I originally went with ZHA and just recently went through the hassle of converting over. It was worth it. IMO, it’s best to just start with zigbee2mqtt, and to convert before you have a lot of devices and automations.
Edit: before I posted this comment, I couldn’t see any comments other than the one I was responding to.
To your point, I clicked on this post hoping to see what OP was going to use and why because I would like to build my own NAS some day. But like you said, this post is a waste of everyone’s time.
My personal anecdote is that I only really cared about the Steam Deck. I would’ve entered the Lenovo one if the Steam Deck one worked.
It never worked for me. If the store didn’t tell me it was pushing updates and about to go live, then I could get through the first few clicks and then “something went wrong,”
So I backed off and waited a while. Then when I came back there was a queue system and I gave up.
On the wiki, the “what is retrodeck” explains it, but it assumes you’re familiar with similar software. It lists some Linux OSs geared towards emulation. I think if you want to get the gist of what it is, look at Batocera.
But yeah, it seems the general idea is it’s a frontend to put all the emulators in one UI.
I’m so happy with my Stream Deck. The improvements are so nice, but I’m not going to upgrade. But it means you get an even better version. So you’ll love it, I’m sure.
Your life is in shambles.
Auto detection for MQTT devices is a bit tricky. I struggled with that myself when I was trying to incorporate data from a web scraper I wrote. This config file here shows what I ended up with to create auto detecting sensors in HA https://github.com/chunkystyles/reservationsScraper/blob/main/mqttConfig.json
Each one of the devices gets registered at start up of the app.
If I were doing this all over again, I probably wouldn’t use auto detect sensors. I’d manually configure them. Here’s some examples of that kind of configuration I used for some HVAC remote devices I built:
mqtt: sensor: - name: "makerfabs_remote_1" state_topic: "makerfabs/hvacremote/1/status_out" force_update: true expire_after: 125 - name: "makerfabs_remote_2" state_topic: "makerfabs/hvacremote/2/status_out" force_update: true expire_after: 125 - name: "makerfabs_remote_3" state_topic: "makerfabs/hvacremote/3/status_out" force_update: true expire_after: 125 - name: "makerfabs_remote_4" state_topic: "makerfabs/hvacremote/4/status_out" force_update: true expire_after: 125
For these to work, you just put them in your “configuration.yaml” file in HA.