A Bug Occurs Where Sending an IR Command to the Air Conditioner Always Sends the Same Command

[yyverse]

Analysis

Many people have reported the same issue in the link below, and it appears that this issue has recently started occurring. Specifically, regardless of the value of the parameter, the IR signal transmitted is always the same. This issue only occurs when using the API and does not occur with the iOS app or scene automation. Please refer to the link below for more details: #363

Expected Behavior

Please revert the API server behavior so that, as before, it transmits the infrared code according to the parameter specified when using the API.

Steps To Reproduce

1. Send the following command and confirm that the air conditioner operates. The response from the API server will indicate success.

{
    "command": "setAll",
    "parameter": "26,1,3,on",
    "commandType": "command"
}

2. Send the following command and confirm that the air conditioner does not turn off. The response from the API server will indicate success.

{
    "command": "setAll",
    "parameter": "26,1,3,off",
    "commandType": "command"
}

3. Use the app to turn off the relevant air conditioner.
4. Check the history of the air conditioner within the app and verify that the result of the API execution is irregular.

Logs

{'statusCode': 100, 'body': {}, 'message': 'success'}

Configuration

{
    "command": "setAll",
    "parameter": "26,1,3,on",
    "commandType": "command"
}

Environment

• OS:
• Software:
• Node:
• npm:

Additional Context

No response

[MrXANA91]

I can no longer reproduce this.
Has issue been solved for you as well @yyverse ?

[tcavin]

Hi,
@MrXANA91 This issue has been solved on my side too
Just be careful of one thing : The temperature must be an integer when sent to the API (floating number is not allowed and raise a 190 Internal server error).
I'm not sure It was the case before, since I had to make little changes in my code to handle this