Why is HomeHabit (like rotini before) ignoring my translation in strings?
I am using openhab transformation services
My openhab sitemap shows the correct way, only homehabit is ignoring this.
Exactly…
For example i am using items like this:
String testitem "Testitem [MAP(translation.map):%s]" {binding}
translation.map for example:
-=undefiniert
OPEN=Offen
CLOSED=Geschlossen
So the translation should be shown ?!
Or am I wrong?
In this particular case, if this is used as contact sensor, then the app UI has its own text for open/closed state.
Transformed strings might be possible to use but only in certain case, like in widgets that show value as is such as Value widget, but I don’t think this is what you are looking for.
That is exactly what I want. Open/Close was only an example. I know that there are sensor Widgets.
I want to use this translation in value widgets, but it doesn’t work. It stays in the original value and not in translation.
Got it. Let me see what can be done about that.
(Going to move last few posts into separate thread)
Is there something new about this or multilanguage support at all?
Not yet 
Multi-language support is still on a backlog.
Transformed strings have been attempted but it just didn’t fit into the way data is processed in HomeHabit at that time. It should be revisited due to some changes in data processing that are being implemented right now. Will update soon.
Good news! Transformed strings processing is possible now and has been implemented for the next release.
Fix is now available on a beta channel.
@igor great News for me, will try it as soon as possible.
Available on a beta channel? Sorry for that stupid question, but what does that mean? Can I do a normal app update to get it?
Yes, if in Play Store listing you enrolled as “beta tester”, you’d get versions sooner before official release. Those versions might be less stable.
@igor Tried it, sorry to say that, nur its not working.
In dropdown menu to select the value translation is shown, but the widget shows still the original text.
Even creating the widget new didnt solve the Problem.
What is the item type? Is it Text? It might be getting confused which state to take in a widget.
I believe other item types should work. Meanwhile, I will check on Text items.
its a String item
Yes, it is being implemented now. Should be available soon.
