andarotajo

Currently running into the same issues described here and it just feels so clunky without a built-in solution. But I couldn't find a better solution other than the ones provided...

> ... as well as tests covering the new functionality. I just saw with the rebasing that I had added tests for the config flow GPS option in my initial...

I'm sorry I think I broke something while rebasing... Can I somehow salvage this? I followed the due to a conflict [docs](https://developers.home-assistant.io/docs/development_catching_up/) but probably missed something Edit: Fixed it luckily...

I'm pretty new to Python so thanks for all the help and patience! I'll make a follow-up PR for the tests and for error handling with repair issues too when...

https://github.com/home-assistant/core/pull/96027 just got merged so this is ready :)

No I pretty much forgot about it. It's not that bad for me since I only have one of those sensors. I didn't want to just copy the config and...

Getting the same error for quite a while now. My current workaround is calling `homassistant.reload_all` ~5 seconds after starting the add-on (i start it via automation only after a successful...

I'm experiencing the same issue. Not sure since when this has been happening though

Noticed the same "ENOENT" error recently. On every save it pops up for the files `automations.yaml`, `scenes.yaml` and `scripts.yaml`. My configuration is on GitHub so I don't have those files...

I just noticed the same problem with my new QRevo Master. I have all the settings, i.e. fan speed, mop intensity and mop mode, on `Custom` currently. Just setting the...