Constant timeouts. Attached what was returned when I tried to install dorita #109
Comments
|
+1, checked my credentials. Log shows as: |
|
+1, same issue. 6/8/2022, 9:29:33 AMRoomba BridgeNew RoombaWARNINGTimed out after 60001ms trying to connect to Roomba |
karlvr
added
question
|
Please test this again with the latest beta release. There were issues with Node 18 and with J7 that are hopefully resolved. Other issues with connecting to Roomba occur if there is something else connected to Roomba, like the app, or another Roomba integration. Please re-open if you continue to have the same issue. |
|
Still getting this pretty constantly with a 960, reserved IP address on the roomba, Node v16 and v18, reboots and reconnects on all applicable devices and services. 1.2.2 remains the most stable and responsive (for me at least) |
|
@asweet could you please post some logs of this issue from the latest plugin version? |
|
I get similar issues with my 960... it seems to happen most often (but not always) when the Roomba gets interrupted during a cleaning cycle (ex. the battery dies before it makes it back to the base). It does seem to be better with the latest version, but I will keep an eye on it and try to capture some logs the next time I see it occur. |
|
@karlvr Sorry for the radio silence, been a while since I looked at this. Not sure I have the logs from two weeks back. On the other hand, after having some difficulties rolling back to 1.2.2, I've since completely reinstalled the roomba2 plugin, and cleared out any plugin data from before (if there was any... I don't remember), and set it all up from scratch on version 1.4 with node v16.18.1 (I bounced between node versions). So far, so good, even when the roomba dies in the middle of a job. Only getting "Releasing an unexpected Roomba instance" notifications, but the plugin is functioning properly from what I can see so far. |
|
May have spoke too soon. got a long string of Connect timed out alerts. Roomba has a reserved IP address, so that didn't change, it was also definitely connected to wifi the whole time. I was able to connect to it through the iRobot app when I noticed that homekit wasn't able to talk to the bot. Rebooting the roomba didn't resolve it, but subsequently rebooting the entire homebridge server did. I'll turn on debug logs for the plugin and report more if it happens again. |
|
OK, @karlvr this might be a bit overkill, but I'm attaching 2 hours of annotated plugin debug log. At a high level, here's what happens: Problem seems to be cleared from then on. Until it happens again, of course. Versions and configurations Throughout the process, apart from intentional restarts and disconnects, pings from my laptop to the roomba were rock solid (generally single digit millisecond ping time, negligible packet loss). From memory, I get the feeling that the disconnects tend to start happening generally after the roomba has completed a job, but not all the time. I'm wondering if it's reporting something back to iRobot, and in so doing somehow blocks the plugin from connecting. This seems to be supported by the dns server logs for the roomba's queries, which I've attached to the log file. |
|
Hey Facing exactly same issue with 980 with Fixed IP address on the bot. And indeed Irobot app is still working but not anymore on Homebridge. iT Was working Yesterday, and now the plugin cannot Reach him anymore. BTW, saying is not able to reach, I tried tthe command getpassword for the sake of it is still working for a part, he is able to give blid and other info, but he is not able to get the password. Here is the error from the get password if it can help to solve the probs: Error: connect ETIMEDOUT 192.168.1.11:8883 Node.js v18.12.1 |
|
Please try the latest beta 1.5.0-beta.0 (instructions for installation at https://github.com/homebridge-plugins/homebridge-roomba2/wiki/Pre-release-versions) as I have changed the connection logic to support more / newer Roomba's. |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
1 similar comment
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
|
This issue has been closed as no further activity has occurred. |
I get constant timeouts. Had odd returns when I pasted sudo npm install -g dorita980 command in tp://hoobs.local:9090
hoobs@hoobs:~ $
hoobs@hoobs:~ $ sudo npm install -g dorita980
[sudo] password for hoobs:
npm WARN deprecated har-validator@5.1.5: this library is no longer supported
npm WARN deprecated request-promise@4.2.6: request-promise has been deprecated because it extends the now deprecated request package, see request/request#3142
npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated request@2.88.2: request has been deprecated, see request/request#3142
changed 126 packages, and audited 127 packages in 20s
3 packages are looking for funding
run
npm fundfor details4 high severity vulnerabilities
To address all issues (including breaking changes), run:
npm audit fix --force
Run
npm auditfor details.hoobs@hoobs:~ $
Steps to Reproduce (for bugs)
It's my current log when I start Roomba2
Versions
The text was updated successfully, but these errors were encountered: