Don’t remind me …. The doublespeak at my company …… we had to use GitHub for the built in AI, but couldn’t even evaluate GitLab’s AI because it costs extra

Note that the top “ribbon “ is visible from all of those ribbon choices, while the content pane stuff, like the “About” box are only visible in “Code”

Comments like this are so frustrating to see, as my company goes backwards, moving from Gitlab to GitHub.

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

• Zigbee - open standard, lots of inexpensive sensors
• Z-Wave - devices need to pay for certification but are more standard. I found more smart switches using this in my area
• Thread - the new standard. Same frequency as Zigbee but IPv6 based. Slowly rolling out.

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

• can be used interactively just like any switch
• continue to work as expected even if ha is down
• typically act as routers to strengthen your local area mesh. I have switches acting as routers for Zigbee, zwave, and Thread, so all my local area meshes are solid everywhere
• then I can automate

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

• Thread - given Apple, Amazon, and Google support and the standardization work, I expect this to be the future. Eventually. But I’m getting impatient. If I’m buying a device, I prefer Thread but usually it’s not yet
• z-Wave - my first, and most devices. Basically this was what was most available at local stores when I started. No complaints
• Zigbee - by far the biggest selection of simple, cheap sensors. I need to more of those
• all too much is WiFi but I try to avoid

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

I’m not entirely sure why all the hate : Jenkins can do the most things the must ways. And yes, it’s so much nicer defining a pipeline with a fully functional language than an assortment of yaml files

Actually that was my response when my company wanted to start using Gitlab ci. It only has one way of doing things so you can probably get a faster start if you had no ci, were a small company, and had simple builds. However we’re over 4,000 builds in many languages from 12 year old monoliths to modern micro services and containers…… and way too much godawful JavaScript. Do you want the quick and simple tool great for a small startup or the all powerful kitchen sink of tools?

Home Assistant hs communities to share exactly that

My similar script has a very different goal: at midnight if someone is still up, it dims the family room light and announces on speaker”hey kids, it’s time for bed”

As everyone else says, look at home bridge. I use HA for my automation but use the bridge to expose many devices to HomeKit.

I verified I can set up HomeKit and use family share for my family to see the dashboards I set up there

Signing (intermediate) certs have been compromised before. That means a bad actor can issue fake certs that are validated up to your root ca certs

While you can invalidate that signing cert, without useful and ubiquitous revocation lists, there’s nothing you can do to propagate that.

A compromised signing certs, effectively means invalidating the ca cert, to limit the damage

Hosting email just saved the day! My ex got locked out of her email account and password resets were blocked. However she still had one “home” forwarding email configured as a recovery address, so we were able to redirect it somewhere accessible and unlock her email account!

A buddy of mine did that by ups. His “offsite backup” was a raspberry pi zip tied to a couple drives and mailed to me. All I needed to do was plug it in to power and Ethernet (and trust him on my network).

When a drive died, he mailed another one and I mailed the original back