-
-
Notifications
You must be signed in to change notification settings - Fork 31.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
iRobot Roomba J7+ fails to be detected or connected #111599
Comments
Hey there @pschmitt, @cyr-ius, @shenxn, @Xitee1, @Orhideous, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) roomba documentation |
If this ends up being a duplicate at it would be more helpful for me to put logs elsewhere let me know. |
I have the same problem since sometime yesterday or the day before. HA integration that has been in succesfull use for at least a year just stopped working. Device not found, IP not found. HA in Docker installation. The device is i7 and it's working otherwise, just not with the integration anymore. |
I have the same problem with a roomba j7. The device is detected and HA gives me the opportunity to configure it. Then, the device IP is shown and after clicking on "Send" and waiting some time, I get "connection failed." Nothing in the logs. HA 2024.2.4. |
A nugget of information that OP did not provide is that he's also unable to connect to the device via roombapy to get the password. I believe this issue should be forwarded to the upstream library and corrected there. The error he recieved when attempting to get the password is:
conversation -> https://community.home-assistant.io/t/irobot-roomba-init/687957/32 |
Yep, same for me. At least I get a "File" name, but that won't help:
I can ping to the roomba from the host and from within the container. |
@egg02 If you have a Linux-based system nearby, you can try to probe your robot with a new CLI. It's still WIP, but nevertheless. python -m venv test_roombapy
source ./test_roombapy/bin/activate
pip install git+https://github.com/pschmitt/roombapy@cli#egg=roombapy[cli]
roombapy discover 192.168.0.100 # replace 192.168.0.100 with Roomba address |
I found my Roomba Combo again with 2024.2.4 BUT the state attributes seem to have been lost. What showed for example as status = 'Charging' in 2024.2.2, now shows as 'Nul'. Also the custom vacuum card in Lovelace has been completely blanked even if the vacuum is present in the Lovelace overview page (and the commands like 'clean', 'stop' and 'return to dock' work) |
I'm having the same problem, using 2024.2.4. It detects the Roomba (j7+), but I can't add it. Note that this same Roomba was working perfectly until the 2024.2.3 bug made me try to remove and re-add it. @Orhideous I tried that, and it's giving me a "No robots found". |
@esdcmc If all attributes (shown in device dashboard) are missing, that's a different problem. Open an issue for it and attach a screenshot, please. |
@mancontr Well, that's interesting. Looks like either the robot is ignoring broadcast packets, or something in the network is blocking them, which is why the library can't detect robots. Actually, there is no need for UDP discovery to control a bot. If the IP address of the Roomba is known, and we are sure that it is the Roomba and not the teapot on the other end, we can try a direct MQTT connection. Ping me on HA discord, if you want to help with testing. |
That didn't work:
|
One other thing I noticed, possibly related, if I try to ping the vacuum directly I get ping response times in the 50-200 ms range. Maybe it's just that round trip time killing it. That said, no clue why it's that slow, network is healthy and nothing else pings like that. |
I have the same problem with my j7+. The robot is fairly new therefore I am not so sure how it behaved in earlier versions. On 24.2.2 (& 24.2.4) it was not able to connect, so used the dorita980 library to receive the credentials. With the IP address I tried to connect but it failed (unknown error occurred). Are you interested in any special logs? @Orhideous I am quite new to HA, so excuse my knowledge about necessary information regarding logs and how to access them etcetera. |
j7 is found but won't connect. j9 is not found. Can pull info with RoombaCloudUtility and ping both. j7 used to be found and configured until 24.2.3. Thank you for your efforts. |
I have the same issue with a J7. The Roomba has the Software version 23.37.5. It will be found but when I'm trying to add it it comes with failed to connect. |
Not sure if that's related, but I also started having some connection issues on my s9+ today, but it resolved after rebooting the roomba from the iRobot app. Below is the error I was getting.
|
Thanks, after the reboot I am finally asked for the password. But I'm still unable to retrieve it (connection refused). Might try different methods get the password, but I have no time for that right now. |
Better, but no success yet. I was able to retrieve the apssword via dorita980, but still got "connection failed" after entering it. |
Success! Well, at least a workaround. What I did:
Note: Anyway, it worked! Thanks to @tom3q for the hint! Roomba J7 |
Same issue with a brand new J9+ here. Had an i7 that was working flawlessly and have a Braava that continues to. I can retrieve BLID and password through the cloud without a problem. But when I try to add to HA, the integration doesn't find any new iRobot device on my network even though my Netgear Orbi HA integration "sees" the J9+ (as does my router software). It always ends with a "Failed to connect" error. I'm making sure that no other iRobot connection/app is open and that the robot has been rebooted. Nothing in the logs. Appreciate any suggestions. |
Same thing here with J7+, although have only recently tried. Never got it to work. I have my creds ready to input but never get past the manual input ip part. |
Strange, revisited the homeassistant integration with little hope, but it found my robot after inputing the IP and the password I extracted with dorita 980 worked! |
I still can't get my J9+ integrated. Tried again today. The integration finds the robot on my network, but then won't find the password and won't accept my manual entry of the password either. Log shows the follow error: Logger: roombapy.remote_client Can't connect to 192.168.1.49 |
This might be connected to too short timeouts, I wrote a comment in the roombapy repository about it. |
Any news? Still impossible to integrate? |
FWIW I haven't had any issue with my s9+ since last time I posted. |
J7+ still not connecting. retrieved blid and password, but getting "Failed to connect" in HA after submitting... |
Ditto here. Worse, I’m not sure who the devs are, so I don’t know who to communicate with about the problem. No judgment here, just desperation. Anyone know where to go? |
Solution found for J7/J9. |
J7+ getting "Failed to connect" |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
The problem
I have an Irobot J7+ I am trying to add onto the HA integration. My older roomba works fine, but the j7+ shows as not visible on the network, and if I provide an IP it just gives failed to connect.
What version of Home Assistant Core has the issue?
2024.2.4
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
roomba
Link to integration documentation on our website
https://www.home-assistant.io/integrations/roomba/
Diagnostics information
When I try to add this roomba it just claims it can't find it and errors out. Oddly when I check the debug logs I find that is can see it, but the wizard doesn't consider it reachable for some reason.
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
I have a second irobot 980 which works flawlessly, so it's probably nothing inherint in my network.
The text was updated successfully, but these errors were encountered: