# Alternative suggestion for Alexa alexa-remote2 issues

**URL:** <https://discourse.nodered.org/t/alternative-suggestion-for-alexa-alexa-remote2-issues/82092>\
**Category:** General\
**Created:** [16 October 2023 20:07 UTC](https://discourse.nodered.org/t/alternative-suggestion-for-alexa-alexa-remote2-issues/82092 "2023-10-16T20:07:14Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![cymplecy](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/cymplecy/32/2773_2.png) [@cymplecy](https://discourse.nodered.org/u/cymplecy)\
**Post date:** [16 October 2023 20:07 UTC](https://discourse.nodered.org/t/alternative-suggestion-for-alexa-alexa-remote2-issues/82092/1 "2023-10-16T20:07:14Z")

</div>

Just to say, that when I started off with Alexa and Node-RED, I used (and still do) @hardillb node-red-contrib-home-skill  
[https://alexa-node-red.bm.hardill.me.uk/docs](https://alexa-node-red.bm.hardill.me.uk/docs)

When remote2 came along - it was a more flexible and I then used it for new routines

But since the remote2 device activity issues have become more prevalent, I've invested a bit more time with Ben's solution (which has been rock-sold for a long time)

There are of course, many ways to interface with Alexa (Blueprint skills for instance) but Ben's solution is an easy way of interfacing to Alexa - I find Blueprint skills a bit more of a faff personally

---

<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:** [17 October 2023 00:58 UTC](https://discourse.nodered.org/t/alternative-suggestion-for-alexa-alexa-remote2-issues/82092/2 "2023-10-17T00:58:15Z")

</div>

Shush we don't want everyone using it 😉

Unfortunately it doesn't offer the device activity, nor the name of the device that triggers the message.

---

<div class="post-metadata">

**Author:** ![ghayne](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ghayne/32/39_2.png) [@ghayne](https://discourse.nodered.org/u/ghayne)\
**Post date:** [17 October 2023 16:14 UTC](https://discourse.nodered.org/t/alternative-suggestion-for-alexa-alexa-remote2-issues/82092/3 "2023-10-17T16:14:09Z")

</div>

> [@cymplecy](#):
>
> Ben's solution (which has been rock-sold for a long time)

I've been using it since "Then". As you say, rock solid.

---

<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:** [16 December 2023 16:14 UTC](https://discourse.nodered.org/t/alternative-suggestion-for-alexa-alexa-remote2-issues/82092/4 "2023-12-16T16:14:49Z")

</div>

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