Maybe?! https://github.com/emoncms/emoncms/pull/1779 looks promising:
I have some problems with string values - it seems like emoncms is just discarding them - is that expected? There are some which are obviously booleans (on / off / true / false / yes / no) which could be mapped to 1 or 0 with a generic function. Does that make sense to consider adding lower down in the MQTT service before it submits the values, or is there somewhere else that’s worth considering (on the way “in” to emoncms)?
However, some of the fields reported by ebusd are enums (see https://github.com/john30/ebusd-configuration/blob/master/ebusd-2.1.x/en/vaillant/_templates.csv#L86 for example) - is there somewhere in the pipeline I’d be able to configure a mapping for those I cared about?