Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Parse temperature and humidity from GVH5101 #13

Closed
wants to merge 1 commit into from

Conversation

zrhutto
Copy link
Contributor

@zrhutto zrhutto commented Jan 11, 2022

Small patch to correctly parse temperature and humidity information from GVH5101 devices that has reports values at different offsets than GVH5075/GVH5074. Reusing the existing file given the similarities of the two devices. Device type detection based on signature in advertising packet.

I could see an argument in keeping device type files separate (i.e., a new file for GVH5101), but it felt somewhat wasteful with ~80% of the file staying the same.

Small patch to correctly parse temperature and humidity information from GVH5101 devices that has reports values at different offsets than GVH5075/GVH5074. Reusing the existing file given the similarities of the two devices. Device type detection based on signature in advertising packet.
@tony-fav
Copy link
Owner

tony-fav commented Jan 11, 2022

This is great!

We discussed this in discord, but I'm putting here for the record.

Referring to another reference, it looks like that model number needs the same treatment of negative temp as the 5075. So, we can move the block that flips the basenum to after the device choice if statement.

Also, if you refer to the ATCpvvx driver, I list out 3 aliases for the driver at the bottom This should now support: GVH5072, GVH5075, GVH5101, and GVH5102. So, let's do the same thing here. There's also a spot in blerry_main.be to edit here. Can you make sure it has all 4? Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants