slaesh

@edufolly any idea that could help me? =)

Glad to hear that! :) Currently switching to GraphQL subscriptions but will come back in some time though! ;) Thanks! since it's already on your list.. Can/should we close this?...

Still not possible? @HJianBo This request was old, maybe in the meantime things changed :) I saw this here: https://www.emqx.com/en/blog/develop-emqx-plugin-using-python using the hooks-api.. Use-Case: appending a timestamp to JSON-payloads. thanks!...

nvm, found this here: https://github.com/emqx/emqx-extension-examples/tree/master/exhook-svr-go works fine! thanks!

thanks @Hedda ! Sure, sounds great. Thanks for your request. Currently stuck during a business trip. Maybe write me for more details https://t.me/slaesh

do it like this instead: ```js const customStoreFile = `${__dirname}${path.sep}bunq-js-client-data.json`; // run the file store with a location to store the data const storageInstance = JSONFileStore(customStoreFile); ```

Maybe [this](https://github.com/platformio/platform-espressif32/issues/947) is related?

same issue here. appears "sometimes" after a disconnect/reconnect. is this a problem of "this lib" to poll something what does not exist? or is the mqtt-broker polling something which is...

thanks @bertmelis so.. asynctcp polls an already closed connection.. but "we", the asyncmqttclient, are keeping a "broken" connection somehow alive/in-memory? or is the "memoryleak" in asynctcp too? which is polling...

it does not stack up.. after another reconnect/disconnect.. it is gone. not sure "where" this gets stuck and why it's not "self-healing" :thinking: trying to dig into it sooner or...