Fix Victron BLE false reauth on unrecognised advertisement mode bytes

[rajlaud]

Proposed change

Guard the reauth key-validity check so it only runs on BLE advertisements
whose device type detect_device_type() actually recognises.

Advertisements with unrecognised mode bytes caused validate_advertisement_key()
to return False (because it calls detect_device_type() internally, which
returns None). The reauth guard counted this as a key failure, and after 3 such
advertisements the integration would incorrectly trigger a reauth flow telling
users their encryption key had expired — even though the key was perfectly valid.

Unrecognised advertisements are now treated as neutral: they neither increment
nor reset the consecutive failure counter.

Type of change

• Bugfix (non-breaking change which fixes an issue)

Additional information

• This PR fixes or closes issue: fixes Victron BLE Expired Key Errors in 2026.4.2 #168019
• This PR is related to issue:
• Link to documentation pull request:
• Link to developer documentation pull request:
• Link to frontend pull request:

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.

[Copilot]

Pull request overview

This PR fixes a false reauth flow in the Victron BLE integration by ensuring the “consecutive key failure” counter is only affected by advertisements that the parser can actually classify, preventing unrecognised mode bytes from being treated as key failures.

Changes:

• Guard the reauth/key-validity logic so it only runs for instant-readout (0x10) advertisements with a recognised device type.
• Treat unrecognised advertisements as neutral (do not increment or reset the failure counter).
• Add regression tests/fixtures covering unrecognised-mode advertisements and mixed sequences (bad → bad → unrecognised → bad).

Show a summary per file

File	Description
homeassistant/components/victron_ble/init.py	Adds a recognisability guard (0x10 + detect_device_type) before counting key validation failures for reauth.
tests/components/victron_ble/fixtures.py	Adds a BluetoothServiceInfo fixture with an unrecognised mode byte for regression testing.
tests/components/victron_ble/test_sensor.py	Adds helpers and tests ensuring unrecognised-mode advertisements are neutral and don’t cause false reauth.

Copilot's findings

• Files reviewed: 3/3 changed files
• Comments generated: 0

[Copilot]

Pull request overview

Fixes a Victron BLE false reauth trigger by ensuring the “consecutive key failures” counter is only affected by advertisements whose device type is actually recognized by the parser.

Changes:

• Guard the reauth key-validity check to run only on recognizable instant-readout Victron advertisements; treat unrecognized mode bytes as neutral.
• Add a new test fixture representing an unrecognized mode byte advertisement.
• Add regression tests to ensure unrecognized-mode advertisements do not trigger reauth and do not reset/increment the failure counter.

Show a summary per file

File	Description
homeassistant/components/victron_ble/init.py	Updates the reauth guard logic to ignore unrecognized advertisements so they don’t cause false reauth flows.
tests/components/victron_ble/fixtures.py	Adds a BLE service-info fixture with an unrecognized mode byte for regression testing.
tests/components/victron_ble/test_sensor.py	Adds helper injection + two regression tests covering the neutral behavior and counter semantics.

Copilot's findings

• Files reviewed: 3/3 changed files
• Comments generated: 0 new