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

Missing target (add entity, etc) in Action node for tts.google_translate_say #1698

Closed
juansahome opened this issue Nov 24, 2024 · 3 comments
Closed

Comments

@juansahome
Copy link

Describe the bug

When you place Action Node in Home Assistant and you select the action "tts.google_translate_say" the target fields are not loaded, so you cannot select the entities from the front-end view

To Reproduce

  1. Deploy Action Node
  2. Select Action as tts.google_translate_say
  3. No target menu is deployed so you cannot choose the target.

Expected behavior

Being able to select the target, as for the rest of the nodes

Screenshots

image

Example Flow

No response

Environment Information

Tried in two different devices (NAS & Raspberry) with HA OS.
HA Version: 2024.11.3
Node red version: 18.1.1

Additional context

Similar issue: #1648 (comment)

@bertca
Copy link

bertca commented Nov 26, 2024

Same problem here with hvac, input_boolean, ...
Sometimes after restarting Home Assistant and/or Node Red, the targets are back (for a while). I'm trying to figure out when they go and when they are back, but I can't see any pattern in it...
A workaround is to use the data expression field, but to my opinion this is a step back.

@zachowj
Copy link
Owner

zachowj commented Nov 26, 2024

@juansahome For tts.google_translate_say actions, the entity_id must be specified in the data field, not the target field. This is why there's no target selector when using the action tts.google_translate_say. Additionally, google_translate_say is considered a [legacy action](https://www.home-assistant.io/integrations/google_translate/#action-say-legacy), and Home Assistant recommends using tts.speak instead.

@bertca Your issue seems different. It's likely that you're not running the latest version of the Home Assistant nodes.

@juansahome
Copy link
Author

Hi @zachowj thanks for your help!

I tested and it's working with the instructions you shared, Thank you a lot for your help! Needing to add each device inside data it's a little bit a mess when you have several, but at list is working.

THanks again!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants