Larry Gregory

In an effort to reduce configuration bloat, I am going to close this as "not planned". We can re-evaluate this decision in the future if there is sufficient demand.

I'm now thinking that mapping `hass.attributes` as [flattened](https://www.elastic.co/guide/en/elasticsearch/reference/current/flattened.html) would make the most sense.

> Another option here would be to put each domain into its own Index / Datastream. This would allow each domain to use its domain-specific mapping while allowing users to...

@strawgate Thanks, I wasn't aware that Kibana lacked support for the flattened type. I also didn't know that other data sources already work this way. Given that, I'm happy to...

> I'm coming back to this as I just stumbled today over the alias setup etc. I wonder if we could introduce a new config (which becomes the default for...

> I would switch over to an integration package having the templates etc. inside (see https://github.com/ruflin/ruflin-integration-package for inspiration). All the elasticsearch integration would do is push the zip file for...

> The package installation takes care of all the edge cases, roll overs etc. and allows you to package additional assets like dashboards etc. into it. It also means you...

_Thank you for contributing to this issue, however, we are closing this issue due to inactivity as part of a backlog grooming effort. If you believe this feature/bug should still...

I'm very excited for this feature, and appreciative of the team's continued efforts. I see in the [docs for this feature](https://nodejs.org/docs/latest-v21.x/api/permissions.html#limitations-and-known-issues) that "Native modules are restricted by default when using...

> We can add an `--allow-addons` flag @legrego. I'll be working on that, but once you enable it addons will bypass any permission imposed by the permission model (the same...