Add Midea Mission II / Blanc / OSK105 support

Hello!
ttimpe seems that he can't add support for my AC units.
Could you please check my problem?  I'll give you all the information you will ask for.
https://github.com/ttimpe/homebridge-midea/issues/22

can you send me log from midea-discover (midea-msmart)
and log from Homebridge

PS C:\Windows\system32> midea-discover
INFO:msmart.cli:msmart version: 0.1.24
INFO:msmart.cli:Sending Device Scan Broadcast...
INFO:msmart.cli:Midea Local Data <IP_ADDRESS> 5a5a011178007a8000000000000000000000000031860000000f0000000000000000000001000000bed0c42c09c6869c68f709c439ddd7c86d9105e62ecb16d02758ac609ec336022944c4d5d678b27e3af86c2f0a05e5353138812529f656f11ede2cf6c6f24937dc3c2f38a728a5f89e566c86ec2511f5
INFO:msmart.cli:Decrypt Reply: <IP_ADDRESS> 0f01a8c02c19000030303030303050303030303030305131333435424242383133423143303030300b6e65745f61635f33423143
INFO:msmart.cli:*** Found a supported device - type: '0xac' - version: V2 - ip: <IP_ADDRESS> - port: 6444 - id:<PHONE_NUMBER>0993 - sn: 000000P0000000Q1345BBB813B1C0000 - ssid: net_ac_3B1C
INFO:msmart.cli:Midea Local Data <IP_ADDRESS> 5a5a011178007a800000000000000000000000002d8d00000010000000000000000000000100000041cfef89714a40f14eaff1b9997da71d4638abd1036c0c7456fc1216fa4ada4df8eb4e6be9c5f604a80a8e2c60c7455bef6822de29b5480c56a9f078403d42d8cda8d3263ad8086ceb89967f05af6cde
INFO:msmart.cli:Decrypt Reply: <IP_ADDRESS> 1101a8c02c19000030303030303050303030303030305131333435424242383045453433303030300b6e65745f61635f45453433
INFO:msmart.cli:*** Found a supported device - type: '0xac' - version: V2 - ip: <IP_ADDRESS> - port: 6444 - id:<PHONE_NUMBER>0557 - sn: 000000P0000000Q1345BBB80EE430000 - ssid: net_ac_EE43
INFO:msmart.cli:Midea Local Data <IP_ADDRESS> 5a5a011178007a80000000000000000000000000f0a7020000110000000000000000000001000000f40095035369b85f7320e87095eb71886d9105e62ecb16d02758ac609ec33602f1e3ac1a84677a3a0eae1e5b6f8a54c60d9bb7cebde267d6dd5f6362b614250a446ce2f965c2739178ffb15ffdaaa793
INFO:msmart.cli:Decrypt Reply: <IP_ADDRESS> 1501a8c02c19000030303030303050303030303030305131333435424242383134303532303030300b6e65745f61635f34303532
INFO:msmart.cli:*** Found a supported device - type: '0xac' - version: V2 - ip: <IP_ADDRESS> - port: 6444 - id:<PHONE_NUMBER>6256 - sn: 000000P0000000Q1345BBB8140520000 - ssid: net_ac_4052
INFO:msmart.cli:Midea Local Data <IP_ADDRESS> 5a5a011178007a800000000000000000000000002f8d00000010000000000000000000000100000014f1d37c4bb2bf0a06dbb077c93ca09b3b8d9005b4dff2c93252bd142b8b2d2a5199f536707be93697c8596684b69fa2e81361f7369246e4c0e95ce1a47786f90455977e9241e2dbb3d61d1a782f8f44
INFO:msmart.cli:Decrypt Reply: <IP_ADDRESS> 1001a8c02c19000030303030303050303030303030305131463043394431314638344534303030300b6e65745f61635f38344534
INFO:msmart.cli:*** Found a supported device - type: '0xac' - version: V2 - ip: <IP_ADDRESS> - port: 6444 - id:<PHONE_NUMBER>0559 - sn: 000000P0000000Q1F0C9D11F84E40000 - ssid: net_ac_84E4

my AC is V2 and it's work with this plugin.
Turn on Debug mode on Homebridge settings.
and send me log from homebridge

