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

Improve Ikea Idasen config flow error messages #101567

Merged
merged 1 commit into from
Oct 7, 2023

Conversation

abmantis
Copy link
Contributor

@abmantis abmantis commented Oct 7, 2023

Proposed change

There are a few issues with bleak with bluez, that don't manifest when using ESPHome BT Proxy.

One of them is the lack of an agent on bleak (hbldh/bleak#1434)
which is already mentioned on the docs (home-assistant/home-assistant.io#29207).
With ESPHome, it works.

Another difference is that when using ESPHome BT Proxy, the desk pairs even if it is not
in pairing mode anymore, while this does not happen with bleak/bluez.

Also, bleak/bluez fails to connect a lot more often than ESPHome.

Diff for dependecy update: abmantis/idasen-ha@1.4...1.4.1

Type of change

  • Dependency upgrade
  • Bugfix (non-breaking change which fixes an issue)
  • 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

Checklist

  • The code change is tested and works locally.
  • Local tests pass. Your PR cannot be merged unless tests pass
  • There is no commented out code in this PR.
  • I have followed the development checklist
  • I have followed the perfect PR recommendations
  • The code has been formatted using Black (black --fast homeassistant tests)
  • Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

If the code communicates with devices, web services, or third-party tools:

  • The manifest file has all fields filled out correctly.
    Updated and included derived files by running: python3 -m script.hassfest.
  • New or updated dependencies have been added to requirements_all.txt.
    Updated by running python3 -m script.gen_requirements_all.
  • For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
  • Untested files have been added to .coveragerc.

To help with the load of incoming pull requests:

@home-assistant
Copy link

home-assistant bot commented Oct 7, 2023

Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍

Learn more about our pull request process.

@home-assistant home-assistant bot marked this pull request as draft October 7, 2023 09:37
@abmantis abmantis marked this pull request as ready for review October 7, 2023 14:29
@home-assistant home-assistant bot requested a review from frenck October 7, 2023 14:30
@abmantis
Copy link
Contributor Author

abmantis commented Oct 7, 2023

I think this could also go into a point release for the current one, as we got quite a few user report just in the first days after release.

@frenck frenck added this to the 2023.10.2 milestone Oct 7, 2023
Copy link
Member

@frenck frenck left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, @abmantis 👍

../Frenck

@frenck frenck merged commit da3e36a into home-assistant:dev Oct 7, 2023
34 checks passed
@github-actions github-actions bot locked and limited conversation to collaborators Oct 8, 2023
@@ -64,6 +64,9 @@ async def async_step_user(
desk = Desk(None)
try:
await desk.connect(discovery_info.device, monitor_height=False)
except AuthFailedError as err:
_LOGGER.exception("AuthFailedError", exc_info=err)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Using both the exception logging method and exc_info isn't needed.

We normally don't log the stack trace if the exception is known.

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

Successfully merging this pull request may close these issues.

None yet

3 participants