If you’ve been following the SharkIQ integration issues (51 GitHub issues, the big one at #151845 with 88+ comments), you know it’s been broken for a while with no fix in sight.
I got fed up and built a workaround: shark2mqtt is a standalone Python service that bridges SharkNinja’s cloud API to Home Assistant via MQTT autodiscovery. You get a full vacuum entity plus battery, WiFi signal, error sensors, and room-specific/Matrix cleaning — all in a Docker container.
Tested with two US-region models:
Shark AI Ultra Robot Vacuum with Self-Empty Base (UR250BEXUS)
Shark Matrix Plus Robot Vacuum and Mop with Self-Empty HEPA Base (UR2360EEUS)
Other models may work. PRs welcome if you get one running!
Thanks for this! I’ve set it up and it detected my two Shark vacs.
One of them works perfectly, but on the other (a UR250BE0US), while it can be viewed and directly controlled, no rooms show up or can be addressed by a “clean_room” command.
Do you know if there’s a way to force the bridge to re-poll that data? Or are rooms automatically polled in every update?
wow this is awesome, thanks for sharing! i’ve been stuck with the broken integration for months and just kinda gave up on automations for my shark. gonna give this a try on my docker box this weekend. really like that you included the wifi and battery sensors too, that’s super handy. if i run into anything weird i’ll drop an issue on github. appreciate the work!
I came across this randomly after after entirely too long of being frustrated with the on-going Google to Shark auth token API problems. Clearly they have no intention to fix it at this point. This has solved all my wifes frustrations with it, which in turn solved all my frustrations with it. So, thank you for this - this is awesome!
Hello, thank you so much for this great opportunity. I’ve managed to get it working so far. Is there a way to choose whether the robot should mop or vacuum?Model:RV282WZEEU
