The “It currently does NOT work with the newer x05 Wi-Fi models” note is the key thing here, and it’s worth explaining why, because it’s not a bug that’ll get fixed in the existing integration — the 105/405/505 (and other newer models) are a different generation entirely. iRobot calls it “Prime”; people here have been calling it “V4”. It doesn’t speak local MQTT with a blid/password at all — it’s cloud-only, different auth, different everything under the hood. The existing Roomba integration (and roombapy, which it’s built on) fundamentally can’t be extended to cover it — it would need to be a separate client.
So I’ve been building one: roombapy-prime — a from-scratch async Python client for exactly this generation, reverse-engineered from the Prime app (decompilation + the app’s own bundled config files, not guesswork). I posted about it here: Looking for iRobot Prime/V4-generation owners to test a new Python library
Between the four of you (@chairstacker, @dunderhead, @nathanmeyers, @gogorichie) there’s a decent little cluster of 105/405 owners in this one thread — exactly the hardware I have no way to test against myself. If any of you are willing to run a read-only diagnostic script against your account (logs in, reads state/favorites/history — never sends a command or changes anything), that’s genuinely the bottleneck right now:
pip install git+https://github.com/johnnyh1975/roombapy-prime.git
roombapy-prime-validate --username [email protected] --country-code US
I also maintain ha_roomba_plus (unrelated name collision with your “Roomba Plus” model, sorry for the confusion that’s probably about to cause) — a HACS integration currently covering Classic-protocol robots. The plan, once roombapy-prime is confirmed working, is to fold Prime/V4 support into that same integration so this generation isn’t left out permanently. Right now that’s blocked entirely on real accounts confirming the library actually works — which is where this thread’s owners would help a lot.