I would like to request some improvements of the Aqara M3 hub IR remote functionality:
(1) when adding, for example, an LG TV, it will try to match 41 devices. The matching is done by common IR commands like power on. Because these commands common across many different models, it is likely to be a hit. As my TV matches the first option presented, it does not give me a lot of confidence that this is the best option. The devices identified by a number like ID1167 (the first option) which is not descriptive. There should be a better way to identify the correct (or best) option.
(2) The TV template used has a “10-key” button. My assumption was that it would be a button to navigate to another screen with a 10-key keypad, but it seems to be a single button which can have an IR code assigned. If there is a real 10-key keypad, it would be great if it would be documented how to use it, if there is not, it would be great if it can be implemented. Bonus request: the M3 hub is sold in Japan and it would be great if it would implement a 12-key keypad (all TVs sold in Japan use 12-keys, coming from the days that TV only supported 12 channel VHF; VHF is long gone, but the 12-key keypad is still there even on the most sophisticated TVs).
(3) the “custom” layout seems to be keys in a matrix. It would be great if the user could create a custom layout, either from scratch or based on an existing layout.
(4) when using IR commands in automation, it is important to be able to send “discrete” IR codes instead of “toggle” codes. For example, Power On or Power Off instead of Power Toggle. Another example is Input HDMI 1 instead of Input Toggle. This discrete codes cannot be learned from an existing remote. A lot of the discrete codes can be found on the Internet and most of the time they use Pronto HEX code. It would be great if IR commands can be assigned to buttons using HEX code.