vacuumpizzas

I would have expected studios to use a 3rd party system back then. GameSpy was huge in that era to cover that functionality.

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.

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.

What did you map your boost and jump to?

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:

1. The wrapper has 2 major components. Make sure you’re running both of them.
2. Slim down your config.
3. You mentioned you have your own decoders. Double check the rtl_433 version that’s being used in the add-on to ensure everything is compatible.

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.

Ah that’s good to know. I suppose this is a reasonable limit to what I gain by living on the bleeding edge.

Upgraded the UI to 0.18.0-rc1 and the backend to a few commits ahead of 0.18.0-rc1. I haven’t seen this issue so far today.

And I just got a 14 day-old post. So it seems like the issue is still there.