I have decoded entire ClimaButler protocol.
As far as I understand, you're using an opaque 64 bit integer as data to send to Climatebutler devices.
What I have done, is reverse-engineer that bitstream of 52 bit and wrote an encoder and a decoder.
This allows for adjusting temperature, power, fan speed, mode, swing, and timers independently without capturing a billion individual IR readings from an existing remote and sending those.
You can find a full breakdown of the protocol here, a reference implementation here, and additional notes here.
I reverse-engineered the protocol using an RM4 Mini and the climatebutler remote model AR-715.
My decode.ts in the same repo is largely based on your work in src/ir_ClimaButler.cpp, so I am taking the opportunity here to contribute back.
Note to that this file in particular is AI generated (the rest of the repo is not), so expect low quality code.
If you got any questions regarding implementation or protocol details, feel free to reach out here or on Discord @j0code.
I have decoded entire ClimaButler protocol.
As far as I understand, you're using an opaque 64 bit integer as data to send to Climatebutler devices.
What I have done, is reverse-engineer that bitstream of 52 bit and wrote an encoder and a decoder.
This allows for adjusting temperature, power, fan speed, mode, swing, and timers independently without capturing a billion individual IR readings from an existing remote and sending those.
You can find a full breakdown of the protocol here, a reference implementation here, and additional notes here.
I reverse-engineered the protocol using an RM4 Mini and the climatebutler remote model AR-715.
My decode.ts in the same repo is largely based on your work in
src/ir_ClimaButler.cpp, so I am taking the opportunity here to contribute back.Note to that this file in particular is AI generated (the rest of the repo is not), so expect low quality code.
If you got any questions regarding implementation or protocol details, feel free to reach out here or on Discord @j0code.