Skip to content

Conversation

@starkillerOG
Copy link
Contributor

@starkillerOG starkillerOG commented Nov 27, 2025

Breaking change

Proposed change

Bump reolink-aio to 0.16.6:
Additions:

Bug fixes:

Optimizations:

Full Changelog: starkillerOG/reolink_aio@0.16.5...0.16.6

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

  • I understand the code I am submitting and can explain how it works.
  • 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 Ruff (ruff format homeassistant tests)
  • Tests have been added to verify that the new code works.
  • Any generated code has been carefully reviewed for correctness and compliance with project standards.

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.

To help with the load of incoming pull requests:

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

This PR bumps the reolink-aio dependency from version 0.16.5 to 0.16.6 for the Reolink integration. The upstream library update includes bug fixes (KeyError fixes, alarm support checks), new Baichuan protocol fallback support for various commands, and optimizations for Baichuan-only cameras.

Key Changes

  • Updated dependency version from 0.16.5 to 0.16.6 across all requirement files
  • Upstream library adds Baichuan protocol fallbacks for alarm and encoding management
  • Upstream library fixes KeyError when chime name not present in DingDongOpt

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File Description
requirements_test_all.txt Updated reolink-aio test dependency to version 0.16.6
requirements_all.txt Updated reolink-aio runtime dependency to version 0.16.6
homeassistant/components/reolink/manifest.json Updated reolink-aio requirement to version 0.16.6 in integration manifest

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, @starkillerOG 👍

../Frenck

                       

Blogging my personal ramblings at frenck.dev

@frenck frenck merged commit a00923c into home-assistant:dev Nov 27, 2025
68 of 69 checks passed
@starkillerOG starkillerOG deleted the bump_reolink0166 branch November 27, 2025 09:23
frenck pushed a commit that referenced this pull request Nov 27, 2025
@github-actions github-actions bot locked and limited conversation to collaborators Nov 28, 2025
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.

Failed setup, will retry: 'name' Reolink integration fails to change motion sensitivity of RLC-410-5MP camera

2 participants