data-enabler
10 seconds delay
I started using this plugin but I'm experiencing a strange issue. I configured many actions to perform GET requests against a localhost nodered server. Randomly some actions execute very slowly and I can't understand what is happening. If I restart the streamdeck software the issue goes away (or appears on other buttons) without changing any configuration.
Here some more details on what happens.
I put a console.log just before the fetch, and another one as the first row inside checkResponseStatus, so just before and after the fetch: the first log appears as soon as I press the button on the streamdeck.
Then nothing happens for a couple of seconds, from 10 to 15, then I receive the network call in the backend and the streamdeck gets the response almost immediately.
Seems like the fetch doesn't start, for some reason.
Any hints? Ever experienced something like this?
Hmm, I don't think I've ever noticed any significant delays before the request gets sent in my own personal use, though this does make me think that it may be useful to have some immediate feedback in addition to feedback when the request completes.
How many instances of the action do you have, and how frequently are you using them? My immediate ideas are that it could either be an issue that scales with usage like a memory leak, or maybe the Stream Deck SDK is intercepting fetch requests to do some extra checks of some kind.
I have five requests set up. From what I understood the only thing that seems possible to me is that the SDK is doing something: the code reaches the fetch statement but the http request starts late.
When the problem presents itself, it is on the same action, while the others work correctly.
Any ideas on how to get more info to understand what is going on or how to reproduce the issue sistematically?
The intermediate feedback could be nice: one of the actions is pretty slow to complete and an early feedback could be very useful
Unfortunately the SDK isn't open-source to my knowledge, though maybe you could at least log the fetch object and see if it's been overridden somehow.
Monitoring the network connections coming from the Stream Deck application might also provide some answers.