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

Pending documentation for “low-code” Room-Specific Roomba clean jobs #37195

Open
kylehakala opened this issue Jan 29, 2025 · 1 comment
Open

Comments

@kylehakala
Copy link
Contributor

kylehakala commented Jan 29, 2025

Feedback

Hey there!

I’ve made a PR to add in the steps to capture the Room/Zone ID and other map IDs needed to create custom cleaning jobs for a Roomba to go to a specific room/zone(s).

Check it out here — I’m open to feedback of course too! #37134

(Pardon the duplication of the issue, I somehow managed to fill out the issue form without the URL field and it kept the bot from properly tagging the issue)

Thanks for the consideration here!

-Kyle

URL

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

Version

No response

Additional information

The steps are a combination of a couple years worth of forum posts and Reddit threads and blog posts that outlined parts of the process using tail commands, or spinning up the external docker container to run the query for the last command.

After so many awesome improvements to both the Roomba integration and the HA platform, this can now be accomplished using only the native HA Debug logging with the built-in log viewer in settings (no need to launch a command line or download extra tools).

The only barrier to entry is the willingness to visually look at the JSON in the search results in the log viewer UI to copy the various IDs. And maybe a little patience.

It seems that baking this data into sensors or attributes or diagnostic sensors isn’t an ideal setup to implement based on past PRs and conversations around adding that functionality (mostly around the sheer mass of useless data that would pile up inside Home Assistant).

A relatively clean documented process can close the gap on users scouring for solutions on how to leverage existing Rooms or Zones in their iRobot app, and more technical users may find additional information in the logs that they could use to create more advanced automated jobs for triggering multiple Roomba passes in a room, etc.

Let me know if there is any feedback over on the PR!

@home-assistant
Copy link

Hey there @pschmitt, @cyr-ius, @shenxn, @Orhideous, mind taking a look at this feedback 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 feedback.
  • @home-assistant rename Awesome new title Renames the feedback.
  • @home-assistant reopen Reopen the feedback.
  • @home-assistant unassign roomba Removes the current integration label and assignees on the feedback, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information) to the feedback.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information) on the feedback.

@kylehakala kylehakala marked this as a duplicate of #37191 Jan 29, 2025
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

1 participant