RoboMagus

> But if we release 1.34.0 tomorrow, you would still need to change it unless you use :1 which then doesn't help either, and for us it's the same as...

> using :1 is not allowed either, since that basically is latest Why would `:1` not be allowed? As far as docker tags are concerned that is a perfectly valid...

From what I can tell any entities that are disabled will not have a state at all, and thus show up as `missing` to The Watchman. Ignoring the `missing` state...

Turns out querying the HA entity_registry is quite easy to implement. I've opened up a PR that implements the option to ignore entities depending on what disabled them: #161

> Yea I am not sure it will be acceptable to include the old branding there 🤔 Well, any entities inside HA that have its icon set to `mdi:home-assistant` will...

If you agree with this approach I'd prefer looking into creating a separate PR which would patch any use of `mdi:home-assistant` to be in line with what would be shown...

Was just about to create a feature request asking the exact same thing before I stumbled upon this issue. The request: Use multiple SemVer tags when releasing new Docker images....

@gauthier-th, I might be wrong as I don't daily dabble in JS development, but the docs you refer to are for a package named `semantic-release-docker`, not `semantic-release-docker-buildx` which is not...

After some tinkering with these NPM build / release tools I've managed to fabricate a working solution for this issue. It's a bigger change than intended as it required migrating...

Found [this thread](https://community.home-assistant.io/t/esphome-logger-to-a-file/245946/4) on logging to file.