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

Allow setting of temperature unit (F or C) when setting temperature #39

Merged
merged 2 commits into from
Sep 1, 2024

Conversation

bm1549
Copy link
Owner

@bm1549 bm1549 commented Sep 1, 2024

Built on top of #37 (thank you @casebeer !)

Allows for the setting of temperature Unit (either Unit.FAHRENHEIT or Unit.CELSIUS) when using set_temperature

Supports fixing bm1549/home-assistant-frigidaire#56

Should also address remaining issues with #19 (as noted in #34 (comment))

casebeer and others added 2 commits August 30, 2024 02:01
Expose set_temperature_{f,c} functions wrapping the underlinging
Frigidaire actions Setting.TARGET_TEMPERATURE_{F,C}. This allows users
of this client (e.g. the Home Assistant component) to set a target
temperature in either F or C without performing temperature conversion;
callers that natively use F will set the TARGET_TEMPERATURE_F, while
callers that store C will set the TARGET_TEMPERATURE_C.

These two functions replace the previous `set_temperature()` function
(which implicitly required callers to convert target temperatures to
degrees Fahrenheit), and so constitute a breaking API change.

Supports fixing bm1549/home-assistant-frigidaire#56
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.

2 participants