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 Event - Audioplayer State Change does not see playing in > 5.0.25 #125

Closed FlorianDessloch closed 1 year ago

FlorianDessloch commented 1 year ago

Since a while ago the "Alexa Event" node set to "Audioplayer State Change" does not see the event "PLAYING" and send it out in msg.payload.audioPlayerState any more. INTERRUPTED and STOPPED are recognized and transmitted.

How to reproduce: Set up a "Alexa Event" node set to "Audioplayer State Change". Connect a debug node set to complete msg to the output. Tell Alexa to play a song, no event will be recognized. Tell Alexa to stop. An Event will trigger.

occures in version > 5.0.25 resetting to 5.0.25 solves the problem.

dajuly20 commented 1 year ago

I think I have the same problem. I could confirm it with your repro steps, exactly the same behaviour.

I tried downgrading too.. but for me it didn't work. What version did you go back to? Was it really .25?

I went back all the way to .22 where I gave up ^^ Maybe something on the side of Amazon was changed?

bbindreiter commented 1 year ago

@FlorianDessloch which version did you rollback to to make it work again? Thanks for reporting

FlorianDessloch commented 1 year ago

@bbindreiter I rolled back to 5.0.25. I don't know, if it occurs in 5.0.26, cause I skipped this version. that version comes with a downside, too. I get errors at 4pm CET every day, but it does not restart nodered. it seems to reauthenticate an initialize. 5.0.27 used to restart my nodered multiple times a day.

github-actions[bot] commented 1 year ago

This issue is stale because it has been open for 30 days with no activity.

github-actions[bot] commented 1 year ago

This issue was closed because it has been inactive for 14 days since being marked as stale.