Possible memory leak
CptArn opened this issue · comments
I've seen this in my debug log of docker but i'm not sure if this is a problem.
dobiss2mqtt |
dobiss2mqtt | > dobiss2mqtt@0.1.0 start:prod /app
dobiss2mqtt | > NODE_ENV=production node ./dist/index.js
dobiss2mqtt |
dobiss2mqtt | (node:20) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 message listeners added to [MqttClient]. Use emitter.setMaxListeners() to increase limit
I don't think it's an issue. Memory usage is stable I think ? Around 65Mb for me. Or have you seen otherwise ? It is just creating a bunch of listeners in a short timeframe at the start.
I haven't looked into it too deeply but i've noticed that from time to time, i have to reboot the application. Do you have auto discovery on or have you configured all your lights in the configuration in home assistant? I see sometimes home assistant is not changing lights and the state is always off (even with greater polling)
I have to reboot my server once in a while but that's for other reasons. Other than that o have no issues. I only have my relays configured in dobiss2mqtt. Not in HASS. When your dobiss no longer responds, does the dobiss mobile app still work? Or it's purely dobiss2mqtt that needs a reset for everything to work again?
With the increase of the timeout, it's working better. But sometimes the requests are not transferred to dobiss. I'm guessing that when i use the app, it 'wakes' the dobiss programmer and at that point, it is working again. I will be adding a few zigbee devices that will trigger the lights, so maybe at that point, it will be working better. I only have put my dimmers and relais in the dobiss2mqtt and let it auto discovery. So i'm not sure how to configure it with optimistic setting so the state can be correct.