Allow forcing lower-casing of entity ids.

Some devices append a .Battery_State while some append .battery_state.

This could be reconciled by forcing lower-case, and/or a separate mapping output that is forced into a lower-case state.

[legrego]

My concern is that I will be adding a non-trivial number of custom_entities to accomplish what I want, rather than a single line blanket configuration argument.

Yeah, I’ve had a hard time balancing the configuration options here (easy vs. highly customizable). We could of course support both, but I was trying to converge on a set of config options that would satisfy most folks, most of the time.

That being said, I don’t really envision folks wanting to force lower case for some entities, but not others. Perhaps an all-or-nothing config would be better in this case.

In the mapping, are these entity_ids always keyword? What if they were inverted default, where keyword was the default type, but text as well (.text)? This would allow for easy, analyzed search of substrings within heavily dot-infested entity ids.

Yes, they are stored as keyword today, but I don’t see a reason why we couldn’t/shouldn’t also store as .text:

https://github.com/legrego/homeassistant-elasticsearch/blob/e25f33250c2e7ac4b966a826d8c2900b4c0eb894/custom_components/elastic/index_mapping.json#L15-L18

[untergeek]

Hard to argue about backward compatibility. I think the principle of least astonishment implies we shouldn’t change it.

However, what if we alter the mapping to make it a separate field of the parent mapping?

entity_id.lower? or entity_id.downcase?