[4/9/2021, 10:11:58 PM] [midea-air] Login successful
[4/9/2021, 10:11:58 PM] [midea-air] getUserList called
[4/9/2021, 10:12:04 PM] [midea-air] Adding new device: Office
[4/9/2021, 10:12:04 PM] [midea-air] created device Office with id<PHONE_NUMBER>6256 and type 172
[4/9/2021, 10:12:04 PM] [midea-air] Device type is  172
[4/9/2021, 10:12:04 PM] [midea-air] Adding new device: Master bedroom
[4/9/2021, 10:12:04 PM] [midea-air] created device Master bedroom with id<PHONE_NUMBER>0993 and type 172
[4/9/2021, 10:12:04 PM] [midea-air] Device type is  172
[4/9/2021, 10:12:04 PM] [midea-air] Adding new device: Children bedroom
[4/9/2021, 10:12:04 PM] [midea-air] created device Children bedroom with id<PHONE_NUMBER>0557 and type 172
[4/9/2021, 10:12:04 PM] [midea-air] Device type is  172
[4/9/2021, 10:12:04 PM] [midea-air] Adding new device: Living Room
[4/9/2021, 10:12:04 PM] [midea-air] created device Living Room with id<PHONE_NUMBER>0559 and type 172
[4/9/2021, 10:12:04 PM] [midea-air] Device type is  172
[4/9/2021, 10:12:05 PM] [midea-air] Triggered GET Active, returning: undefined
[4/9/2021, 10:12:05 PM] [midea-air] Triggered GET CurrentHeaterCoolerState: 0
[4/9/2021, 10:12:05 PM] [midea-air] Triggered GET TargetHeaterCoolerState while powerState is: 0
[4/9/2021, 10:12:05 PM] [midea-air] Triggered GET CurrentTemperature: 0
[4/9/2021, 10:12:05 PM] [midea-air] Triggered GET RotationSpeed: 0
[4/9/2021, 10:12:05 PM] [midea-air] Triggered GET swingMode: 0
[4/9/2021, 10:12:05 PM] [midea-air] Triggered GET handleCoolingThresholdTemperature: 0
[4/9/2021, 10:12:05 PM] [homebridge-midea-air] This plugin generated a warning from the characteristic 'Cooling Threshold Temperature': characteristic was supplied illegal value: number 0 exceeded minimum of 17. See https://git.io/JtMGR for more info.
[4/9/2021, 10:12:05 PM] [homebridge-midea-air] Error:
at CoolingThresholdTemperature.Characteristic.characteristicWarning (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:2038:105)
at CoolingThresholdTemperature.Characteristic.validateUserInput (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1946:16)
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1533:24
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/util/once.ts:9:18
at MideaAccessory.handleCoolingThresholdTemperatureGet (/homebridge/node_modules/homebridge-midea-air/lib/MideaAccessory.js:337:9)
at CoolingThresholdTemperature.emit (events.js:315:20)
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1508:14
at new Promise ()
at CoolingThresholdTemperature. (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1506:12)
at step (/usr/local/lib/node_modules/homebridge/node_modules/tslib/tslib.js:143:27)
[4/9/2021, 10:12:05 PM] [midea-air] Triggered GET handleHeatingThresholdTemperature: 0
[4/9/2021, 10:12:05 PM] [homebridge-midea-air] This plugin generated a warning from the characteristic 'Heating Threshold Temperature': characteristic was supplied illegal value: number 0 exceeded minimum of 17. See https://git.io/JtMGR for more info.
[4/9/2021, 10:12:05 PM] [homebridge-midea-air] Error:
at HeatingThresholdTemperature.Characteristic.characteristicWarning (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:2038:105)
at HeatingThresholdTemperature.Characteristic.validateUserInput (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1946:16)
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1533:24
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/util/once.ts:9:18
at MideaAccessory.handleHeatingThresholdTemperatureGet (/homebridge/node_modules/homebridge-midea-air/lib/MideaAccessory.js:352:9)
at HeatingThresholdTemperature.emit (events.js:315:20)
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1508:14
at new Promise ()
at HeatingThresholdTemperature. (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1506:12)
at step (/usr/local/lib/node_modules/homebridge/node_modules/tslib/tslib.js:143:27)
[4/9/2021, 10:12:05 PM] [midea-air] Triggered GET TemperatureDisplayUnits false
[4/9/2021, 10:12:05 PM] [midea-air] Triggered GET Active, returning: undefined
[4/9/2021, 10:12:05 PM] [midea-air] Triggered GET CurrentHeaterCoolerState: 0
[4/9/2021, 10:12:05 PM] [midea-air] Triggered GET TargetHeaterCoolerState while powerState is: 0
[4/9/2021, 10:12:05 PM] [midea-air] Triggered GET CurrentTemperature: 0
[4/9/2021, 10:12:05 PM] [midea-air] Triggered GET RotationSpeed: 0
[4/9/2021, 10:12:05 PM] [midea-air] Triggered GET swingMode: 0
[4/9/2021, 10:12:05 PM] [midea-air] Triggered GET handleCoolingThresholdTemperature: 0
[4/9/2021, 10:12:05 PM] [homebridge-midea-air] This plugin generated a warning from the characteristic 'Cooling Threshold Temperature': characteristic was supplied illegal value: number 0 exceeded minimum of 17. See https://git.io/JtMGR for more info.
[4/9/2021, 10:12:05 PM] [homebridge-midea-air] Error:
at CoolingThresholdTemperature.Characteristic.characteristicWarning (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:2038:105)
at CoolingThresholdTemperature.Characteristic.validateUserInput (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1946:16)
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1533:24
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/util/once.ts:9:18
at MideaAccessory.handleCoolingThresholdTemperatureGet (/homebridge/node_modules/homebridge-midea-air/lib/MideaAccessory.js:337:9)
at CoolingThresholdTemperature.emit (events.js:315:20)
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1508:14
at new Promise ()
at CoolingThresholdTemperature. (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1506:12)
at step (/usr/local/lib/node_modules/homebridge/node_modules/tslib/tslib.js:143:27)
[4/9/2021, 10:12:05 PM] [midea-air] Triggered GET handleHeatingThresholdTemperature: 0
[4/9/2021, 10:12:05 PM] [homebridge-midea-air] This plugin generated a warning from the characteristic 'Heating Threshold Temperature': characteristic was supplied illegal value: number 0 exceeded minimum of 17. See https://git.io/JtMGR for more info.
[4/9/2021, 10:12:05 PM] [homebridge-midea-air] Error:
at HeatingThresholdTemperature.Characteristic.characteristicWarning (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:2038:105)
at HeatingThresholdTemperature.Characteristic.validateUserInput (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1946:16)
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1533:24
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/util/once.ts:9:18
at MideaAccessory.handleHeatingThresholdTemperatureGet (/homebridge/node_modules/homebridge-midea-air/lib/MideaAccessory.js:352:9)
at HeatingThresholdTemperature.emit (events.js:315:20)
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1508:14
at new Promise ()
at HeatingThresholdTemperature. (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1506:12)
at step (/usr/local/lib/node_modules/homebridge/node_modules/tslib/tslib.js:143:27)
[4/9/2021, 10:12:05 PM] [midea-air] Triggered GET TemperatureDisplayUnits false
[4/9/2021, 10:12:05 PM] [midea-air] Triggered GET Active, returning: undefined
[4/9/2021, 10:12:05 PM] [midea-air] Triggered GET CurrentHeaterCoolerState: 0
[4/9/2021, 10:12:05 PM] [midea-air] Triggered GET TargetHeaterCoolerState while powerState is: 0
[4/9/2021, 10:12:05 PM] [midea-air] Triggered GET CurrentTemperature: 0
[4/9/2021, 10:12:05 PM] [midea-air] Triggered GET RotationSpeed: 0
[4/9/2021, 10:12:05 PM] [midea-air] Triggered GET swingMode: 0
[4/9/2021, 10:12:05 PM] [midea-air] Triggered GET handleCoolingThresholdTemperature: 0
[4/9/2021, 10:12:05 PM] [homebridge-midea-air] This plugin generated a warning from the characteristic 'Cooling Threshold Temperature': characteristic was supplied illegal value: number 0 exceeded minimum of 17. See https://git.io/JtMGR for more info.
[4/9/2021, 10:12:05 PM] [homebridge-midea-air] Error:
at CoolingThresholdTemperature.Characteristic.characteristicWarning (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:2038:105)
at CoolingThresholdTemperature.Characteristic.validateUserInput (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1946:16)
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1533:24
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/util/once.ts:9:18
at MideaAccessory.handleCoolingThresholdTemperatureGet (/homebridge/node_modules/homebridge-midea-air/lib/MideaAccessory.js:337:9)
at CoolingThresholdTemperature.emit (events.js:315:20)
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1508:14
at new Promise ()
at CoolingThresholdTemperature. (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1506:12)
at step (/usr/local/lib/node_modules/homebridge/node_modules/tslib/tslib.js:143:27)
[4/9/2021, 10:12:05 PM] [midea-air] Triggered GET handleHeatingThresholdTemperature: 0
[4/9/2021, 10:12:05 PM] [homebridge-midea-air] This plugin generated a warning from the characteristic 'Heating Threshold Temperature': characteristic was supplied illegal value: number 0 exceeded minimum of 17. See https://git.io/JtMGR for more info.
[4/9/2021, 10:12:05 PM] [homebridge-midea-air] Error:
at HeatingThresholdTemperature.Characteristic.characteristicWarning (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:2038:105)
at HeatingThresholdTemperature.Characteristic.validateUserInput (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1946:16)
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1533:24
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/util/once.ts:9:18
at MideaAccessory.handleHeatingThresholdTemperatureGet (/homebridge/node_modules/homebridge-midea-air/lib/MideaAccessory.js:352:9)
at HeatingThresholdTemperature.emit (events.js:315:20)
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1508:14
at new Promise ()
at HeatingThresholdTemperature. (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1506:12)
at step (/usr/local/lib/node_modules/homebridge/node_modules/tslib/tslib.js:143:27)
[4/9/2021, 10:12:05 PM] [midea-air] Triggered GET TemperatureDisplayUnits false
[4/9/2021, 10:12:05 PM] [midea-air] Triggered GET Active, returning: undefined
[4/9/2021, 10:12:05 PM] [midea-air] Triggered GET CurrentHeaterCoolerState: 0
[4/9/2021, 10:12:05 PM] [midea-air] Triggered GET TargetHeaterCoolerState while powerState is: 0
[4/9/2021, 10:12:05 PM] [midea-air] Triggered GET CurrentTemperature: 0
[4/9/2021, 10:12:05 PM] [midea-air] Triggered GET RotationSpeed: 0
[4/9/2021, 10:12:05 PM] [midea-air] Triggered GET swingMode: 0
[4/9/2021, 10:12:05 PM] [midea-air] Triggered GET handleCoolingThresholdTemperature: 0
[4/9/2021, 10:12:05 PM] [homebridge-midea-air] This plugin generated a warning from the characteristic 'Cooling Threshold Temperature': characteristic was supplied illegal value: number 0 exceeded minimum of 17. See https://git.io/JtMGR for more info.
[4/9/2021, 10:12:05 PM] [homebridge-midea-air] Error:
at CoolingThresholdTemperature.Characteristic.characteristicWarning (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:2038:105)
at CoolingThresholdTemperature.Characteristic.validateUserInput (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1946:16)
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1533:24
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/util/once.ts:9:18
at MideaAccessory.handleCoolingThresholdTemperatureGet (/homebridge/node_modules/homebridge-midea-air/lib/MideaAccessory.js:337:9)
at CoolingThresholdTemperature.emit (events.js:315:20)
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1508:14
at new Promise ()
at CoolingThresholdTemperature. (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1506:12)
at step (/usr/local/lib/node_modules/homebridge/node_modules/tslib/tslib.js:143:27)
[4/9/2021, 10:12:05 PM] [midea-air] Triggered GET handleHeatingThresholdTemperature: 0
[4/9/2021, 10:12:05 PM] [homebridge-midea-air] This plugin generated a warning from the characteristic 'Heating Threshold Temperature': characteristic was supplied illegal value: number 0 exceeded minimum of 17. See https://git.io/JtMGR for more info.
[4/9/2021, 10:12:05 PM] [homebridge-midea-air] Error:
at HeatingThresholdTemperature.Characteristic.characteristicWarning (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:2038:105)
at HeatingThresholdTemperature.Characteristic.validateUserInput (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1946:16)
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1533:24
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/util/once.ts:9:18
at MideaAccessory.handleHeatingThresholdTemperatureGet (/homebridge/node_modules/homebridge-midea-air/lib/MideaAccessory.js:352:9)
at HeatingThresholdTemperature.emit (events.js:315:20)
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1508:14
at new Promise ()
at HeatingThresholdTemperature. (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1506:12)
at step (/usr/local/lib/node_modules/homebridge/node_modules/tslib/tslib.js:143:27)
[4/9/2021, 10:12:05 PM] [midea-air] Triggered GET TemperatureDisplayUnits false
[4/9/2021, 10:12:31 PM] [midea-air] Triggered GET CurrentTemperature: 0
[4/9/2021, 10:12:31 PM] [midea-air] Triggered GET handleCoolingThresholdTemperature: 0
[4/9/2021, 10:12:31 PM] [homebridge-midea-air] This plugin generated a warning from the characteristic 'Cooling Threshold Temperature': characteristic was supplied illegal value: number 0 exceeded minimum of 17. See https://git.io/JtMGR for more info.
[4/9/2021, 10:12:31 PM] [homebridge-midea-air] Error:
at CoolingThresholdTemperature.Characteristic.characteristicWarning (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:2038:105)
at CoolingThresholdTemperature.Characteristic.validateUserInput (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1946:16)
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1533:24
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/util/once.ts:9:18
at MideaAccessory.handleCoolingThresholdTemperatureGet (/homebridge/node_modules/homebridge-midea-air/lib/MideaAccessory.js:337:9)
at CoolingThresholdTemperature.emit (events.js:315:20)
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1508:14
at new Promise ()
at CoolingThresholdTemperature. (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1506:12)
at step (/usr/local/lib/node_modules/homebridge/node_modules/tslib/tslib.js:143:27)
[4/9/2021, 10:12:31 PM] [midea-air] Triggered GET handleHeatingThresholdTemperature: 0
[4/9/2021, 10:12:31 PM] [homebridge-midea-air] This plugin generated a warning from the characteristic 'Heating Threshold Temperature': characteristic was supplied illegal value: number 0 exceeded minimum of 17. See https://git.io/JtMGR for more info.
[4/9/2021, 10:12:31 PM] [homebridge-midea-air] Error:
at HeatingThresholdTemperature.Characteristic.characteristicWarning (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:2038:105)
at HeatingThresholdTemperature.Characteristic.validateUserInput (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1946:16)
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1533:24
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/util/once.ts:9:18
at MideaAccessory.handleHeatingThresholdTemperatureGet (/homebridge/node_modules/homebridge-midea-air/lib/MideaAccessory.js:352:9)
at HeatingThresholdTemperature.emit (events.js:315:20)
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1508:14
at new Promise ()
at HeatingThresholdTemperature. (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1506:12)
at step (/usr/local/lib/node_modules/homebridge/node_modules/tslib/tslib.js:143:27)
[4/9/2021, 10:12:31 PM] [midea-air] Triggered GET TemperatureDisplayUnits false
[4/9/2021, 10:12:31 PM] [midea-air] Triggered GET TargetHeaterCoolerState while powerState is: 0
[4/9/2021, 10:12:31 PM] [midea-air] Triggered GET CurrentHeaterCoolerState: 0
[4/9/2021, 10:12:31 PM] [midea-air] Triggered GET RotationSpeed: 0
[4/9/2021, 10:12:31 PM] [midea-air] Triggered GET swingMode: 0
[4/9/2021, 10:12:31 PM] [midea-air] Triggered GET Active, returning: undefined
[4/9/2021, 10:12:31 PM] [midea-air] Triggered GET TargetHeaterCoolerState while powerState is: 0
[4/9/2021, 10:12:31 PM] [midea-air] Triggered GET Active, returning: undefined
[4/9/2021, 10:12:31 PM] [midea-air] Triggered GET RotationSpeed: 0
[4/9/2021, 10:12:31 PM] [midea-air] Triggered GET CurrentTemperature: 0
[4/9/2021, 10:12:31 PM] [midea-air] Triggered GET swingMode: 0
[4/9/2021, 10:12:31 PM] [midea-air] Triggered GET handleHeatingThresholdTemperature: 0
[4/9/2021, 10:12:31 PM] [homebridge-midea-air] This plugin generated a warning from the characteristic 'Heating Threshold Temperature': characteristic was supplied illegal value: number 0 exceeded minimum of 17. See https://git.io/JtMGR for more info.
[4/9/2021, 10:12:31 PM] [homebridge-midea-air] Error:
at HeatingThresholdTemperature.Characteristic.characteristicWarning (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:2038:105)
at HeatingThresholdTemperature.Characteristic.validateUserInput (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1946:16)
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1533:24
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/util/once.ts:9:18
at MideaAccessory.handleHeatingThresholdTemperatureGet (/homebridge/node_modules/homebridge-midea-air/lib/MideaAccessory.js:352:9)
at HeatingThresholdTemperature.emit (events.js:315:20)
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1508:14
at new Promise ()
at HeatingThresholdTemperature. (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1506:12)
at step (/usr/local/lib/node_modules/homebridge/node_modules/tslib/tslib.js:143:27)
[4/9/2021, 10:12:31 PM] [midea-air] Triggered GET CurrentHeaterCoolerState: 0
[4/9/2021, 10:12:31 PM] [midea-air] Triggered GET TemperatureDisplayUnits false
[4/9/2021, 10:12:31 PM] [midea-air] Triggered GET handleCoolingThresholdTemperature: 0
[4/9/2021, 10:12:31 PM] [homebridge-midea-air] This plugin generated a warning from the characteristic 'Cooling Threshold Temperature': characteristic was supplied illegal value: number 0 exceeded minimum of 17. See https://git.io/JtMGR for more info.
[4/9/2021, 10:12:31 PM] [homebridge-midea-air] Error:
at CoolingThresholdTemperature.Characteristic.characteristicWarning (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:2038:105)
at CoolingThresholdTemperature.Characteristic.validateUserInput (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1946:16)
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1533:24
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/util/once.ts:9:18
at MideaAccessory.handleCoolingThresholdTemperatureGet (/homebridge/node_modules/homebridge-midea-air/lib/MideaAccessory.js:337:9)
at CoolingThresholdTemperature.emit (events.js:315:20)
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1508:14
at new Promise ()
at CoolingThresholdTemperature. (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1506:12)
at step (/usr/local/lib/node_modules/homebridge/node_modules/tslib/tslib.js:143:27)
[4/9/2021, 10:12:31 PM] [midea-air] Triggered GET Active, returning: undefined
[4/9/2021, 10:12:31 PM] [midea-air] Triggered GET TemperatureDisplayUnits false
[4/9/2021, 10:12:31 PM] [midea-air] Triggered GET TargetHeaterCoolerState while powerState is: 0
[4/9/2021, 10:12:31 PM] [midea-air] Triggered GET CurrentHeaterCoolerState: 0
[4/9/2021, 10:12:31 PM] [midea-air] Triggered GET handleHeatingThresholdTemperature: 0
[4/9/2021, 10:12:31 PM] [homebridge-midea-air] This plugin generated a warning from the characteristic 'Heating Threshold Temperature': characteristic was supplied illegal value: number 0 exceeded minimum of 17. See https://git.io/JtMGR for more info.
[4/9/2021, 10:12:31 PM] [homebridge-midea-air] Error:
at HeatingThresholdTemperature.Characteristic.characteristicWarning (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:2038:105)
at HeatingThresholdTemperature.Characteristic.validateUserInput (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1946:16)
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1533:24
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/util/once.ts:9:18
at MideaAccessory.handleHeatingThresholdTemperatureGet (/homebridge/node_modules/homebridge-midea-air/lib/MideaAccessory.js:352:9)
at HeatingThresholdTemperature.emit (events.js:315:20)
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1508:14
at new Promise ()
at HeatingThresholdTemperature. (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1506:12)
at step (/usr/local/lib/node_modules/homebridge/node_modules/tslib/tslib.js:143:27)
[4/9/2021, 10:12:31 PM] [midea-air] Triggered GET handleCoolingThresholdTemperature: 0
[4/9/2021, 10:12:31 PM] [homebridge-midea-air] This plugin generated a warning from the characteristic 'Cooling Threshold Temperature': characteristic was supplied illegal value: number 0 exceeded minimum of 17. See https://git.io/JtMGR for more info.
[4/9/2021, 10:12:31 PM] [homebridge-midea-air] Error:
at CoolingThresholdTemperature.Characteristic.characteristicWarning (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:2038:105)
at CoolingThresholdTemperature.Characteristic.validateUserInput (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1946:16)
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1533:24
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/util/once.ts:9:18
at MideaAccessory.handleCoolingThresholdTemperatureGet (/homebridge/node_modules/homebridge-midea-air/lib/MideaAccessory.js:337:9)
at CoolingThresholdTemperature.emit (events.js:315:20)
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1508:14
at new Promise ()
at CoolingThresholdTemperature. (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1506:12)
at step (/usr/local/lib/node_modules/homebridge/node_modules/tslib/tslib.js:143:27)
[4/9/2021, 10:12:31 PM] [midea-air] Triggered GET CurrentTemperature: 0
[4/9/2021, 10:12:31 PM] [midea-air] Triggered GET swingMode: 0
[4/9/2021, 10:12:31 PM] [midea-air] Triggered GET RotationSpeed: 0
[4/9/2021, 10:12:31 PM] [midea-air] Triggered GET TargetHeaterCoolerState while powerState is: 0
[4/9/2021, 10:12:31 PM] [midea-air] Triggered GET CurrentTemperature: 0
[4/9/2021, 10:12:31 PM] [midea-air] Triggered GET CurrentHeaterCoolerState: 0
[4/9/2021, 10:12:31 PM] [midea-air] Triggered GET swingMode: 0
[4/9/2021, 10:12:31 PM] [midea-air] Triggered GET Active, returning: undefined
[4/9/2021, 10:12:31 PM] [midea-air] Triggered GET handleHeatingThresholdTemperature: 0
[4/9/2021, 10:12:31 PM] [homebridge-midea-air] This plugin generated a warning from the characteristic 'Heating Threshold Temperature': characteristic was supplied illegal value: number 0 exceeded minimum of 17. See https://git.io/JtMGR for more info.
[4/9/2021, 10:12:31 PM] [homebridge-midea-air] Error:
at HeatingThresholdTemperature.Characteristic.characteristicWarning (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:2038:105)
at HeatingThresholdTemperature.Characteristic.validateUserInput (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1946:16)
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1533:24
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/util/once.ts:9:18
at MideaAccessory.handleHeatingThresholdTemperatureGet (/homebridge/node_modules/homebridge-midea-air/lib/MideaAccessory.js:352:9)
at HeatingThresholdTemperature.emit (events.js:315:20)
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1508:14
at new Promise ()
at HeatingThresholdTemperature. (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1506:12)
at step (/usr/local/lib/node_modules/homebridge/node_modules/tslib/tslib.js:143:27)
[4/9/2021, 10:12:31 PM] [midea-air] Triggered GET RotationSpeed: 0
[4/9/2021, 10:12:31 PM] [midea-air] Triggered GET TemperatureDisplayUnits false
[4/9/2021, 10:12:31 PM] [midea-air] Triggered GET handleCoolingThresholdTemperature: 0
[4/9/2021, 10:12:31 PM] [homebridge-midea-air] This plugin generated a warning from the characteristic 'Cooling Threshold Temperature': characteristic was supplied illegal value: number 0 exceeded minimum of 17. See https://git.io/JtMGR for more info.
[4/9/2021, 10:12:31 PM] [homebridge-midea-air] Error:
at CoolingThresholdTemperature.Characteristic.characteristicWarning (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:2038:105)
at CoolingThresholdTemperature.Characteristic.validateUserInput (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1946:16)
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1533:24
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/util/once.ts:9:18
at MideaAccessory.handleCoolingThresholdTemperatureGet (/homebridge/node_modules/homebridge-midea-air/lib/MideaAccessory.js:337:9)
at CoolingThresholdTemperature.emit (events.js:315:20)
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1508:14
at new Promise ()
at CoolingThresholdTemperature. (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1506:12)
at step (/usr/local/lib/node_modules/homebridge/node_modules/tslib/tslib.js:143:27)
[4/9/2021, 10:12:33 PM] [midea-air] Triggered SET Active: 1
[4/9/2021, 10:12:33 PM] [midea-air] [sendUpdateToDevice]  Command + Header: [90,90,1,0,90,0,32,0,10,0,0,0,10,10,10,3,2,11,18,20,218,73,0,0,0,16,0,0,0,0,0,0,0,0,0,0,0,0,0,0,170,30,172,0,0,0,0,0,3,2,64,67,0,0,127,127,0,48,0,0,0,0,0,0,0,0,0,0,0,135,249,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0]
[4/9/2021, 10:12:34 PM] [midea-air] Triggered SET Active: 1
[4/9/2021, 10:12:34 PM] [midea-air] [sendUpdateToDevice]  Command + Header: [90,90,1,0,90,0,32,0,10,0,0,0,10,10,10,3,2,11,18,20,218,73,0,0,0,16,0,0,0,0,0,0,0,0,0,0,0,0,0,0,170,30,172,0,0,0,0,0,3,2,64,67,0,0,127,127,0,48,0,0,0,0,0,0,0,0,0,0,0,135,249,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0]
[4/9/2021, 10:12:36 PM] [midea-air] Triggered SET Active: 0
[4/9/2021, 10:12:36 PM] [midea-air] [sendUpdateToDevice]  Command + Header: [90,90,1,0,90,0,32,0,10,0,0,0,10,10,10,3,2,11,18,20,218,73,0,0,0,16,0,0,0,0,0,0,0,0,0,0,0,0,0,0,170,30,172,0,0,0,0,0,3,2,64,66,0,0,127,127,0,48,0,0,0,0,0,0,0,0,0,0,0,135,250,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0]
[4/9/2021, 10:12:39 PM] [midea-air] Triggered SET Active: 1
[4/9/2021, 10:12:39 PM] [midea-air] [sendUpdateToDevice]  Command + Header: [90,90,1,0,90,0,32,0,10,0,0,0,10,10,10,3,2,11,18,20,218,73,0,0,0,16,0,0,0,0,0,0,0,0,0,0,0,0,0,0,170,30,172,0,0,0,0,0,3,2,64,67,0,0,127,127,0,48,0,0,0,0,0,0,0,0,0,0,0,135,249,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0]
[4/9/2021, 10:12:39 PM] [midea-air] Triggered SET TargetHeaterCoolerState: 1
[4/9/2021, 10:12:39 PM] [midea-air] [sendUpdateToDevice]  Command + Header: [90,90,1,0,90,0,32,0,10,0,0,0,10,10,10,3,2,11,18,20,218,73,0,0,0,16,0,0,0,0,0,0,0,0,0,0,0,0,0,0,170,30,172,0,0,0,0,0,3,2,64,67,128,0,127,127,0,48,0,0,0,0,0,0,0,0,0,0,0,135,121,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0]
[4/9/2021, 10:12:39 PM] [homebridge-midea-air] Characteristic 'Target Heater-Cooler State': SET handler returned write response value, though the characteristic doesn't support write response. See https://git.io/JtMGR for more info.
[4/9/2021, 10:12:39 PM] [homebridge-midea-air] Error:
at TargetHeaterCoolerState.Characteristic.characteristicWarning (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:2038:105)
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1663:22
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/util/once.ts:9:18
at MideaAccessory.handleTargetHeaterCoolerStateSet (/homebridge/node_modules/homebridge-midea-air/lib/MideaAccessory.js:254:13)
at TargetHeaterCoolerState.emit (events.js:315:20)
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1632:16
at new Promise ()
at TargetHeaterCoolerState. (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1630:14)
at step (/usr/local/lib/node_modules/homebridge/node_modules/tslib/tslib.js:143:27)
at Object.next (/usr/local/lib/node_modules/homebridge/node_modules/tslib/tslib.js:124:57)
[4/9/2021, 10:12:39 PM] [midea-air] Triggered SET Active: 0
[4/9/2021, 10:12:39 PM] [midea-air] [sendUpdateToDevice]  Command + Header: [90,90,1,0,90,0,32,0,10,0,0,0,10,10,10,3,2,11,18,20,218,73,0,0,0,16,0,0,0,0,0,0,0,0,0,0,0,0,0,0,170,30,172,0,0,0,0,0,3,2,64,66,128,0,127,127,0,48,0,0,0,0,0,0,0,0,0,0,0,135,122,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0]
[4/9/2021, 10:12:42 PM] [midea-air] Triggered SET Active: 1
[4/9/2021, 10:12:42 PM] [midea-air] [sendUpdateToDevice]  Command + Header: [90,90,1,0,90,0,32,0,10,0,0,0,10,10,10,3,2,11,18,20,218,73,0,0,0,16,0,0,0,0,0,0,0,0,0,0,0,0,0,0,170,30,172,0,0,0,0,0,3,2,64,67,128,0,127,127,0,48,0,0,0,0,0,0,0,0,0,0,0,135,121,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0]
[4/9/2021, 10:12:42 PM] [midea-air] Triggered SET TargetHeaterCoolerState: 1
[4/9/2021, 10:12:42 PM] [midea-air] [sendUpdateToDevice]  Command + Header: [90,90,1,0,90,0,32,0,10,0,0,0,10,10,10,3,2,11,18,20,218,73,0,0,0,16,0,0,0,0,0,0,0,0,0,0,0,0,0,0,170,30,172,0,0,0,0,0,3,2,64,67,128,0,127,127,0,48,0,0,0,0,0,0,0,0,0,0,0,135,121,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0]
[4/9/2021, 10:12:42 PM] [homebridge-midea-air] Characteristic 'Target Heater-Cooler State': SET handler returned write response value, though the characteristic doesn't support write response. See https://git.io/JtMGR for more info.
[4/9/2021, 10:12:42 PM] [homebridge-midea-air] Error:
at TargetHeaterCoolerState.Characteristic.characteristicWarning (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:2038:105)
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1663:22
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/util/once.ts:9:18
at MideaAccessory.handleTargetHeaterCoolerStateSet (/homebridge/node_modules/homebridge-midea-air/lib/MideaAccessory.js:254:13)
at TargetHeaterCoolerState.emit (events.js:315:20)
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1632:16
at new Promise ()
at TargetHeaterCoolerState. (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1630:14)
at step (/usr/local/lib/node_modules/homebridge/node_modules/tslib/tslib.js:143:27)
at Object.next (/usr/local/lib/node_modules/homebridge/node_modules/tslib/tslib.js:124:57)
[4/9/2021, 10:12:42 PM] [midea-air] Triggered SET Active: 0
[4/9/2021, 10:12:42 PM] [midea-air] [sendUpdateToDevice]  Command + Header: [90,90,1,0,90,0,32,0,10,0,0,0,10,10,10,3,2,11,18,20,218,73,0,0,0,16,0,0,0,0,0,0,0,0,0,0,0,0,0,0,170,30,172,0,0,0,0,0,3,2,64,66,128,0,127,127,0,48,0,0,0,0,0,0,0,0,0,0,0,135,122,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0]
[4/9/2021, 10:12:48 PM] [midea-air] [MideaPlatform.ts] sendCommand (Intent: [sendUpdateToDevice] (set new params?) attempt 1/2) returned error The asyn reply does not exist
[4/9/2021, 10:12:48 PM] [midea-air] [sendUpdateToDevice] Error sending the command: undefined. Trying to re-login before re-issuing command...
[4/9/2021, 10:12:48 PM] [midea-air] [sendUpdateToDevice] Trying to re-login first
[4/9/2021, 10:12:49 PM] [midea-air] [MideaPlatform.ts] sendCommand (Intent: [sendUpdateToDevice] (set new params?) attempt 1/2) returned error The asyn reply does not exist
[4/9/2021, 10:12:49 PM] [midea-air] [sendUpdateToDevice] Error sending the command: undefined. Trying to re-login before re-issuing command...
[4/9/2021, 10:12:49 PM] [midea-air] [sendUpdateToDevice] Trying to re-login first
[4/9/2021, 10:12:53 PM] [midea-air] [MideaPlatform.ts] sendCommand (Intent: [sendUpdateToDevice] (set new params?) attempt 1/2) returned error The asyn reply does not exist
[4/9/2021, 10:12:53 PM] [midea-air] [sendUpdateToDevice] Error sending the command: undefined. Trying to re-login before re-issuing command...
[4/9/2021, 10:12:53 PM] [midea-air] [sendUpdateToDevice] Trying to re-login first
[4/9/2021, 10:12:54 PM] [midea-air] [MideaPlatform.ts] sendCommand (Intent: [sendUpdateToDevice] (set new params?) attempt 1/2) returned error The asyn reply does not exist
[4/9/2021, 10:12:54 PM] [midea-air] [sendUpdateToDevice] Error sending the command: undefined. Trying to re-login before re-issuing command...
[4/9/2021, 10:12:54 PM] [midea-air] [sendUpdateToDevice] Trying to re-login first
[4/9/2021, 10:12:58 PM] [midea-air] [MideaPlatform.ts] sendCommand (Intent: [sendUpdateToDevice] (set new params?) attempt 1/2) returned error The asyn reply does not exist
[4/9/2021, 10:12:58 PM] [midea-air] [sendUpdateToDevice] Error sending the command: undefined. Trying to re-login before re-issuing command...
[4/9/2021, 10:12:58 PM] [midea-air] [sendUpdateToDevice] Trying to re-login first
[4/9/2021, 10:12:59 PM] [midea-air] [MideaPlatform.ts] sendCommand (Intent: [sendUpdateToDevice] (set new params?) attempt 1/2) returned error The asyn reply does not exist
[4/9/2021, 10:12:59 PM] [midea-air] [sendUpdateToDevice] Error sending the command: undefined. Trying to re-login before re-issuing command...
[4/9/2021, 10:12:59 PM] [midea-air] [sendUpdateToDevice] Trying to re-login first

