Closed richsimpson closed 6 months ago
@richsimpson Same thing here. Just started a few hours ago.
Same
Encouraging that the /api/activities should be back open for business soon. Presume that will solve this
Here is the fix: https://github.com/bbindreiter/node-red-contrib-alexa-remote2-applestrudel/pull/157
alexa-remote2 actually lists getActivities as deprecated
Nice one @DanPatten Can I do anything to fix it or just wait for the code owner to update it and get the update from node red palette?
@richsimpson you can just throw https://github.com/DanPatten/node-red-contrib-alexa-remote2-applestrudel/
in as your npm dependancy in node red, and that works. Probably would want to swap back once its merged in here though.
I will merge it today. Nice work @DanPatten
Thank you for contributing.
@sanjay900 can you tell me a step by step how to do that? i have HA OS with terminal. thks :)
Confirm the update solves the issue.
Great work @DanPatten and @bbindreiter
@sanjay900 can you tell me a step by step how to do that? i have HA OS with terminal. thks :)
Update solves it. Via manage palette 👍🏻 then restart node red.
yessssss thank youuuuu :) great work @DanPatten and @bbindreiter
Problem seems to be back although slightly different.
If I initialise I get one OK command, then this.
Odd, It still appears to be working fine for me at the moment
This issue is stale because it has been open for 30 days with no activity.
This issue was closed because it has been inactive for 14 days since being marked as stale.
I have been using the other node/activities
to listen to events (since the events node started playing up some months ago) and to identify the device called (to create a LAST ALEXA sensor), this was working well but now this node reports an error:
"Error: no JSON at handleR..."
Other nodes are working, the routines and so on, so seems its an Amazon end problem, blocking something? Anyone else seeing this or even using this node?
The NodeRed AddOn log shows this:
Everythign up to date, no updates today though so seems to have just happened, hence assumption its an Amazon side issue.