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

[irobot] Request for more detailed authentication steps when using config files #10388

Closed
vidia opened this issue Mar 25, 2021 · 1 comment · Fixed by #17806
Closed

[irobot] Request for more detailed authentication steps when using config files #10388

vidia opened this issue Mar 25, 2021 · 1 comment · Fixed by #17806

Comments

@vidia
Copy link

vidia commented Mar 25, 2021

When I was configuring my Roomba I ran in to two issues that were not covered in the documentation.

First (a small nit) the "Home" button is not present on all Roomba devices. On my Roomba 675 I needed to press "Dock" which was not immediately clear.

Second (the main issue I have), when using config files alongside MainUI in Openhab3, it is not immediately clear where to find the Roomba password after pressing the button. I'd like to suggest one of two solutions:

  1. Add a mention to the docs that the password will be populated in the Thing and that you must copy that into the config files in order for it to persist. Without this detail it causes confusion because the Roomba will appear to work temporarily, but as soon as the Things file is edited, the password is lost and the button needs to be pushed again. I believe this issue is specific to working with config files.
  2. Make a code change to log out the password to the log file so config file users can see and copy the password easily.
@lsiepel lsiepel changed the title [roomba] Request for more detailed authentication steps when using config files [irobot] Request for more detailed authentication steps when using config files Nov 25, 2024
@lsiepel
Copy link
Contributor

lsiepel commented Nov 25, 2024

  1. Should be fixed by the related PR.
  2. It is a bad practice to log passwords to log files (as they tend to end up everywhere). I would call that a won't fix.

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

Successfully merging a pull request may close this issue.

2 participants