bbindreiter
Alexa events no longer firing
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
Yes, same here. Was working 18 hours ago but not firing now. Tried restart of nodered.
Same here as of around 9pm yesterday UK time (though some dodgy responses for several hours before that).
This has happened before on node-red-contrib-alexa-remote2, which I understand these nodes are based on: https://github.com/586837r/node-red-contrib-alexa-remote2/issues/193 I'm working my way through that thread to understand the fix, and whether it might be applicable here too...
The Echo devices now appear to have multiple IP addresses on my network, and I've seen more than one Alexa master device IP address as well. It looks like Amazon may have changed something.
The Alexa Event node is initialising and listening, and not triggering on events. The Alexa Routine node appears to be working correctly.
Restart of node red and Echo devices does not change anything. Creating a new account does not change anything.
Any help appreciated.
Since yesterday evening, the event [On Device Activity] no longer works for me (Austria) on a voice input via the Alexa Echo devices.
- Partially other events are working. I'm afraid Amazon/Alexa API has changed or disabled a feature. Does someone know an alternative solution for such disturbances?
same here , i have tried a complete reinstall on a VM and same issues no activity for on device activity im in the USA
Same here. (U.S.) Using the latest node-red-contrib-alexa-remote2-applestrudel (5.0.27)
Same here using version 5.0.27 on service host layla.amazon.de, page amazon.de, language de-DE. I am implementing a workaround using an Alex routine to flip a virtual switch (openhab) and then get the last active device via GET -> ACTIVITIES node which still works.
hab das gleiche problem (austria). gibt es eine lösung? bzw wird daran gearbeitet ? lg
All this is embarassing. I spent a lot of time to integrate alexa with my system, even with chatgpt. Now it is half dumb, Do any of you have any other alternative node to the device event one? Do you suggest any microphone device acting locally able to hear a command after a wakeup word and pass it via any nodered node?
I have just started looking into this Rhasspy.
https://rhasspy.readthedocs.io/en/latest/
https://www.youtube.com/watch?v=IsAlz76PXJQ
I don't need too much brain power, just enough to understand the 20 phrases or so I use for my automation system, so I am hoping it is enough. If it works for me, I plan to run a central server (an existing Ubuntu server on a NUC), with a few satellite instances running on PI4s with something like Jabra Speak 410s attached. This is not cheap for a multi-room setup, I have a couple of extra PI4s already, so it is worth a shot. If this can break my cloud dependencies, I will be a happy camper. It looks like there may be cheaper ways to go with the satellites, I just started looking this today.
Whisper may be another option, though it sounds like it may need more horsepower to run quickly:
https://github.com/openai/whisper
I know they have integrated it into Home Assistant, not sure if there is node-red package or not.
Same here using version 5.0.27 on service host layla.amazon.de, page amazon.de, language de-DE. I am implementing a workaround using an Alex routine to flip a virtual switch (openhab) and then get the last active device via GET -> ACTIVITIES node which still works.
@axelpip can you post or link your nodered flow for this? I've got openhab and nodered linked up but I'm struggling with the last active device node.
Is this a problem with this plugin or alexa-remote2?
@bbindreiter
I've just tried installing node-red-contrib-alexa-remote2 on different instance of node red, appears to have the same problem.
Same here since ~2 weeks now. Guess some changes on the Alexa-API side needs to be adapted.
Is this a problem with this plugin or alexa-remote2?
@bbindreiter
Sorry, I haven't had the time to check it yet. 99% some change in the Alexa API.
Although it is tempting, its not reliable to build a smart home based on the reversed engineered Alexa API.
Is this a problem with this plugin or alexa-remote2? @bbindreiter
Sorry, I haven't had the time to check it yet. 99% some change in the Alexa API.
Although it is tempting, its not reliable to build a smart home based on the reversed engineered Alexa API.
Yes. But are there nodered stable alternatives for voice input in your opinion ?
A reliable path in my opinion is the workaround via a simulated light bulb. As this is simulated hardware (like hue for instance) I think it is more likely that this support will exist for a long time - otherwise a lot of smart lights would become useless with Alexa. I define then a routine for each command which sets one simulated light bulb to a certain dimming level, which I check then in Node Red. Issue is: I need a seperate routine then for every command, which is a bit annoying to maintain.
Same problem here in the UK. returned from vacation to find my "Good Morning" command no longer made it through to HA to do all the fancy stuff.
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 https://github.com/bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/138#issuecomment-1663524925 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 approach will only work for some event types. In my case I need to catch the event type "On audio player state change"