The first time someone searches a remote community, it’ll start showing up in searches. As soon as someone subscribes to a remote community, posts and comments will start streaming in in real time, and showing up in all.
rs5th
joined 2 years ago
Cabela’s was acquired by Bass Pro in 2017 🤣
Yep, this is a bug that should go away once websocket support is dropped in the next big release.
It's amazing, I think it still requires YAML config, which is a barrier for some folks. Also a bit annoying that it doesn't have it's own dedicated "restart" button like Generic Thermostat, so you have to restart all of HA for the changes to generic_hygrostat to apply.
Here's what I did for humidifiers in my house:
- Dumb, analog-controlled humidifiers (like with the knobs, no digital displays, buttons, modes, etc)
- Local control smart plug (Tasmota flashed Sonoff S31 in my case, but it can be anything)
- Humidity sensor (I use the Zigbee Aqara ones)
- Create a Generic Hygrostat entity
Now you've got a smart humidifier in Home Assistant. You can set the desired humidity, and when the sensor detects it's below this, it'll kick on the smart switch. When it passes the threshold, it'll turn off. It's been great! My humidifiers shut off when the water level drops, so I can even use the power monitoring in the Sonoff switch to send me a "low water" alert when the humidifier should be running, but it's drawing no power!
Yep, using ingress-nginx on k3s as well.
We're using it in production at my day job in a couple of places.
K8s + GitOps is life.
overly complicated for what they need.
👀 glances at the 4 Kubernetes clusters running in my house / personal VPS
I use ingress-ngnix for all my ingress controllers, I've only messed with Traefik a bit in Kubernetes and it felt like it was fighting me the whole time.
I haven't used Docker Swarm (I have barely used Docker Compose), but I have run a couple on-prem Kubernetes clusters (at my house and for clients at my day job) and cloud Kubernetes clusters, so I can speak to how complex it is it set up and run.
My background is systems administration, engineering, IT, and now DevOps. I've been using Linux since Ubuntu 6.06.
I set up my Kubernetes cluster with kubeadm because I wanted to learn, and it took me about a weekend to get my single master, two worker cluster up and running. I think you could probably do this using k3s much faster and have less learning curve (you don't have to care as much about Container Network Interfaces, for example, because k3s makes that decision for you.)
There is a lot of documentation out there on Kubernetes. Helm as a "package manager" (really a templating engine) can be nice if the software you want to deploy has a Helm chart that is well written. Writing your own Helm charts can be a learning process, I've modified some but not written one from scratch yet.
Kubernetes releases new versions about quarterly. I've done several upgrades on my primary home cluster over the course of the past 2 years and they've been pretty smooth, about an hour of time investment ~~total~~ each. And remember, I'm on the more nerdy and complex flavor of Kubernetes. I think with k3s these would be even smoother and quicker.
I feel like Kubernetes knowledge is probably more valuable out in the industry if that's a factor for you. I haven't come across any Docker Swarm clusters in my DevOps travels, just Kubernetes and some HashiCorp Nomad.
I'm curious to see what folks say about Docker Swarm. If you have any questions about Kubernetes or running your workload on it, I'd be happy to try to help!
There are various definitions of “success”. One instance’s definition may well be “replace Reddit”, and another’s might be “create a welcoming community where users feel safe”.