New entity naming or will the naming convention be rolled back? #571
-
Hi forum and a Merry Christmas to You all! Is this "issue" maybe related to the language settings described in this thread #566 My profil language is English, but my system language is Danish. |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 2 replies
-
I've had to remove the logic that suffixed each entry with '#1', '#2', etc when multiple inverters are present: it is incompatible with the HA translation logic and was causing crashes (cfr. #564). I'm surprised that this "breaks" existing installations like shown in your screenshots. The "unique id" which identifies each entity to HA didn't change, which I thought was sufficient to stay compatible with existing installations 🤔. If anybody has any insights in what has gone wrong here: I'm all ears! |
Beta Was this translation helpful? Give feedback.
-
Is there a way to manually change the language back to English, but only for the Huawei integration? |
Beta Was this translation helpful? Give feedback.
-
Thanks!
JensenNick ***@***.***> schrieb am So. 7. Jan. 2024 um 20:30:
… I believe it was suggested by @wlcrs <https://github.com/wlcrs> to set
the language to English while updating the integration and once updated
change the language back to the one you prefer.
—
Reply to this email directly, view it on GitHub
<#571 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A52XJTJNNDIV55UJVZQJJXTYNLZXDAVCNFSM6AAAAABBCHIUTOVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DANBQGA4TG>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
I've had to remove the logic that suffixed each entry with '#1', '#2', etc when multiple inverters are present: it is incompatible with the HA translation logic and was causing crashes (cfr. #564).
I'm surprised that this "breaks" existing installations like shown in your screenshots. The "unique id" which identifies each entity to HA didn't change, which I thought was sufficient to stay compatible with existing installations 🤔. If anybody has any insights in what has gone wrong here: I'm all ears!