-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
[OmniLink] Fix OmniLink temperature/humidity sensors #10130
Conversation
Signed-off-by: Ethan Dye <mrtops03@gmail.com>
Can you edit your first post to give why you are doing the fix? what symptoms? why is it needed? Someone may do a review that may not have the hardware and they will need some context and also it goes into the release notes that all users may click on to read the details. |
I‘m no longer part of the maintainer group, so: no. |
I'm sorry that it came to this. Thanks for all your contributions to this project over the past couple of years. Wishing you the best for the future! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Signed-off-by: Ethan Dye <mrtops03@gmail.com>
Signed-off-by: Ethan Dye <mrtops03@gmail.com> Signed-off-by: John Marshall <john.marshall.au@gmail.com>
Signed-off-by: Ethan Dye <mrtops03@gmail.com>
Signed-off-by: Ethan Dye <mrtops03@gmail.com>
The upstream code the allows connection to the OmniPro uses float values to convert into Omni values, therefore this change was necessary to allow for proper execution of setting temperature commands.
Signed-off-by: Ethan Dye mrtops03@gmail.com