You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I have the application as an add-on in my HomeAssistant, unfortunately the CPU usage increases constantly until it eventually reaches 100% and blocks my entire HomeAssistant server
To Reproduce
Launch Neolink: with only mqtt on
wait an hour
Versions
Neolink software: neolink-latest
Reolink camera model and firmware: 4x Argus 3 Pro
HA-Hardware: PC with 13th Gen Intel® Core™ i9-13900H, HA gets 12 of the Cores
Can you help me? What do you need to find the Isue
The text was updated successfully, but these errors were encountered:
Same here.... funny enough I have a similiar issue on both ends, on the Broker side (eclipse-mosquitto/mosquitto#2807) and just now observed for the first time on the client side (neolink with the same setting as yours with just mqtt enabled). I have no idea, yet but investigating...
A small update on this: In the meantime, I have switched my MQTT broker from Mosquitto to NATS and can confirm that this issue also occurs with NATS. My Neolink configuration is as follows:
I had to restart neolink to bring it back to normal operation. Next time - I guess this will happen in the next 24 hours - I am prepared to run a dtrace script and hopefully can prepare some detailed logs which function consumes most cpu time to narrow it down.
Describe the bug
I have the application as an add-on in my HomeAssistant, unfortunately the CPU usage increases constantly until it eventually reaches 100% and blocks my entire HomeAssistant server
To Reproduce
Versions
Neolink software: neolink-latest
Reolink camera model and firmware: 4x Argus 3 Pro
HA-Hardware: PC with 13th Gen Intel® Core™ i9-13900H, HA gets 12 of the Cores
Can you help me? What do you need to find the Isue
The text was updated successfully, but these errors were encountered: