Alexa-remote-event <<< not working

General
1

I've been using alexa-remote-event from node-red-contrib-alexa-remote-fork to listen to responses from Alexa. It's been working fine for months but today it just seems to ignore the verbal responses.

Has anyone else encountered this??

Screen Shot 06-27-21 at 01.10 PM

Would it be worth swapping over to alexa-remote2-applestrudel as that seems a more recent release??

2

Just went to try mine and it's not picking up what I say but is speaking which is the complete reversal of its standard faulty mode :slight_smile:

From my logs, looks like it stopped outputting after Friday 21:00 UTC last night

I'm on a slightly patched original remote2

stop/restarting NR has made no diff

3

Thanks Simon for your feedback - as least it confirms I'm not going crazy!!!

4
1 Like
5

Hi Steff,
Thanks for the heads-up on that.
I hope it gets fixed soon as I'm working on creating a project using Alexa for my IoT students.

6

Really glad to know I'm not the only one experiencing this issue. I'll be following the thread on GitHub- thanks for flagging that!

7

applestrudel update is out

I'm having to update my node,js version as the main node Apollon77/alexa-remote doesn't support V10 anymore

8

Thanks Simon @cymplecy ,
I can report I've installed AppleStrudel and can (thankfully) capture verbal responses from Alexa again.

9

After update it "did" work a few times but seems broken again :pleading_face:

10

Still working for me here in the UK.

11

Just rebooted my pi4 and working again, will have to see how it goes :wink:

12

Fingers crossed for you.

13

looks like reboot broke influxdb, the joys of computing ..........

14

After 24 hours of fiddling around - finally got applestrudel installed (on its own without any legacy nodes getting installed/re-installed) and NR can now hear Alexa commands again :slight_smile:

Of course, now that I've got it listening again - I've got the old problem of it's not speaking to me :slight_smile:

15

Well - simple press of my initiliase inject and it's speaking to me :slight_smile:

but ... :slight_smile:

it seems like the message structure has changed

I start my processing using
image

and there is no payload.activity status object anymore in the message :frowning:

(This is with saying "Alexa, Simon says test")

image

So I'll need to investigate what I need to do

16

I've removed the if test and all seems OK :slight_smile:
image

17

I've managed to get my flow working again with the updated Alexa (applestrudel) node.

Screen Shot 10-12-21 at 11.40 AM
Screen Shot 10-12-21 at 11.40 AM1100Ă—162 16.5 KB

Here's what the code looks like in the function node 'Capture question'.

var device_name = msg.payload.name;
var summary = msg.payload.description.summary;

 if ((summary != "alexa") && (summary != "")) {
     
    msg.payload = {};

    msg = {
        topic: "Alexa_response",
        device_name: device_name,
        payload: {
            "summary": summary
        }
}
    node.status({text:"Device_name is "+ device_name + " Summary = " + summary});
    return msg;
}
else {
    return null;
}
18

Yep - I do the same
image

19

12 posts were split to a new topic: Trouble getting started with Alexa-remote

20

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