Does anyone have a workaround to the frequent failures of this node because you need to log on to Amazon to update the damned cookie?
I would be OK with some regularity, like once a month, then I can put a reminder on my calendar. But no. This “log on to 192.168.1.35:3456” happens with no regularity. Sometimes a few weeks, sometimes a few hours.
Thanks. That explains why there have been no updates for almost a year…
Is this a direct replacement for node-red-contrib-alexa-remote2?
In other words, do I just remove node-red-contrib-alexa-remote2 and install node-red-contrib-alexa-cakebaked? Or, do I need to edit every node with the same names?
@stevemann unfortunately they are different. The way it works is if the original maintainer of the node/integration/etc isn’t responsive, there is no way to take over the repo. At that point all you can do is copy the project and continue under a new name.
I can’t find the source where I extracted this information but, to install cakebackeds coming from the original alexa-remote2, do this:
Export all flows to file
Delete all flows
Uninstall “node-red-contrib-alexa-remote2” via UI
Install “node-red-contrib-alexa-cakebaked” via UI
Import flows from file
Restart Node-RED
The same thing happens to me, I would love to receive an answer. I have no idea why every three days it stops working for me and I have to restart node red.
ah first you must create a file
you can do this by creating an exec node
with the command “touch file”
this will create a file called file in the directory /opt/
then inside of node-red auth under file path enter /opt/file
You might also try this, refreshes the cookie every hour. I can’t remember the last time I logged into alexa via node-red once I started using this. Will need to update the settings, basically just select the alexa account I believe.