search

dingo35 / ha-SmartEVSEv3

Integrate SmartEVSEv3 with HomeAssistant through custom component
13 stars 8 forks source link

Improvement: Better naming policy when using multiple smartevse's #18

Closed HA-TB303 closed 4 months ago

HA-TB303 commented 9 months ago

When adding multiple smartevse's to home assistant: CleanShot 2023-11-30 at 16 00 14

CleanShot 2023-11-30 at 16 00 53

They get entities like:

CleanShot 2023-11-30 at 16 01 43

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.

dingo35 commented 7 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...

HA-TB303 commented 7 months ago

Understood. Hope you find a solution because renaming 204 entities is no fun :)

HA-TB303 commented 5 months ago

For now I am using mqtt. Strangely that does support beter distinguishable naming:

CleanShot 2024-03-19 at 14 33 47

CleanShot 2024-03-19 at 14 34 15

CleanShot 2024-03-19 at 14 34 40

Maybe get the two naming policies aligned?

Thanks for your time looking into this!

dingo35 commented 5 months ago

Im expecting a breaking change in SmartEVSE v3.5.1 and then I will address this too (since it would be breaking too).

dingo35 commented 4 months ago

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...

HA-TB303 commented 4 months ago

Yes, MQTT will do for now. :)