Handling of dynamically provided backend strings about architecture

[balloob]

We should add it to the docs

[balloob]

I think that we should not try to translate those at all. Just show them as we get them from the API?

[emlove]

I'd personally be OK with accepting that source options are going to be human friendly strings. It does mean that if you use them in automations you'll have to use human friendly names as part of your code, but I think that's probably the most straightforward option.

I think that's been the defacto standard so far, but I don't know if we've formally decided that, since it runs counter to the way we handle most of our attributes.

[MartinHjelmare]

Why should the backend care about frontend formatting?

We should be consistent in the backend to make it easy for users with automations.

The frontend should handle its formatting.

[emlove]

I'd certainly be open to a proposal for a better way to handle this.