"Mopping attachment removed. Please check."
I got my RV50 so I could leave it to the mopping, but now it can't complete a single task without the infernal notification. This seems to have gotten worse since the latest firmware, which I didn't think was possible. Anybody else had the same issue and more importantly found a solution?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Your case seems to require further investigation. To assist with this case, a specialist will help to follow it up through email. Please check your inbox later to confirm.
If the email you used to register for the TP-Link community is not your contact email or you cannot access it, please send me your contact email through private message.
- Copy Link
- Report Inappropriate Content
Eskirrow wrote
I got my RV50 so I could leave it to the mopping, but now it can't complete a single task without the infernal notification. This seems to have gotten worse since the latest firmware, which I didn't think was possible. Anybody else had the same issue and more importantly found a solution?
@Eskirrow Ok, interesting. I have exactly the same problem. After a thoroughly good clean, it helped. I bought new mop heads, and I wondered if that had resolved it. But it started up again, and I can observe now that every time it moves the movable mop pad out to start cleaning in a corner, it momentarily loses contact. By the time it has thrown the error, it has often picked up contact again, but it has to be manually restarted. I guess one way to resolve this would be to simply have a two- or three-second delay on the sensor so that if it feels it's lost but it was actually just going over a bump, it wouldn't throw an error straight away and could continue mopping. But I'm interested if there's a resolution. @Wayne-TP
- Copy Link
- Report Inappropriate Content
Muzza-72 wrote
Eskirrow wrote
I got my RV50 so I could leave it to the mopping, but now it can't complete a single task without the infernal notification. This seems to have gotten worse since the latest firmware, which I didn't think was possible. Anybody else had the same issue and more importantly found a solution?
@Eskirrow Ok, interesting. I have exactly the same problem. After a thoroughly good clean, it helped. I bought new mop heads, and I wondered if that had resolved it. But it started up again, and I can observe now that every time it moves the movable mop pad out to start cleaning in a corner, it momentarily loses contact. By the time it has thrown the error, it has often picked up contact again, but it has to be manually restarted. I guess one way to resolve this would be to simply have a two- or three-second delay on the sensor so that if it feels it's lost but it was actually just going over a bump, it wouldn't throw an error straight away and could continue mopping. But I'm interested if there's a resolution. @Wayne-TP
A beta firmware is available to resolve this issue. If you would like to try it, send me the Mac address of your device via private message.
Before the Upgrade
(1) Please be sure you have read the Beta Test Agreement before upgrading the Pre-release firmware!
(2) How to update the firmware of the Tapo devices on the Tapo App
(3) Firmware downgrade is not supported. When a new official version is released, updating it will overwrite the beta version.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@Muzza-72 Beta firmware has been sent to your device, you may check it 30 minutes later in the Tapo app and perform the update.
- Copy Link
- Report Inappropriate Content
@Wayne-TP thank you.
Beta Firmware received and updated.
ISSUE RESOLVED!
The edge mop head is able to move position without triggering the alert. (and stopping the cleaning)
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 205
Replies: 6
Voters 0
No one has voted for it yet.
