About Coolix

[hassbian-ABC]

When coolix receives the infrared code from the remote control, it becomes uncontrollable

[hassbian-ABC]

Using bin compiled from IRMQTTServer

[NiKiZe]

Why did you ignore the issue template?
What are you sending to the AC when this happens?
And what does the original remote send when you are trying to do the same action?

You will have to collect this data. With the information provided so far we can't even guess what you are doing and what is happening.

[hassbian-ABC]

The remote control only controls the air conditioning on, there is nothing extra

[NiKiZe]

With this issue, what is your expected actions from this library?
Taking in to consideration that we don't know how to reproduce the issue you are seeing.

[crankyoldgit]

@hassbian-ABC I'm sorry if this comes across as snappy or terse. It's not meant to be. You are going to need to provide more information before we can help you. A LOT more information.
If you don't, I dont want to, but I'm inclined to close this issue if you don't.

e.g. Have you turned on DEBUG and looked at the serial output?

You haven't even listed what version of the library and IRMQTTServer you're using. Nor the mode the A/C Remote was trying to send, what the state of IRMQTTServer was in prior (and after) and what on earth "it becomes uncontrollable" actually & effectively means.

We are NOT mind-readers. You are our eyes and ears. We can only work on what you tell us.
Telling us "A Coolix remote breaks something" doesn't tell us much at all.

[hassbian-ABC]

After receiving the infrared code, Coolix will reset the sensorTemperature to 0.00, which will become uncontrollable

[hassbian-ABC]

If the sensorTemperature is reset to kNoTempValue, everything becomes normal

[crankyoldgit]

Can you please supply the sequence of messages that the actual remote is sending? e.g.
Using IRrecvDumpV3 example code to capture the actual IR messages.

[hassbian-ABC]

Okay, I will finish it in my free time

[crankyoldgit]

I've reviewed the relevant code in the library, and nothing jumps out at me. Thus, I'm going to need the actual message (The Coolix 24-bit message code/number) to look any further into this.

[hassbian-ABC]

Is IRrecvDumpV2 okay? @crankyoldgit

[hassbian-ABC]

#821

[crankyoldgit]

Is IRrecvDumpV2 okay? @crankyoldgit

Yes.

[crankyoldgit]

#821

Not relevant as we need to know the message that YOUR remote is generating, and with the current version of the library.

[hassbian-ABC]

新建 文本文档.txt
use IRremoteESP8266-2.8.5

[hassbian-ABC]

IRrecvDump is now running and waiting for IR input on Pin 13
Timestamp : 000005.708
Library : v2.8.5

Protocol : COOLIX
Code : 0xB21FD8 (24 Bits)
Mesg Desc.: Power: On, Mode: 2 (Auto), Fan: 0 (Auto0), Temp: 26C, Zone Follow: Off, Sensor Temp: Off
uint16_t rawData[199] = {4398, 4440, 482, 1702, 484, 594, 482, 1700, 480, 1702, 482, 596, 482, 596, 480, 1702, 482, 596, 482, 596, 480, 1702, 530, 548, 478, 600, 478, 1704, 502, 1680, 482, 596, 476, 1706, 482, 596, 482, 596, 478, 600, 478, 1704, 482, 1700, 480, 1704, 478, 1704, 482, 1700, 482, 1700, 500, 1682, 504, 1678, 528, 550, 482, 596, 480, 596, 480, 598, 482, 596, 478, 1704, 474, 1708, 478, 600, 476, 1706, 482, 1700, 480, 598, 478, 598, 480, 598, 482, 596, 476, 602, 478, 1704, 498, 580, 476, 600, 500, 1684, 498, 1684, 480, 1704, 504, 5254, 4398, 4442, 478, 1704, 480, 596, 480, 1702, 480, 1702, 480, 598, 480, 596, 478, 1704, 478, 600, 506, 572, 490, 1692, 480, 596, 478, 600, 504, 1678, 478, 1704, 504, 574, 502, 1680, 482, 596, 502, 576, 502, 576, 480, 1702, 480, 1704, 478, 1704, 478, 1706, 478, 1704, 480, 1702, 476, 1706, 498, 1684, 476, 602, 480, 598, 500, 576, 480, 596, 502, 576, 476, 1706, 500, 1684, 506, 572, 476, 1706, 502, 1680, 494, 584, 478, 600, 478, 598, 502, 574, 504, 574, 498, 1684, 482, 596, 482, 596, 478, 1704, 476, 1706, 500, 1682, 476}; // COOLIX B21FD8
uint64_t data = 0xB21FD8;

Timestamp : 000025.956
Library : v2.8.5

Protocol : COOLIX
Code : 0xB21F98 (24 Bits)
Mesg Desc.: Power: On, Mode: 2 (Auto), Fan: 0 (Auto0), Temp: 27C, Zone Follow: Off, Sensor Temp: Off
uint16_t rawData[199] = {4394, 4446, 480, 1704, 478, 600, 476, 1706, 474, 1708, 480, 598, 478, 600, 502, 1680, 478, 598, 480, 598, 500, 1682, 502, 576, 476, 602, 474, 1708, 488, 1694, 478, 600, 498, 1684, 478, 600, 498, 578, 476, 602, 478, 1702, 480, 1702, 476, 1706, 474, 1708, 476, 1706, 476, 1706, 474, 1708, 474, 1708, 474, 604, 478, 600, 474, 602, 506, 572, 478, 598, 480, 1700, 502, 576, 480, 598, 478, 1704, 480, 1704, 476, 602, 476, 602, 480, 598, 500, 576, 480, 1702, 482, 1700, 478, 600, 500, 578, 476, 1708, 504, 1678, 500, 1684, 476, 5282, 4394, 4442, 498, 1684, 476, 602, 502, 1680, 478, 1704, 504, 574, 480, 596, 480, 1702, 476, 602, 500, 578, 482, 1700, 498, 578, 502, 576, 480, 1702, 504, 1678, 478, 600, 480, 1702, 482, 596, 476, 602, 480, 598, 482, 1700, 476, 1708, 480, 1700, 476, 1708, 498, 1684, 480, 1702, 502, 1680, 478, 1704, 482, 596, 480, 606, 470, 598, 480, 598, 476, 602, 476, 1706, 480, 598, 476, 600, 480, 1702, 476, 1708, 480, 598, 560, 518, 554, 524, 548, 530, 482, 1700, 478, 1706, 482, 596, 478, 600, 478, 1704, 480, 1702, 476, 1708, 550}; // COOLIX B21F98
uint64_t data = 0xB21F98;

