![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/8286e071-7449-4413-a084-1eb5242e2cf4.png)
Lemmy’s allowlist feature is generally recommended against. It limits federation to only that list, which makes discoverability harder than it already is.
For a self-serving instance, it’s more tenable to use a blocklist and federate normally.
Lemmy’s allowlist feature is generally recommended against. It limits federation to only that list, which makes discoverability harder than it already is.
For a self-serving instance, it’s more tenable to use a blocklist and federate normally.
I use the Ecowitt moisture sensors for potted plants. Given their size, I wouldn’t recommend using them for your lawn because you have to be sure to not hit them when mowing.
Automated irrigation systems are reasonably consistent. I moved from my lawnless apartment to a house with a backyard of grass. I left out a few empty containers across the lawn, waited for the first watering cycle, and adjusted the timings based on the distribution.
IIRC, Gitlab labels it “merge train”
Every day, that list of people grows: https://xkcd.com/1053
I’m a few versions behind, but I’m using the add-on without issue. A few things I would check if my setup failed:
From the /r/homeassistant lurking days, I know that some other people skip the add-on in favor of using a script or another machine that proxies the data into HA. So there are a few other options in case the add-on approach doesn’t seem to be working quite right.
US states. If I have more than 50 different host names to manage, I should re-evaluate my hobbies. And then lazily move on to US state capitals.