# How to set up an alexa voice command correctly in nodered

**URL:** <https://discourse.nodered.org/t/how-to-set-up-an-alexa-voice-command-correctly-in-nodered/79789>\
**Category:** General\
**Tags:** node-red-contrib-alexa-remote2-applestrudel\
**Created:** [13 July 2023 12:35 UTC](https://discourse.nodered.org/t/how-to-set-up-an-alexa-voice-command-correctly-in-nodered/79789 "2023-07-13T12:35:54Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![franz](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/franz/32/71949_2.png) [@franz](https://discourse.nodered.org/u/franz)\
**Post date:** [13 July 2023 12:35 UTC](https://discourse.nodered.org/t/how-to-set-up-an-alexa-voice-command-correctly-in-nodered/79789/1 "2023-07-13T12:35:54Z")

</div>

- I use the node-red-contrib-alexa-remote2-applestrudel in nodered.

- I can get an external thermometer to read the temperature via the voice command "alexa external thermometer" but lately alexa responds with a description of the mercury thermometer interrupts them amid and then responds with the correct temperature values.

- When writing the nodered stream and after a few months of operation it has always responded correctly; only ultimante presents the problem.

- I would like to know if it happens to you and how you solved the 'anomaly.

---

<div class="post-metadata">

**Author:** ![DiverRich](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/diverrich/32/64523_2.png) [@DiverRich](https://discourse.nodered.org/u/DiverRich)\
**Post date:** [13 July 2023 17:12 UTC](https://discourse.nodered.org/t/how-to-set-up-an-alexa-voice-command-correctly-in-nodered/79789/2 "2023-07-13T17:12:08Z")

</div>

I can't say for sure what's causing your specific problem, but for quite a while I had several detailed flows to control Alexa with voice commands. In my case, I was able to turn on/off devices/lights at specific times with voice commands. But when they added that option to Alexa natively it completely broke many of my Alexa based flows. I'm still experimenting with how to make everything work like it used to.

---

<div class="post-metadata">

**Author:** ![Sean-McG](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/sean-mcg/32/54677_2.png) [@Sean-McG](https://discourse.nodered.org/u/Sean-McG)\
**Post date:** [14 July 2023 00:18 UTC](https://discourse.nodered.org/t/how-to-set-up-an-alexa-voice-command-correctly-in-nodered/79789/3 "2023-07-14T00:18:25Z")

</div>

> [@franz](#):
>
> "alexa external thermometer"

Your command is very terse, in these cases I find it helps to be more verbose

Does it work if you say "alexa what is the external thermometer temperature"

---

<div class="post-metadata">

**Author:** ![franz](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/franz/32/71949_2.png) [@franz](https://discourse.nodered.org/u/franz)\
**Post date:** [14 July 2023 05:45 UTC](https://discourse.nodered.org/t/how-to-set-up-an-alexa-voice-command-correctly-in-nodered/79789/4 "2023-07-14T05:45:59Z")

</div>

I had already tried, but it still continues with the stupid thermometer explanations , do you know if there is a command to disable the explanations of the terms that alexa listens to?

---

<div class="post-metadata">

**Author:** ![Sean-McG](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/sean-mcg/32/54677_2.png) [@Sean-McG](https://discourse.nodered.org/u/Sean-McG)\
**Post date:** [14 July 2023 14:58 UTC](https://discourse.nodered.org/t/how-to-set-up-an-alexa-voice-command-correctly-in-nodered/79789/5 "2023-07-14T14:58:25Z")

</div>

From your description it seems like an Amazon issue rather than the node.

A couple of things to try

Change the name of the device to something more unique. eg garden  
"alexa what is the garden temperature"

If you have no luck with that you could setup a Q&A "skill"

---

<div class="post-metadata">

**Author:** ![dynamicdave](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dynamicdave/32/96_2.png) [@dynamicdave](https://discourse.nodered.org/u/dynamicdave)\
**Post date:** [14 July 2023 15:24 UTC](https://discourse.nodered.org/t/how-to-set-up-an-alexa-voice-command-correctly-in-nodered/79789/6 "2023-07-14T15:24:24Z")

</div>

As @Sean-McG suggested, the Q&A Skill in Blueprints might be helpful. Here's a link to a thread.

> [@Pure fun with Alexa and Alexa Skills](https://discourse.nodered.org/t/pure-fun-with-alexa-and-alexa-skills/46867):
>
> Now the authentication problem with various Alexa nodes has been sorted I thought I'd try something new. I used [BluePrints](https://blueprints.amazon.co.uk/home) to create a Q&A skill called 'Give me a status report' then linked that in the flow below. I've arranged for various devices around my home to report their status to a database that is accessed from the flow and sent to the appropriate Alexa device. Here's an example of capturing feedback from Sonoff-S20 switches and writing the status to a dB.

Last week I connected a SonOff S26 mains switch to power my colour laser.  
As shown below I can utter various commands and ask for a status report.

 ![a_laser_A](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/7/0/705eac31c56353706ff98d31edbce4b88a2ebff7.png)  
 ![a_laser_B](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/e/6/e61d8e9392d51bd47dd87827db87df51f0edc9c1.png)

---

<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:** [12 September 2023 15:25 UTC](https://discourse.nodered.org/t/how-to-set-up-an-alexa-voice-command-correctly-in-nodered/79789/7 "2023-09-12T15:25:09Z")

</div>

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