@dimillian Yes! It's my main development tool, since it strikes the right balance between editor and IDE for me. And it's fast, unlike all the Electron-based stuff out there.

I need to check out those backgrounds, didn't know it was a thing 🙂

@tomayac @homeassistant

Note that I don’t use a HA integration for it either, but IIRC it does support MQTT and has its own HTTP API

@tomayac @homeassistant

Yes! Try the ones at https://go-e.com/en/ 🙂

I’ve been pretty happy with mine so far, but I don’t have anything set up for excess solar (though it does support it)

@jaffathecake If the data in the map/trie is itself a problem, you could split it up and lazily load it. I worked on an icon system where the approach we ended up taking was to generate a server-side spritemap for only the icons in use on the page, and then kick off a low-priority background load for the full set, to speed up future icons.

One approach you could take in your case would be to split up the trie, and include the most popular icons in it, but lazily load other branches as needed.

@jaffathecake The assumption would be that there's a single one. That's what I meant with potentially misunderstanding your requirements; is the requirement that we avoid any sort of map (including a spritemap)?

If so, then the best approach I can think of is a trie. It's a good data structure to use for this sort of indexing.