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

Did google_tts change once again? No TTS from google_translate for #43801

Closed
Mariusthvdb opened this issue Dec 1, 2020 · 44 comments · Fixed by #43863
Closed

Did google_tts change once again? No TTS from google_translate for #43801

Mariusthvdb opened this issue Dec 1, 2020 · 44 comments · Fixed by #43863

Comments

@Mariusthvdb
Copy link
Contributor

Mariusthvdb commented Dec 1, 2020

The problem

As of today, all google_tts notifications stopped working once again, without any change on my side in the config. As far as I can see, no automatic updates have happened in the backend, supervisor is still on 2020.11.0.

Environment

  • Home Assistant Core release with the issue: 118.4
  • Last working Home Assistant Core release (if known): 118.4
  • Operating environment (OS/Container/Supervised/Core): OS
  • Integration causing this issue: Google Translate
  • Link to integration documentation on our website: https://www.home-assistant.io/integrations/google_translate/

Problem-relevant configuration.yaml

tts:
  - platform: google_translate
    service_name: google_say
    cache: false

Traceback/Error logs

2020-12-01 09:12:48 ERROR (MainThread) [homeassistant.components.tts] Error on init TTS: No TTS from google_translate for 

Additional information

@pepe59
Copy link

pepe59 commented Dec 1, 2020

Yes, I confirm the same problem with me. It happened at night. I did not make any configuration changes in HA.

@spider7611
Copy link

