Correct Govee H5071 device detection - #1588
Merged
Ernst79 merged 1 commit intoSep 8, 2026
Merged
Conversation
Ernst79
approved these changes
Sep 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
Correct the device-type detection for Govee H5071 sensors.
Problem
The Govee parser compared the service UUID against the decimal literal
5071instead of the hexadecimal value0x5071.As a result, advertisements from real H5071 devices could never match the intended H5071 branch and were incorrectly identified as H5051.
Fix
Use the correct hexadecimal service UUID value when detecting H5071 devices.
H5071 advertisements are now identified correctly, while existing H5051 and other Govee model handling remains unchanged.
A regression test covers H5071 detection.