Open S-E-B-123 opened 2 months ago
I can confirm i see the same. was ok till today and working like a charm. no updates done and stopped working.
tried fresh/refresh auth no change there was ha and node red update so did them as was broken anyway and no change. node red node-red-contrib-amazon-echo had update so i did this and no change
just letting you know what i done, will wait for devs to look as i know you always do your best. thanks in advance
Just came here to report it has stopped working for me as well
same to me...nothing changed > reinstall, refresh without effect.
+1 from Italy since 2 days ago
@bbindreiter It seems you need to update alexa-remote2 dependency to version 7.0.4 I manually installed it and it fixed the problem for me. Amazon making changes again I guess, keep up the good work ;-)
@smcgann99 "It seems you need to update alexa-remote2 dependency to version 7.0.4 I manually installed it and it fixed the problem for me."
I updated it via: "npm i alexa-remote2" but without any effect - are there any additional actions that you recommend to do (you did)?
@bbindreiter It seems you need to update alexa-remote2 dependency to version 7.0.4 I manually installed it and it fixed the problem for me. Amazon making changes again I guess, keep up the good work ;-)
Thanks, will try it today
As I've told @smcgann99 in the NodeRED forum, this also didn't make any difference for me
For some reason, running the install command didn't update the alexa-remote2 package
When I went to check - mine was still on a version 6
I decided to try removing it using npm remove alexa-remote2 and it said it uninstalled 4 packages
I then re-ran npm install alexa-remote2 and it installed 4 packages and my version is now 7.0.4
And now it works again :slight_smile:
Unfortunately I removed (npm remove alexa-remote2) and installed (npm install alexa-remote2) with no effect by now
btw how can I check the alexa_remote2 version, as it does'nt apperar in "manage palette" menu?
@brunialti
version check: "npm list" make sure that the npm uninstall/intall is run in the right folder: ".node-red" > example: /home/pi/.node-red
working again now!
"how can I check the alexa_remote2 version"
go into your .node-red/node_modules/alexa-remote2 folder then open up package.json in a text editor and it says its version near the top
{
"name": "alexa-remote2",
"version": "7.0.4",
"description": "Remote Control for amazon echo devices",
....
Can confirm, it does work for me with 5.0.49 and alexa-remote2 7.0.3. Will publish a new version anyway. Anyway, stop relying on that function, it is not sustainable.
{
"data": {
"timestamp": 1713426027160,
"device": {
"deviceName": "Echo Office",
"deviceEntityId": null
},
"voiceHistoryRecordItems": [
{
"timestamp": 1713426027147,
"transcriptText": "alexa what's the time",
},
{
"timestamp": 1713426027162,
"transcriptText": "The time is 9:40 AM.",
]
}
]
},
"conversionDetails": {
"CUSTOMER_TRANSCRIPT": [
{
"timestamp": 1713426027147,
"transcriptText": "alexa what's the time",
}
],
"ALEXA_RESPONSE": [
{
"timestamp": 1713426027162,
"transcriptText": "The time is 9:40 AM.",
}
]
},
"name": "Echo Office",
"description": {
"summary": "what's the time"
},
"alexaResponse": "The time is 9:40 AM.",
}
Please try 5.0.50, it uses the latest alexa-remote2 (7.0.4). Thanks!
thanks @bbindreiter ive just checked and the update is not available yet on the pallete but ill check again later. Thanks again for you update, FYI, i do not solely rely on this function, but when it works its grate so its very helpful. when it doesn't we have app button, wall button and longer voice commands to work with.
we are just lazy and like to say short commands like Alexa light or Alexa tv and it knows where we are to turn on the correct device. This solution that sometimes has issue is better than any other solution that I know.
Edited Update now available on palette. updated on my machine and worked right away
The new release solves my problem.
Unfortunately I still can't get my flow working even with 7.0.4.
I have alexa-remote2 7.0.4 and alexa-cookie 5.0.2 installed (confirmed by checking package.json files).
An Alexa Event node, configured to report Device Activity, indicates "listening" (see screenshot below).
A Debug node is connected to the Alexa Event node (plus other nodes that form the flow).
I have spoken requests to several Echo devices but no device activity events are ever reported by the Debug node (or received by the other nodes).
I have restarted Node-Red and re-initialized the cookie several times the problem persists. I would appreciate suggestions for what I should check/try next.
FWIW, here's how the Alexa account is configured:
I hoped this update would solve the Device activity node but it's no dice on my end. (UK) would this be region specific since some ppl confirm this working for them?
I hoped this update would solve the Device activity node but it's no dice on my end. (UK) would this be region specific since some ppl confirm this working for them?
I'm in the uk and worked fine for me since update as above. Just commenting to advise I'm uk too
I wonder how our configurations are different. I just reinstalled the node and rebooted the pi then tried it again. Unfortunately without luck on my end.
I'm VERY keen to get this functionality back.
On Tue, 23 Apr 2024, 19:11 sicampbell82, @.***> wrote:
I hoped this update would solve the Device activity node but it's no dice on my end. (UK) would this be region specific since some ppl confirm this working for them?
I'm in the uk and worked fine for me since update as above. Just commenting to advise I'm uk too
— Reply to this email directly, view it on GitHub https://github.com/bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/188#issuecomment-2073074374, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKDRL265H6Y2662GEJPGHHDY62P4XAVCNFSM6AAAAABGKAYAGWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANZTGA3TIMZXGQ . You are receiving this because you commented.Message ID: <bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/188/2073074374 @github.com>
Not sure but as listed above in comment https://github.com/bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/188#issuecomment-2059875301
these are my changes when debugging that did not work and then i updated node-red-contrib-alexa-remote2-applestrudel to 5.0.50 and restarted then it all just worked again
I had some time to spin up new NR instance - (3.1.9 and 5.0.50 version od the node) basic innit node and on device activity - nothing when I speak to all my echos. I can direct smart devices from NR
Not that it will probably fix your issue but don't use the Initialise node anymore Set the Auto Init parameter to On instead And remember to set your deployment option to Modified Nodes in case you haven't done that
What colour is your on device node status. O don't really like it being gray. Feels like it should be another colour.
On Sat, 27 Apr 2024, 07:53 Simon Walters, @.***> wrote:
Not that it will probably fix your issue but don't use the Initialise node anymore Set the Auto Init parameter to On instead And remember to set your deployment option to Modified Nodes in case you haven't done that
— Reply to this email directly, view it on GitHub https://github.com/bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/188#issuecomment-2080391274, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKDRL236XAAIZ76MDGPDUADY7NDP3AVCNFSM6AAAAABGKAYAGWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBQGM4TCMRXGQ . You are receiving this because you commented.Message ID: <bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/188/2080391274 @github.com>
Its grey when listening - turns to green when something detected
turns green when something detected
How I wish it would do that again but, in my case, it hasn't in a long time.
Given that no one has indicated there's anything wrong with the configuration I posted above, it's all the more perplexing.
Many people have many issues with this node -in the past - it's not been working for me but 90% of others have been happy.
Its not a node to rely on as it's all reverse-engineered and Amazon can (and do) change things around whenever they want to
One day we'll find out that it depends whether you bought one of your Echos on a Tuesday or not :)
Duh. Alexa account configuration has a on/off toggle for device activity. I completely missed this. I'm not sure in what circumstances I'd like this to be off as I can simply not use the node... But toggling it fixed the issue for me and I have my device activities back again 😍😍😍
On Sat, 27 Apr 2024, 13:54 Simon Walters, @.***> wrote:
Many people have many issues with this node -in the past - it's not been working for me but 90% of others have been happy.
Its not a node to rely on as it's all reverse-engineered and Amazon can (and do) change things around whenever they want to
One day we'll find out that it depends whether you bought one of your Echos on a Tuesday or not :)
— Reply to this email directly, view it on GitHub https://github.com/bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/188#issuecomment-2080590759, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKDRL26IUP23TY2ZMOPDMOTY7ONY5AVCNFSM6AAAAABGKAYAGWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBQGU4TANZVHE . You are receiving this because you commented.Message ID: <bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/188/2080590759 @github.com>
It's off per default to ease traffic on Amazon servers. They have asked us, actually Apollon77, to add this.
toggling it fixed the issue for me
I tried switching that setting from On
to Off
(deploy) and back to On
(deploy) but the Alexa Event node still fails to report events.
If I add an Alexa Routine node, its Devices list displays all my Echo devices, so alexa-remote2 is communicating with Amazon's servers (it retrieved all device names including one I added recently). However, the Alexa Event node doesn't report any events that occur on those devices.
I noticed that the Alexa Event node's description says:
Listens to Push events. Events must be enabled for this account.
Regarding "Events must be enabled for this account", is it referring to the Alexa Event node's account configuration, specifically the Event
field must be set to On
? Or is that a setting in my Amazon account? Because I don't recall ever having to enable anything in my Amazon account.
Grasping at straws ...
Alexa account configuration has a on/off toggle for device activity.
Is this a different option somewhere that's not the Events and Auto Query Activities toggle in the account node? You don't mention them by name so wondering if I may have missed it as well. Thanx Michael
This is in the configuration node for the Alex's remote. It's easy to miss if you used it before and you assume that you know the options by heart. Open it up and you will see the toggle just below other settings
On Sat, 25 May 2024, 23:26 Michael Murphy, @.***> wrote:
Alexa account configuration has a on/off toggle for device activity.
Is this a different option somewhere that's not the Events and Auto Query Activities toggle in the account node? You don't mention them by name so wondering if I may have missed it as well. Thanx Michael
— Reply to this email directly, view it on GitHub https://github.com/bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/188#issuecomment-2131567959, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKDRL2ZYWWPQ56OYUYNFXYLZEEFZRAVCNFSM6AAAAABGKAYAGWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZRGU3DOOJVHE . You are receiving this because you commented.Message ID: <bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/188/2131567959 @github.com>
Sorry, I’m Just not getting it. If I go to the right side-bar and open the configuration node for the Alexa remote account I get the same options…
@.***
Michael Murphy Ocean Blue Properties Coosa Island Storage Bullets Mini Storage 107 Coosa Island Rd Cropwell, AL 35054 205-600-4463
From: NotEnoughTech @.> Sent: Saturday, May 25, 2024 5:32 PM To: bbindreiter/node-red-contrib-alexa-remote2-applestrudel @.> Cc: Michael Murphy @.>; Comment @.> Subject: Re: [bbindreiter/node-red-contrib-alexa-remote2-applestrudel] Alexa Event -> On Device Activity not working since today (Issue #188)
This is in the configuration node for the Alex's remote. It's easy to miss if you used it before and you assume that you know the options by heart. Open it up and you will see the toggle just below other settings
On Sat, 25 May 2024, 23:26 Michael Murphy, @.<mailto:@.>> wrote:
Alexa account configuration has a on/off toggle for device activity.
Is this a different option somewhere that's not the Events and Auto Query Activities toggle in the account node? You don't mention them by name so wondering if I may have missed it as well. Thanx Michael
— Reply to this email directly, view it on GitHub https://github.com/bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/188#issuecomment-2131567959, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKDRL2ZYWWPQ56OYUYNFXYLZEEFZRAVCNFSM6AAAAABGKAYAGWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZRGU3DOOJVHE . You are receiving this because you commented.Message ID: <bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/188/2131567959 @github.com>
— Reply to this email directly, view it on GitHubhttps://github.com/bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/188#issuecomment-2131577567, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAZDP7UL6MPZRQK63TROZTDZEEGPJAVCNFSM6AAAAABGKAYAGWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZRGU3TONJWG4. You are receiving this because you commented.Message ID: @.**@.>>
I'm getting a screenshot got you one sec
On Sun, 26 May 2024, 05:25 Michael Murphy, @.***> wrote:
Sorry, I’m Just not getting it. If I go to the right side-bar and open the configuration node for the Alexa remote account I get the same options…
@.***
Michael Murphy Ocean Blue Properties Coosa Island Storage Bullets Mini Storage 107 Coosa Island Rd Cropwell, AL 35054 205-600-4463
From: NotEnoughTech @.> Sent: Saturday, May 25, 2024 5:32 PM To: bbindreiter/node-red-contrib-alexa-remote2-applestrudel @.> Cc: Michael Murphy @.>; Comment @.> Subject: Re: [bbindreiter/node-red-contrib-alexa-remote2-applestrudel] Alexa Event -> On Device Activity not working since today (Issue #188)
This is in the configuration node for the Alex's remote. It's easy to miss if you used it before and you assume that you know the options by heart. Open it up and you will see the toggle just below other settings
On Sat, 25 May 2024, 23:26 Michael Murphy, @.<mailto:@.>> wrote:
Alexa account configuration has a on/off toggle for device activity.
Is this a different option somewhere that's not the Events and Auto Query Activities toggle in the account node? You don't mention them by name so wondering if I may have missed it as well. Thanx Michael
— Reply to this email directly, view it on GitHub < https://github.com/bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/188#issuecomment-2131567959>,
or unsubscribe < https://github.com/notifications/unsubscribe-auth/AKDRL2ZYWWPQ56OYUYNFXYLZEEFZRAVCNFSM6AAAAABGKAYAGWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZRGU3DOOJVHE>
. You are receiving this because you commented.Message ID:
<bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/188/2131567959
@github.com>
— Reply to this email directly, view it on GitHub< https://github.com/bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/188#issuecomment-2131577567>, or unsubscribe< https://github.com/notifications/unsubscribe-auth/AAZDP7UL6MPZRQK63TROZTDZEEGPJAVCNFSM6AAAAABGKAYAGWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZRGU3TONJWG4>.
You are receiving this because you commented.Message ID: @.**@.>>
— Reply to this email directly, view it on GitHub https://github.com/bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/188#issuecomment-2132059564, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKDRL253YXOEBVR7ETFYADLZEFP3JAVCNFSM6AAAAABGKAYAGWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZSGA2TSNJWGQ . You are receiving this because you commented.Message ID: <bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/188/2132059564 @github.com>
Step 1 this should be on - then reboot
I must have something else going on because I have had auto query on for a while (toggled on/off) rebooted etc.. Still no events. All the other nodes are working as expected. I have an Astro project that I’m working on. Trying 2 use node-red to control it. Its been interesting so far…Have you worked with it yet? I have another alexa issue with that has me stumped. Zero support for it so far…
2024-05-26_03-21-04.pnghttps://1drv.ms/i/s!ApYuqualHfEeo58l20dSYkELZy_sJw?e=QCf2qV
Michael
From: NotEnoughTech @.> Sent: Sunday, May 26, 2024 12:17 AM To: bbindreiter/node-red-contrib-alexa-remote2-applestrudel @.> Cc: Michael Murphy @.>; Comment @.> Subject: Re: [bbindreiter/node-red-contrib-alexa-remote2-applestrudel] Alexa Event -> On Device Activity not working since today (Issue #188)
image.png (view on web)https://github.com/bbindreiter/node-red-contrib-alexa-remote2-applestrudel/assets/42407403/41c82eb7-f46a-4b08-9bc0-6f08cdba6b7b Step 1 image.png (view on web)https://github.com/bbindreiter/node-red-contrib-alexa-remote2-applestrudel/assets/42407403/1919c99c-7945-4810-ad82-a799c31f0d4b this should be on - then reboot
— Reply to this email directly, view it on GitHubhttps://github.com/bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/188#issuecomment-2132070087, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAZDP7QQS3JREGZ3EOVPZFLZEFV6BAVCNFSM6AAAAABGKAYAGWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZSGA3TAMBYG4. You are receiving this because you commented.Message ID: @.**@.>>
I haven't heard of Astro. About the issue, are you able to try on a clean instance to see if there is something else affecting your installation?
I went as far as removing AlexaRemote2 and then re-installing still nothing. Nothing in the logs give me a clue of why I’m not receiving events. It’s got me stumped.
Astro https://a.co/d/ahjbaRR
Michael
From: NotEnoughTech @.> Sent: Sunday, May 26, 2024 3:50 AM To: bbindreiter/node-red-contrib-alexa-remote2-applestrudel @.> Cc: Michael Murphy @.>; Comment @.> Subject: Re: [bbindreiter/node-red-contrib-alexa-remote2-applestrudel] Alexa Event -> On Device Activity not working since today (Issue #188)
I haven't heard of Astro. About the issue, are you able to try on a clean instance to see if there is something else affecting your installation?
— Reply to this email directly, view it on GitHubhttps://github.com/bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/188#issuecomment-2132140406, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAZDP7RR23PK2VGA6ZCILNDZEGO45AVCNFSM6AAAAABGKAYAGWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZSGE2DANBQGY. You are receiving this because you commented.Message ID: @.**@.>>
Oh this is Astra, I remember this. I think the common consensus was, that having Amazon Echo with a camera on was bad enough, we don't need one that roams haha my test server has just this: [image: image.png] Works fine.
did you use npm to remove AR2? A new instance will take moments to confirm. I assume you can log in and operate other Alexa functions?
Mat Zolnierczyk
Maker, Robotics Engineer
Owner | NotEnoughTech @.*** notenoughtech.com Teesside, North Yorkshire, UK [image: facebook] https://www.facebook.com/NotEnoughTECH/ [image: twitter] https://twitter.com/NotEnoughTECH [image: linkedin] https://www.linkedin.com/in/mat-zolnierczyk/ [image: instagram] https://www.instagram.com/notenoughtech/
On Sun, May 26, 2024 at 6:16 PM Michael Murphy @.***> wrote:
I went as far as removing AlexaRemote2 and then re-installing still nothing. Nothing in the logs give me a clue of why I’m not receiving events. It’s got me stumped.
Astro https://a.co/d/ahjbaRR
Michael
From: NotEnoughTech @.> Sent: Sunday, May 26, 2024 3:50 AM To: bbindreiter/node-red-contrib-alexa-remote2-applestrudel @.> Cc: Michael Murphy @.>; Comment @.> Subject: Re: [bbindreiter/node-red-contrib-alexa-remote2-applestrudel] Alexa Event -> On Device Activity not working since today (Issue #188)
I haven't heard of Astro. About the issue, are you able to try on a clean instance to see if there is something else affecting your installation?
— Reply to this email directly, view it on GitHub< https://github.com/bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/188#issuecomment-2132140406>, or unsubscribe< https://github.com/notifications/unsubscribe-auth/AAZDP7RR23PK2VGA6ZCILNDZEGO45AVCNFSM6AAAAABGKAYAGWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZSGE2DANBQGY>.
You are receiving this because you commented.Message ID: @.**@.>>
— Reply to this email directly, view it on GitHub https://github.com/bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/188#issuecomment-2132290499, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKDRL27QXAOUVRTHPOHPP6TZEIKILAVCNFSM6AAAAABGKAYAGWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZSGI4TANBZHE . You are receiving this because you commented.Message ID: <bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/188/2132290499 @github.com>
I have had auto query on for a while (toggled on/off) rebooted etc.. Still no events. All the other nodes are working as expected.
You are not alone. I also have Auto Query set to On and it still fails to receive events. Other nodes work properly, just not Device Activity. It used to work but hasn't for a long time. Its fragility has convinced me to abandon alexa-remote2 and explore other solutions.
Yeah I have about given up also. Have spent many hours trying to get this to work.. Looking @ Voice Monkey - Supercharge Your Alexa Routineshttps://voicemonkey.io/
Michael From: tdejneka @.> Sent: Sunday, May 26, 2024 1:34 PM To: bbindreiter/node-red-contrib-alexa-remote2-applestrudel @.> Cc: Michael Murphy @.>; Comment @.> Subject: Re: [bbindreiter/node-red-contrib-alexa-remote2-applestrudel] Alexa Event -> On Device Activity not working since today (Issue #188)
I have had auto query on for a while (toggled on/off) rebooted etc.. Still no events. All the other nodes are working as expected.
You are not alone. I also have Auto Query set to On and it still fails to receive events. Other nodes work properly, just not Device Activity. It used to work but hasn't for a long time. Its fragility has convinced me to abandon alexa-remote2 and explore other solutions.
— Reply to this email directly, view it on GitHubhttps://github.com/bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/188#issuecomment-2132327281, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAZDP7TQ6HP2XJE4J5GXMNDZEITIFAVCNFSM6AAAAABGKAYAGWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZSGMZDOMRYGE. You are receiving this because you commented.Message ID: @.**@.>>
So it seems it's time to accept this is dead and move on? What other options there are for people with Alexas that are pretty much useless now?
I'm not sure what could stop others but once I enabled that toggle things were working for me. Would be good to pull resources together and figure out what else is making this behave badly Mat Zolnierczyk
Maker, Robotics Engineer
Owner | NotEnoughTech @.*** notenoughtech.com Teesside, North Yorkshire, UK [image: facebook] https://www.facebook.com/NotEnoughTECH/ [image: twitter] https://twitter.com/NotEnoughTECH [image: linkedin] https://www.linkedin.com/in/mat-zolnierczyk/ [image: instagram] https://www.instagram.com/notenoughtech/
On Tue, Jun 4, 2024 at 4:07 PM jonferreira @.***> wrote:
So it seems it's time to accept this is dead and move on? What other options there are for people with Alexas that are pretty much useless now?
— Reply to this email directly, view it on GitHub https://github.com/bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/188#issuecomment-2147776779, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKDRL26L3UDB3VYKK7W7SZLZFXJ47AVCNFSM6AAAAABGKAYAGWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBXG43TMNZXHE . You are receiving this because you commented.Message ID: <bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/188/2147776779 @github.com>
pull resources together and figure out what else is making this behave badly
I'm running the latest version of alexa-remote2 (5.0.50) on Node-Red (17.0.12 as a Home Assistant Add-on). The Alexa Event node indicates "listening" but no event is ever received. All other nodes work (such as turning on a light or TTS) only the Alexa Event node remains forever silent. It worked for a few years then, about half a year ago, it stopped and none of the subsequent versions of alexa-remote2 have resuscitated it.
It's configured like this:
I noticed this recently as well. One of my installs is still working, but the other install is no longer receiving events as of today. All other aspects (that I use) are still working fine, such as changing volume and looking at lists, but the on device event is broken for me.
After a long time Device Events are finally working again for me. I have updated from 5.0.49 to 5.0.50, set "Auto Query Activities" from unset to "On" and restarted Node Red. Thanks to @notenoughtech, I wasn't aware of that setting.
I'm pleased to hear it's working for you. Happy days
On Mon, 1 Jul 2024, 10:48 Chris380, @.***> wrote:
After a long time Device Events are finally working again for me. I have updated from 5.0.49 to 5.0.50, set "Auto Query Activities" from unset to "On" and restarted Node Red. Thanks to @notenoughtech https://github.com/notenoughtech, I wasn't aware of that setting.
— Reply to this email directly, view it on GitHub https://github.com/bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/188#issuecomment-2199707745, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKDRL23OFT5VKFMDOAJKQT3ZKEQWPAVCNFSM6AAAAABGKAYAGWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJZG4YDONZUGU . You are receiving this because you were mentioned.Message ID: <bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/188/2199707745 @github.com>
updated from 5.0.49 to 5.0.50, set "Auto Query Activities" from unset to "On" and restarted Node Red.
FWIW, in the screenshot I posted last month, I'm using the same version with the same settings and it fails to detect events.
Nobody has come forward to explain why those settings work for some users but not others. I assume that's because no one has sufficient understanding of how this actually works under the hood. Or whoever does understand it doesn't have the time to explain it. Either way, it leaves me with a non-functional Alexa Event Node and no clear way to fix it.
If you see anything different in that screenshot compared to your settings, please let me know. Thank you.
updated from 5.0.49 to 5.0.50, set "Auto Query Activities" from unset to "On" and restarted Node Red.
FWIW, in the screenshot I posted last month, I'm using the same version with the same settings and it fails to detect events.
Nobody has come forward to explain why those settings work for some users but not others. I assume that's because no one has sufficient understanding of how this actually works under the hood. Or whoever does understand it doesn't have the time to explain it. Either way, it leaves me with a non-functional Alexa Event Node and no clear way to fix it.
If you see anything different in that screenshot compared to your settings, please let me know. Thank you.
I am in the UK so slightly different settings and mine partially responds. IE 1 in 5 times I get a response...
For some reason I do get quite frequent connect/disconnects. Did you set up something to see if the same happens to you?
Since today "on device activity" is no longer working. When I ask Alexa something, no event / message is generated anymore.
If I use the "Volume change" function of the "Alexa event"-node, an event/message is generated. Is this a known problem or is there any advice on how I can solve the problem?
Update: with updated
alexa-remote2
version7.0.4
it's working again