Have problem too. :(

@probot-home-assistant
Copy link

google_translate documentation
google_translate source
(message by IssueLinks)

@Jack465
Copy link

Jack465 commented Dec 1, 2020

Just to add onto this, I am getting the same problem whenever I try to use the TTS integration.

Clearing my logs, and then trying to send a message to a media player device, I get the following two errors.

Unable to find token seed! Did https://translate.google.com change?
Error on init TTS: No TTS from google_translate for 'hello from home assistant'

@willysoft80
Copy link

Same problem

@DidrikN
Copy link

DidrikN commented Dec 1, 2020

Same problem.

@frenck
Copy link
Member

frenck commented Dec 1, 2020

⚠️ Please

Instead of replying with "same problem", "+1", "here as well" or "same for me", please just add a 👍 to the original topic post all at the top of this page:

#43801 (comment)

Thanks 👍

@muzzak123
Copy link

muzzak123 commented Dec 2, 2020

It might be related/the same issue as here [Error in TTS #123]Hypnos3/node-red-contrib-cast#123

@tomvhoogmoed

This comment has been minimized.

@majkers
Copy link

majkers commented Dec 2, 2020

@pvizeli you were added in my #43844. Mind taking look at this one?

@colethegamer123
Copy link

colethegamer123 commented Dec 2, 2020

Just a little information. If you are using Cloud Nabu Casa, you can change the service from tts.google_say to tts.cloud_say and it will work like this.

EDIT: That is also not a solution, because all my TTS automations was in the language of Hungarian, now it drops error: "Not supported language hu". Both Service have problems then :(

@frenck
Copy link
Member

frenck commented Dec 2, 2020

@majkers Please don't ping people to pull them into the conversation. That is considered impolite. Thanks 👍

@hmmbob
Copy link
Contributor

hmmbob commented Dec 2, 2020

@marvin-w did some good work here. Anybody else who'd like to test his fixes? You can do so by using the changed files as custom_component.

@hmmbob
Copy link
Contributor

hmmbob commented Dec 2, 2020

Just a little information. If you are using Cloud Nabu Casa, you can change the service from tts.google_say to tts.cloud_say and it will work like this.

EDIT: That is also not a solution, because all my TTS automations was in the language of Hungarian, now it drops error: "Not supported language hu". Both Service have problems then :(

Nabu Casa does only support en-US, de-DE, and es-ES, as per https://www.nabucasa.com/config/tts/.

BUT.... there is a change inbound that will allow other languages to, including hu-HU.
See NabuCasa/hass-nabucasa#203

@colethegamer123
Copy link

Just as information, the changes will be implemented in 0.118.5? Thank you.

@hmmbob
Copy link
Contributor

hmmbob commented Dec 2, 2020 via email

@Mariusthvdb
Copy link
Contributor Author

Mariusthvdb commented Dec 2, 2020

Aww that is really too bad, having to wait more than 10 more days without notifications ..... seriously glad this got sorted (thanks!)
Would have hoped this to justify a patch though

@hmmbob
Copy link
Contributor

hmmbob commented Dec 2, 2020

You don't have to wait if you are comfortable enough to install a custom_component:

#43801 (comment)

@afraazali
Copy link

You don't have to wait if you are comfortable enough to install a custom_component:

#43801 (comment)

Did this and it worked! Will remove once the update is out. Thank you for the quick fix.

@colethegamer123
Copy link

Also working for me. Perfect solution. Thanks for your proactive hard work and also for the installation guide for the new ones.

@Mariusthvdb
Copy link
Contributor Author

You don't have to wait if you are comfortable enough to install a custom_component:

#43801 (comment)

thanks, great idea!
but... I did and this is what's returned:

Schermafbeelding 2020-12-02 om 23 13 09

@mauromognon
Copy link

You don't have to wait if you are comfortable enough to install a custom_component:

#43801 (comment)

it worked for me too, thanks a lot

@hmmbob
Copy link
Contributor

hmmbob commented Dec 2, 2020

You don't have to wait if you are comfortable enough to install a custom_component:
#43801 (comment)

thanks, great idea!
but... I did and this is what's returned:

Schermafbeelding 2020-12-02 om 23 13 09

Strange, because those are the exact two languages I tested it with.

What is your config? And what version of HA are you running? How do you trigger the TTS?

@Mariusthvdb
Copy link
Contributor Author

Mariusthvdb commented Dec 2, 2020

duh, thought had re-saved my files from the previous edit to tts.cloud_say back to tts.google_say again.

but I hadn't...

so sorry for the confusion.
back in business!
using:

  intercom_text_message:
    alias: Intercom text message
    mode: queued
    icon: mdi:text-to-speech
    sequence:
      - condition: state
        entity_id: input_boolean.announce_intercom
        state: 'on'
      - service: script.text_message_the_boss
        data:
          text_message: >
            {{states('input_select.intercom_message')}}
      - condition: template
        value_template: >
          {{states(states('sensor.intercom')) not in ['unknown','unavailable']}}
      - service: media_player.volume_set
        data:
          entity_id: >
            {{states('sensor.intercom')}}
          volume_level: >
            {{states('input_number.intercom_volume')|float}}
      - service: tts.google_say
        data:
          language: >
            {{states('input_select.intercom_language')|lower}}
          entity_id: >
            {{states('sensor.intercom')}}
          message: >
            {{states('input_select.intercom_message')}}

thanks so much

@muzzak123
Copy link

Will the 0.119 release also fix the same issue in the Node-Red Cast module I mentioned above ?

@frenck
Copy link
Member

frenck commented Dec 3, 2020

@muzzak123 You should ask that with the node-red cast module. This is Home Assistant, not Node-RED. The changes here do not apply, as both are written in completely different programming languages.

@muzzak123
Copy link

@frenck - I'm sorry I don't understand your comment above ? Aren't you also the sponsor for the Node Red plugin. That was the reason I mentioned it to you.

@hmmbob
Copy link
Contributor

hmmbob commented Dec 3, 2020

That could be true, but it is not linked to this issue as it is a completely other piece of software. Please create an issue at that code base.

@spider7611
Copy link

@marvin-w did some good work here. Anybody else who'd like to test his fixes? You can do so by using the changed files as custom_component.

Not working for me. :(
Download the 3 file and in the custom_components make google_translate folder and put the 3 files in. Restart HA and not working when I type something to my google home mini.

artwork: cover entity: media_player.google_home_mini hide: icon_state: false name: true power_state: false source: false volume: false icon: 'mdi:google-home' tts: entity_id: media_player.google_home_mini language: hu platform: google_translate service: tts.google_translate_say type: 'custom:mini-media-player'

@frenck
Copy link
Member

frenck commented Dec 3, 2020

@hmmbob
Copy link
Contributor

hmmbob commented Dec 3, 2020

@marvin-w did some good work here. Anybody else who'd like to test his fixes? You can do so by using the changed files as custom_component.

Not working for me. :(
Download the 3 file and in the custom_components make google_translate folder and put the 3 files in. Restart HA and not working when I type something to my google home mini.

artwork: cover entity: media_player.google_home_mini hide: icon_state: false name: true power_state: false source: false volume: false icon: 'mdi:google-home' tts: entity_id: media_player.google_home_mini language: hu platform: google_translate service: tts.google_translate_say type: 'custom:mini-media-player'

That use case ( type something in the media player TTS box) was tested too and worked. I just confirmed that it works here, locally, again. There might be something wrong with your setup. Did you download the raw files? How did you configure tts?

@spider7611
Copy link

spider7611 commented Dec 3, 2020

Before it was worked good with this setup:

`tts:

@hmmbob
Copy link
Contributor

hmmbob commented Dec 3, 2020

What does your log say?

@spider7611
Copy link

Nothing special:
2020-12-03 08:28:10 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for samsungtv_smart which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant. 2020-12-03 08:28:10 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for smartir which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant. 2020-12-03 08:28:10 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for favicon which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant. 2020-12-03 08:28:10 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for spotcast which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant. 2020-12-03 08:28:10 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant. 2020-12-03 08:28:10 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for browser_mod which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant. 2020-12-03 08:28:10 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for zigbee2mqtt_networkmap which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant. 2020-12-03 08:28:13 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for philips-airpurifier which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant.

@hmmbob
Copy link
Contributor

hmmbob commented Dec 3, 2020

I don't see the google translate custom component being loaded. Ensure you placed the files in custom_components/google_translate/ folder in your config. Ensure you used the correct version of the files (raw files from Github) and restart HA.

@Mariusthvdb
Copy link
Contributor Author

0.119, scheduled for 13 Dec. Op wo 2 dec. 2020 22:27 schreef colethegamer123 notifications@github.com:

btw, its going to be release version 1.0 !

@willysoft80
Copy link

I don't see the google translate custom component being loaded. Ensure you placed the files in custom_components/google_translate/ folder in your config. Ensure you used the correct version of the files (raw files from Github) and restart HA.

The files are gone...Error 404

@hmmbob
Copy link
Contributor

hmmbob commented Dec 3, 2020

Yeah, that's because it got merged. I'll update the link - try this one:

https://github.com/home-assistant/core/tree/dev/homeassistant/components/google_translate

@spider7611
Copy link

spider7611 commented Dec 3, 2020

googletranslet
Here is the 3 file restart HA and not working.

Here is the error in log: 2020-12-03 11:57:58 ERROR (SyncWorker_5) [homeassistant.loader] Error parsing manifest.json file at /config/custom_components/google_translate/manifest.json: Expecting value: line 7 column 1 (char 6)

Maybe not download the files properly? How to download RAW from there?

@willysoft80
Copy link

Yeah, that's because it got merged. I'll update the link - try this one:

https://github.com/home-assistant/core/tree/dev/homeassistant/components/google_translate

Thanks. It works

@hmmbob
Copy link
Contributor

hmmbob commented Dec 3, 2020

Maybe not download the files properly? How to download RAW from there?

Yeah, judging by file size and the error, you did not download the raw files. Go to the link i provided, click each file and hit the raw button (or right-click the raw button, "save link as")

image

@spider7611
Copy link

Perfect. That was the problem. Thank You!!

@SteveDinn
Copy link
Contributor

SteveDinn commented Dec 3, 2020

I know this Google TTS issue has been resolved, but in the spirit of getting off the cloud, had anyone thought about integrating mycroft's 'mimic' TTS utility?

https://mycroft-ai.gitbook.io/docs/mycroft-technologies/mimic-overview

@frenck
Copy link
Member

frenck commented Dec 3, 2020

Alright, this is all getting off-topic a bit. The issue has been fixed and merged to dev and currently in the beta as well. Thanks all 👍

@home-assistant home-assistant locked and limited conversation to collaborators Dec 3, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.