-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Translation of LWT payload #9395
Comments
I do not see a translation for LWT payload in the cz laguage file. There is no other file for language specific translations. It looks like you have redefined "somewhere" |
Please see link, which is mentioned. I used standard tasmota-cz.bin, no changes. When I tested now with standard tasmota.bin, everything is OK. |
There are indeed translatioms in the cz.h language file. A change is needed in the language file. |
Trouble is some other languages did indeed translate online/offline in their language.... What is common sense here.... |
Translate Neaktivní/Aktivní back to english original. arendst#9395
May be we need to move the |
I vote for moving out of language file too. I didnt even recognized that this was LWT... |
Make LWT state message user configurable (#9395)
PROBLEM DESCRIPTION
Don't know, if this problem is in all languages, but in Czech version of Tasmota v8.5.0.1 is problem with translation of LWT payload.
It shows
Aktivní/Neaktivní
instead ofOnline/Offline
.This can make problems with another softwares/plugins, which expect standard english words.
REQUESTED INFORMATION
Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!
Backlog Template; Module; GPIO 255
:Backlog Rule1; Rule2; Rule3
:Status 0
:(Please use
weblog 4
for more debug information)TO REPRODUCE
Check payload of
/tele/device-id/LWT
and power cycleEXPECTED BEHAVIOUR
Use standard english strings, not translated.
SCREENSHOTS
If applicable, add screenshots to help explain your problem.
ADDITIONAL CONTEXT
Add any other context about the problem here.
(Please, remember to close the issue when the problem has been addressed)
The text was updated successfully, but these errors were encountered: