Closed HA-TB303 closed 4 months ago
You are absolutely right; this is the result of HA not having normalized their data structure. I will look for a solution, am a bit hesitant because it will break backwards compatability...
Understood. Hope you find a solution because renaming 204 entities is no fun :)
For now I am using mqtt. Strangely that does support beter distinguishable naming:
Maybe get the two naming policies aligned?
Thanks for your time looking into this!
Im expecting a breaking change in SmartEVSE v3.5.1 and then I will address this too (since it would be breaking too).
The breaking change is not happening, turns out my code is more future resistant than I thought :-) .
BUT this turns out to be a very difficult change, even ChatGPT couldn't help me out on this one. I understand you worked around it by using MQTT.
If some python/ninja2 wizzard has a PR for this I gladly will accept it...
Yes, MQTT will do for now. :)
When adding multiple smartevse's to home assistant:![CleanShot 2023-11-30 at 16 00 14](https://github.com/dingo35/ha-SmartEVSEv3/assets/9609805/2d2bfcdf-4c97-4aa5-b951-be203e0df893)
They get entities like:
This is quit confusing. It would be better if they would be added like:
sensor.smartevse_6845_access sensor.smartevse_6847_access sensor.smartevse_6848_access sensor.smartevse_6849_access etc...
Renaming 204 entities + future changes is undoable and renaming the devices, does not (bulk) change the entities.