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
75 stars 20 forks source link

Alexa events no longer firing #138

Closed dshmaui closed 5 months ago

dshmaui commented 1 year ago

I'm unsure what happened, but I'm using this node-red integration for my home assistant setup. It was working earlier this morning, but now the Alexa events are no longer firing, even though I haven't changed anything. I tried reloading the Alexa login, restarting node-red, and restarting home assistant, but none of that seemed to work. I'm on the latest version of the node. Any advice or fixes would be greatly appreciated. Thanks!

Edit: The whole node isn't broken, sending commands to Alexa still works, the node just won't fire events from Alexa

mm20102010 commented 1 year ago

Same here, Brazilian account

smcgann99 commented 1 year ago

@Apollon77 @bbindreiter - It seems that after the Alexa account node is initialised the activity stops working again...

Apollon77 commented 1 year ago

Any debug log available?

khaue commented 1 year ago

I am experiencing the same problem on device listening activity. Where can I find the detailed log? In node red log I did not see any usefull information

claudiopj commented 1 year ago

I am experiencing the same problem

josue1988 commented 1 year ago

En españa, igual..

khaue commented 1 year ago

@bbindreiter Check the logs - if your push connection is "reconnecting" all the time then you got a block on amazon side. In fact you can only fix that by killing all infos including device ids and such and do a complete new cookie process as "new device".

What do you mean with killing ALL infos including device ids? The applestrudel nodes?

sreevo commented 1 year ago

es geht nicht mehr :(

Apollon77 commented 1 year ago

We are one it but it will need some days ... switching to Wireshark ... yeeaayyy

bbindreiter commented 1 year ago

Thanks @Apollon77

lbreggi commented 1 year ago

thanks a lot @Apollon77 - do you need any log or something else? thanks again!

niwre2019 commented 1 year ago

Many Thanks @Apollon77

Apollon77 commented 1 year ago

If someone had experience in sniffing network traffic from mobile apps with wireshark incl tls decrypting .... that would help ;-)

Babelbernd commented 1 year ago

I could provide a Teams Session for my Android Phone and Windows Computer

Apollon77 commented 1 year ago

I could provide a Teams Session for my Android Phone and Windows Computer

Means you can sniff all traffic already incl. TLS decyption ? if yes then lets find another place (Whatsapp, Discord, telegram) to chat and sync ... write me an email iobroker@fischer-ka.de

gledsonrabelo commented 1 year ago

Stopped working again for me too. Brazilian account.

brunialti commented 1 year ago