It’s seem that the plugin pull your AC’s but the command protocol is different.
I’ll check it

did you add deviceId to config?

Yes! Added 4 devices with the IDs from discover and horizontal swing mode

it's look like the Header is deferent.
do you know programming?

I do not want to say I know programming, but maybe I can say I able to read it. If I can help somehow to fix this to you, or you can just tell me what to check please let me know.
Thank you.

any help is blessing.
but now I don't know how to fix it.
I'll try to figure how to add support for more AC units.

Hi I just publish a beta version. 1.0.9-beta.1
try it and tell me if your AC working

Hi! I can only see 1.0.8 as last version.

Go to homebridge, plugins, push the wrench on the bottom right and then install previous version

midea.log.txt
Not working....

O.K.

I'll try to edit the code of mac-zhou/midea-ac-py local communication HA plug-in to see the list of api communication between HA and AC. This plug in works but the homebridge integration isn't so good. If the local communication is the same with the midea server you can find the solution there.

this maybe can help

I couldn't try the 1.0.9 beta version.
I don't know why its not installing on Hoobs.

I remove this version

Just to ensure....
This plugin works on Hoobs?

I don't see why not.

Try 1.2.0-beta.1

I will give it a shot! Thanks
From: Yossi Hillali @.>
Reply-To: hillaliy/homebridge-midea-air @.>
Date: Monday, May 24, 2021 at 10:51 AM
To: hillaliy/homebridge-midea-air @.>
Cc: Subscribed @.>
Subject: Re: [hillaliy/homebridge-midea-air] Midea Mission II support (#3)
Try 1.2.0-beta.1
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/hillaliy/homebridge-midea-air/issues/3#issuecomment-847141426, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AIBFA5QY6CM2AN2RRP4OVDTTPJYYJANCNFSM42QSFIGA.

1.2.0 beta 3 and dont work...

Put Homebridge in debug mode. Check if this plugin can pull the state of your device.
You supposed to see:

Active state
Current temperature
Current heater cooler state
and more.....

And
log.txt

Results

check if device dongle is OSK103.
It's look like

All 4 ACs are same model Mission II with the same dongle OSK102

Do you have Discord?

Sent you at<EMAIL_ADDRESS>

Hello!
i got two mission 2 ACs and i have the same problem. The ACs are comming up in homebridge but can’t controll them and both of the shows temperature 100C sometimes. The wifi adapters are CE-SK103.
thanks a lot!

Hi SK103 & OSK103 don't work with this plugin. Midea changed the command protocol.
If someone will publish the New Midea API I'll add support.

Hi SK103 & OSK103 don't work with this plugin. Midea changed the command protocol.
If someone will publish the New Midea API I'll add support.

Oh, ok! Thanks anyway

My dongles are model K42RAWF.
Do you know if will support?
Em sex., 28 de mai. de 2021 às 06:27, bgeri85 @.***>
escreveu:

Hi SK103 & OSK103 don't work with this plugin. Midea changed the command
protocol.
If someone will publish the New Midea API I'll add support.
Oh, ok! Thanks anyway
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/hillaliy/homebridge-midea-air/issues/3#issuecomment-850283812,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AL35XTKUYN6F6WRWJ3CDBFDTP5OWLANCNFSM42QSFIGA
.

I think that your dongle is EU-SK103X
If I'm right for now no
Until someone will publish the new midea API

I got it.
Do you think I can use other dongle on the AC?
In fact, do you know if exists other midea dongle similar that I can try?
Em sáb., 12 de jun. de 2021 às 04:09, Yossi Hillali <
@.***> escreveu:

I think that your dongle is EU-SK103X
If I'm right for now no
Until someone will publish the new midea API
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/hillaliy/homebridge-midea-air/issues/3#issuecomment-860012399,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AL35XTIR2ZWOBUBZCEZHD7LTSMBZBANCNFSM42QSFIGA
.

Yes you can use OSK102 dongle.
I'm using it.

I found this project. maybe it can help you.
https://github.com/reneklootwijk/mideahvac-dongle

but the original wi-fi dongle for your device is OSK102 or did you adapted?
Em sáb., 12 de jun. de 2021 às 15:05, Yossi Hillali <
@.***> escreveu:

Yes you can use OSK102 dongle.
I'm using it.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/hillaliy/homebridge-midea-air/issues/3#issuecomment-860088569,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AL35XTM6PSAXL6I3GVSOSHLTSOOVZANCNFSM42QSFIGA
.

My dongle is now OSK103, it's different..

I'm using the original dongle - OSK102

Try Version 1.2.8

Same errors. I Sent you the log to discord

Hi SK103 & OSK103 don't work with this plugin. Midea changed the command protocol. If someone will publish the New Midea API I'll add support.

Hi,
It is really strange, I got one of my AC's to work fine with OSK103. Others do not work, but shows the status only. Another wired thing is I cant see nothing from plugin in log in both cases.

Now This plugin support OSK103 but there is some Devices that call Midea Mission II / U
You can see the state on these devices but not control them.
No solution yet.

Now This plugin support OSK103 but there is some Devices that call Midea Mission II / U You can see the state on these devices but not control them. No solution yet.

Many thanks for explanations.
So than Midea Blanc series is same unsupported as Mission II/U

I have a Midea Blanc series with dongle OSK103. Today, with the latest update, v1.5.2,  I am able to turn “on” the unit with Homebridge/HomeKit. I have never been able to do this before.
I am unable to change mode/temperature/fan speed. I am also not able to turn the unit “off” again through Homebridge/HomeKit.

Thanks for the feedback.
I'll keep looking for the new Midea protocol

Same issue for me. However I can confirm that this integration in home assistant does work: https://github.com/mac-zhou/midea-ac-py
So if you'd adapt your code to send out the same commands, they would work fine.

Your welcome to try

Okay looks like the Home Assistant Midea integration is vastly different from this one for Homebridge. In the Python one they're using the local network to communicate through raw TCP packets directly to the dongle instead of using the Midea Air APIs.
I think building something similar for Homebridge would be the way to go in the far future: no dependency on Midea's servers being online, would work if your internet connection is down (as long as you have wi-fi) and less issues when moving to a new API like what Midea announced with MSmart.
For now I'll try to see if I can intercept the HTTP requests that my mobile app is sending and figure out what is the difference between what this Homebridge plugin is sending.

You're welcome to help if you wan't.
Will be better taking via Discord.

I just got a second MiniSplit unit for the my workshop, unfortunetly it came with a US-OSK105. If I can help getting this modual working I would be available.
Here is my logs:
[2022-11-21, 9:18:06 a.m.] [midea-air] Updating accessory: Workshop2<PHONE_NUMBER>83162)
[2022-11-21, 9:18:06 a.m.] [midea-air] [updateValues] Header + Command: 90,90,1,16,89,0,32,0,80,0,0,0,169,65,48,9,14,5,20,20,213,50,1,0,0,17,0,0,0,4,2,0,0,1,0,0,0,0,0,0,170,32,172,0,0,0,0,0,0,3,65,129,0,255,3,255,0,2,0,0,0,0,0,0,0,0,0,0,0,0,3,205,156,16,184,113,186,162,129,39,12,160,157,100,102,118,15,154,166
[2022-11-21, 9:18:06 a.m.] [midea-air] Send command to: Workshop2<PHONE_NUMBER>83162) [updateValues] attempt 1/2 success!
[2022-11-21, 9:18:06 a.m.] [midea-air] Target Temperature: 18˚C
[2022-11-21, 9:18:06 a.m.] [midea-air] Indoor Temperature: 6.4˚C
[2022-11-21, 9:18:06 a.m.] [midea-air] Swing Mode set to: 0
[2022-11-21, 9:18:06 a.m.] [midea-air] Fahrenheit set to: false
[2022-11-21, 9:18:06 a.m.] [midea-air] Turbo Fan set to: false
[2022-11-21, 9:18:06 a.m.] [midea-air] Eco Mode set to: false
[2022-11-21, 9:18:06 a.m.] [midea-air] Turbo Mode set to: false
[2022-11-21, 9:18:06 a.m.] [midea-air] Comfort Sleep set to: false
[2022-11-21, 9:18:06 a.m.] [midea-air] Dryer set to: false
[2022-11-21, 9:18:06 a.m.] [midea-air] Purifier set to: false
[2022-11-21, 9:18:06 a.m.] [midea-air] Power State set to: 0
[2022-11-21, 9:18:06 a.m.] [midea-air] Operational Mode set to: 4
[2022-11-21, 9:18:06 a.m.] [midea-air] Fan Speed set to: 102
[2022-11-21, 9:18:06 a.m.] [midea-air] Full data: 11000000,0,10000010,1100110,1111111,1111111,0,0,0,0,0,111110,11111111,110,0,100,0,0,0,0,0,0,0,0,0,0,0,0,11,11110101,1000001,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
[2022-11-21, 9:18:06 a.m.] [midea-air] [updateValues] Send update command to: Workshop2<PHONE_NUMBER>83162)
[2022-11-21, 9:18:07 a.m.] [midea-air] Send command to: Den<PHONE_NUMBER>6294) [updateValues] attempt 1/2 success!
[2022-11-21, 9:18:07 a.m.] [midea-air] Target Temperature: 22˚C
[2022-11-21, 9:18:07 a.m.] [midea-air] Indoor Temperature: 22.5˚C
[2022-11-21, 9:18:07 a.m.] [midea-air] Outdoor Temperature: -8˚C
[2022-11-21, 9:18:07 a.m.] [midea-air] Swing Mode set to: 3
[2022-11-21, 9:18:07 a.m.] [midea-air] Fahrenheit set to: false
[2022-11-21, 9:18:07 a.m.] [midea-air] Turbo Fan set to: false
[2022-11-21, 9:18:07 a.m.] [midea-air] Eco Mode set to: false
[2022-11-21, 9:18:07 a.m.] [midea-air] Turbo Mode set to: false
[2022-11-21, 9:18:07 a.m.] [midea-air] Comfort Sleep set to: false
[2022-11-21, 9:18:07 a.m.] [midea-air] Dryer set to: false
[2022-11-21, 9:18:07 a.m.] [midea-air] Purifier set to: false
[2022-11-21, 9:18:07 a.m.] [midea-air] Power State set to: 1
[2022-11-21, 9:18:07 a.m.] [midea-air] Operational Mode set to: 4
[2022-11-21, 9:18:07 a.m.] [midea-air] Fan Speed set to: 102
[2022-11-21, 9:18:07 a.m.] [midea-air] Full data: 11000000,1,10000110,1100110,1111111,1111111,0,110011,0,0,0,1011111,100010,0,0,0,0,0,0,0,0,0,0,0,10100,10111000,0,0,0,0,0,0,0,0,0,0,0,0

