Larry Gregory

Hey @ankerstal, thanks for opening this issue. I intentionally took a simple/opinionated approach to ILM, due to the sheer number of available configuration options. I'm not personally interested in allowing...

I see there are a number of 👍 reactions to this issue. Can anyone weigh in on my questions above? > I'm not opposed to skipping policy overwrite, but I...

Thanks @erikveg I agree this would be useful. From a security perspective I think we should prefer an API Key over traditional username/password

@erikveg, Thinking about this a bit more: would you prefer to create the API Key yourself, and store that within this component (like we do with username/password today), or would...

Hey @josemotta, thanks for the feedback. I don't have any plans to remove the manual configuration method anytime soon, but I may decide not to add new config settings to...

Thanks for your interest! Yeah I need better docs for sure for this. If you're using Visual Studio Code, then this project includes a [dev container](https://code.visualstudio.com/docs/remote/devcontainerjson-reference) that to my knowledge...

@ruflin I think `metrics` makes sense for this component. At this point, I think a single dataset is all we'd need. What do you think about any of these options?...

> One thing I'm stumbling over is hass prefix instead of home_assisstant or ha. I'm still new to Home Assistant and I just run it in a docker container without...

> The only way I can think of to remove the problem completely is to use `hass.attributes.{DOMAIN}.{ENTITY_ID}.*` ++ I think this is close. `entity_id` is _technically_ the concatenation of `domain`...

> In general it means we'll never be able to share visualisation because we have different entity_id, but I don't see any other solution... Yeah which is sad, but that...