I Used to be like this but now I disagree. I intentionally use “folders” instead of Linux directories or gitlab groups.
Folders are distinct and meaningful, while directories and groups have multiple meanings not clear without context.
I would have liked it just for the integration with code reviews, but we didn’t even get a chance to try because “it’s too expensive” …… as we’re migrating from on-prem infrastructure licensed per site to cloud infrastructure charged per usage, and with no valid cost comparison
I hope not: we’re migrating from Gitlab to GitHub. I was never a fan because of the lack of enterprise features in GitHub (folders, with more granularity of settings and permissions, scalable usability), and certainly GitLab CI was extremely limited but wtf
I can’t comment on Plex vs JellyFin, but it’s an interesting perspective that $3/mon for remote access is too much
I use another piece of opensource software, where I consider that a plus. It takes the headache and security issues off my hands, while I can support the developers with a small contribution for an optional feature
I recently ordered a Trmnl, because it looks like they do what I want, and I keep not doing it as a project. I haven’t gotten it yet but ….
My impression is it’s more of a finished product, not a project. If there is a plugin doing what you want, then it’s a simple configuration. However if you want to customize, you may need to pay for a developer account
My experience with a Pi4B has been rock solid and plenty fast for what I’ve tried so far, at low power consumption.
While I had problems in the beginning, it was all from the micro-SD card. People here will recommend staying away but I’ve had no problems since buying an “extreme” card. Well, starting to hit the size limit now - I can no longer kick off multiple concurrent updates because limited free space available on, I think, 16G card. Get bigger
If you’re starting with ha, don’t feel confined to only one.
IMPORTANT: a local area mesh is not just a low powered way of connecting devices but is inherently local-only. Highly recommended
The more common local area meshes include
The new Matter/Thread standard has support of the major players (Apple, Google, Amazon) so seems like the way to go for the future, but products are slow to roll out so you can’t count on it yet
Personally I found the strengths of each compelling so quickly added all three of the above to my ha setup. Ha is fine with it so why limit yourself
I follow the principle that devices must work “as expected” for my users, automation adds capabilities but does not replace them. This comes together with a focus on smart switches
Arguably had to. For too many years Misguided us policies prevented exporting software with useful encryption, arguably blocked it entirely from opensource. Among the consequences was an encryption industry n Israel suitable for opensource
People think the current us administration is doing a lot of awful things to a lot of people buts it’s worse that they hold themselves above the law to do it, above the limits of their power, above the checks and balances that usually prevent authoritarianism
Among the many bad stereotypes of royalty is the blatant nepotism, self-enrichment, and total disregard for their constituents. Somehow they have no shame in accepting bribes, do not even try to hide it, and no shame using their authority to establish business “deals@ for family and friends
Anyone try Rancher? Is that still a thing? When I looked into k8s a few years back, Ranchers was highly recommended to simplify managing k8s if you couldn’t automate. Supposedly friendly and free.
Step 0. Make sure your networking equipment can do vlans and subnets.
Given how much I paid for a “high end” consumer router, I just assumed ……
I got into each mesh technology for specific devices. Home Assistant supports them all and they seem to coexist just fine in my use case.
I have a small to medium setup with only a few simple automations and a focus on voice control and scheduling
Preference
But it also helps that my approach is generally switches and outlets. Hard-wired, predictable network, tend to be repeaters. I have comparatively fewer leaf nodes.
This approach also fits in with my biggest challenge. While my house is small, it’s an older one with dense materials that blocks a lot of radio signals. For example I have no cell phone reception inside yet strong signal just out any door. My focus on switches and outlets overcome this with a repeater in every room
So for example a few years back I got a z-wave IR blaster to control a mini-split AC because at the time I mostly used z-wave. I already had a z-wave light switch in the same room, acting as a repeater, so no worries about connectivity. Now I have both z-wave and Zigbee light switches in that room so expect both meshes to be strong for any future devices in that room
I’ll also vote to reconsider WiFi. Home Assistant supports a variety of local mesh networks that by default can’t connect to the cloud and whose devices are cheaper and lower power.
I use all three of zwave, Zigbee, and thread; ha works with whatever you need.
I choose to pay for remote access, but it’s for convenience and to support the developers. You are free to configure it yourself in a couple ways (and there is decent documentation) or do without remote access
I don’t know how you set up remote access for OpenHab, but from a quick glance at the web site it looks similar
Sort of related, but I recommended against my teen getting a Mac laptop for college because it is different and he wasn’t familiar with it. While that’s not obstacle for us techies, it seems to be for normies. However he has had no issues.
In case that extrapolates to Linux …. A different UI, different paradigms, aren’t necessarily an obstacle to normies
We’re forming a squad! Almost a team!
It was a gift, over 20 years ago. I married her
Look at OP, claiming to have that mythical girlfriend who will make a sandwich without escalating privileges
Yeah a directory … that thing we need ldap for, right?