As you can see in the video the buttons randomly stop working and don’t send the infrared commands.
This can’t be relied on when used remotely or for automations, if you are not in the same room you don’t know if it worked or not.
Recent purchase, less than 2 weeks old, updated to the latest firmware, there video is taken after a fresh restart.
Hi!
Works like a charm with my AC.
Yes you have to be patient between two button pushes, but I guess it is a safety not to “blur” the IR signal.
Also it has a status return, so you know if it worked.
Because of using HomeKit I don’t have an AC controller in Apple Home. I don’t mind it so much now 
You are not missing much, the integration with Apple Home via Matter also has other issues, it sometimes sends 3 commands instead of one.
For example I have an apple home automation to turn it off when leaving but instead of turning the ac off, it first turns it off, then back on but set to heat, then sets the temp. Other times it just works fine.
Not even sure if that’s the fault of Apple or the M3, but in general I find the whole experience kind of disappointing.
can you resend the video? it seems is pause.
The infrared emitting surface of the M3 is located on the four sides of its body. You can try facing the air conditioner directly, reducing the obstacles between M3 and the air conditioner, and see if it can optimize the control effect.
It’s very obvious in the video when the IR lights are triggered, the problem is that sometimes they are not even when the blue light is blinking.
Is not about the ac unit not receiving the signal, it’s just not being sent.
The vid plays fine btw, maybe it’s your connection, let it to load a bit.
That’s an interesting idea, I’ll try to test it.
Does it do the same thing if you wait a bit more between commands?
On mine I can do it as fast as you actually, but I’m wondering whether there’s some sort of sync between the AC Unit and the M3, as to ack that it received the command.
I have noticed that if I change the AC using the remote, the M3 is catching the order: don’t know if it’s from the remote or from the unit though
Thats shame. I have AC controller from other brand and it works flawless! Hope M3 will get some updates to adress this.
My M-3 hub controls our older Mitsubishi wall mounted split heat pump better than the original manufacture’s thermostat. I suspect much depends on hub placement- distance and line of sight, and the proper selection of the M-3 control app. Perhaps the apps for the different manufacturers differ in the control ability of the various units?
I went thru the IR selection wizard, all buttons work fine. Line of sight is not a problem, it’s just not using the IR blaster sometimes.
I doubt there’s any sync between AC and the M3 unit, it’s just an IR led.
Anyway I can’t seem to reproduce the issue today, buttons work even when pressed very fast.
As I said initially, it appears that it stops working randomly.
After reviewing your video (finally able to play it!)
Summarized your issues as follows:
Issue 1: When you press the button on the app, the command will first be sent to the cloud server, then sent to the M3, and only then will the infrared signal be emitted. Therefore, when you press the button too fast, there will be a situation where the M3 cannot respond in time. It is recommended that you set up a scene to turn on the air conditioner to the preset mode and temperature, which can improve the success rate of your command execution.
Issue 2: When you synchronize the air conditioning mode to Apple Home, you will find that the temperature is fixed at 25.5 degrees Celsius. This is because your M3 is not connected to the temperature and humidity sensor, and the program has set a fixed temperature.
Therefore, suppose you give Siri an instruction: Turn on the air conditioner and set the temperature to 26 degrees Celsius. Siri will determine that 26 degrees is higher than 25.5 degrees Celsius. Therefore, the final instruction it will issue will be: Turn on the air conditioner, set to heating mode, and set the temperature to 26 degrees Celsius. Even if your intention is to save electricity for the air conditioner, it will stubbornly insist that this is the desired temperature for the room. The suggested approach is that when you set up automation on Apple or give instructions to Siri, break it down into multiple steps: Hey Siri, turn on the air conditioner; Hey Siri, set the cooling mode to 26 degrees Celsius.
Thank you for coming back to look at this and for you suggestions.
I’m afraid I doubt the reason behind the IR not triggering is pressing the button too fast since I noticed it happening even with a lot more pause between attempts.
Also notice that the hub has no issue responding by blinking the blue light, it’s the IR blaster that is not firing.
Finally this looks like a bug, even if the scene workaround you suggest would work, users should not be forced to do that for what is just basic functionality.
The M3 it is in fact connected to a T1 temperature and humidity sensor.
Regarding splitting the automation in 3 separate commands: I don’t see how that can fix it if the individual commands are unreliable and don’t always do what they should.
