Fixing weather_HassGetWeather and person_HassGetState #1768
Replies: 8 comments 17 replies
-
will do so today evening (CET) for German language -> Done #1777 |
Beta Was this translation helpful? Give feedback.
-
@tetele Do you want us to do it ASAP or are you expecting any further changes to the #1767 and we should wait for it to be finalized and merged? |
Beta Was this translation helpful? Give feedback.
-
Spanish changes completed, waiting for home-assistant/core#105524. |
Beta Was this translation helpful? Give feedback.
-
NL done as well #1771 |
Beta Was this translation helpful? Give feedback.
-
PR's are approved and waiting to be merged. One small hiccup in the HA core PR, but it will be fixed soon. Please proceed with the changes :) |
Beta Was this translation helpful? Give feedback.
-
PT-BR done #1786 |
Beta Was this translation helpful? Give feedback.
-
Catalan [CA] done at #1787 |
Beta Was this translation helpful? Give feedback.
-
I will try to get Danish (DA) done tonight. |
Beta Was this translation helpful? Give feedback.
-
Hey @home-assistant/language-leaders!
You might have noticed in a production environment that the
weather_HassGetWeather
intent doesn't really work (it doesn't provide the weather condition) and that theperson_HassGetState
intent is really hit and miss.The reason behind this is that both intents use the state value for making decisions upon which to build the response, but the state is translated before being used in the intent response. This is by design, as you want to say that a battery "isn't on, but off" in the same language in which the question was received.
Since we're less than 36h away from the Chapter 5 stream, I was going to propose we fix the sentences for
weather
andperson
state in the short time we have until then, so that people can enjoy the functionality as soon as possible.To prevent breaking changes, I've made a core PR that introduces both the translated and untranslated state as state attributes, thus preserving the current translated state behavior. The PR is still under review, though, so I wouldn't recommend that you fix the sentences/responses/tests directly on the
main
branch of the intents repo. Instead, I've created anuntranslated-state
branch, upon which I've opened a PR to fix the English sentences.This PR is also pending review and I'd recommend you subscribe to it to get notifications in case anything changes.The PR has been approved and merged, so it's a good example of what needs to be doneI kindly ask you to do the same for the languages you are leading as I did for English:
untranslated-branch
in your fork:git fetch upstream untranslated-state
, assuming the remote pointing tohome-assistant/intents
is calledupstream
git checkout untranslated-state
git branch xx-untranslated-changes
wherexx
could be a language code. Feel free to name your branch however you want, thoughuntranslated-state
branch by using a URL similar to this untranslated-state...your-name:intents:xx-untranslated-state (you need to edit the URL to make it work)untranslated-state
branch as soon as yousee [EN] Fix intents with untranslated state #1767 being merged (changes may still occur)canOnce home-assistant/core#105524 gets merged into
core
, we can also merge the new branch into the intents repo and create a new release. That way, we will sync our effort and not introduce breaking changes.Beta Was this translation helpful? Give feedback.
All reactions