Thank you for submitting your repository to HACS (Home Assistant Community Store).

Your submission is in the review queue:
Your repository is waiting to be reviewed and included in HACS.

You can view the current queue here. Pull requests are processed in the order they were created, oldest first.

What to avoid during review:
To help reviewers work efficiently, don't do the following:

• Comment on the pull request - The reviewer will contact you when they have feedback or questions.
• Open a new pull request - This won't speed up the process and creates duplicate work.
• Ask followers to comment on the pull request - This won't speed up the process and may delay your review.
• Merge in the default branch - Only do this if a maintainer asks you to resolve a merge conflict.

If you need to make changes:
You can continue updating your repository while waiting for review. Changes to your repository will be reflected when the reviewer examines it. Only comment on the pull request if you need to withdraw your submission or have critical information for reviewers.

About draft pull requests:
Draft pull requests aren't included in the review queue. Your pull request may be marked as draft by a reviewer if issues need to be addressed. Once you've resolved all issues, mark it as ready for review to re-enter the queue.

What happens next:
Once a reviewer examines your submission, they'll either:

• Approve and merge your pull request if everything meets the requirements
• Request changes or ask questions if adjustments are needed

Hi @frenck, thanks for the review! Both issues are addressed in v2.2.6.

1. config_flow.py line 156 — removed the erroneous await. async_show_form is not a coroutine and now returns the form result directly, so the no_devices error path displays the error form instead of crashing.

2. Reauth / reconfigure now reload the entry — both SOURCE_REAUTH and SOURCE_RECONFIGURE branches in async_step_device now use self.async_update_reload_and_abort(entry, data=data, unique_id=dev_id), so after a ConfigEntryAuthFailed the new token is saved and the entry is immediately set up again (no error state until restart), with the unique id check matching the correct entry.

Release: https://github.com/RockJesus/ha-jiachao/releases/tag/v2.2.6
HACS Action: https://github.com/RockJesus/ha-jiachao/actions/runs/40212181633/job/121225570423
Hassfest: https://github.com/RockJesus/ha-jiachao/actions/runs/40212181589/job/121225570107

All checks green. Thanks!