Hi Everyone,
First of all, thank to everybody for your positive feedback. That’s super motivating. Happy to see that I am not only doing myself a favor here.
Regarding retaining the entity data: @TheSerapher is right. Its about the unique IDs. I see 2 options:
- Align my integrations unique IDs with those of Fenecon2Mqtt. I don’t know the naming scheme of Fenecon2Mqtt (I never installed it myself). Can somebody share? I will consider it as a viable option if I can (technically) do the same and want (does it make sense?) to.
- Users need to manually migrate the data using some update statements in the database. Its doable and no super complex: Migrate energy statistics from one entity to another - #7 by BrentV (but of course its more than just some random clicks in a ready UI).
Regarding my PR for OpenEMS, I am confident it will get merged.
Regarding the current naming pattern: I use 1:1 the channels names as they come from the backend. And due to HomeAssistant rules, default names are aligned with sensor IDs. See the statement about property has_entity_name here. For design reasons, I want to keep the sensor IDs aligned with the channel IDs. Users will have to manually change the names (as correctly explained by @benniju)
I intend to maintain a ranked ToDo list in the repo Readme so everybody knows what to expect sooner and what later (or possibly even never 
). Please note that I am working on this topic only during late evenings for limited time (father of 3 and full-time professional in a relevant position).