Cloud_say volume not working

Configuration
1

hello,
Am using cloud.say and do some TTS to my amazon tablets.

service: tts.cloud_say
data:
  entity_id: media_player.e573a061_4437bb43
  message: Central heat has been switched off automatically.

It does work.
Then I tried to adjust the volume, because when it runs sometimes it is too late and volume is too loud.

data:
  volume_level: 0.1
service: media_player.volume_set
target:
  entity_id:
    - media_player.e573a061_4437bb43

The service runs and I can double check from entities state that the volume attribute has been adjusted accordingly. Here is a screenshot for your reference.

εικόνα
εικόνα1229×555 27.2 KB

My problem is that if the TTS replays the volume is still 100%.
It seems that it doesn’t consider the volume which has been set to 10%

Anyone had the same problem please? Have you found a solution ?

2

One potential solution to this problem would be to use the media_player.volume_set service in the same automation that is used to trigger the tts.cloud_say service. This way, the volume level can be set before the message is played, ensuring that the correct volume is used.

3

I confirmed with you that is been used to the same automation. Like the following

 - ...... 
 - data:
      volume_level: 0.4
    service: media_player.volume_set
    target:
      entity_id:
        - media_player.e573a061_4437bb43
  - service: tts.cloud_say
    data:
      entity_id: media_player.e573a061_4437bb43
      message: Η κεντρική θέρμανση έσβησε αυτόματα.
      language: el-GR
    alias: Μήνυμα στα Ελληνικά στο tablet της Σοφίτας

I first adjust volume level and then at the next action I use cloud.say.
It seems that the volume level (which has been adjusted) is not considered and cloud.say TTS plays at 100% volume.

4

Please put a delay between the action of setting the volume and sending the message. This will allow time to correctly set volume before executing the send of the message string.

5

thank you for your reply.
I tried that too. It doesn’t make any difference.

Volume set to 1 (100%) or 0.1 (10%) sounds the same …

6

Please share your tts.cloud_say script, this will help establish if there are any inconsistencies in the variables used.

Within your tts.cloud_say script sequence, the data passed should look like this:

- service: media_player.volume_set
      data_template:
        entity_id: "{{ sonos_entity }}"
        volume_level: "{{ volume }}"

Where the value in the entity_id & volume_level defined variable(s). i.e. sonos_entity & volume, should be the same naming as the data you are passing.

7

Here it is. The exact script I am using which doesn’t conside sound adjustment

alias: test volume
description: ""
trigger:
  - platform: time
    at: "23:00:00"
condition: []
action:
  - data:
      volume_level: 0.1
    service: media_player.volume_set
    target:
      entity_id:
        - media_player.e573a061_4437bb43
  - delay:
      hours: 0
      minutes: 0
      seconds: 10
      milliseconds: 0
  - service: tts.cloud_say
    data:
      entity_id: media_player.e573a061_4437bb43
      message: The central heat has been switched off automatically.
      language: el-GR
mode: single
8

Hi! Did you figure out the problem? I am facing the same problem with my Google Nest Minis. Everything with tts.cloud_say is 100%.
Did you find a solution?

9

I don’t know exactly why, but at least I know the cause now. The Google Home Resume Script seems to be the cause of the problems. I deactivated automation.00_google_home_automatic_resume. I guess something will not work with that script anymore, but so far it seems to be still working and the volume works!