Skip to content
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

Integration "iRobot Roomba and Braava" fails to configure (504 Gateway Time-out) #83255

Closed
lindhe opened this issue Dec 4, 2022 · 10 comments
Closed

Comments

@lindhe
Copy link
Contributor

lindhe commented Dec 4, 2022

The problem

When I try to setup the "iRobot Roomba and Braava" integration, I get an error message and the configuration fails. Nothing pops up in the logs during the process.

Initially Eventually
Screenshot from 2022-12-04 16-31-19 Screenshot from 2022-12-04 16-31-46

What version of Home Assistant Core has the issue?

core-2022.11.5

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

Integration causing the issue

iRobot Roomba and Braava

Link to integration documentation on our website

https://www.home-assistant.io/integrations/roomba/

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

@home-assistant
Copy link

home-assistant bot commented Dec 4, 2022

Hey there @pschmitt, @cyr-ius, @shenxn, mind taking a look at this issue as it has been labeled with an integration (roomba) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of roomba can trigger bot actions by commenting:

  • @home-assistant close Closes the issue.
  • @home-assistant rename Awesome new title Change the title of the issue.
  • @home-assistant reopen Reopen the issue.
  • @home-assistant unassign roomba Removes the current integration label and assignees on the issue, add the integration domain after the command.

(message by CodeOwnersMention)


roomba documentation
roomba source
(message by IssueLinks)

@ptoal
Copy link

ptoal commented Dec 8, 2022

I'm experiencing the same issue. Roomba 960 Firmware: 2.4.16-126. I recently discovered that my roomba was not connected to Home Assistant, so deleted it, and am trying to re-add it. I most commonly get this error:

Config flow could not be loaded: <html><body><h1>504 Gateway Time-out</h1> The server didn't respond in time. </body></html>

Sometimes I get this:

Config flow could not be loaded: 500 Internal Server Error Server got itself in trouble

I see the following in the core logs:

Logger: aiohttp.server
Source: components/roomba/config_flow.py:331
First occurred: 10:55:28 (4 occurrences)
Last logged: 11:35:28

Error handling request
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/aiohttp/web_protocol.py", line 433, in _handle_request
    resp = await request_handler(request)
  File "/usr/local/lib/python3.10/site-packages/aiohttp/web_app.py", line 504, in _handle
    resp = await handler(request)
  File "/usr/local/lib/python3.10/site-packages/aiohttp/web_middlewares.py", line 117, in impl
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 60, in security_filter_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 222, in forwarded_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 28, in request_context_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 81, in ban_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 236, in auth_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/view.py", line 136, in handle
    result = await result
  File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 148, in post
    return await super().post(request)
  File "/usr/src/homeassistant/homeassistant/components/http/data_validator.py", line 73, in wrapper
    result = await method(view, request, data, *args, **kwargs)
  File "/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py", line 71, in post
    result = await self._flow_mgr.async_init(
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 226, in async_init
    flow, result = await task
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 253, in _async_init
    result = await self._async_handle_step(flow, flow.init_step, data, init_done)
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 368, in _async_handle_step
    result: FlowResult = await getattr(flow, method)(user_input)
  File "/usr/src/homeassistant/homeassistant/components/roomba/config_flow.py", line 140, in async_step_user
    devices = await _async_discover_roombas(self.hass, self.host)
  File "/usr/src/homeassistant/homeassistant/components/roomba/config_flow.py", line 331, in _async_discover_roombas
    discovered = await hass.async_add_executor_job(discovery.get_all)
  File "/usr/local/lib/python3.10/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/local/lib/python3.10/site-packages/roombapy/discovery.py", line 32, in get_all
    response = self._get_response()
  File "/usr/local/lib/python3.10/site-packages/roombapy/discovery.py", line 53, in _get_response
    data = raw_response.decode()
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xf3 in position 0: invalid continuation byte

@nukefrenzy
Copy link

Possibly a similar issue on my 960 running firmware v2.4.13-119:

image

Logs show the following:

Logger: roombapy.remote_client
Source: /usr/local/lib/python3.10/site-packages/roombapy/remote_client.py:63
First occurred: 12:02:40 PM (5 occurrences)
Last logged: 12:08:01 PM
Unable to connect to 192.168.20.34

Logger: roombapy.remote_client
Source: /usr/local/lib/python3.10/site-packages/roombapy/remote_client.py:58
First occurred: 12:02:40 PM (15 occurrences)
Last logged: 12:08:01 PM
Can't connect to 192.168.20.34, error: [Errno 111] Connection refused

@MinimalMule
Copy link

sounds suspiciously like the issue I've reported here, seems that in general this integration is now broken...

@issue-triage-workflows
Copy link

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.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

@lindhe
Copy link
Contributor Author

lindhe commented Mar 17, 2023

It's still relevant and should stay open.

@Andystew94
Copy link

Any progress on this?

@RTS007
Copy link

RTS007 commented Jul 31, 2023

+1

@issue-triage-workflows
Copy link

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.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

@issue-triage-workflows issue-triage-workflows bot closed this as not planned Won't fix, can't repro, duplicate, stale Nov 5, 2023
@hughb8on
Copy link

not stale

@github-actions github-actions bot locked and limited conversation to collaborators Dec 12, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

7 participants