[Deprecated] Amazon Alexa Text to Speech (TTS) v0.6.2 - Direct Integration (USA, Canada, UK, Italy, Australia, & Brazil)

So I've enabled Alexa, and it appears to be working.

I want notifications when a door opens. Is there no way to just send a chirp sound instead of text-to-speech? I no this sounds silly, but I want to just send a chime.

How about sending via TTS the word "chirp" ? :wink:

I do not know of a way to make the Alexa devices 'chirp'.

You could use Pushover to receive a notification with a specific sound on a particular iOS or Android device whenever a door is opened.

3 Likes

You would have to use Echo Speaks for that as you can search for audio files on various services. Alexa TTS is strictly text to speech.

The other option is to use either Sonos or some other sort of DLNA/media player.

LMAO

1 Like

Okay thanks

LMAO.... Dan that deserves a 100 kudos !

Greetings to all:
I am new kid in the block and have trying to install App and Driver as instructed. All done well as expected, but I do not hear any thing when testing with speak button in the device page. Any advise? Do I need to install Amazon Echo App and Amazon Echo Skill? I am using Echo dot. Thanks

What country are you in? If you want to use the native Hubitat Integration with Alexa, the best method is to start from within the Alexa App on your phone. Add the Hubitat Skill from within the Alexa App if your country is supported. During the installation, you'll be prompted for your Hubitat Portal credentials. Once you select your hub, the Amazon Echo Skill will be automatically installed on your Hubitat hub.

The older Amazon Echo App should only be used in countries that the Alexa Skill has not yet been published.

As for the Alexa TTS Manager, it does not require either of the official Amazon integrations in order to work. However, your country is pretty important as the current App/Driver is only supported in a few countries currently. If you were able to have the Alexa TTS Manager App automatically discover and create the child devices for each of your Echo/Dot/Spot/Show devices, the TTS should work. Make sure the volume on your Amazon device is turned up/not muted, and type a simple phrase into the child device's Speak command, and then click the SPEAK button.

Thanks Dan for quick replying. I am in NC, USA. Two child devices were created for my two echo dots. I turned the volume high and just put single word "testing"; nothing happen after clicking Speak button. I will try again, if not I will update you tomorrow.
Regards
Tito

How about in the Live Logs? Any clues there as to what might be going on? You didn't invalidate the cookie by signing out of the browser session?

Dan:
Please see the live logs at below. I did not sign-out the session. I think, there might communication issue between HE and cloud. I am planning to reinstall the complete process.

Regards
Tito

Are you only showing the Child Device Live Logs? How about the Parent Alexa TTS Manager App's Live Logs?

1 Like

Good Morning
Dan:
The first log is from Child and the next one from parent.

Parent's Live log

Please advise.

Thanks
Regards
Tito

I really don't have any idea what could be wrong. If any of the web calls to the Alexa web site were failing, we'd see Error messages in the Live Logs. My Alexa devices are still speaking properly.

Thanks Dan for your review. I will reinstall all and update you as soon I return from my trip to Toronto this weekend. Thanks again. Regards, Tito

Good Afternoon

Dan:
I got them working!!!! It was a big lesson learn.

While I was with ST, I had installed Echoassistant that also mapped to these two Echo devices. So, I removed all the apps related to Echoassistant and disconnected these echo devices from these Apps and de registered - registered the echo devices again with new names. Now, they are working. Thanks for your help. Regards, Tito

2 Likes

I’m having issues. Logs are telling me my cookie has expire.... I relogged in and it says it updated the cookie but logs are saying different.

Isn’t it supposed to be auto refreshing the cookie ?

The auto refresh for the cookie requires you to run a separate NodeJS server on your network. Have you completed that configuration? I did not write that portion, so you might need help from @gabriele if you're having issues with that section of the code.

All,

I had some time off work so I implemented set/get volume controls. I have branched, updated and submitted a pull request to @ogiewon's github repository. In the meantime, you can take a look at GITHUB Repository

Cheers.

This is a great enhancement! Thank you. I have accepted your pull request, and I made some minor tweaks to the Child Alexa TTS driver. Nothing significant, just added an importURL to make it simpler to keep the code up to date, and I added the Refresh Capability which simply calls your new "getVolume" command. This will allow users to use Rule Machine to "Refresh" the volume without need for a custom command.

I have tested both the updated App and Driver. The setVolume works great. However I cannot seem to make the getVolume work. I keep getting the following errors:

app:2942019-04-04 09:32:50.671 pm error'getVolume()': Error making Call (getMessage): Bad Request
app:2942019-04-04 09:32:50.670 pm error'getVolume()': Error making Call (Status): 400
app:2942019-04-04 09:32:50.669 pm error'getVolume()': Error making Call (Data): [message:null]
app:2942019-04-04 09:32:50.259 pm debugParams: [uri:https://alexa.amazon.com/api/np/player?...

Any idea what is going on? It appears that the version of the App in the PR does not send a 'body' for the getVolume command??? That seems a little odd. Also, even if a valid response was returned, the code doesn't appear to do anything with it except perform a log.debug. This data would need to be sent back to the child to update its attributes.

@thomas.c.howard - It appears that today, the setVolume feature is no longer working for me. I am getting the following response...

[app:294](http://192.168.1.143/logs#app294)2019-04-05 05:55:51.234 pm [error](http://192.168.1.143/installedapp/configure/294)'setVolume()': Error making Call (getMessage): Not Found

[app:294](http://192.168.1.143/logs#app294)2019-04-05 05:55:51.232 pm [error](http://192.168.1.143/installedapp/configure/294)'setVolume()': Error making Call (Status): 404

[app:294](http://192.168.1.143/logs#app294)2019-04-05 05:55:51.229 pm [error](http://192.168.1.143/installedapp/configure/294)'setVolume()': Error making Call (Data): {"message":"No routes found","userFacingMessage":null}

Is it still working for you? I'm not sure what has changed since last night.