Add Fahrenheit support for Coolix #2214
Open
Conversation
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
gongloo
added a commit
to gongloo/OutEquipAC
that referenced
this pull request
Jul 30, 2025
This relies on https://github.com/gongloo/IRremoteESP8266 having been cloned alongside this project, until crankyoldgit/IRremoteESP8266#2214 lands.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I have an air conditioner for my van sold by OutEqiupPro which shows Fahrenheit values on its display, and has a Fahrenheit mode on its remote (switched into by pressing both Turbo and Swing buttons simultaneously). Even if the unit itself is somewhat reprehensible, it does have the advantage of finer granularity for this unit!
Unfortunately the implementation in Coolix for this remote is rather hacky: apparently a couple of the parity bits are overridden to indicate the Fahrenheit range being used. Yuck. I dumped all of the relevant values for my use case into a spreadsheet and worked out the encoding with the help of my favorite LLM friend Gemini. Magical!
I've implemented some decoding and encoding logic for this harebrained scheme. Happy to take suggestions on how to improve this so that it's more intelligible, and/or matches the coding style of this repo, etc. I'm also not sure if this PR even has a place here, since this might be a special-case for just one make; let me know if that's the case and I'll close it out.