Bosch Air Con: The Extra Buttons
Last time I got Home Assistant controlling my Bosch air con by decoding the remote’s mode, temperature and fan frames. That left a pile of buttons on the remote that I hadn’t touched: tilt, ion, the display and so on. As promised in a footnote, it was “a job for another day”, and today was that day, or at least the day I learned a few more.
This post only covers the buttons I’m (pretty) sure about. There were a few more captures that I haven’t pinned down yet, and they can wait for a follow-up. Consider this post field notes, rather than something to rely on for now.
A Second Blaster
I’ve picked up a second blaster, to cover another room, this time a Tuya TS1201 (_TZ3290_7v1k4vufotpowp9z), and unlike the ZG-IR01 it doesn’t need a custom quirk: ZHA’s built-in ZosungIRBlaster_ZS06 quirk picks it up as it is.
Learning a code works the same way as before, but what comes back doesn’t: Tuya’s own compressed format rather than the ZG-IR01’s Broadlink-style codes (the review has the details). Once decompressed, the timings matched the ZG-IR01 captures:
| Element | Duration |
|---|---|
| Header | ~4.4 to 4.6 ms mark and space |
| Bit mark | ~500 µs |
0 space | ~500 µs |
1 space | ~1.64 ms |
Here’s how the start of the tilt frame (more on that below) looks on the wire, most significant bit first:
B9~B9 (46)The header, then B9 and its inverse 46. Every bit is a 500 µs mark, and the length of the space after it says whether it’s a 0 or a 1.
I checked the decoding against a few codes I already knew from last time, and they came out the same.
The Feature Frames
Every frame here is a Coolix-style 6-byte frame, each byte followed by its inverse and the whole thing sent twice, just like the state frames from last time. The difference is the first byte. The state frames all start with B2, while the feature buttons use other headers:
| Header | Purpose |
|---|---|
B2 | Full state (mode, temperature, fan), covered last time |
B9 | Feature commands, F5 xx |
B5 | Features with separate on and off codes, F5 xx |
B9: Toggles
Here’s the tilt button, which moves the vane:
B9header46~headerF5always F50A~F505feature: tiltFA~featureTilt, B9 F5 05, sent twice
The fifth byte picks the feature:
| Feature byte | Button |
|---|---|
05 | Tilt (vane), short press |
41 | Ion |
09 | AC display on/off |
Ion and the display are toggles: pressing the button to turn it on and pressing it again to turn it off send exactly the same code1. That’s a bit of a pain for Home Assistant. IR is one-way, so if anyone uses the real remote, Home Assistant has no way of knowing whether the display is currently on or off2.
B5: Silent Mode
Silent mode is nicer. It has its own codes for on and off:
B5header4A~headerF5always F50A~F5B6feature: silent on49~featureSilent on, B5 F5 B6, sent twice
Silent on is B6 and silent off is B7, so the lowest bit is the switch: 0 for on and 1 for off.
1011011feature: silent0onThe feature byte, B6
Final Thoughts
So far these are mostly just captures. Sending already works with the new blaster, but these feature codes need more testing with the actual AC units.
There’s plenty still on the list: the rest of the tilt codes, a few frames I can’t explain yet, the Eco button (which sends nothing at all in heat mode) and, once it all checks out, adding the buttons to the bosch_ir integration. A project for another day, again.
-
I captured the display button three times, once by accident when I turned the display off without meaning to. ↩︎
-
Interestingly, the remote shows the state on its own screen, even though it only sends “toggle”. So it’s possible for the remote and the AC to get out of sync, say if one press doesn’t reach the AC, or I’ve made a mistake. ↩︎