Skip to content
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

Pt br leofig rj #1413

Closed
wants to merge 36 commits into from
Closed

Conversation

leofig-rj
Copy link

Updated intents: _common.yaml, light_HassTurnOn.yaml, light_HassTurnOff.yaml, light_HassLightSet.yaml, fan_HassTurnOn.yaml and fan_HassTurnOff.yaml.
Updated responses: HassTurnOn.yaml and HassLightSet.yaml.
In pt-br.

name: "all"
response: fans_area
- sentences:
- "<desligar> (todo[s] [o[s]] ventilador[es] [da casa] | [todo[s]] [o[s]] ventilador[es] da casa)"

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it makes no sense todo[s] and the two options inside (<OPTION_1> | <OPTION_2>) are basically the same, aren't they?

And since it's an action to turn all the fans off, [os] makes more sense than [o[s]]

What do you think of updating it to:

- sentences:
    - "<desligar> [todos] [os] ventiladores [da casa]"

name: "all"
response: fans_area
- sentences:
- "<ligar> (todo[s] [o[s]] ventilador[es] [da casa] | [todo[s]] [o[s]] ventilador[es] da casa)"
Copy link

@brunoluvizotto brunoluvizotto Jun 2, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same suggestion I left for the intent for turning off all the fans:

I think it makes no sense todo[s] and the two options inside (<OPTION_1> | <OPTION_2>) are basically the same, aren't they?

And since it's an action to turn all the fans on, [os] makes more sense than [o[s]]

What do you think of updating it to:

- sentences:
    - "<ligar> [todos] [os] ventiladores [da casa]"


# Max/Min brightness
- sentences:
- "<mudar_valor_numerico> [a] luminosidade <no_nome> [no] {brightness_level:brightness}"
Copy link

@brunoluvizotto brunoluvizotto Jun 2, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggestion: replacing [no] with [no|em|para] since it makes sense to say:

Ajustar luminosidade da luz para 10 or even
Ajustar luminosidade da luz em 10

# Max/Min brightness
- sentences:
- "<mudar_valor_numerico> [a] luminosidade <no_nome> [no] {brightness_level:brightness}"
- "<mudar_valor_numerico> [no|em] {brightness_level:brightness} [a] luminosidade <no_nome>"

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggestion: replacing [no|em] with [no|em|para] since it makes sense to say:

Ajustar para 10 a luminosidade da luz

response: brightness

- sentences:
- "<mudar_valor_numerico> [a] luminosidade <na_area> [no] {brightness_level:brightness}"

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggestion: replacing [no] with [no|em|para] since it makes sense to say:

Ajustar luminosidade na sala para 10 or even
Ajustar luminosidade na sala em 10

@frenck
Copy link
Member

frenck commented Jun 9, 2024

Since there was no response at all, I'm declaring this PR stale and closing it.
Feel free to re-open this PR when you feel like that is the appropriate thing to do.

../Frenck

@frenck frenck closed this Jun 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants