I’m running HASS with Node Red 15.1.1 and works perfectly with Alexa-Remote2 integration. If I update to 16.0.2 I ruin my Alexa-Remote2 integration and it is asking me to go to https:\myhomeassistant:3457 to re-login to Amazon. This failes with “page not found” at Amazon so I’m forced to restore a full backup from the previous day to get it to work again.
Is this because the add-on is old and deprecated? I could always try to upgrade to alexa-remote2-appelstrudel, but I do not want to experiment if the issue still is the same with that fork of Alexa integration. Anyone else got issues with Alexa on 16.0.2 ?
I thought the login was 3456. I’m away from my computer so I cant double check and could be wrong. I also don’t use Node Red as add on so mine could be completely different.
I’ve used Applestruedel since it was forked and has worked fine. It is glitchy right now if you rely on the listening node but the developer is working on it.
Yeah, the port seems dynamic and can be changed. The port is correct in my case. But after upgrading to Node-RED 16.0.2 I’m asked to relogin to Alexa. This is where it fails. I see the Amazon page, I can login. But after login I get “Page not found” and the token/cookie remains unchanged and the Alexa-Remote2 keeps saying I need to login to fetch the token/cookie (and is not working of course).
Did you update to 16.0.2 with Appelstruedel and it still works without any need to re-login? If so I’ll proceed with exporting the nodes per the update instruction and try this fork instead.
Great. That might be the solution to the problem. I’ll try it tomorrow. Besides, do you see any winnings with moving from Alexa-Remote2 to the Appelstrudle build? Anything specific that’s not working on the old build vs the fork build?