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
Bump pyMicrobot to 0.0.10 #109628
Bump pyMicrobot to 0.0.10 #109628
Conversation
Ensure Microbot is connected after linking
Up version
Up version PyMicroBot==0.0.10
Up version PyMicroBot==0.0.10
hassfest fail
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please split the PRs and when creating the PR for the config flow fix, please add unit tests since the config flow is required to have 100% coverage
Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍 |
Correct integration type
revert changes
revert changes
not sure how to make the CI run again PRs have been split |
Proposed change
The integration has recently stopped working. Where the integration is already installed, the device is always unavailable. Installing from fresh is impossible as the config flow fails at the pairing stage.
This is part 1 to get it working again.
spycle/pyMicroBot@v0.0.9...v.0.0.10
Type of change
Additional information
Checklist
ruff format homeassistant tests
)If user exposed functionality or configuration variables are added/changed:
If the code communicates with devices, web services, or third-party tools:
Updated and included derived files by running:
python3 -m script.hassfest
.requirements_all.txt
.Updated by running
python3 -m script.gen_requirements_all
..coveragerc
.To help with the load of incoming pull requests: