# TTS with Denon Receiver

**URL:** <https://discourse.nodered.org/t/tts-with-denon-receiver/54174>\
**Category:** Share Your Projects\
**Created:** [23 November 2021 18:49 UTC](https://discourse.nodered.org/t/tts-with-denon-receiver/54174 "2021-11-23T18:49:20Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![donniev](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/donniev/32/51475_2.png) [@donniev](https://discourse.nodered.org/u/donniev)\
**Post date:** [23 November 2021 18:49 UTC](https://discourse.nodered.org/t/tts-with-denon-receiver/54174/1 "2021-11-23T18:49:20Z")

</div>

I struggled getting TTS to work with my Denon receiver and I thought I would post a few tips here in hopes of saving others a bit of time;

1. Play\_media loads a resource and plays it BUT ALSO adds it to the queue (playlist). This leads to strange behavior on subsequent messages. The new message is played and then the queue starts playing. I have no idea why this happens.

2. The solution is to call the clear\_playlist service before issuing another command.

3. I only need a few sound bites they are static. Rather than call Amazon Polly repeatedly I have saved the responses in mp3 files and now use those files.

4. The easiest way to access them is put them in a folder under www in your ha installation.

5. I use this in my service call to play\_media (data):

```auto
{

"media_content_id": "https://ha.vawter.com/local/music/{{payload}}.mp3",
"media_content_type": "music"
}

```

There would normally be a port number but I am reverse proxying with nginX which handles the SSL and forwards to 1823 on the VM running HA.

I hope this saves someone a few cycles.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [22 January 2022 18:49 UTC](https://discourse.nodered.org/t/tts-with-denon-receiver/54174/2 "2022-01-22T18:49:27Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.