Hi, thanks for the logs but for now it's don't help.

Okay looks like the Home Assistant Midea integration is vastly different from this one for Homebridge. In the Python one they're using the local network to communicate through raw TCP packets directly to the dongle instead of using the Midea Air APIs.
I think building something similar for Homebridge would be the way to go in the far future: no dependency on Midea's servers being online, would work if your internet connection is down (as long as you have wi-fi) and less issues when moving to a new API like what Midea announced with MSmart. I assume this is what you're doing with the announcement in the README, but that repo is still private so I can't help with the work there.
For now I'll try to see if I can intercept the HTTP requests that my mobile app is sending and figure out what is the difference between what this Homebridge plugin is sending.

Hello @sdebruyn - I am having the same problem here. It turns out my model is Blanc and using OSK103. So I can only view the status of the aircons and not control them. I was really hoping you made progress on this new plugin at all? please let me know. thank you very much

Hi I'm having the same issue with a SURREY AC (another Midea Brands in Argentina). I don't know how to know if it uses OSK102, 103 or 105 like you.
Here is the Homebridge Debug:
Trying to Turn ON Heat on AC.
6/28/2023, 11:17:19 AM] [midea-air] Triggered SET Active To: 1 [6/28/2023, 11:17:19 AM] [midea-air] [sendUpdateToDevice] Header + Command: [90,90,1,16,90,0,32,0,1,0,0,0,189,179,57,14,12,5,20,20,29,129,0,0,0,16,0,0,0,4,2,0,0,1,0,0,0,0,0,0,170,30,172,0,0,0,0,0,3,2,64,1,139,40,127,127,0,60,0,0,0,0,0,0,0,0,0,0,0,108,151,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0] [6/28/2023, 11:17:30 AM] [midea-air] Send command to: Surrey<PHONE_NUMBER>6775) [sendUpdateToDevice] attempt 1/2 returned error: The asyn reply does not exist  (3176)
These is the status of AC:
[6/28/2023, 11:16:44 AM] [midea-air] [updateValues] Send update command to: Surrey<PHONE_NUMBER>6775) [6/28/2023, 11:17:12 AM] [midea-air] Updating accessory: Surrey<PHONE_NUMBER>6775) [6/28/2023, 11:17:12 AM] [midea-air] [updateValues] Header + Command: 90,90,1,16,89,0,32,0,80,0,0,0,169,65,48,9,14,5,20,20,213,50,1,0,0,17,0,0,0,4,2,0,0,1,0,0,0,0,0,0,170,32,172,0,0,0,0,0,0,3,65,129,0,255,3,255,0,2,0,0,0,0,0,0,0,0,0,0,0,0,3,205,156,16,184,113,186,162,129,39,12,160,157,100,102,118,15,154,166 [6/28/2023, 11:17:14 AM] [midea-air] Send command to: Surrey<PHONE_NUMBER>6775) [updateValues] attempt 1/2 success! [6/28/2023, 11:17:14 AM] [midea-air] Target Temperature: 27˚C [6/28/2023, 11:17:14 AM] [midea-air] Indoor Temperature: 18˚C [6/28/2023, 11:17:14 AM] [midea-air] Outdoor Temperature: 10.5˚C [6/28/2023, 11:17:14 AM] [midea-air] Swing Mode set to: 12 [6/28/2023, 11:17:14 AM] [midea-air] Fahrenheit set to: false [6/28/2023, 11:17:14 AM] [midea-air] Turbo Fan set to: false [6/28/2023, 11:17:14 AM] [midea-air] Eco Mode set to: false [6/28/2023, 11:17:14 AM] [midea-air] Turbo Mode set to: false [6/28/2023, 11:17:14 AM] [midea-air] Comfort Sleep set to: false [6/28/2023, 11:17:14 AM] [midea-air] Dryer set to: false [6/28/2023, 11:17:14 AM] [midea-air] Purifier set to: false [6/28/2023, 11:17:14 AM] [midea-air] Power State set to: 0 [6/28/2023, 11:17:14 AM] [midea-air] Operational Mode set to: 4 [6/28/2023, 11:17:14 AM] [midea-air] Fan Speed set to: 40 [6/28/2023, 11:17:14 AM] [midea-air] Full data: 11000000,0,10001011,101000,1111111,1111111,0,111100,0,0,0,1010110,1000111,0,0,0,0,0,0,0,0,0,10011100,110,1000000,0,0,0,0,0,0,0,0,0,0,0,0 [6/28/2023, 11:17:14 AM] [midea-air] [updateValues] Send update command to: Surrey<PHONE_NUMBER>6775) [6/28/2023, 11:17:19 AM] [midea-air] Triggered SET Active To: 1 [6/28/2023, 11:17:19 AM] [midea-air] [sendUpdateToDevice] Header + Command: [90,90,1,16,90,0,32,0,1,0,0,0,189,179,57,14,12,5,20,20,29,129,0,0,0,16,0,0,0,4,2,0,0,1,0,0,0,0,0,0,170,30,172,0,0,0,0,0,3,2,64,1,139,40,127,127,0,60,0,0,0,0,0,0,0,0,0,0,0,108,151,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0] [6/28/2023, 11:17:30 AM] [midea-air] Send command to: Surrey<PHONE_NUMBER>6775) [sendUpdateToDevice] attempt 1/2 returned error: The asyn reply does not exist  (3176) [6/28/2023, 11:17:42 AM] [midea-air] Updating accessory: Surrey<PHONE_NUMBER>6775) [6/28/2023, 11:17:42 AM] [midea-air] [updateValues] Header + Command: 90,90,1,16,89,0,32,0,80,0,0,0,169,65,48,9,14,5,20,20,213,50,1,0,0,17,0,0,0,4,2,0,0,1,0,0,0,0,0,0,170,32,172,0,0,0,0,0,0,3,65,129,0,255,3,255,0,2,0,0,0,0,0,0,0,0,0,0,0,0,3,205,156,16,184,113,186,162,129,39,12,160,157,100,102,118,15,154,166 [6/28/2023, 11:17:44 AM] [midea-air] Send command to: Surrey<PHONE_NUMBER>6775) [updateValues] attempt 1/2 success! [6/28/2023, 11:17:44 AM] [midea-air] Target Temperature: 27˚C [6/28/2023, 11:17:44 AM] [midea-air] Indoor Temperature: 18˚C [6/28/2023, 11:17:44 AM] [midea-air] Outdoor Temperature: 10.5˚C [6/28/2023, 11:17:44 AM] [midea-air] Swing Mode set to: 12 [6/28/2023, 11:17:44 AM] [midea-air] Fahrenheit set to: false [6/28/2023, 11:17:44 AM] [midea-air] Turbo Fan set to: false [6/28/2023, 11:17:44 AM] [midea-air] Eco Mode set to: false [6/28/2023, 11:17:44 AM] [midea-air] Turbo Mode set to: false [6/28/2023, 11:17:44 AM] [midea-air] Comfort Sleep set to: false [6/28/2023, 11:17:44 AM] [midea-air] Dryer set to: false [6/28/2023, 11:17:44 AM] [midea-air] Purifier set to: false [6/28/2023, 11:17:44 AM] [midea-air] Power State set to: 0 [6/28/2023, 11:17:44 AM] [midea-air] Operational Mode set to: 4 [6/28/2023, 11:17:44 AM] [midea-air] Fan Speed set to: 40 [6/28/2023, 11:17:44 AM] [midea-air] Full data: 11000000,0,10001011,101000,1111111,1111111,0,111100,0,0,0,1010110,1000111,0,0,0,0,0,0,0,0,0,10011100,110,1000000,0,0,0,0,0,0,0,0,0,0,0,0 [6/28/2023, 11:17:44 AM] [midea-air] [updateValues] Send update command to: Surrey<PHONE_NUMBER>6775) [6/28/2023, 11:18:12 AM] [midea-air] Updating accessory: Surrey<PHONE_NUMBER>6775) [6/28/2023, 11:18:12 AM] [midea-air] [updateValues] Header + Command: 90,90,1,16,89,0,32,0,80,0,0,0,169,65,48,9,14,5,20,20,213,50,1,0,0,17,0,0,0,4,2,0,0,1,0,0,0,0,0,0,170,32,172,0,0,0,0,0,0,3,65,129,0,255,3,255,0,2,0,0,0,0,0,0,0,0,0,0,0,0,3,205,156,16,184,113,186,162,129,39,12,160,157,100,102,118,15,154,166 [6/28/2023, 11:18:14 AM] [midea-air] Send command to: Surrey<PHONE_NUMBER>6775) [updateValues] attempt 1/2 success! [6/28/2023, 11:18:14 AM] [midea-air] Target Temperature: 27˚C [6/28/2023, 11:18:14 AM] [midea-air] Indoor Temperature: 18˚C [6/28/2023, 11:18:14 AM] [midea-air] Outdoor Temperature: 10.5˚C [6/28/2023, 11:18:14 AM] [midea-air] Swing Mode set to: 12 [6/28/2023, 11:18:14 AM] [midea-air] Fahrenheit set to: false [6/28/2023, 11:18:14 AM] [midea-air] Turbo Fan set to: false [6/28/2023, 11:18:14 AM] [midea-air] Eco Mode set to: false [6/28/2023, 11:18:14 AM] [midea-air] Turbo Mode set to: false [6/28/2023, 11:18:14 AM] [midea-air] Comfort Sleep set to: false [6/28/2023, 11:18:14 AM] [midea-air] Dryer set to: false [6/28/2023, 11:18:14 AM] [midea-air] Purifier set to: false [6/28/2023, 11:18:14 AM] [midea-air] Power State set to: 0 [6/28/2023, 11:18:14 AM] [midea-air] Operational Mode set to: 4 [6/28/2023, 11:18:14 AM] [midea-air] Fan Speed set to: 40 [6/28/2023, 11:18:14 AM] [midea-air] Full data: 11000000,0,10001011,101000,1111111,1111111,0,111100,0,0,0,1010110,1000111,0,0,0,0,0,0,0,0,0,10011100,110,1000000,0,0,0,0,0,0,0,0,0,0,0,0 [6/28/2023, 11:18:14 AM] [midea-air] [updateValues] Send update command to: Surrey<PHONE_NUMBER>6775) [6/28/2023, 11:18:42 AM] [midea-air] Updating accessory: Surrey<PHONE_NUMBER>6775) [6/28/2023, 11:18:42 AM] [midea-air] [updateValues] Header + Command: 90,90,1,16,89,0,32,0,80,0,0,0,169,65,48,9,14,5,20,20,213,50,1,0,0,17,0,0,0,4,2,0,0,1,0,0,0,0,0,0,170,32,172,0,0,0,0,0,0,3,65,129,0,255,3,255,0,2,0,0,0,0,0,0,0,0,0,0,0,0,3,205,156,16,184,113,186,162,129,39,12,160,157,100,102,118,15,154,166 [6/28/2023, 11:18:44 AM] [midea-air] Send command to: Surrey<PHONE_NUMBER>6775) [updateValues] attempt 1/2 success! [6/28/2023, 11:18:44 AM] [midea-air] Target Temperature: 27˚C [6/28/2023, 11:18:44 AM] [midea-air] Indoor Temperature: 18˚C [6/28/2023, 11:18:44 AM] [midea-air] Outdoor Temperature: 10.5˚C [6/28/2023, 11:18:44 AM] [midea-air] Swing Mode set to: 12 [6/28/2023, 11:18:44 AM] [midea-air] Fahrenheit set to: false [6/28/2023, 11:18:44 AM] [midea-air] Turbo Fan set to: false [6/28/2023, 11:18:44 AM] [midea-air] Eco Mode set to: false [6/28/2023, 11:18:44 AM] [midea-air] Turbo Mode set to: false [6/28/2023, 11:18:44 AM] [midea-air] Comfort Sleep set to: false [6/28/2023, 11:18:44 AM] [midea-air] Dryer set to: false [6/28/2023, 11:18:44 AM] [midea-air] Purifier set to: false [6/28/2023, 11:18:44 AM] [midea-air] Power State set to: 0 [6/28/2023, 11:18:44 AM] [midea-air] Operational Mode set to: 4 [6/28/2023, 11:18:44 AM] [midea-air] Fan Speed set to: 40 [6/28/2023, 11:18:44 AM] [midea-air] Full data: 11000000,0,10001011,101000,1111111,1111111,0,111100,0,0,0,1010110,1000111,0,0,0,0,0,0,0,0,0,10011100,110,1000000,0,0,0,0,0,0,0,0,0,0,0,0
If I turn it ON from my cellphone with the Midea APP (in this country called Surrey Smart App) I get the new status of the AC Powered ON.
[6/28/2023, 11:21:14 AM] [midea-air] [updateValues] Send update command to: Surrey<PHONE_NUMBER>6775) [6/28/2023, 11:21:42 AM] [midea-air] Updating accessory: Surrey<PHONE_NUMBER>6775) [6/28/2023, 11:21:42 AM] [midea-air] [updateValues] Header + Command: 90,90,1,16,89,0,32,0,80,0,0,0,169,65,48,9,14,5,20,20,213,50,1,0,0,17,0,0,0,4,2,0,0,1,0,0,0,0,0,0,170,32,172,0,0,0,0,0,0,3,65,129,0,255,3,255,0,2,0,0,0,0,0,0,0,0,0,0,0,0,3,205,156,16,184,113,186,162,129,39,12,160,157,100,102,118,15,154,166 [6/28/2023, 11:21:44 AM] [midea-air] Send command to: Surrey<PHONE_NUMBER>6775) [updateValues] attempt 1/2 success! [6/28/2023, 11:21:44 AM] [midea-air] Target Temperature: 27˚C [6/28/2023, 11:21:44 AM] [midea-air] Indoor Temperature: 18˚C [6/28/2023, 11:21:44 AM] [midea-air] Outdoor Temperature: 10.5˚C [6/28/2023, 11:21:44 AM] [midea-air] Swing Mode set to: 12 [6/28/2023, 11:21:44 AM] [midea-air] Fahrenheit set to: false [6/28/2023, 11:21:44 AM] [midea-air] Turbo Fan set to: false [6/28/2023, 11:21:44 AM] [midea-air] Eco Mode set to: false [6/28/2023, 11:21:44 AM] [midea-air] Turbo Mode set to: false [6/28/2023, 11:21:44 AM] [midea-air] Comfort Sleep set to: false [6/28/2023, 11:21:44 AM] [midea-air] Dryer set to: false [6/28/2023, 11:21:44 AM] [midea-air] Purifier set to: false [6/28/2023, 11:21:44 AM] [midea-air] Power State set to: 0 [6/28/2023, 11:21:44 AM] [midea-air] Operational Mode set to: 4 [6/28/2023, 11:21:44 AM] [midea-air] Fan Speed set to: 40 [6/28/2023, 11:21:44 AM] [midea-air] Full data: 11000000,0,10001011,101000,1111111,1111111,0,111100,0,0,0,1010110,1000111,0,0,0,0,0,0,0,0,0,10011100,110,1000000,0,0,0,0,0,0,0,0,0,0,0,0 [6/28/2023, 11:21:44 AM] [midea-air] [updateValues] Send update command to: Surrey<PHONE_NUMBER>6775) [6/28/2023, 11:22:12 AM] [midea-air] Updating accessory: Surrey<PHONE_NUMBER>6775) [6/28/2023, 11:22:12 AM] [midea-air] [updateValues] Header + Command: 90,90,1,16,89,0,32,0,80,0,0,0,169,65,48,9,14,5,20,20,213,50,1,0,0,17,0,0,0,4,2,0,0,1,0,0,0,0,0,0,170,32,172,0,0,0,0,0,0,3,65,129,0,255,3,255,0,2,0,0,0,0,0,0,0,0,0,0,0,0,3,205,156,16,184,113,186,162,129,39,12,160,157,100,102,118,15,154,166 [6/28/2023, 11:22:18 AM] [midea-air] Send command to: Surrey<PHONE_NUMBER>6775) [updateValues] attempt 1/2 success! [6/28/2023, 11:22:18 AM] [midea-air] Target Temperature: 27˚C [6/28/2023, 11:22:18 AM] [midea-air] Indoor Temperature: 18˚C [6/28/2023, 11:22:18 AM] [midea-air] Outdoor Temperature: 12.5˚C [6/28/2023, 11:22:18 AM] [midea-air] Swing Mode set to: 12 [6/28/2023, 11:22:18 AM] [midea-air] Fahrenheit set to: false [6/28/2023, 11:22:18 AM] [midea-air] Turbo Fan set to: false [6/28/2023, 11:22:18 AM] [midea-air] Eco Mode set to: false [6/28/2023, 11:22:18 AM] [midea-air] Turbo Mode set to: false [6/28/2023, 11:22:18 AM] [midea-air] Comfort Sleep set to: false [6/28/2023, 11:22:18 AM] [midea-air] Dryer set to: false [6/28/2023, 11:22:18 AM] [midea-air] Purifier set to: false [6/28/2023, 11:22:18 AM] [midea-air] Power State set to: 1 [6/28/2023, 11:22:18 AM] [midea-air] Operational Mode set to: 4 [6/28/2023, 11:22:18 AM] [midea-air] Fan Speed set to: 40 [6/28/2023, 11:22:18 AM] [midea-air] Full data: 11000000,1,10001011,101000,1111111,1111111,0,111100,0,0,0,1010110,1001011,0,0,0,0,0,0,0,0,0,10011100,10000,110001,0,0,0,0,0,0,0,0,0,0,0
Any help will be appreciated!

In case any of you want to use Homebridge with an OSK105 dongle, I've made a plugin which communicates with the Midea AC on local network, not through cloud, and it's working with the mentioned dongle. The plugin is still in development (so there is no npm package at the moment), but you are welcome to try and test it. https://github.com/kovapatrik/homebridge-midea

In case any of you want to use Homebridge with an OSK105 dongle, I've made a plugin which communicates with the Midea AC on local network, not through cloud, and it's working with the mentioned dongle. The plugin is still in development (so there is no npm package at the moment), but you are welcome to try and test it. https://github.com/kovapatrik/homebridge-midea-platform

It works! THANK YOU!

Thank you very much. I've been looking for such a plugin for a year.

Hi, my AC connects with the NetHome Plus app, is thera any way to add it?

Dear Patrik! It works like a charm, but there are a few bugs, questions

in ios homekit the on/off button/switch does nothing, changing cool-off-dry-heat works and moving the switch but vice versa is not - in homebridge its do the same as the default tile so its maybe unnecessary
If the ac has two swing modes only one oscillationg come up (marked that i have both vertical and horizontal)
Display off is not showing in HK - but i think its a homekit limitation (in homebridge it works)
FanOnly mode is set but cant see an option on the accessories neither in HB or HK
IDK that activating eco mod is possible

Thanks a lot again for the great plugin!

In case any of you want to use Homebridge with an OSK105 dongle, I've made a plugin which communicates with the Midea AC on local network, not through cloud, and it's working with the mentioned dongle. The plugin is still in development (so there is no npm package at the moment), but you are welcome to try and test it. https://github.com/kovapatrik/homebridge-midea-platform

Dear Patrik! It works like a charm, but there are a few bugs, questions

in ios homekit the on/off button/switch does nothing, changing cool-off-dry-heat works and moving the switch but vice versa is not - in homebridge its do the same as the default tile so its maybe unnecessary
If the ac has two swing modes only one oscillationg come up (marked that i have both vertical and horizontal)
Display off is not showing in HK - but i think its a homekit limitation (in homebridge it works)
FanOnly mode is set but cant see an option on the accessories neither in HB or HK
IDK that activating eco mod is possible

Thanks a lot again for the great plugin!

Thanks for the feedback but please create issues in the my repository, don't spam this one about another plugin!


Issue with response parameter

I've tried integrating this with Fortify / Jetstream on my login page.
Below is in my FortifyServiceProvider
`
Fortify::authenticateUsing(function (Request $request) {
$user = User::where('email', $request->email)->first();
$request->validate([
'cf-turnstile-response' => ['required', Rule::turnstile()],
]);
        if ($user &&
            Hash::check($request->password, $user->password)) {
            return $user;
        }

        return false;
    });

`
Then in the login view, I have added the component

                         <x-turnstile data-theme="light"/>

