Events are not firing again for several people #142
Comments
cymplecy
changed the title
|
Hm … I‘m not at home till the weekend. Son-in-law fact debug logs and check what comes in via wsmqtt would be the only helping to get an idea. But it might be that Amazon now also closes this way :-( |
|
i have same problem! |
|
same here, all other nodes are working....events no, it's grayed out and not receiving anything. |
|
@Apollon77 Looks like events are no longer occurring via wsmqtt, I connected directly to that WS and not seeing anything. Is there an alternative here? It does appear the API supports returning recent events although probably not a great solution for real time as compared to a websocket connection. |
|
What api you talk about? |
|
Apollon, pls help us :( we need you |
|
If someone is firm with sniffing ios/android network traffic including tls decoding using wireshark or such ... contact me. So you know what we do currently ... this is not that funny doing as it sounds reading. lets see if we find a way |
The alexa API can be reached at: https://www.amazon.com/alexa-privacy/apd/rvh/customer-history-records-v2?startTime=1693630800000&endTime=1693710556556&disableGlobalNav=false You can view recent history at: https://www.amazon.com/alexa-privacy/apd/rvh |
|
Ahh you mean that api. Yes this is not the topic here because we need to know when to get these data |
|
Same for me. Other nodes work, "Alexa Event" says "listening" but does not emit anything. |
Yes same here for me as well, hope it gets fixed as it was very very useful |
|
I'm in communication with @bbindreiter ... stay tuned ... and prepare your system: It will require Node.js 16+ !
|
|
There is a new version available (5.0.40), please update and make sure Events is "On" in Account settings. Everything should work then again. Please donate to Apollon77 using the link above if you rely on this functionality. |
|
still not working for me... :( |
|
@Apollon77 I can confirm that the "Alexa Event" is working now again (layla.amazon.de is my service host). Great work! |
|
For some reason, V5.0.40 wasn't showing as being available in the palette but installing from command worked and back in the listening business once I'd configured Events = On @Apollon77 (and @bbindreiter ) for your efforts Also to everyone who relies on this |
|
Unsure what's happening with this new update, but it's causing my nodered to continuously crash.
|
|
Hm. One thing is this error about timeout value. Please use the mentioned node --trace-warnings parameter for modeled start to trace the codeplace and report here. Something tries to set a timeout if 720h or 30d which is too long. Find it because it gives a lot of issue! Maybe also check config if the node? Other then that the getaddr error means that there is a dns lookup issue. And btw: show your config of the Alexa node in any case. Wh it tries for you to connect to far east server? Japanese? Australia account? |
|
Hi all, Thanks for the work you have all done on this to get events working again. I updated my installation, set events to on, restarted node-red and the events reset itself to blank so had to set it to on again. After another restart the setting was retained. However after a couple of minutes the events stopped firing again. I'm using NodeJS 18 if that is of any help. Does anyone know how I can get the events to fire all of the time like they used to or what I can do to help debug the issue? Thanks in advance! |
|
@Bismar locate that file and remove the .au at the end of the Hostname. Does it work then ? |
|
@elgerg show your node config. Especially the domains names in there. |
Here you go: |
|
Should work. Other users reported it working. Try a restart. Else need debug logs |
|
Ok, so it worked for a few minutes then stopped again. How do I get the debug logs? Sorry for the noob question but I've not had to do this before.. Thanks |
|
also in the uk but debugging on a flight..... |
|
In fact I mainly assuming is not so much about that domain but where your Amazon account is located. So even if you use .co.uk but have an us account then we simply assume wrong. |
|
@bbindreiter i think I add a new config variable to set/override that settings. Most likely easier on the long run. |
|
@cymplecy is your simon says just sending text to speech to the device? to clarify on mine all my voice prompts triggered by HA all continue to work. (doors opening/closing, doorbell ...) all fire in HA and alexa speaks the commands fine, looks like i can also see the volume changes on the drvices ok as well. the only thing that fails for me is when i initiate the speech commands, these dont get picked up. |
|
"to clarify on mine all my voice prompts triggered by HA all continue to work. (doors opening/closing, doorbell ...) all fire in HA and alexa speaks the commands fine, looks like i can also see the volume changes on the drvices ok as well." Yes - its just the listening for spoken events that is problematic - all else works " is your simon says just sending text to speech to the device?" - I've got another Pi connected to a speaker that's next to an Echo and that runs my "simon says" counting up When everthing working - it can count up to 40 (4 per minute) and all are picked up by the NR On Device Activity node When it goes into failure mode its approximately one minute of working - one minute of not working So, at this present time, I'm saying that if I restart Node-RED and it only initialises once, then it seems to work reliably. But if re-initialises (either by direct inject into the node or due to it being redeployed - then it goes into the intermittant mode So, now I've got all the Alexa nodes on it's own Pi with only one flow tab and I've locked it so I don't accidently change it. I'll see what happens - I'll run my test routine every now and again just to make sure it works (just done another 10 minute run - all fine) |
|
That's what I thought just wanted to make sure I was explaining my self tidy. I have restarted my node red and am no longer getting the http2-push close errors as yet, will see how long it takes to break. |
|
It could be a link between this two issues? |
|
I wouldn't know but suspect not as that's a crash report as opposed to the intermittent failures that we are seeing |
|
Still working ok here, restarted node-red and haven't touched it since, just periodically checking voice responses are picked up. also i do have a flow to init and auth that runs once an hour,
i found it somewhere as a solution to having to reauth manually a while ago, don't know of this is the best way or the right way but its been working fine so don't think its impacting but just incase. just had a failure..... but then it started working again.. (edit again) 1 Oct 13:51:10 - [debug] [server:Hassio] HA State: running
1 Oct 13:51:10 - [debug] [server:Home Assistant] HA State: running
1 Oct 13:51:21 - [debug] Flushing localfilesystem context scope e8bd56f8f70ccb15
1 Oct 13:51:21 - [debug] Flushing localfilesystem context scope global
1 Oct 13:51:22 - [debug] [alexa-remote-account:Main] Alexa-Remote HTTP2-PUSH: Close: undefined: undefined
1 Oct 13:51:22 - [debug] [alexa-remote-account:Main] Alexa-Remote HTTP2-PUSH: Retry Connection in 1s
1 Oct 13:51:23 - [debug] [alexa-remote-account:Main] Alexa-Remote: Update access token ...
1 Oct 13:51:23 - [debug] [alexa-remote-account:Main] Alexa-Remote HTTP2-PUSH: Use host bob-dispatch-prod-eu.amazon.com
1 Oct 13:51:23 - [debug] [alexa-remote-account:Main] Alexa-Remote HTTP2-PUSH: Initialization completed
1 Oct 13:52:24 - [debug] [alexa-remote-account:Main] Alexa-Remote: Update access token ...
1 Oct 13:52:24 - [debug] [alexa-remote-account:Main] Alexa-Remote HTTP2-PUSH: Use host bob-dispatch-prod-eu.amazon.com
1 Oct 13:52:24 - [debug] [alexa-remote-account:Main] Alexa-Remote HTTP2-PUSH: Initialization completed```
|
|
I read in the previous post ..
and @knolleary write "we don't support HTTP2 " Excuse me, but I don't understand ..... |
|
Nick is saying its not a node red issue, that's all. |
|
I think the problem may be not shutting down previously open Alexa-remote2 http2 connections which is why it works initially until you deploy the node again. |
|
ok so its been over an hour now and i still have functionality, im still seeing the undefined close but less often and it seems to be self recovering from them. It looks as if retry isnt working correctly but the update token is fixing it? |
|
still working fine with the last changed made by @DanPatten, i removed my auto init/authenticate flow as that was triggering the initialize on each boot / redeploy and every hour, dont know if it had any effect but i see no ill effect in the changes my side., |
|
Updated to v5.0.43 - no change as far as I can tell If the Init node is re-initilised, then within two minutes, the events stop being received (and then cycle on/off every few minutes) Now - if we stop re-initialising, then we won't invoke the poor behaviour and we'd be alright unfortunately, exactly the same behaviour is triggered if you do a Full deploy :( That can be avoided as well but a lot of NR users will leave their installation in default Full deployment setting and will get hit by the issue This shows my test logs showing the missing gaps So, AFAICT to avoid the issue, you have to:
|
|
@cymplecy Those two steps is exactly how I have mine setup so it makes sense why mine works. Basically need to shutdown any existing connections when calling init and that does not appear to be happening. The intermittently comes from having 2 open connections to Amazon open which causes events to not get received because the event is fired by the wrong listener. |
|
I did manually initialize and I'm getting this:
Can anybody help please? |
|
At the moment , don't manually initialise - just use auto init
[image: image.png]
…On Wed, 4 Oct 2023 at 09:07, obaldius ***@***.***> wrote:
I did manually initialize and I'm getting this:
[image: image]
<https://user-images.githubusercontent.com/61756214/272505355-61195692-120d-4e39-aae4-6a125cf2b09d.png>
—
Reply to this email directly, view it on GitHub
<#142 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAR7RND7MGYGJVLMZDW62RDX5UKMRAVCNFSM6AAAAAA4ESII4KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBWGM2TIMJXGI>
.
You are receiving this because you were mentioned.Message ID:
<bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/142/1746354172
@github.com>
|
|
Amazon stopped sending "Activity" push notifications ... but also the alexa app is not getting them ... sooo lets see if it is an error or wanted |
|
+1 |
|
Ok guys, @bbindreiter released 5.0.45 of the node with a new version of the library: It should bring back the activity event like before ... I added some workarounds that try to detect activities also without the proper events. Please make sure to DISABLE all manual activity/history triggering you added as woraround yourself I hope it works. Ingo PS: Donations always welcome ;-)) |
|
@Apollon77 |
|
I updated the pallete, restarted Node Red, deleted old Listening Node and added a new one, and even rebooted the RPi hosting Node Red and nothing shows in the Debug Node attached to Listening Node. I never did any of the workarounds; just patiently waited for the fix. Events is On in the Config node. Any other suggestions to try? |
|
Was your palette showing 5.0.45 - mine wasn't at first |
This fixed things for me! Just updated to 5.0.45 in NodeRed - rebooted, and all my events started working again! Wow, big thank you @Apollon77 + @bbindreiter! |
|
I released an update to my lib with improvements and optimizations. That should fix cases where it stayed empty. |
Nice, 5.0.46 released. |
|
I will close this issue now, let's continue here: #152 |
and others
https://discourse.nodered.org/t/alexa-on-device-activity-not-working/80901/1
The text was updated successfully, but these errors were encountered: