Andrew Berry

Hm, I thought the default topic is `rtl_433/+/events`. I don't think we support using anything other than an "event" item, which is what using `rtl_433/#` would subscribe to. The docs...

In the short term, the best thing to do is to only use the autodiscovery addon when trying to add new devices. This was added as step 5 in the...

Since commenting on this, I learned that you can not only allow specific protocols, but you can disable them as well. For new installs, the latest release will start with...

I just gave this a try, and it looks to be working for me. Here's my whole configuration file: ``` device 0 output mqtt://${host}:${port},user=${username},pass=${password},retain=${retain},devices=asdf[/id] report_meta time:iso:tz:local convert si output kv...

We have a bug with output buffering that can cause logs to be delayed until there’s further input. are you putting device before or after the output line? I think...

I've tagged a new release today which fixes the output buffering. Are you still having any trouble with this?

To do that, I think we'd need to parse the `secrets.yaml` file (with python?), but then we'd end up having to write them back out to disk (following the work...

We no longer require secrets to be stored in the config, as long as you're using the MQTT broker within Home Assistant. Does that solve this need for you?

No, it's not, and we should improve that text. > and an external MQTT server location Yes, that's what I was trying to get at - there's no way for...

@sdt16 I don't see a PR upstream with that, can you link if you did get it filed?