Packages were a great idea, until they weren't (Trigger-based template sensors)

[seanomat]

I was so happy when packages were introduced. Finally a way to organize all the different entities by topic (weather, presence, security, etc.) and have everything together in one place. No searching around, switching between several files, etc.

In come “Trigger-based template sensors” and it all goes to hell.

Is there any rationale behind the limitation of “Trigger-based template sensors” not being “packagable”? It seems so arbitrary!

I know this has been discussed before, just wanted to bring it up again:

Allow integration template: in packages

the new top level integration template: offers great new functionality (much appreciated trigger based template sensors). However, unfortunately we can not configure these in our packages. There’s been some discussion on this, eg see: and it would be appreciated very much if the new integration template: could be configured in packages, just like any other top level integration can be. This way we can keep all relevant config sections together. I am aware we can do: template: !include …

[koying (Chris B)]

I would bet on “oversight”.

But I don’t really see a point on opening a new thread above the feature request and the github issue(s). It’s not like users can do anything about it.

[sparkydave (🇦🇺 Dave)]

Please close this thread. You can ‘bring it up again’ in the original thread.

[petro]

It’s not an oversite, the current packaging solution is completely hacked into home assistant currently and there is no maintainer for it. It has been brought up many times and there’s a highly voted feature request asking for the functionality. Please take the time to vote for that feature request. In time, a solution will be reached but you’ll have to remain patient.