Four fixes and a safeguard.
Dyson fans that ignore presses
A Dyson fan's rolling counter belongs to the remote, not to each button, and has three values. HAIR kept one per button, so a press after a different button could reuse the value the fan last accepted, and the fan ignored it. HAIR now keeps one counter per device, steps it in the order the handset uses, and picks up from a handset press that a receiver hears. Thanks to @channafam for the captures that settled it (#33).
A temperature call that names a mode
climate.set_temperature with an hvac_mode now switches to that mode, so "heat to 26" sent while the unit is in cool or off goes out as heat at 26. With the mode set to off, the unit turns off and keeps the temperature for next time.
Toggle power buttons
A fan, TV, light, switch or air conditioner whose only power code is a toggle no longer turns on when asked to turn off while HAIR already shows it off, or the reverse. HAIR now sends nothing in that case; separate on and off codes are always sent. A power sensor or on/off entity on the device keeps the state HAIR shows right. Reported by @channafam (#229).
Long sends heard as presses
After a long send of repeated frames, the last frames HAIR's own receivers hear are no longer mistaken for a press of the remote.
Library decoders
HAIR now keeps using its own decoder for a protocol until it has checked that the infrared library's decoder reads the same codes the same way. Nothing changes on any current Home Assistant release. The point is that a future library update can't relabel saved buttons on its own.
Full changelog: CHANGELOG.md