Error in log pointing to possible memory leak

[johanschelin]

Is your problem within Home Assistant (Core or Z-Wave JS Integration)?

NO, my problem is NOT within Home Assistant or the ZWave JS integration

Is your problem within Z-Wave JS UI (formerly ZwaveJS2MQTT)?

NO, my problem is NOT within Z-Wave JS UI

Checklist

• I have checked the troubleshooting section and my problem is not described there.

• I have read the changelog and my problem was not mentioned there.

Describe the bug

I am not sure if this is important, but will log the issue to see, as I can't find any useful information from googling this:

What causes the bug?
Not sure

What do you observe?
Only that this error is written in the log.

Steps to reproduce the behavior:
As soon as I do a restart av the Add-on this always arises.

The error that is logged is the following:
(node:157) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 error listeners added to [Keyv]. Use emitter.setMaxListeners() to increase limit
(Use node --trace-warnings ... to show where the warning was created)

Is this something known that I should only disregard, or is it something you think we should dig deeper into?

Device information

Manufacturer:
Model name:
Node ID in your network:

How are you using node-zwave-js?

• zwave-js-ui (formerly zwavejs2mqtt) Docker image (latest)
• zwave-js-ui (formerly zwavejs2mqtt) Docker image (dev)
• zwave-js-ui (formerly zwavejs2mqtt) Docker manually built (please specify branches)
• ioBroker.zwave2 adapter (please specify version)
• HomeAssistant zwave_js integration (please specify version)
• pkg
• node-red-contrib-zwave-js (please specify version, double click node to find out)
• Manually built from GitHub (please specify branch)
• Other (please describe)

Which branches or versions?

zwave-js-ui: 8.8.0
zwave-js: 10.4.0
home id: 4110551221
home hex: 0xf50208b5

Did you change anything?

no

If yes, what did you change?

No response

Did this work before?

Don't know, this is a new device

If yes, where did it work?

No response

Attach Driver Logfile

Will attach log if you think this issue is worth digging into. (Am in the middle of a long running firmware update, so dont want to restart and change loglevel now)

[zwave-js-bot]

👋 Hey @johanschelin!

Thanks for opening an issue! It doesn't look like you provided a logfile though. While not strictly necessary for every issue, having a driver log is required to diagnose most issues.

Please consider uploading a logfile that captures your problem.

[AlCalzone]

@robertsLando does Keyv ring a bell with you?

[robertsLando]

@AlCalzone By checking yarn.lock it's a dependency of cacheable-request and esm2cjs modules, the first is also a dep of got that I think is what you are using to make some api calls, could be that maybe?

Yeah I think it's got: sindresorhus/got#1523

[AlCalzone]

meh...

[AlCalzone]

That's what you get for not implementing everything yourself 🙄