May it be usefull, I have the same problem (node is showing listening status but it does'nt send any message from Alexa). Looking forward to Apollon news. Thank you!

josue1988 commented 1 year ago

image

While you cannot use the routine services (summary, response, etc.) I cannot spend so much time at home without using the Alexa speakers for my routines, I depend a lot on the speakers.

So in the meantime, I have to do a momentary "patch", with alexa home as a trigger...

To give some ideas while you solve the problem... after this, I will deactivate the alexa home node, with the "device" light Routines, I really only use it to obtain the values from 1 to 100%, and in the mobile app, do a Routine, for example:

Turn on light bulb 1 Device > Routines > 1%

josue1988 commented 1 year ago

image

I really like using Routine better, it's more powerful.

I couldn't get voice user to work... that would be great

Apollon77 commented 1 year ago

As short update ... Seems we discovered anything and building it right now ... expect an update for friday. BUT we will require node.js 16+ (!!) So maybe already prepare your systems if not already on such a version.

andesse commented 1 year ago

Not one we can buy of the shelf, at least I am not aware. And it makes sense because cloud gives them control and more revenue.

I have seen some DIY projects that run on Raspberries, e.g. Rhasspy. Also some development on HA.

The suggestion from #138 (comment) to use a fake light bulb device and set up some routines that set the brightness (0-100) is not bad. I use it myself (a little different). You can then can map the values to a command of your choice.

So for instance define a routine "Close Garage door" that actually sets the brightness of the fake lightbulb to 0, and "Open Garage door" sets it to 1. This change you can pick up in node-red and act on it.

https://flows.nodered.org/node/node-red-contrib-amazon-echo-theukshadow

This contrib is so good! Thanks for the recommendation. I use this to get everything into Node-RED and applestrudel for response. Can’t believe that node-red-contrib-amazon-echo-theukshadow works local without a cloud dependency, what a good find! Thanks

claudiopj commented 1 year ago

As short update ... Seems we discovered anything and building it right now ... expect an update for friday. BUT we will require node.js 16+ (!!) So maybe already prepare your systems if not already on such a version.

hi, what time will you release the new version?

Apollon77 commented 1 year ago

hi, what time will you release the new version?

I'm in communication with @bbindreiter ... stay tuned ... it comes when it comes

If it works and you like my work ... I'm happy for any Donations: https://github.com/sponsors/Apollon77 / https://paypal.me/Apollon77

bbindreiter commented 1 year ago

I have just released 5.0.40, which should, thanks to Apollon77, make push events working again.

You'll need NodeJS 16 installed and please make sure that Events is set to "On" in your node red alexa account settings.

Thank you!

claudiopj commented 1 year ago

I have just released 5.0.40, which should, thanks to Apollon77, make push events working again.

You'll need NodeJS 16 installed and please make sure that Events is set to "On" in your node red alexa account settings.

Thank you!

NodeJS 16 installed in home assistant? Sorry i'm new...

mm20102010 commented 1 year ago

everything is working again, including "on audio player state change"

claudiopj commented 1 year ago

"on audio player state change"

still not working for me... :(

raceconditions commented 1 year ago

I have just released 5.0.40, which should, thanks to Apollon77, make push events working again. You'll need NodeJS 16 installed and please make sure that Events is set to "On" in your node red alexa account settings. Thank you!

NodeJS 16 installed in home assistant? Sorry i'm new...

You guys rock! Quick question, do you mean >=16 or ==16? Trying the v16 LTS scripts are screaming about deprecation (maintenance ends this month apparently) so curious if I can just go with 18.

If you're not sure - happy to test it out.

EDIT - deb.nodesource.com scripts are screaming about a different deprecation warning, but question still stands

mm20102010 commented 1 year ago

https://github.com/sponsors/Apollon77

it worked just for a few minutes. not working anymore : (

brutus6506 commented 1 year ago

I'm really happy that you managed to solve it, it was really important to me. A thousand thanks

Apollon77 commented 1 year ago

Nodejs 16 of higher.

If it is not working provide debug logs ... most likely @bbindreiter need to tell how to get them.

Also show config including info on region of the account and such

smcgann99 commented 1 year ago

Working OK for me even audio player state change too, which has been broken for some time

Many Thanks !!!!

lbreggi commented 1 year ago

I have just released 5.0.40, which should, thanks to Apollon77, make push events working again.

You'll need NodeJS 16 installed and please make sure that Events is set to "On" in your node red alexa account settings.

Thank you!

I have the same issue, running the latest docker version available in HACS, but issue remain the same

claudiopj commented 1 year ago

image

events is on, but only show listening and i get no response

lbreggi commented 1 year ago

I have just released 5.0.40, which should, thanks to Apollon77, make push events working again. You'll need NodeJS 16 installed and please make sure that Events is set to "On" in your node red alexa account settings. Thank you!

I have the same issue, running the latest docker version available in HACS, but issue remain the same

I found the issue - for some reason the "events" field was blank; changing to On solved the problem! many thanks!

claudiopj commented 1 year ago

I have just released 5.0.40, which should, thanks to Apollon77, make push events working again. You'll need NodeJS 16 installed and please make sure that Events is set to "On" in your node red alexa account settings. Thank you!

I have the same issue, running the latest docker version available in HACS, but issue remain the same

I found the issue - for some reason the "events" field was blank; changing to On solved the problem! many thanks!

My events field war not blank and not solve the problem... i use node red

smcgann99 commented 1 year ago

@claudiopj do you have NodeJS 16 or above ?

claudiopj commented 1 year ago

@claudiopj do you have NodeJS 16 or above ?

installed on my windows 11. I use home assistant in virtual box

gerlinl commented 1 year ago

The new version is working for me on a HomeAssistant system. I did have to set "events:" to "on" in the Alecxa account setup (in Node-RED) setup.

For those of you that have Node-RED installed in a system where you cannot easily determine your node version. This flow should output the node version to the debug window.

[{"id":"36012e5c49ad2542","type":"tab","label":"Flow 1","disabled":false,"info":"","env":[]},{"id":"6545547b0106901a","type":"inject","z":"36012e5c49ad2542","name":"","props":[{"p":"payload"},{"p":"topic","vt":"str"}],"repeat":"","crontab":"","once":false,"onceDelay":0.1,"topic":"","payload":"","payloadType":"date","x":280,"y":300,"wires":[["f0516f5f38a54485"]]},{"id":"f0516f5f38a54485","type":"exec","z":"36012e5c49ad2542","command":"node","addpay":"","append":"-v","useSpawn":"false","timer":"","winHide":false,"oldrc":false,"name":"","x":450,"y":300,"wires":[["e9c88d5068914b7c"],[],[]]},{"id":"e9c88d5068914b7c","type":"debug","z":"36012e5c49ad2542","name":"debug 6","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"false","statusVal":"","statusType":"auto","x":640,"y":300,"wires":[]}]

claudiopj commented 1 year ago

The new version is working for me on a HomeAssistant system. I did have to set "events:" to "on" in the Alecxa account setup (in Node-RED) setup.

For those of you that have Node-RED installed in a system where you cannot easily determine your node version. This flow should output the node version to the debug window.

v18.17.0 but i cannot get command

image

gerlinl commented 1 year ago

I am also on v18.17.0, and my config looks like the same as yours, other than I am using the US Amazon config. Maybe it is related to that. I am attaching a screenshot of my config just in case I am missing something else that is different.

I am assuming you restarted node-red after updating the module. I just used the GUI in HomeAssistant to restart node-red. I did not restart anything else. As soon as I set events to "on" and deplored, I was back in business.

Alexa_Events_On

lbreggi commented 1 year ago

I’m using pt-BR as well and it’s working. Let me know if you want to compare something

Sent from my iPhone

On Sep 8, 2023, at 19:57, claudiopj @.***> wrote:



I am also on v18.17.0, and my config looks like the same as yours, other than I am using the US Amazon config. Maybe it is related to that. I am attaching a screenshot of my config just in case I am missing something else that is different.

I am assuming you restarted node-red after updating the module. I just used the GUI in HomeAssistant to restart node-red. I did not restart anything else. As soon as I set events to "on" and deplored, I was back in business.

[Alexa_Events_On]https://user-images.githubusercontent.com/2956655/266752830-309f3caf-6c6f-4108-a5c2-1b9ac69c96ab.jpg

yes i restarted node-red after updating the module... so problem is probably related of page and language

— Reply to this email directly, view it on GitHubhttps://github.com/bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/138#issuecomment-1712367795, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AGEJQ7UB3ULFM53PWPGS5DLXZO5ITANCNFSM6AAAAAA27HDMAI. You are receiving this because you commented.Message ID: @.***>

mm20102010 commented 1 year ago

I'm also using pt-BR, but it worked only for a few minutes and suddenly stopped again

claudiopj commented 1 year ago

I'm also using pt-BR, but it worked only for a few minutes and suddenly stopped again

i have no ideia anymore.. i have unninstall applestrudel, alexa-media-player, all nodes.. nothing works

Apollon77 commented 1 year ago

@claudiopj first of all ... makes it really sense to post hourly? Can you imagine that there are timezones that sleep when you are awake? Come on.

ok Brazil is something I did not encountered so far and so we need to check. So we need to find out which amazon server we need to use in Brazil. If you like then experiment around ... locate that file and place https://github.com/Apollon77/alexa-remote/blob/9289914c549590fd91884fbec5f2eba52a1fa4d0/alexa-http2push.js#L33 on your local machine and try to add an else case for amazon.com.br - I would try the "na" host first? Tell what works and we can officially add it. @bbindreiter or what would you use for Brazil?

bbindreiter commented 1 year ago

Yes, prod-na. It makes sense geographically.

Apollon77 commented 1 year ago

library updated (6.0.2) ... can be tried

bbindreiter commented 1 year ago

@claudiopj can you please try what @Apollon77 suggested and report back if it works. If it does I can update to 6.0.2 so the fix will be available for everyone. Thanks

bwims commented 1 year ago

I have just released 5.0.40, which should, thanks to Apollon77, make push events working again.

You'll need NodeJS 16 installed and please make sure that Events is set to "On" in your node red alexa account settings.

Thank you!

It's probably important to note that for Docker installations of Node-Red, the version of NodeJS in the docker container needs to be >= 16 NOT the version that may be installed outside of the Docker container.

bwims commented 1 year ago

Works for me, using alexa.amazon.co.uk

I did have to re-enable events as "on".