Timestamp : 000048.482
Library : v2.8.5

Protocol : COOLIX
Code : 0xB21F88 (24 Bits)
Mesg Desc.: Power: On, Mode: 2 (Auto), Fan: 0 (Auto0), Temp: 28C, Zone Follow: Off, Sensor Temp: Off
uint16_t rawData[199] = {4398, 4440, 476, 1708, 480, 598, 474, 1708, 480, 1702, 480, 598, 480, 598, 478, 1704, 476, 602, 500, 576, 478, 1704, 504, 574, 480, 596, 476, 1706, 478, 1704, 478, 600, 504, 1678, 490, 588, 482, 596, 482, 596, 478, 1704, 476, 1706, 478, 1704, 476, 1706, 482, 1700, 474, 1708, 482, 1702, 502, 1680, 480, 598, 476, 600, 482, 596, 474, 604, 478, 600, 478, 1704, 478, 600, 480, 598, 480, 598, 500, 1682, 476, 600, 478, 600, 480, 598, 478, 600, 474, 1708, 474, 1708, 478, 1704, 478, 600, 478, 1704, 482, 1700, 476, 1708, 478, 5280, 4394, 4442, 506, 1678, 476, 602, 480, 1702, 480, 1702, 478, 600, 480, 596, 476, 1706, 478, 600, 500, 578, 478, 1704, 480, 598, 478, 600, 502, 1682, 500, 1682, 502, 576, 504, 1678, 482, 596, 504, 572, 476, 600, 480, 1702, 480, 1702, 480, 1702, 480, 1704, 474, 1708, 480, 1702, 478, 1704, 480, 1702, 476, 602, 474, 604, 476, 600, 478, 600, 476, 600, 498, 1684, 500, 576, 504, 574, 478, 598, 480, 1702, 474, 602, 476, 602, 500, 576, 478, 600, 484, 1698, 476, 1704, 480, 1702, 478, 600, 478, 1702, 478, 1706, 500, 1682, 478}; // COOLIX B21F88
uint64_t data = 0xB21F88;

Timestamp : 000075.045
Library : v2.8.5

Protocol : COOLIX
Code : 0xB27BE0 (24 Bits)
Mesg Desc.: Power: Off
uint16_t rawData[199] = {4396, 4444, 482, 1702, 476, 602, 502, 1680, 478, 1704, 502, 576, 502, 576, 476, 1706, 480, 598, 500, 578, 480, 1704, 502, 576, 476, 602, 482, 1700, 480, 1702, 506, 574, 476, 1704, 504, 574, 500, 1682, 478, 1704, 474, 1708, 478, 1704, 480, 598, 498, 1684, 476, 1706, 476, 1708, 504, 574, 504, 574, 476, 602, 478, 598, 476, 1706, 476, 602, 504, 574, 478, 1704, 476, 1706, 498, 1684, 478, 600, 482, 596, 486, 592, 474, 604, 492, 584, 482, 596, 480, 598, 478, 598, 474, 1708, 480, 1702, 482, 1700, 478, 1704, 476, 1708, 504, 5254, 4398, 4440, 480, 1704, 478, 600, 478, 1704, 476, 1706, 490, 588, 474, 602, 476, 1706, 500, 578, 500, 576, 480, 1704, 476, 602, 502, 576, 480, 1702, 478, 1704, 494, 584, 500, 1682, 476, 602, 478, 1704, 478, 1704, 474, 1708, 498, 1684, 480, 598, 478, 1704, 474, 1708, 480, 1702, 476, 602, 478, 600, 500, 578, 482, 596, 498, 1684, 480, 598, 478, 600, 480, 1702, 480, 1702, 478, 1706, 478, 598, 480, 598, 482, 596, 476, 602, 480, 598, 478, 598, 476, 600, 482, 596, 480, 1702, 476, 1706, 474, 1708, 480, 1702, 480, 1702, 476}; // COOLIX B27BE0
uint64_t data = 0xB27BE0;

[crankyoldgit]

After receiving the infrared code, Coolix will reset the sensorTemperature to 0.00, which will become uncontrollable

Interesting, because my testing it seems to report the sensorTemperature as 31.
Regardless, I think the problem is it's reporting a sensor temp in the .toCommon() method when it shouldn't be.

[crankyoldgit]

@hassbian-ABC Can you please download and test PR #2015 / branch Issue2012 and confirm if that fixes your problem.

Thanks in advance.

@NiKiZe The continuous build is failing due to what seems to be an update in the Blynk library behaviour. The failing test should be fixed by #2016. When approved & merged, I'll rebase and merge etc.

[hassbian-ABC]

Okay, I'll test it later @crankyoldgit

[hassbian-ABC]

Everything has changed very well @crankyoldgit

[hassbian-ABC]

Thank you @crankyoldgit