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

mirobo id_file is not being created automatically #1205

Closed
fabian727 opened this issue Dec 2, 2021 · 3 comments · Fixed by #1207
Closed

mirobo id_file is not being created automatically #1205

fabian727 opened this issue Dec 2, 2021 · 3 comments · Fixed by #1207
Labels

Comments

@fabian727
Copy link

I followed the manual and got stuck at the step to install the firmware:
mirobo --token XXXXXXXXXXXXXXXX --ip ROBOT_IP_ADDRESS update-firmware path/to/built/image.pkg

instead of the update procedure, I got errors.
I got them fixed by creating an id file with {} as content and reference it.
Instead of above command, I would suggest to use:

echo {} >> id_file.txt mirobo --id-file id_file.txt --token XXXXXXXXXXXXXXXX --ip ROBOT_IP_ADDRESS update-firmware path/to/built/image.pkg

Afterwards I also had to downgrade the producers firmware and everything worked like it should.

Thank you for your service, time and effort in this project. I wouldn't have bought an automatic cleaner, which phones home.

@fabian727 fabian727 added the bug label Dec 2, 2021
@rytilahti rytilahti changed the title Install Process lags id_file mirobo id_file is not being created automatically Dec 2, 2021
@rytilahti
Copy link
Owner

Hi and thanks for the report, glad that you like the project :-)

Some recent change broke the id file creation logic. Until that is fixed, creating that file manually ($HOME/.cache/python-miio/python-mirobo.seq with {} as content) also works if you want to avoid using --id-file.

@fabian727
Copy link
Author

can you enhance the manual or fix it? Did take the most time of the installation procedure to get the googling done ;)

@rytilahti
Copy link
Owner

The linked PR should fix this, I suppose it wasn't caught earlier as most of the users (if existing) had already used mirobo already at least once, so it was working just fine :-)

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

Successfully merging a pull request may close this issue.

2 participants