@Liam1110 I'm having the exact same problem. Taken out and cleaned the brush several times as well as in and around where it sits despite absolutely no dirt or debris being there...still the same error every single time regardless.

  @ShaunTheSheriff  yeah started doing it more and more often this morning so took it back and swapped for a different brand. Unfortunate because all my home cameras are with tapo so was excited to have it all on one app. 

Same thing here. It's been cleaning fine for the last couple of weeks but three nights ago it got stuck in the lounge overnight. When I found it I started it again and it got stuck a few seconds later. After that it was fine. Two nights ago it did the same thing in the same exact two places. Last night it did it again, same two places again, but now it has added a few more places in another room. Every time I check the brush, there's nothing there. Last night I even tried cleaning the brush as much as I could, making sure it span in place, but it still did it.

There was a firmware update a few days ago. I wonder if that has introduced a bug so it's more sensitive now? For me, it does always get stuck when it's next to a wall or furniture. It has never done it in the middle of the floor.

  @Wayne-TP Thanks for the response, unfortunately due to the frequency it was happening we ended up taking it back. The store didnt have another one in stock so ended up getting a different brand robot vacuum. 

  @Wayne-TP I've already got two tickets open, one through emailing support and another through live chat but have yet to receive a reply from either beyond the initial "we're investigating it". I'll probably end up returning it if I haven't had any solutions in the next few days and go with a different brand as it's essentially an expensive paperweight at this point.

  @Liam1110 i have the exact same issue , fiest carpet vacuum and it gets stuck atound the edge, and has done everytime since , usually in a similar place too. 
 I have sent videos to tplink support, hopingthey will get onto a firmware update to sort it out.

 Ive had the rv30 plus for 2 years doing the same house without a single issue. So it had to be this vaccum and its software

  @Al599 Yeah I've got a friend with the rv30 and it runs flawlessly, I've got more carpeted rooms then them so went with the rv50 for the auto mop removal.

Hoping there's an update soon. It was perfectly fine the first few days of having it then it all went south. As well as the main brush stuck error I've noticed the perfect fit setting now acts weird such as attaching the mops after cleaning a purely carpeted room/zone then going over that area again with the mops raised. The object avoidance also seems to have gone missing, before it would detect any toys my son left laying in the middle of the room and go around them, now it just tries to plow right on through/over them no matter how big they are.

  @ShaunTheSheriff 

I'm having the same problem. It started yesterday after no apparent issue before hand. On carpets, within 1-2 minutes (of trying to vacuum but running the brush in reverse repeatedly activating the cutter trying to clear the 'blockage') the robot stops and throws the error, no amount of cleaning, restarting etc. resolve the issue. It only happens on carpets, though on non-carpeted flooring the robot vibrates/makes noise every so often (maybe running the cutter as it sounds similar). The robot can complete a full 'cleaning' cycle on carpets with the brush removed too.