Verify that the MAC address that Fully Kiosk reported is usable #94887
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed change
On modern Android devices, the real MAC address is not exposed to applications, therefore, what Fully Kiosk reports is usually not usable as an ID.
On Android 13 (Samsung Galaxy Tab A7 Lite), Fully Kiosk reports "02:00:00:00:00:00" if "randomized MAC" is disabled, which leads to merging unrelated issues (similar issue to #77722).
This PR enhances MAC validation: if the second least significant bit is set in the MAC address, it's a locally administered MAC and should not be used as an identifier in HA.
Type of change
Additional information
I contacted Fully Kiosk author about this issue, and here is what he said:
Checklist
black --fast 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: