AirCon icon indicating copy to clipboard operation
AirCon copied to clipboard

temperature jumps to 36 when adjustments are made

Open dansrogers opened this issue 3 years ago • 6 comments

Hi there,

I'm using the following config file:

{
    "name": "AC000W002946576",
    "app": "fglair-us",
    "model": "AP-WC2E",
    "sw_version": "bc 2.6.17-fgl2 06/29/20 09:03:57 ID jre/mfg/2dfbf5d",
    "dsn": "AC000W002946576",
    "temp_type": "C",
    "mac_address": "XXXXX",
    "ip_address": "XXXXX",
    "lanip_key": "XXXXX",
    "lanip_key_id": XXXXX
}

I'm experiencing several issues. First is that it autodetected Fahrenheit, but the device is clearly reporting in Celsius. I manually edited temp_type to fix this.

Second is that when I try to make adjustments to temperature the climate control UI on the lovelace dashboard, small adjustments causes the temperature in the UI to jump to 36 degrees. For example, it's currently at 76. I then press the up arrow once, and the UI briefly show 77 degrees and the will jump to 36 degrees. In the official android app, and on the wall controller, it still shows 76 degrees. If I make a 2 degree adjustment, then I'll see the adjustment show up in the app and the device.

However there is sometimes an occasional 1 degree difference between the official app and love lace. My guess here is that there is different rounding expectations between the two devices. It looks like if I try to make an adjustment that results in too small of a change, the display errors out and shows 36 degrees.

dansrogers avatar May 23 '22 16:05 dansrogers

Another clue. Here is the mqtt configuration:

{
  "name": "AC000W002946576",
  "unique_id": "b8d7af3e0647",
  "device": {
    "identifiers": [
      "hisense_ac_b8d7af3e0647"
    ],
    "manufacturer": "Hisense (fglair-us)",
    "model": "AP-WC2E",
    "name": "AC000W002946576",
    "sw_version": "bc 2.6.17-fgl2 06/29/20 09:03:57 ID jre/mfg/2dfbf5d"
  },
  "availability": [
    {
      "topic": "hisense_ac/LWT"
    },
    {
      "topic": "hisense_ac/b8d7af3e0647/available/status"
    }
  ],
  "precision": 1,
  "temperature_unit": "C",
  "fan_mode_command_topic": "hisense_ac/b8d7af3e0647/fan_speed/command",
  "fan_mode_state_topic": "hisense_ac/b8d7af3e0647/fan_speed/status",
  "fan_modes": [
    "auto",
    "quiet",
    "low",
    "medium",
    "high"
  ],
  "mode_command_topic": "hisense_ac/b8d7af3e0647/operation_mode/command",
  "mode_state_topic": "hisense_ac/b8d7af3e0647/operation_mode/status",
  "modes": [
    "off",
    "fan_only",
    "heat",
    "cool",
    "dry",
    "auto"
  ],
  "swing_mode_command_topic": "hisense_ac/b8d7af3e0647/af_vertical_swing/command",
  "swing_mode_state_topic": "hisense_ac/b8d7af3e0647/af_vertical_swing/status",
  "swing_modes": [
    "on",
    "off"
  ],
  "temperature_command_topic": "hisense_ac/b8d7af3e0647/adjust_temperature/command",
  "temperature_state_topic": "hisense_ac/b8d7af3e0647/adjust_temperature/status",
  "max_temp": "30",
  "min_temp": "16"
}

precision: 1 definitely would cause these issues. I tried publishing a precision: 0.1 message but it seems that the addon doesn't respect that and still rounds to even units of temperature

dansrogers avatar May 25 '22 15:05 dansrogers

I have the same problem, especially in cool mode and sometimes in dehumidification mode. I'm transmitting from Nodered using MQTT. I set the temperature to 70F and it immediately goes back to 36F for no apparent reason. I'm trying to find a pattern to easily reproduce, but it's difficult because it seems random. For example, last night from 10PM to 6AM, my heat pump was in 70F cooling mode. Suddenly, at 2:38AM, the temperature automatically set to 36F. From that moment, my automation reset it to 70F every ten minutes and it immediately returned to 36F.

GED8006 avatar May 18 '24 11:05 GED8006

I have the same problem, especially in cool mode and sometimes in dehumidification mode. I'm transmitting from Nodered using MQTT. I set the temperature to 70F and it immediately goes back to 36F for no apparent reason. I'm trying to find a pattern to easily reproduce, but it's difficult because it seems random. For example, last night from 10PM to 6AM, my heat pump was in 70F cooling mode. Suddenly, at 2:38AM, the temperature automatically set to 36F. From that moment, my automation reset it to 70F every ten minutes and it immediately returned to 36F.

I found the explanation for my situation. When I transmit a value lower than that supported by my heat pump (i.e. 18C), the status value sets to 2C and immediately returns to the previous value.

For example :

  1. Initial value: 21C
  2. Transmitted value: 17C
  3. Status value: 2C
  4. Automatically corrected value: 21C

GED8006 avatar May 18 '24 12:05 GED8006

IS it not the the same issue that the one I reported: https://github.com/deiger/AirCon/issues/202

I don't really understand what you mean by "temperature supported by my heatpump"

kevtuning avatar May 18 '24 12:05 kevtuning

Sorry, English is not my native language.

“Temperature supported by my heatpump” is the minimum temperature that I can enter in the FGLair application. This minimum is set at 18C in the application. Transmission of a value lower than 18C by MQTT activates automatic correction.

This is possibly not the same bug as #202, but we should look at the automatic correction made by the code. The 2C value seems suspicious to me.

GED8006 avatar May 18 '24 13:05 GED8006

I add a new observation which causes an automatic change in temperature to 2C.

  1. When the transmitted temperature is outside the range allowed by the heat pump (see details above).
  2. When the transmitted temperature is the same as the current temperature (hisense_ac/abc/adjust_temperature/status).

GED8006 avatar May 19 '24 12:05 GED8006