Hi All, Currently I'm facing an issue with queue-gate (AKA node-red-contrib-queue-gate, q-gate) and I hope the problem is already solved by some of you... There is an example with picture at the page of the node: Retain Until Processed . In that example the node start processing is manually initia…

This is how I do it. [{"id":"b6630ded2db7d680","type":"inject","z":"bdd7be38.d3b55","name":"","props":[{"p":"payload"},{"p":"topic","vt":"str"}],"repeat":"","crontab":"","once":false,"onceDelay":0.1,"topic":"","payload":"","payloadType":"date","x":140,"y":480,"wires":[["ed63ee4225312b40"]]},{"id":"…

If you can help provide the necessary German translation we can get it fixed

The translation by deepl.com is fine, but even translate.google.com is ok (I checked both of them).

There is still an issue: The Alexa functionality is done by the node call service which doesn't wait for the end of the processing (asynchrone), thus, there is still a collision of the messages. The simplified subflow: [{"id":"8246f0e467c3a7ec","type":"subflow","name":"Wohnzimmer-TV: Text+Audio o…

[image] jf64: Although it is still time based instead of event driven, it seems to be working. It isn't time based, the next message is released when you tell it to release it, via the Flush message. The rate setting is purely so that you can specify a timeout such that if a message never co…

[image] jf64: The Alexa functionality is done by the node call service which doesn't wait for the end of the processing (asynchrone), thus, there is still a collision of the messages. Well if there is no way of knowing when the previous message has finished processing then this approach will …

[image] Colin: Is it possible to tell that the call service has completed by using some effect of whatever the call service node does. It would only go, if there would be a kind of media_player.in_use functionality, which is not the case -AFAIK. Even the Queue functionality of the node call s…

You can use node-red-contrib-alexa-remote2-applestrudel (node) - Node-RED to integrate with Alexa, these node would give a response when the speech is finished, allowing for the flush command.

Thank you, I'll try it and will give you feedback here.

Sorry, but I have no idea how to initialize those applestrudel stuff: If I'm starting some of those Alexa-nodes, the response is: open http://localhost:3456/ in your browser which would be fine, but I have no browser on my HA installation (in Virtual Box) and I don't know how to get there any. I…

The same browser you are using the editor on, open a new window and enter the url. You then get a amazon login page. There are many topics on this forum on how to initialise the nodes Search results for 'alexa remote2 initialise' - Node-RED Forum

Node-RED

Node-RED Forum

Queue-gate (q-gate) question

General

E1cid 24 March 2024 00:46 28

I am out of ideas, except try the initialise flow here Help saving cookie with alexa-remote2-applestrudel

Topic		Replies	Views
Message Throttling/limits and Message Totals General	12	328	24 April 2025
[ANNOUNCE] node-red-contrib-queue-gate Share Your Nodes	27	2508	5 November 2019
Delay logic request for suggestions General	11	486	9 August 2020
Opinions please - delay - queue option Feature Requests	23	2061	13 September 2021
Rate limiting based on exec node completion General	44	1404	2 January 2022

Copyright OpenJS Foundation and Node-RED contributors. All rights reserved. The OpenJS Foundation has registered trademarks and uses trademarks. For a list of trademarks of the OpenJS Foundation, please see our Trademark Policy and Trademark List. Trademarks and logos not indicated on the list of OpenJS Foundation trademarks are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.

Queue-gate (q-gate) question

Related topics