search

bbindreiter / node-red-contrib-alexa-remote2-applestrudel

Node-Red Nodes for interacting with Alexa
https://flows.nodered.org/node/node-red-contrib-alexa-remote2-applestrudel
MIT License
74 stars 20 forks source link

Events not firing again 12Oct #152

Closed cymplecy closed 3 months ago

cymplecy commented 8 months ago

Several of us on the Node-RED forum have noticed that events are not being received From my own logs - this started after 14:33 GMT

Stopping/starting NR doesn't make it work again :(

DanPatten commented 8 months ago

Can confirm my events are becoming spotty again

Martin-OHV commented 8 months ago

Same here again :-(

GianZambo commented 8 months ago

Same here

brunialti commented 8 months ago

+1

gattokotatsu commented 8 months ago

Same here, sorry.

msp1974 commented 8 months ago

Same here in UK

s1nbad commented 8 months ago

same here - Thailand

Matten-Matten commented 8 months ago

hey all,

already tested "reset" -> "Fresh Authentication" -> Proxy login via "open ... in your Browser"?

That worked for me

greeting matten matten

cymplecy commented 8 months ago

That didn't work for me

Are you sure you are able to listen to events?

On Sat, 14 Oct 2023 at 08:52, Matten-Matten @.***> wrote:

hey all,

already tested "reset" -> "Fresh Authentication" -> Proxy login via "open ... in your Browser"?

That worked for me gruß matten matten

— Reply to this email directly, view it on GitHub https://github.com/bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/152#issuecomment-1762705209, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAR7RNC2AWMJTIAP4CZB7BDX7JADNANCNFSM6AAAAAA56DZ3JY . You are receiving this because you authored the thread.Message ID: <bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/152/1762705209 @github.com>

Martin-OHV commented 8 months ago

Reset / Fresh Auth wont work here as well (Germany)

GianZambo commented 8 months ago

Not work for me (Italy)

Matten-Matten commented 8 months ago

@cymplecy

sorry, I got confused.

Alexa states arrive,

but no device activity

Tinbum1 commented 8 months ago

Same here- UK.

rodrigofragadf commented 8 months ago

Same here in Brazil

obaldius commented 8 months ago

same here Spain

Varguit commented 8 months ago

Same here in Catalonia

f0rc3r commented 8 months ago

+1 Germany

obaldius commented 8 months ago

will this be left like this??? won't events ever work again?

bbindreiter commented 8 months ago

I will probably remove the event node. People are building their home automation based on it and then we have issues like this one, where all weight is on one man's shoulders

obaldius commented 8 months ago

I hope you don't do that, it's really useful. If it fails every now and then it's ok, it's way worse to remove it....

obaldius commented 8 months ago

TBH with you the event node was quite a mess when cakebaked was the owner. It would fail every other month and it was still valuable to have it.

Ever since you took it over it's been almost rock solid, like night and day different. I really hope you can find the heart to keep on with this and keep the event node alive.

I'm really thankful for everything you've done during this last couple of years.

Kind regards

bbindreiter commented 8 months ago

It's all @Apollon77, I'm just integrating his lib but thank you very much. I would happily keep this event node but some users rely on it apparently. I just want to avoid a situation where someone locks themselves out or something.

Apollon77 commented 8 months ago

I have some ideas to at least workaround a bit. Will potentially not that perfect as before. We will see. Needs some days ... not at home currently that often so no Alexa test devices with me.

Martin-OHV commented 8 months ago

It's all @Apollon77, I'm just integrating his lib but thank you very much. I would happily keep this event node but some users rely on it apparently. I just want to avoid a situation where someone locks themselves out or something.

Please dont remove this functionality! True - some people use this to build their smart home on it (like me) but it is currently the only way how i can use voice control to my smarthome. if you remove it, i dont have any possibility to use voice control... so better havent it some times than havent it any time :-)

Is there anything we can do to support you please let us now. And no worrys if fixing issues can not be done just in time - i think, no one of us here will expect this.

Unfortunatly i am not an js coder, but if i can assist with testing or anything else let me know.

Stay motivated - we count on you 2 (@bbindreiter and @Apollon77 )

Ans many many thanks for your tireless effort

Martin (Berlin)

niwre2019 commented 8 months ago

I can only agree, it would be a real pity if this functionality would no longer exist.

gattokotatsu commented 8 months ago

Is there a document or some blog post or other resources that explain what changes in the behaviour of the alexa system that brakes the alexa-remote functionality? And since it's (correct me if I'm wrong) a "virtual" echo device, how those kind of devices still work after these changes occour? Sorry for the curiosity.

aferrato commented 8 months ago

First of all, thank you to those who contribute to the project! I agree as well, it would be very useful to be able to preserve the 'events' node. I used it to manage Alexa lists and synchronize them with other services. I noticed that the app receives real-time updates for adding or removing products. Maybe there's a workaround for managing the lists?

Apollon77 commented 8 months ago

@gattokotatsu Because these are all inofficial "Alexa App and internal API" related topics ... indeed no there is nothing oficially available :-) In fact they do not send a push information anymore they were sending before. any the functionality relied in this information. So we now need to find things around this.

sicampbell82 commented 8 months ago

I too am eagerly watching and hoping for this to be fixed. its a lazy use of it but i and my family plus kids am so used to walking into any room and saying tv on or light on and as this function states what device the request comes from it means node red/ha know that its the the tv in room x. 1st word issues but i just don't want to start saying, living room tv on or bedroom tv on, if i don't have too.

thanks so much for your work so far. if anyone else know how to pass this data then i would be very please to know.

I don't even need to know the words that are spoken, if i say to Alexa "tv on" i can let Alexa handle the voice as i do now and replies "ok"

but other than that Alexa doesn't do anything.

At the moment i just listen for what Alexa asks to decode and send that into node red along with the name of that Alexa

from there i trigger nod red commands but i send it to the room name of said Alexa command so bedroom tv for example.

I assume many of you are doing the same, but i was thinking since we all coming her for same answer someone, or one of the amazing dev's fixing this, my have or come up with a solution so if we can't listen to the words said anymore in order to get the name of the device sending the command, is there a way to do a different action and grab the name?

If i set Alexa to toggle on and off an Alexa routine/dummy light/switch does anyone know of any way to find out what device did the action?

obaldius commented 8 months ago

it would definetely be a huge loss....

DanPatten commented 8 months ago

I have a temporary fix for you based on the fact that getting customer history records still works in alexa-remote2

  1. Setup node-red-contrib-amazon-echo
  2. Add a node and setup a routine with whatever to trigger that node
  3. Now make changes to node-red-contrib-alexa-remote2-applestrudel as outlined here
  4. Now add an Alexa Other Node -> Activities and now you have the latest activity that you can trigger from your virtual device created by node-red-contrib-amazon-echo

Example flow: https://pastebin.com/raw/XsghGwt7

To add routine in Alexa App:

1.Add when with your phrase(s) like "How much did it rain last night"

  1. Add WILL -> Smart Home -> Light -> Select your device you added above, mine is called "Test Device" -> Turn ON
  2. (optional) Add another routine -> Device Settings -> Stop Audio -> Associated Device (This allows for custom responses that you control)
  3. Save routine
cymplecy commented 8 months ago

@DanPatten Works for me :)

I use a different node for my virtual devices node-red-contrib-home-skill (maintained by Ben Hardill - an NR expert and part of the FlowFuse team) and it works with it.

If we are lucky, it will work with any choice of virtual devices

Here's a screenshot of my generic virtual "Lights" device connected to the Get activites and the name of the device that I spoke to ends up in payload[0].name image

So this way, I can carry on just saying Lights on/off in a room and then have NR sort out which real devices need switching on/off

cymplecy commented 8 months ago

@GianZambo Can you post your problem on the Node-RED forum in order to keep this thread for the applestrudel problems please :)

https://discourse.nodered.org

GianZambo commented 8 months ago

Ok, and thank you for help ... :)

bbindreiter commented 8 months ago

5.0.44 released with @DanPatten 's fix. Thank you!

spants commented 8 months ago

Maybe my use case is slightly different: 1) I can say "Alexa, water temperature" or "Alexa, rubbish collection" 2) The event used to fire and I save the device name in a global/flow variable. 3) The msg.payload.description.summary is checked for my phrases above and a switch node directs it to a flow of routines 4) The Alexa answers to the devicename stored above

would I have to use a phrase like "Alexa, turn water temperature on" or "alexa, turn rubbish collection on" to do it now?

nrscreen

Apollon77 commented 8 months ago

Yes, two different topic. The event will be fixed hopefully later today. I'm in final testing of an solution.

lucasschvantes commented 8 months ago

Hi

debug_alexa_event

Sorry for my ignorance,

I installed this plugin a week ago, so I wasn't able to use it when it was working.

I can carry out all the other procedures, including the "Hello World", except for the Device Activity. I saw in a video that this debug would show which echo was called, and then I could use that information.

Am I wrong? Besides configuring the node, is there any other dependency I need to install?

Node-RED Current version: 14.6.3

node-red-contrib-alexa-remote2-applestrudel 5.0.44

Home Assistant 2023.10.5 Supervisor 2023.10.1 Operating System 11.1 Frontend: 20231005.0 - latest

cymplecy commented 8 months ago

The node is currently broken This place is to to talk about the technical issues Please post general questions on the HA forum

lucasschvantes commented 8 months ago

Sorry for my question,

As bbindreiter mentioned it was fixed, I thought it was okay, but if it's broken, I'll wait.

Apollon77 commented 8 months ago

seee https://github.com/bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/152#issuecomment-1783017587 ... he mixed things ...

bbindreiter commented 8 months ago

Thanks! https://github.com/bbindreiter/node-red-contrib-alexa-remote2-applestrudel/releases/tag/5.0.45

Apollon77 commented 8 months ago

Ok guys, one note to 5.0.45: It should bring back the activity event like before ... I added some workarounds that try to detect activities also without the proper events.

Please make sure to DISABLE all manual activity/history triggering you added as woraround yourself

I hope it works.

Ingo

PS: Donations always welcome ;-))

f0rc3r commented 8 months ago

Thanks

Tinbum1 commented 8 months ago

Thank you for the Fix. :)

rodrigofragadf commented 8 months ago

Thank you very much for the fix!

Apollon77 commented 8 months ago

@Martin-OHV And thank you very much for your support!!

obaldius commented 8 months ago

@Apollon77 @bbindreiter you are the best. I know I know, @Apollon77 does pretty much everything and blah blah... you both are the best!

pkkrusty commented 8 months ago

I am getting responses again with latest push, but JSON response payload.description.summary used to give the transcribed audio (i.e. what I said, which i would parse to trigger responses) now gives a blank field.

I guess a workaround would be to make a routine for each thing with a custom response from Alexa (which is included in the JSON under payload.alexaResponse)

p.s. Thank you for the work on this solution.

Apollon77 commented 8 months ago

I currently prepare another optimization update that then needs to be picked up into a new node version ... With short interactions and "bad timing" it can be in the current version that some texts are not correctly delivered. this should be fixed in next version. maybe then it is better