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

Roborock issue with second Vacuum #134358

Open
CrazyAngelFir3 opened this issue Dec 31, 2024 · 6 comments
Open

Roborock issue with second Vacuum #134358

CrazyAngelFir3 opened this issue Dec 31, 2024 · 6 comments

Comments

@CrazyAngelFir3
Copy link

The problem

i have 2 Roborock hoovers, one "upstairs" and one "Downstairs". it wont add the second hoover to my account although they are both working fine in the app.

What version of Home Assistant Core has the issue?

Os

What was the last working version of Home Assistant Core?

Os

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Roborock

Link to integration documentation on our website

No response

Diagnostics information

config_entry-roborock-01JG8TY76FRV98FJ721EA31WKV (1).json

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Logger: homeassistant.components.roborock
Source: components/roborock/__init__.py:219
integration: Roborock (documentation, issues)
First occurred: December 29, 2024 at 10:10:22 AM (4 occurrences)
Last logged: 5:26:18 PM

Not setting up Upstairs because the coordinator failed to get data for the first time using the offline client Please create an issue with the following error included: 'int' object has no attribute 'name'

Additional information

No response

@home-assistant
Copy link

Hey there @Lash-L, mind taking a look at this issue as it has been labeled with an integration (roborock) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of roborock can trigger bot actions by commenting:

  • @home-assistant close Closes the issue.
  • @home-assistant rename Awesome new title Renames the issue.
  • @home-assistant reopen Reopen the issue.
  • @home-assistant unassign roborock Removes the current integration label and assignees on the issue, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


roborock documentation
roborock source
(message by IssueLinks)

@svzi
Copy link

svzi commented Dec 31, 2024

I'm experiencing the exact same issue. The first device get's integrated, but the second doesn't show up in Home Assistant. I've already removed the integration and re-added, but that didn't help either.

@Lash-L
Copy link
Contributor

Lash-L commented Jan 1, 2025

If your second device is a Q Revo Master, this is fixed in 2025.1 when it comes out.

@CrazyAngelFir3
Copy link
Author

CrazyAngelFir3 commented Jan 1, 2025 via email

@svzi
Copy link

svzi commented Jan 1, 2025

For me that's the case as well. Thanks for the heads up. Now waiting for the update to arrive. 😎

@ericgross
Copy link

I have a Q5 that is not showing up - do you think that is fixed similarly? Thank you for your efforts!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants