Brandon Rothweiler

Yeah, I also noticed that their examples doesn't have this problem. That's why I think it might be an HA bug. For future reference, this is how I tested it:...

This issue should not have been closed. The [NextDNS integration](https://www.home-assistant.io/integrations/nextdns) that was added to Home Assistant allows monitoring NextDNS statistics and controlling basic NextDNS settings from Home Assistant, but it...

Thanks @tribut! By the way, I tried changing the volume mount to be read-only, like this: ``` volumes: - ./data:/config - ./data/docker/run:/etc/services.d/home-assistant/run:ro ``` It seemed to work. I did see...

I'd like to share my particular use case and why I think it would be helpful if `reverse_proxy` supported HTTP/3 for communication with upstream backends. I run a double-layer Caddy...

@mholt Thanks! I agree it certainly shouldn't be a high priority. At this point it's just a nice to have.

I previously reported this in https://github.com/alandtse/tesla/issues/39 but it was closed for some reason.

This is not stale, the issue still exists in 2022.12.

@Vudentz Sure, here are the logs when running with valgrind: [valgrind.log](https://github.com/bluez/bluez/files/10212072/valgrind.log) Also, running bluetoothd with valgrind actually fixes the issue, I assume because it allows bluetoothd to continue despite the...

@Vudentz Sorry, I'm not very familiar with BlueZ and am honestly not sure how to do either of those things. Would you mind briefly summarizing the steps? I'm on an...

@Vudentz With help from @dlech I was able to get the debug symbols installed. Here is the valgrind log with debug symbols: [valgrind_with_symbols.log](https://github.com/bluez/bluez/files/10212611/valgrind_with_symbols.log) I would still need some guidance in...