However, when trying to login I am getting the following error:
The response parameter has already been validated before.
I also have the @turnstile scripts directive in my layouts file under the header

You should make app/Http/Requests/CustomLoginRequest.php
<?php

namespace App\Http\Requests;

use Illuminate\Validation\Rule;
use Laravel\Fortify\Fortify;
use Laravel\Fortify\Http\Requests\LoginRequest;

class CustomLoginRequest extends LoginRequest
{
    /**
     * Get the validation rules that apply to the request.
     *
     * @return array
     */
    public function rules()
    {
        return [
            Fortify::username() => 'required|string',
            'password' => 'required|string',
            'cf-turnstile-response' => ['required', Rule::turnstile()],
        ];
    }
}

app/Providers/FortifyServiceProvider.php

class FortifyServiceProvider extends ServiceProvider
{
    /**
     * Register any application services.
     */
    public function register(): void
    {
        $this->app->bind(LoginRequest::class, CustomLoginRequest::class);
    }

    ...
}

resources/views/auth/login.blade.php

                <x-turnstile />


Opendata Export & Result Button Fixes & Localization of End Results

Adds Export functionality for the Open Data Portal as PDFs.
Fixes 'Start Over' button to return to start on Result screen.
Fixes "Choose File' button to load results correctly on Results screen.
Updates version to 0.8
Moves the Github Link to a button.
Moves "Start Over" button on result screen to fit correctly.
Adds an alternate language field for textboxes tied to the Export via model attribute.
Adds titles to subsections in Exports. (eg: "De-Risking And Mitigation Measures - Procedural Fairness")
Fix missing Business Drivers and About Systems sections not appearing.

Just closing and re-opening to try and trigger the Netlify build


Clean-up pulltoken & pushtoken manipulation && support multiple registries all at once

After this change, operator will collect all pullsecrets available on the cluster and combine them into a single one and provide -pullsecret variable to the Falcon Installer & Injector.
This is useful in cases where non-standard registry is used OR multiple registries are being used.
Example:

openshift cluster using Red Hat registries together with EKS registries, but not openshift/imagestreams

/cc @jhseceng


There is some way to filter users one each other?

Hey,
We are implementing sendbird + widget in our platform but we have a particular case where clients can only see support users on chat users list, they cannot see another clients, for example.
We can manage widget's online users list to filter what kind of users a specific user can see?
Also, we can disable logout button on widget?
Thanks

Hi @wenderjean
We provide some filter as userIds, metaDataKey, and metaDataValue in UserListQuery.
Please, follow below.
const sb = new SendBird({ appId: 'YOUR_APP_ID' });
let query = sb.createUserListQuery();
// let query = sb.createUserListQuery(['user_id_1', 'user_id_2']);
query.metaDataKey = 'key';
query.metaDataValue = 'value';
query.next(function(res, err) {
    console.log(res, err);
});

If you want to disable logout button, you can modify the code as the conditions you want.
Thank you for your interest in SendBird SDK. :)

Hey @Alchemist85K , but is possible to tell widget to follow my query when rendering the list of users to start a chat?

@wenderjean .
The sample is initializing the userListQuery variable when starting a new chat.
Please modify the sample you download, if you don't want to it.
Thanks.


Add documentation for text functions in SQL

prior pr - #1166

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
8 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.03%) to 98.971%

Files with Coverage Reduction
New Missed Lines
%

core/src/executor/evaluate/mod.rs
8
98.12%

Totals

Change from base Build<PHONE_NUMBER>:
0.03%

Covered Lines:
45225

Relevant Lines:
45695

💛  - Coveralls


error MSB6003: The specified task executable "MakePri.exe" could not be run. System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.VisualStudio.Utilities.Internal, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.

