I am planning to purchase a TP-Link Tapo RV10/RV30 Vacuum. Wanted to know if this vaccum would be supported in Home Assistant.
I know there isn’t any official Tapo integration yet but I already have a C210 camera which I have integrated into Home Assistant using a custom component. Hence I would be really interested if there would be a possibility of an official/custom integration soon.
Hello buddy. Did you ever get the RV30?
I’ve just bought one and wondered if it’s compatible with HA?
No. I wasn’t sure of the compatibility myself and was holding off the purchase till I knew more.
Hi, do You have news? Is the Tapo RV10/RV30 Vacuum supported in Home Assistant?
Thank You,
Simone
I am also interested in RV30 integration.
I would like to know also about this vacuum.
I’ve got the RV30, and from what I can see in the app there is no local API exposed for it… 
Yes, looks like we are simply out of luck, the vacuum works great but I am really sad I cannot integrate it into my Homeassistant setup.
Could you not use it via Alexa Media Player?
It works with Google Home and Alexa.
I also purchased an RV30 before checking compatibility with HA, just assumed it would based on existing Tapo/Kasa integrations.
I was able to get a VERY basic integration working. If you make a toggle or button in HA through the Helpers screen, it is possible to expose it to Alexa or Google Home.
I exposed these entities to Alexa via the Home Assistant Cloud subscription for experimenting, but I assume this can be done manually as well.
In Alexa I then set up a basic routine, if HAtoggle = On, start vacuum, if HAtoggle = Off, stop vacuum. I also then exposed this toggle in HA to Homekit so I can start from Apple Home.
When turned on it defaults to the whole home cleaning mode, which is fine for my use case. Again, incredibly basic, but perhaps this may help!
Unfortunately I haven’t found another way for my RV20 Max Plus, which makes me pretty sad…
But thanks for sharing the idea, @sidcremer !
Hey TAPO (if you happen to read this): can you please provide the API also for the vacuum cleaners (just a few basic functions)? More functions via Alexa is also an idea (but not as good, because the status of the device is always missing).
Ok, that’s the only way it works at the moment, so I created two switches START and STOP as described above - unfortunately it only worked for me with helpers “input_boolean.xxx”.
This caused a bit of confusion as START and STOP could then be set in the HA dashboard at the same time.
To avoid this, I simply set the triggered switch back to “off” after 1 minute using automation.
When you now select a switch, the vacuum cleaner is triggered and after 1 minute the switch is automatically off. Now you can select one of the switches again.
Maybe this idea will help someone else… Or maybe someone has a better idea…
We (the upstream library & the integration maintainers) have been working on this (Add ssltransport for robovacs by rytilahti · Pull Request #943 · python-kasa/python-kasa · GitHub, Initial support for vacuums (clean module) by rytilahti · Pull Request #944 · python-kasa/python-kasa · GitHub) but it’s still work in progress. The vacuums use a different protocol than rest of the devices, so it required more effort than other devices.
As none of us developers have a test device, it has been a bit cumbersome to test but we now have some people who can run tests for us. If you are interested in testing & helping out (especially if you are comfortable with git & console) with testing, feel free to contact me on the homeassistant discord (my forum profile has infos).
If you want to follow the process of getting this work integrated to the homeassistant integration, you can activate notifications for this pull request: Initial implementation for tplink tapo vacuums by rytilahti · Pull Request #131965 · home-assistant/core · GitHub - we are currently aiming to get these supported for the 2025.1 release.
This is much appreciated. Useless with git and console - I could learn but I am very time poor.
fantastic, I’m buying a Tapo RV30 max this week.
As the beta cut is going to happen very soon and the PRs are still open & require testing, it will not unfortunately made it into the 2025.1 release as I thought it would