hi @marcel_verpaalen could there be a memory leak in the recent version? 06:27:27.010 [ERROR] [internal.DiscoveryServiceRegistryImpl] - Cannot notify the DiscoveryListener org.eclipse.smarthome.config.discovery.internal.PersistentInbox on Thing discovered event! java.lang.IllegalStateException: Ti…

I don’t think anything changed recently in the miio code.. But indeed this needs to be monitored to understand what’s behind it Was this a onetime event, or you see this behavior more often?

for the moment it seems like one time event I did read most of the things .. also my MI things Can it be related it always finds the roborock s50 with 2 entries in auto discovery?

[image] shorty707: Can it be related it always finds the roborock s50 with 2 entries in auto discovery? this is expected behavior… there are actually 2 independent methods for discovering devices. So far I was not able to avoid the double entries in a good way

Hi, On my machine the leaking started as well: [image] I do not think i have updated neither openhab (running on a Raspberry PI) nor the Mi IO - Plugin. But i do apt update && apt upgade regularly. So maybe this has something to do with the runtime envrironment? I do use the Oracle JDK: java …

I think this is related to [image] Xiaomi Robot Vacuum Binding Bindings Indeed, thanks, Note that it may be a more generic issue somehow as I can see also I’m still in the dark on the cause of it… Are you using text config or the thing via paperUI discov…

Hi, I´m using text config only on OpenHAb stable / 2.4.0. It used to work for quiet a few months without any issues. Then OpenHab stopped responding and needs to be restarted. It keeps on doing so until now. After every two days or so the number of Mi IO MessageSenderThreads is within several th…

I guess you have in your thing file you have not defined your deviceId Can you please add the deviceId for your device (you can see it in the parperUI screen). I expect that will solve your issue. (it is mandatory config in the current version)

Marcel, Your are totally right. Adding the deviceId in the .things-File did the trick. Just one Mi IO MessageSenderThread lives happily. The moment i remove the deviceId from the .thing-Config, new Mi IO MessageSenderThreads are spawned (and start to sum up till OOM). I wonder how you found this…

openHAB Community

Memory Leak MI IO?

Add-ons Bindings

marcel_verpaalen (Marcel) February 21, 2019, 8:35pm 6

I think this is related to

I’m still in the dark on the cause of it…
Are you using text config or the thing via paperUI discovery ?