Andee78
February 6, 2023, 5:52pm
105
Its still there…
Fifthy
February 21, 2023, 9:05am
106
Great integration, however is it possible to alter the colors of the map etc like you can in the xiaomi map extractor integration? I had the map extractor integration from before and changing the values in the configuration.yaml obviously doesn’t work for this.
Andee78
February 25, 2023, 11:30am
107
My integration keeps stopping connecting to my Roborock since a couple of days ago. I then have to uninstall the integration, restart Hassio and then reinstall it, then it works for a while. Anyone else experiencing problems too?
lanejonath
April 10, 2023, 8:02pm
109
It looks really great. I’m trying to reproduice the same things on my side, but I have some difficulties.
kiwikern
April 25, 2023, 6:12pm
110
The custom integration is integrated into core
home-assistant:dev ← Lash-L:roborock_hacs_conversion
opened 05:51PM - 09 Mar 23 UTC
<!--
You are amazing! Thanks for contributing to our project!
Please, DO N… OT DELETE ANY TEXT from this template! (unless instructed).
-->
## Breaking change
<!--
If your PR contains a breaking change for existing users, it is important
to tell them what breaks, how to make it work again and why we did this.
This piece of text is published with the release notes, so it helps if you
write it towards our users, not us.
Note: Remove this section if this PR is NOT a breaking change.
-->
The current Roborock integration which is just an alias for Xiaomi Miio will no longer be an alias, but instead will be this integration. I'm not sure what the best way to handle this is. In my opinion, a dedicated Roborock integration should take priority over an alias integration. But I'm not sure how that will affect current users
## Proposed change
<!--
Describe the big picture of your changes here to communicate to the
maintainers why we should accept this pull request. If it fixes a bug
or resolves a feature request, be sure to link to that issue in the
additional information section.
-->
This is a conversion of the popular hacs integration: https://github.com/humbertogontijo/homeassistant-roborock. It aims to allow users to be able to use the Roborock app and the home assistant integration, rather than having to use the Xiaomi app. The roborock app gives a significantly better use experience than the Xiaomi app for Roborock users. The aim is also to provide better support for Roborock specific devices.
Because this is a HACS conversion, the original project was very large. I tried to remove things that would not be needed for an initial PR. Some files are still rather larger as it was difficult to determine what was worth removing to keep the PR small and what was functionality that it didn't make sense to remove( A large portion of this PR is from test on vacuum.py. I could potentially remove them to keep the PR smaller, but I wasn't sure if it made sense)
Here are the features that exist that were removed for this PR and will be added in future PRS once this is merged in:
- Email/Password login
- Map support
- Binary Sensors
- Sensors
- Option Flow
- Manual Vacuum control
- go to x y location
- mopping
- services
This integration uses the following pypi package: https://github.com/humbertogontijo/python-roborock
As a note, the mock data is around 1/3 of this pr, so it is not quite as big as it originally seems
## Type of change
<!--
What type of change does your PR introduce to Home Assistant?
NOTE: Please, check only 1! box!
If your PR requires multiple boxes to be checked, you'll most likely need to
split it into multiple PRs. This makes things easier and faster to code review.
-->
- [ ] Dependency upgrade
- [ ] Bugfix (non-breaking change which fixes an issue)
- [x] New integration (thank you!)
- [ ] New feature (which adds functionality to an existing integration)
- [ ] Deprecation (breaking change to happen in the future)
- [ ] Breaking change (fix/feature causing existing functionality to break)
- [ ] Code quality improvements to existing code or addition of tests
## Additional information
<!--
Details are important, and help maintainers processing your PR.
Please be sure to fill out additional details, if applicable.
-->
- This PR fixes or closes issue: fixes #
- This PR is related to issue:
- Link to documentation pull request: https://github.com/home-assistant/home-assistant.io/pull/26520
## Checklist
<!--
Put an `x` in the boxes that apply. You can also fill these out after
creating the PR. If you're unsure about any of them, don't hesitate to ask.
We're here to help! This is simply a reminder of what we are going to look
for before merging your code.
-->
- [x] The code change is tested and works locally.
- [x] Local tests pass. **Your PR cannot be merged unless tests pass**
- [x] There is no commented out code in this PR.
- [x] I have followed the [development checklist][dev-checklist]
- [x] I have followed the [perfect PR recommendations][perfect-pr]
- [x] The code has been formatted using Black (`black --fast homeassistant tests`)
- [x] Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- [x] Documentation added/updated for [www.home-assistant.io][docs-repository]
If the code communicates with devices, web services, or third-party tools:
- [x] The [manifest file][manifest-docs] has all fields filled out correctly.
Updated and included derived files by running: `python3 -m script.hassfest`.
- [x] New or updated dependencies have been added to `requirements_all.txt`.
Updated by running `python3 -m script.gen_requirements_all`.
- [x] For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
- [x] Untested files have been added to `.coveragerc`.
<!--
This project is very active and we have a high turnover of pull requests.
Unfortunately, the number of incoming pull requests is higher than what our
reviewers can review and merge so there is a long backlog of pull requests
waiting for review. You can help here!
By reviewing another pull request, you will help raise the code quality of
that pull request and the final review will be faster. This way the general
pace of pull request reviews will go up and your wait time will go down.
When picking a pull request to review, try to choose one that hasn't yet
been reviewed.
Thanks for helping out!
-->
To help with the load of incoming pull requests:
- [x] I have reviewed two other [open pull requests][prs] in this repository.
[prs]: https://github.com/home-assistant/core/pulls?q=is%3Aopen+is%3Apr+-author%3A%40me+-draft%3Atrue+-label%3Awaiting-for-upstream+sort%3Acreated-desc+review%3Anone+-status%3Afailure
<!--
Thank you for contributing <3
Below, some useful links you could explore:
-->
[dev-checklist]: https://developers.home-assistant.io/docs/en/development_checklist.html
[manifest-docs]: https://developers.home-assistant.io/docs/en/creating_integration_manifest.html
[quality-scale]: https://developers.home-assistant.io/docs/en/next/integration_quality_scale_index.html
[docs-repository]: https://github.com/home-assistant/home-assistant.io
[perfect-pr]: https://developers.home-assistant.io/docs/review-process/#creating-the-perfect-pr
Here it is: Roborock - Home Assistant
5 Likes
Lash-L
April 29, 2023, 1:07am
111
Starting to be integrated! Don’t expect all of the features straight out of the gate. It will be a while until all of the custom component features are in the core version.
2 Likes
fr0z3n
May 21, 2023, 7:22am
112
Has anyone identified a way to tell the robot to “wash mop” from home assistant?
S7 maxV Ultra Dock using the latest HACS version of the integration
I found the send command for emptying the dust bin (app_start_collect_dust).
But could not find the send command for washing the mop.
EDIT: Nevermind - found it - it is app_start_wash
splat10
May 23, 2023, 7:18pm
113
The best thing i’ve got here is the ability to now automate going to my pin location at a specific time and day of the week for cleaning, water fill, and mop change. The goto service is great, the biggest challenge was figuring out the coordinates of my pin. Had to use the xiomi map and look at the card configuration YAML based on my room borders to get it close then dial it in by trial and error. What would be great is if there was an entity for current position (x,y) or x pos and y pos. It must be available since the map shows the bot.
Really dumb question, but how do I use this in automations. I can do the triggers, the question is regarding the actions.
Overnight, when I go to bed, I’m wanting to have fan speed: Quiet
I thought this would work, but it doesnt seem to change the fan speed. Where am I wrong?
This is for overnight, when the alarm turns on. (Let Geoff clean works, but not the changing speeds/intensity).
thekow
July 6, 2023, 9:30pm
115
I have the q7 max. I have used the integrated roborock integration and it works fine. But do I need to add a different integration and do the token extraction still to get the map?
Does anyone have issues with the new core integration? It used to work before but now all I get is@gmail.com ’ for roborock integration not ready yet: There are no devices that can currently be reached.; Retrying in background "
Should I switch over to the core integration, as opposed the GitHub repository custom integration? As of this morning for some reason none of my vacuum’s entities are availabled - several reloads/restarts have not fixed the issue.
cmartens
December 10, 2023, 2:27pm
118
Hi Adam, I like the Roborock S7 Max image that you are using in your vacuum card. Can you please share the file? Thanks in advance. Kind regards, Corne
Any idea how I can attach the map to a notification? Map is in image.roborock_s6_maxv_nedervaningen but camera.snapshot doesn’t work to save it and I can’t use it directly in a notification.
bobzer
December 23, 2023, 3:01am
120
I feel like this could help you
At least it was a good start for me
If you look closely its a bad edit. attached the original too
1 Like
