Hi guys,
Many users have reported this problem and we got it fixed in Luban v4.5! You can try it and check if the problem persists. 
I don’t understand how this is a Luban bug. Even if it is, the SM firmware itself should prevent this from ever happening.