VoiceRSS seams to be broken?

Configuration
1

I’m testing out the new stuff, Google TTS is working but VoiceRSS isn’t.
I’m using the same code, I have setup an API code and I have tested it manually and it works, but running it through HA returns a “mp3”-file containing the following text: ERROR: The text is not specified!

Looking on GitHub I can see a fix for VoiceRSS has been checked in to 0.35.3, so this might already be fixed but just in case I’m doing something wrong or anyone else is having the same issue I’ll post a thread about it.

1 Like
2

Don’t seam to be fixed still…

3

I took mine out because of the issue and was waiting on the pending merge. I’ll try it again after I eat (missed lunch) and let you know if it’s working for me.

4

Got it working now, it’s using a non supported forma for Sonos as default.
So it has actually been fixed in 0.35.3 but to use it with sonos the format needs to be set manually.

tts:
  - platform: voicerss
    api_key: '******************************'
    language: 'en-gb'
    format: '44khz_16bit_stereo'
5

But why don’t this work?

test:
  alias: "Test VoiceRSS Template"
  sequence:
    service: tts.voicerss_say
    entity_id: media_player.office
    data_template:
      message: 'Temperature is {{ sensor.netatmo_outdoor_temperature }}.'
      cache: false
6

Example in docs is wrong and misleading - I had the same issue. Should be:

message: 'Temperature is {{ states.sensor.netatmo_outdoor_temperature.state }}.'

Otherwise you get the error, “‘sensor’ is undefined”

7

Awesome stuff @rpitera that works perfect, thank you!

1 Like
8

Cool, glad I could help. I’m going to have to try setting it up again as I like the UK voice accent and I think VoiceRSS sounded better than Google’s version.

I don’t know why, but on any TTS like my phone, I always set it to either UK or Aussie English. Something about the accent sounds right to me…