Why there is a generalized IRac.cpp for Air Conditioning devices but not for other device types?

[hem-bhagat-tark]

I landed on this repository while exploring Tasmota IR Communication. There I saw two commands, IRsend and IRHVAC. IRsend needs to manually send IR Codes for each control action. Whereas using IRHVAC I can simply send values like Power: On, Mode: Auto, .... I found out that HVAC stands for Heating, Ventilation, and Air Conditioning devices.

Since Tasmota uses this library I started exploring this. Here, I see there is a generalized IRac.cpp that can be used to control ACs and there are specific implementations for each vendor like ir_Bosch.cpp, ir_Haier.cpp, etc. But for device types other than ACs, IRsend.cpp is supposed to be used. While using IRsend.cpp I manually need to send the IR codes.

I would like to know why there is no generalized implementation for other device types like IRtv.cpp for TVs. Is there anything fundamentally different about HVAC devices and other device types?

[NiKiZe]

There is no need, and it would be to large.

With ACs you need to keep state, since a IR sequence is not just the button that is pressed, but all the data on the remotes display.

For TVs etc it is one code per button, no state is needed. (And how many different remotes are there?) There is collections for that kind of codes, that kind of data does not make sense to keep in a programming language.

[liudr]

I had the same question so thanks for the response. I was under the impression that each AC command contains everything including set temp and other options but this really clarifies it.