Describe the bug
Almost the same as #4777 , happens occasionally when I update the wasdk nuget to a newer version.
Build log:
1>ListViewSelectedIndex-WinUI.vcxproj -> D:\WinUI-Bug\19-ListViewSelectedIndex\x64\Debug\ListViewSelectedIndex-WinUI\ListViewSelectedIndex_WinUI.exe
1>D:\WinUI-Bug\19-ListViewSelectedIndex\packages\Microsoft.WindowsAppSDK.1.6.240923002\build\Microsoft.Build.Msix.Pri.targets(304,5): error MSB6003: The specified task executable "MakePri.exe" could not be run. System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.VisualStudio.Utilities.Internal, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
1>D:\WinUI-Bug\19-ListViewSelectedIndex\packages\Microsoft.WindowsAppSDK.1.6.240923002\build\Microsoft.Build.Msix.Pri.targets(304,5): error MSB6003: File name: 'Microsoft.VisualStudio.Utilities.Internal, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
1>D:\WinUI-Bug\19-ListViewSelectedIndex\packages\Microsoft.WindowsAppSDK.1.6.240923002\build\Microsoft.Build.Msix.Pri.targets(304,5): error MSB6003:    at Microsoft.VisualStudio.Telemetry.TelemetrySessionInitializer.BuildInitializer(TelemetrySessionSettings telemetrySessionSettings)
1>D:\WinUI-Bug\19-ListViewSelectedIndex\packages\Microsoft.WindowsAppSDK.1.6.240923002\build\Microsoft.Build.Msix.Pri.targets(304,5): error MSB6003:    at Microsoft.VisualStudio.Telemetry.TelemetryService.get_DefaultSession()
1>D:\WinUI-Bug\19-ListViewSelectedIndex\packages\Microsoft.WindowsAppSDK.1.6.240923002\build\Microsoft.Build.Msix.Pri.targets(304,5): error MSB6003:    at Microsoft.Build.Msix.Telemetry.CreateTelemetrySession(String vsTelemetrySession)
1>D:\WinUI-Bug\19-ListViewSelectedIndex\packages\Microsoft.WindowsAppSDK.1.6.240923002\build\Microsoft.Build.Msix.Pri.targets(304,5): error MSB6003:    at System.Collections.Concurrent.ConcurrentDictionary`2.GetOrAdd(TKey key, Func`2 valueFactory)
1>D:\WinUI-Bug\19-ListViewSelectedIndex\packages\Microsoft.WindowsAppSDK.1.6.240923002\build\Microsoft.Build.Msix.Pri.targets(304,5): error MSB6003:    at Microsoft.Build.Msix.TelemetryOperation..ctor(String vsTelemetrySession, String eventNameSuffix)
1>D:\WinUI-Bug\19-ListViewSelectedIndex\packages\Microsoft.WindowsAppSDK.1.6.240923002\build\Microsoft.Build.Msix.Pri.targets(304,5): error MSB6003:    at Microsoft.Build.Msix.Pri.WinAppSdkGenerateProjectPriFile.ExecuteTool(String pathToTool, String responseFileCommands, String commandLineCommands)
1>D:\WinUI-Bug\19-ListViewSelectedIndex\packages\Microsoft.WindowsAppSDK.1.6.240923002\build\Microsoft.Build.Msix.Pri.targets(304,5): error MSB6003:    at Microsoft.Build.Utilities.ToolTask.Execute()
1>D:\WinUI-Bug\19-ListViewSelectedIndex\packages\Microsoft.WindowsAppSDK.1.6.240923002\build\Microsoft.Build.Msix.Pri.targets(304,5): error MSB6003:
1>D:\WinUI-Bug\19-ListViewSelectedIndex\packages\Microsoft.WindowsAppSDK.1.6.240923002\build\Microsoft.Build.Msix.Pri.targets(304,5): error MSB6003: WRN: Assembly binding logging is turned OFF.
1>D:\WinUI-Bug\19-ListViewSelectedIndex\packages\Microsoft.WindowsAppSDK.1.6.240923002\build\Microsoft.Build.Msix.Pri.targets(304,5): error MSB6003: To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
1>D:\WinUI-Bug\19-ListViewSelectedIndex\packages\Microsoft.WindowsAppSDK.1.6.240923002\build\Microsoft.Build.Msix.Pri.targets(304,5): error MSB6003: Note: There is some performance penalty associated with assembly bind failure logging.
1>D:\WinUI-Bug\19-ListViewSelectedIndex\packages\Microsoft.WindowsAppSDK.1.6.240923002\build\Microsoft.Build.Msix.Pri.targets(304,5): error MSB6003: To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
1>D:\WinUI-Bug\19-ListViewSelectedIndex\packages\Microsoft.WindowsAppSDK.1.6.240923002\build\Microsoft.Build.Msix.Pri.targets(304,5): error MSB6003:
1>Done building project "ListViewSelectedIndex-WinUI.vcxproj" -- FAILED.
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========
========== Build completed at 2:23 and took 01.327 seconds ==========
========== Deploy: 0 succeeded, 0 failed, 0 skipped ==========
========== Deploy completed at 2:23 and took 01.327 seconds ==========

Steps to reproduce the bug

Create a packaged winui3 app (C++)
Build once.
Upgrade the wasdk package to a newer version.
Build again.

Expected behavior
No response
Screenshots

NuGet package version
Windows App SDK 1.6.1: 1.6.240923002
Packaging type
Packaged (MSIX)
Windows version
No response
IDE
Visual Studio 2022
Additional context
No response

Did you find a fix?

Hi @HO-COOH,
For this issue and issue #4777, are you still be able to repro it? If so, can you use msbuild -bl switch (msbuild MyProject.proj -bl) to generate a binary log file (.binlog) and share it out. For details, visit this document. Once .binlog file is provided, we can try to figure out what went wrong in the build process.

@LegendaryBlair This issue really only happens when launching for debugging in Visual Studio and trust me, it will reproduce. It does NOT seems to reproduce when using msbuild in command line. In this screenshot I first build it inside visual studio (after downgrading the wasdk version, but upgrading will also easily reproduces), failed with makepri.exe, then run msbuild in the developer terminal, and it build successfully.

Hi @HO-COOH,
Just want to clarify, did this error happen when you press F5 or when you clicked build on a project? F5 operation could do more things like app deployment.
In case the latter, you can try to collect .binlog file following the instructions below:

Install the Project System Tools Extension: This extension is available for Visual Studio 2017, 2019, and 2022. You can find it in the Visual Studio Marketplace and install it directly from Visual Studio.

Open the Build Logging Tool Window: Once the extension is installed, go to View > Other Windows > Build Logging to open the Build Logging tool window.

Start Logging Builds: In the Build Logging tool window, click the Start logging builds button. This will start capturing the build logs for any projects you build in Visual Studio.

Build Your Project: Now, build your project as you normally would by clicking the Build button or using the Build menu.

Stop Logging and Save the .binlog File: After the build is complete, go back to the Build Logging tool window and click the Stop logging builds button. You will be prompted to save the .binlog file, which contains the detailed build logs.

@LegendaryBlair WASDKBuildRepro_Debug_x64_DesignTimeBuild_2024-12-26T23_35_20.5421073+08_00.zip

Hi @HO-COOH
Today I used MSBuild Structured Log Viewer tool to analyze your log. It turned out that this build was successful.
I'm wondering if you can share your solution as zip file so that I can repro from my end.

@LegendaryBlair
Sorry I might be drunk then, I think I build twice and it logged the success one.
Here is the corrected one. WASDKBuildRepro_Debug_x64_Build_2024-12-27T19_45_30.0459603+08_00.zip


Filter events based on location in similar events section

To be done after #198 gets merged
Working on it :+1:

if this one is open could i work on this ?


feature: support props.wrapStyle

Support props.wrapStyle to add styles to wrap domElement

Thanks for creating this pull request. At first glance this looks good, and like a sensible option to add. Will do a deeper review in the next day or two so we can get this merged and published.

Released in https://github.com/single-spa/single-spa-react/releases/tag/v2.12.0. Could you please submit a pull request to the documentation for this? The file to change is https://github.com/single-spa/single-spa.js.org/blob/master/website/versioned_docs/version-5.x/ecosystem-react.md. Thanks for your help with this.

Released in https://github.com/single-spa/single-spa-react/releases/tag/v2.12.0. Could you please submit a pull request to the documentation for this? The file to change is https://github.com/single-spa/single-spa.js.org/blob/master/website/versioned_docs/version-5.x/ecosystem-react.md. Thanks for your help with this.

Pls check this MR: https://github.com/single-spa/single-spa.js.org/pull/211


[Benchmark] Change mii to use persistent deployment and support tensor parallel

Description
When running benchmarks/benchmark/benchmark_throughput.py using deepspeed-mii backend, the original code uses non-persistent pipeline deployment, which does not support tensor parallelism and will generate errors when tp > 1.
Solution
Change deepspeed-mii backend to use persistent deployment.
The code is verified using Llama-2-7b and 4 A100 GPUs. After the change, tensor parallelism (e.g. tp=4) can be correctly supported for deepspeed-mii backend. I also compared performance of running Llama-2-7b on single A100 GPU and the throughput performance is the same as running with non-persistent deployment.
The use of persistent deployment is also encouraged in DeepSpeed's benchmark. (link)
BEFORE SUBMITTING, PLEASE READ THE CHECKLIST BELOW AND FILL IN THE DESCRIPTION ABOVE

 PR Checklist (Click to Expand)
Thank you for your contribution to vLLM! Before submitting the pull request, please ensure the PR meets the following criteria. This helps vLLM maintain the code quality and improve the efficiency of the review process.
PR Title and Classification
Only specific types of PRs will be reviewed. The PR title is prefixed appropriately to indicate the type of change. Please use one of the following:

[Bugfix] for bug fixes.
[CI/Build] for build or continuous integration improvements.
[Doc] for documentation fixes and improvements.
[Model] for adding a new model or improving an existing model. Model name should appear in the title.
[Frontend] For changes on the vLLM frontend (e.g., OpenAI API server, LLM class, etc.)
[Kernel] for changes affecting CUDA kernels or other compute kernels.
[Core] for changes in the core vLLM logic (e.g., LLMEngine, AsyncLLMEngine, Scheduler, etc.)
[Hardware][Vendor] for hardware-specific changes. Vendor name should appear in the prefix (e.g., [Hardware][AMD]).
[Misc] for PRs that do not fit the above categories. Please use this sparingly.

Note: If the PR spans more than one category, please include all relevant prefixes.
Code Quality
The PR need to meet the following code quality standards:

We adhere to Google Python style guide and Google C++ style guide.
Pass all linter checks. Please use format.sh to format your code.
The code need to be well-documented to ensure future contributors can easily understand the code.
Include sufficient tests to ensure the project to stay correct and robust. This includes both unit tests and integration tests.
Please add documentation to docs/source/ if the PR modifies the user-facing behaviors of vLLM. It helps vLLM user understand and utilize the new features or changes.

Notes for Large Changes
Please keep the changes as concise as possible. For major architectural changes (>500 LOC excluding kernel/data/config/test), we would expect a GitHub issue (RFC) discussing the technical design and justification. Otherwise, we will tag it with rfc-required and might not go through the PR.
What to Expect for the Reviews
The goal of the vLLM team is to be a transparent reviewing machine. We would like to make the review process transparent and efficient and make sure no contributor feel confused or frustrated. However, the vLLM team is small, so we need to prioritize some PRs over others. Here is what you can expect from the review process:

 After the PR is submitted, the PR will be assigned to a reviewer. Every reviewer will pick up the PRs based on their expertise and availability.
 After the PR is assigned, the reviewer will provide status update every 2-3 days. If the PR is not reviewed within 7 days, please feel free to ping the reviewer or the vLLM team.
 After the review, the reviewer will put an  action-required label on the PR if there are changes required. The contributor should address the comments and ping the reviewer to re-review the PR.
 Please respond to all comments within a reasonable time frame. If a comment isn't clear or you disagree with a suggestion, feel free to ask for clarification or discuss the suggestion.

Thank You
 Finally, thank you for taking the time to read these guidelines and for your interest in contributing to vLLM. Your contributions make vLLM a great tool for everyone!

@WoosukKwon i recall originally there were some issue with this approach but I don't remember exactly. Do you think this is okay?

To my understanding, the persistent deployment will involve the overhead of handling the requests, while the purpose of benchmark_throughput.py is to get the purse performance of the engine without the overhead.

I think the problem for non-persistent pipeline is that it does not support tuning tensor parallel degree when invoked (to my understanding). It seems that we need to wrap the program with deepspeed launcher according to this post.

FYI - The way deepspeed-mii works is slightly different from vllm or tensorrt-llm since its inference engine is essentially taken from deepspeed and the batching logics happens on the deepspeed-mii layer. That's why unlike LLM from vLLM, their client object is essentially an API server/persistent deployment under the hood.