HI

I receive the following warning after the latest update to 4.9

"ClimateDevice is deprecated, modify MideaClimateACDevice to extend ClimateEntity"

As I have read : There has been a change with naming the entities. For now they’re just a warning for the code owners to do some work. But after a certain update it will break.
All integrations in Home Assistant have been upgraded. Custom component authors need to do the migration themselves. You can do this while keeping backwards compatibility by using the following snippet:

https://developers.home-assistant.io/blog/2020/05/14/entity-class-names/?fbclid=IwAR31aU6j2Z5zyX0DhwArOXHnI9YWMkcueVM7rRCHS1FfhFcLG4uitA528yM

This is my configuration.yaml - which was working fine before the update

climate:

Configuration for MideaA/C

• platform: midea_ac
  host: !secret ac_ip
  id: !secret ac_id

Describe the bug （描述一下问题）
A clear and concise description of what the bug is.

Versions (版本信息)

• Home Assistant version: 0.110.5
• Midea msmart version:

ha 控制页面设置空调扫风模式，隔几秒钟后自动切换回off状态

Describe the bug （描述一下问题）

Currently dehumidifer like EVA II PRO WiFi Smart Dehumidifier are not working, although the Midea Air application works with them just fine.

The following error occurs when the integration starts:

I also noticed that in the library for the device type for a dehumidifer you have code 0x00 when it should be 0xA1

Screenshots / Logs / Pcap File（屏幕截图/日志/抓包文件）

Logger: homeassistant.helpers.entity
Source: custom_components/midea_ac/climate.py:108
First occurred: 11:16:32 AM (205 occurrences)
Last logged: 12:10:40 PM

Update for climate.midea_ac_e42300000011 fails
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 279, in async_update_ha_state
await self.async_device_update()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 470, in async_device_update
await self.async_update()
File "/config/custom_components/midea_ac/climate.py", line 108, in async_update
await self.hass.async_add_executor_job(self._device.refresh)
File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/local/lib/python3.7/site-packages/msmart/device.py", line 173, in refresh
data = self._lan_service.appliance_transparent_send(data)
File "/usr/local/lib/python3.7/site-packages/msmart/lan.py", line 69, in appliance_transparent_send
response = bytearray(self.request(data))[40:88]
TypeError: 'NoneType' object is not iterable

Versions (版本信息)

• Home Assistant version: 0.110.2
• Midea msmart version: 0.1.13

2020-06-14 15:19:20 INFO (SyncWorker_8) [homeassistant.components.zeroconf] Starting Zeroconf broadcast
2020-06-14 15:19:30 INFO (SyncWorker_6) [msmart.lan] Connect the Device 192.168.2.181:6444 TimeOut for 10s. don't care about a small amount of this. if many maybe not support.
2020-06-14 15:19:37 INFO (SyncWorker_17) [msmart.lan] Connect the Device 192.168.2.181:6444 TimeOut for 10s. don't care about a small amount of this. if many maybe not support.
日志如下：
2020-06-14 15:19:45 INFO (SyncWorker_9) [msmart.lan] Connect the Device 192.168.2.181:6444 TimeOut for 10s. don't care about a small amount of this. if many maybe not support.
2020-06-14 15:20:02 INFO (SyncWorker_12) [msmart.lan] Connect the Device 192.168.2.181:6444 TimeOut for 10s. don't care about a small amount of this. if many maybe not support.
2020-06-14 15:20:18 INFO (SyncWorker_10) [msmart.lan] Connect the Device 192.168.2.181:6444 TimeOut for 10s. don't care about a small amount of this. if many maybe not support.
2020-06-14 15:20:34 INFO (SyncWorker_8) [msmart.lan] Connect the Device 192.168.2.181:6444 TimeOut for 10s. don't care about a small amount of this. if many maybe not support.
2020-06-14 15:20:50 INFO (SyncWorker_15) [msmart.lan] Connect the Device 192.168.2.181:6444 TimeOut for 10s. don't care about a small amount of this. if many maybe not support.
2020-06-14 15:21:06 INFO (SyncWorker_14) [msmart.lan] Connect the Device 192.168.2.181:6444 TimeOut for 10s. don't care about a small amount of this. if many maybe not support.
2020-06-14 15:21:22 INFO (SyncWorker_19) [msmart.lan] Connect the Device 192.168.2.181:6444 TimeOut for 10s. don't care about a small amount of this. if many maybe not support.
Versions (版本信息)

• Home Assistant version: 0.110.1
• Midea msmart version: 插件版本是0.1.18

I am working on a homebridge plugin for Midea AC units and I‘m trying to get the firmware version currently running on the device.

Does anyone know if the firmware version is embedded somewhere in the appliance response?

I already found a call to the cloud API (https://mapp.appsmb.com/v1/app2base/data/transmit?serviceUrl=/ota/version) in the app, however my call (using the applianceId and the userId as parameters) is failing with ValueInvalid error. Is anyone interested in this, familiar with the API and wanting to help?

Thank you

Tobias Timpe

temp_step 为非1的情况设置不能生效

1. 在configuration.yaml 中添加tem_step:
   temp_step: 0.5

2. 通过UI 设置温度

3. 设置后过一会系统返回整数位的值并刷新UI位整数位，比如设置的是28.5度，最后刷新后为28，设置的是29.5度返回的就是29

Expected behavior
可以正确安装步长设置，当然前天是空调是支持的

Versions

• Home Assistant version: 109.6
• Midea integration version (commit hash):
  commit 99ba820
  Author: mac_zhou [email protected]
  Date: Fri May 8 16:01:06 2020 +0800

I have a midea air conditioner with integrated wifi .... I followed all the parameters indicated by the repositories but nothing .... there is the extent of the air conditioner but nothing works ....

空调当前温度显示为102.5度
在美的美居里面显示是正常的（室外:24度 室内:25度）

After the update, this error is reported:
(core in docker: 0.109.6)

ERROR (MainThread) [homeassistant.components.climate] Error while setting up midea_ac platform for climate
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 178, in _async_setup_platform
await asyncio.wait_for(asyncio.shield(task), SLOW_SETUP_MAX_WAIT)
File "/usr/local/lib/python3.7/asyncio/tasks.py", line 442, in wait_for
return fut.result()
File "/config/custom_components/midea_ac/climate.py", line 65, in async_setup_platform
client = midea_device(device_ip, int(device_id), device_port)
TypeError: init() takes 3 positional arguments but 4 were given

Describe the bug （描述一下问题）
I get Authentication Failed in HA logs and so components its not initialized

Screenshots / Logs / Pcap File（屏幕截图/日志/抓包文件）
Logger: homeassistant.components.climate
Source: custom_components/midea_ac/climate.py:73
Integration: Termostato (documentation, issues)
First occurred: 22:24:19 (1 occurrences)
Last logged: 22:24:19

Error while setting up midea_ac platform for climate
Traceback (most recent call last):
File "/home/pi/hassmar20/lib/python3.7/site-packages/homeassistant/helpers/entity_platform.py", line 193, in _async_setup_platform
await asyncio.shield(task)
File "/home/pi/.homeassistant/custom_components/midea_ac/climate.py", line 73, in async_setup_platform
device.authenticate(device_8370_only_ac_mac, device_8370_only_wifi_ssid, device_8370_only_wifi_pw)
File "/home/pi/hassmar20/lib/python3.7/site-packages/msmart/device.py", line 43, in authenticate
self._authenticate()
File "/home/pi/hassmar20/lib/python3.7/site-packages/msmart/device.py", line 46, in _authenticate
self._lan_service.authenticate(self._mac, self._wifi_ssid, self._wifi_pw)
File "/home/pi/hassmar20/lib/python3.7/site-packages/msmart/lan.py", line 68, in authenticate
self._authenticate()
File "/home/pi/hassmar20/lib/python3.7/site-packages/msmart/lan.py", line 80, in _authenticate
raise error
File "/home/pi/hassmar20/lib/python3.7/site-packages/msmart/lan.py", line 76, in _authenticate
tcp_key = self.security.tcp_key(response, self._key)
File "/home/pi/hassmar20/lib/python3.7/site-packages/msmart/security.py", line 90, in tcp_key
raise Exception('authentication failed')
Exception: authentication failed

Versions (版本信息)

• Home Assistant version: 0.115.6
• Midea msmart version: 0.1.20 (support-8370 version)

三台相同型号的美的空调，刚开始都可以正常接入，其中两台使用几天后一直报timeout，从log上看是有收到报文的，大佬帮忙看看是插件的问题还是其他问题，app 三台都可以正常控制，所以应该不是网络问题。
2020-06-08 17:28:04 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.childrenroom_aircondition is taking over 10 seconds
2020-06-08 17:28:04 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.secondaryroom_aircondition is taking over 10 seconds
2020-06-08 17:28:04 INFO (SyncWorker_12) [msmart.lan] Connect the Device 192.168.1.136:6444 TimeOut for 10s. don't care about a small amount of this. if many maybe not support.
2020-06-08 17:28:04 DEBUG (SyncWorker_12) [msmart.device] refresh - Recieved from 192.168.1.136, e85e02000022:
2020-06-08 17:28:04 INFO (SyncWorker_3) [msmart.lan] Connect the Device 192.168.1.130:6444 TimeOut for 10s. don't care about a small amount of this. if many maybe not support.
2020-06-08 17:28:04 DEBUG (SyncWorker_3) [msmart.device] refresh - Recieved from 192.168.1.130, 1f850200001b:
2020-06-08 17:28:10 DEBUG (SyncWorker_9) [msmart.packet_builder] Finalize request data: aa20ac00000000000003410000ff03ff00020000000000000000000000000004e9
2020-06-08 17:28:10 DEBUG (SyncWorker_11) [msmart.packet_builder] Finalize request data: aa20ac00000000000003410000ff03ff00020000000000000000000000000004e9
2020-06-08 17:28:10 DEBUG (SyncWorker_8) [msmart.packet_builder] Finalize request data: aa20ac00000000000003410000ff03ff00020000000000000000000000000004e9
2020-06-08 17:28:10 DEBUG (SyncWorker_9) [msmart.lan] Sending to 192.168.1.131:6444 5a5a011168002000000000000000000000000000e2740200001c0000000000000000000000000000c7ec8e4276f8accc266a4648044169534ef900b4addf8808145b702d1c28520aec9d938eeaae3d871b99ce4b7e20a37bd8e11e52e30e33efebb4f556214a58a2.
2020-06-08 17:28:10 DEBUG (SyncWorker_11) [msmart.lan] Sending to 192.168.1.136:6444 5a5a011168002000000000000000000000000000e85e020000220000000000000000000000000000c7ec8e4276f8accc266a4648044169534ef900b4addf8808145b702d1c28520aec9d938eeaae3d871b99ce4b7e20a37b45ed13363ac83da9f77862d07955814c.
2020-06-08 17:28:10 DEBUG (SyncWorker_8) [msmart.lan] Sending to 192.168.1.130:6444 5a5a0111680020000000000000000000000000001f850200001b0000000000000000000000000000c7ec8e4276f8accc266a4648044169534ef900b4addf8808145b702d1c28520aec9d938eeaae3d871b99ce4b7e20a37b2aa3c0ae20c7311a637cdcff277ce635.
2020-06-08 17:28:11 DEBUG (SyncWorker_9) [msmart.lan] Received from 192.168.1.131:6444 5a5a011168002000000000000000000000000000e2740200001c0000000000000000000000000000c7ec8e4276f8accc266a4648044169534ef900b4addf8808145b702d1c28520aec9d938eeaae3d871b99ce4b7e20a37bd8e11e52e30e33efebb4f556214a58a2.
2020-06-08 17:28:11 DEBUG (SyncWorker_9) [msmart.device] refresh - Recieved from 192.168.1.131, e2740200001c: aa23ac00000000000203c0004e667f7f00000000006cff1200540000000000000000ad3c
2020-06-08 17:28:11 DEBUG (SyncWorker_9) [msmart.command] Appliance response data: c0004e667f7f00000000006cff1200540000000000000000ad3c
2020-06-08 17:28:20 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.childrenroom_aircondition is taking over 10 seconds
2020-06-08 17:28:20 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.secondaryroom_aircondition is taking over 10 seconds
2020-06-08 17:28:20 INFO (SyncWorker_11) [msmart.lan] Connect the Device 192.168.1.136:6444 TimeOut for 10s. don't care about a small amount of this. if many maybe not support.
2020-06-08 17:28:20 DEBUG (SyncWorker_11) [msmart.device] refresh - Recieved from 192.168.1.136, e85e02000022:
2020-06-08 17:28:20 INFO (SyncWorker_8) [msmart.lan] Connect the Device 192.168.1.130:6444 TimeOut for 10s. don't care about a small amount of this. if many maybe not support.
2020-06-08 17:28:20 DEBUG (SyncWorker_8) [msmart.device] refresh - Recieved from 192.168.1.130, 1f850200001b:
2020-06-08 17:28:26 DEBUG (SyncWorker_18) [msmart.packet_builder] Finalize request data: aa20ac00000000000003410000ff03ff00020000000000000000000000000004e9
2020-06-08 17:28:26 DEBUG (SyncWorker_0) [msmart.packet_builder] Finalize request data: aa20ac00000000000003410000ff03ff00020000000000000000000000000004e9
2020-06-08 17:28:26 DEBUG (SyncWorker_1) [msmart.packet_builder] Finalize request data: aa20ac00000000000003410000ff03ff00020000000000000000000000000004e9
2020-06-08 17:28:26 DEBUG (SyncWorker_18) [msmart.lan] Sending to 192.168.1.131:6444 5a5a011168002000000000000000000000000000e2740200001c0000000000000000000000000000c7ec8e4276f8accc266a4648044169534ef900b4addf8808145b702d1c28520aec9d938eeaae3d871b99ce4b7e20a37bd8e11e52e30e33efebb4f556214a58a2.
2020-06-08 17:28:26 DEBUG (SyncWorker_0) [msmart.lan] Sending to 192.168.1.136:6444 5a5a011168002000000000000000000000000000e85e020000220000000000000000000000000000c7ec8e4276f8accc266a4648044169534ef900b4addf8808145b702d1c28520aec9d938eeaae3d871b99ce4b7e20a37b45ed13363ac83da9f77862d07955814c.
2020-06-08 17:28:26 DEBUG (SyncWorker_1) [msmart.lan] Sending to 192.168.1.130:6444 5a5a0111680020000000000000000000000000001f850200001b0000000000000000000000000000c7ec8e4276f8accc266a4648044169534ef900b4addf8808145b702d1c28520aec9d938eeaae3d871b99ce4b7e20a37b2aa3c0ae20c7311a637cdcff277ce635.
2020-06-08 17:28:27 DEBUG (SyncWorker_18) [msmart.lan] Received from 192.168.1.131:6444 5a5a011168002000000000000000000000000000e2740200001c0000000000000000000000000000c7ec8e4276f8accc266a4648044169534ef900b4addf8808145b702d1c28520aec9d938eeaae3d871b99ce4b7e20a37bd8e11e52e30e33efebb4f556214a58a2.
2020-06-08 17:28:27 DEBUG (SyncWorker_18) [msmart.device] refresh - Recieved from 192.168.1.131, e2740200001c: aa23ac00000000000203c0004e667f7f00000000006cff1200540000000000000000ad3c
2020-06-08 17:28:27 DEBUG (SyncWorker_18) [msmart.command] Appliance response data: c0004e667f7f00000000006cff1200540000000000000000ad3c
2020-06-08 17:28:36 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.childrenroom_aircondition is taking over 10 seconds
2020-06-08 17:28:36 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.secondaryroom_aircondition is taking over 10 seconds
2020-06-08 17:28:36 INFO (SyncWorker_0) [msmart.lan] Connect the Device 192.168.1.136:6444 TimeOut for 10s. don't care about a small amount of this. if many maybe not support.
2020-06-08 17:28:36 INFO (SyncWorker_1) [msmart.lan] Connect the Device 192.168.1.130:6444 TimeOut for 10s. don't care about a small amount of this. if many maybe not support.
2020-06-08 17:28:36 DEBUG (SyncWorker_1) [msmart.device] refresh - Recieved from 192.168.1.130, 1f850200001b:
2020-06-08 17:28:36 DEBUG (SyncWorker_0) [msmart.device] refresh - Recieved from 192.168.1.136, e85e02000022:
2020-06-08 17:28:41 DEBUG (SyncWorker_9) [msmart.packet_builder] Finalize request data: aa20ac00000000000003410000ff03ff00020000000000000000000000000004e9
2020-06-08 17:28:41 DEBUG (SyncWorker_7) [msmart.packet_builder] Finalize request data: aa20ac00000000000003410000ff03ff00020000000000000000000000000004e9
2020-06-08 17:28:41 DEBUG (SyncWorker_17) [msmart.packet_builder] Finalize request data: aa20ac00000000000003410000ff03ff00020000000000000000000000000004e9
2020-06-08 17:28:41 DEBUG (SyncWorker_9) [msmart.lan] Sending to 192.168.1.131:6444 5a5a011168002000000000000000000000000000e2740200001c0000000000000000000000000000c7ec8e4276f8accc266a4648044169534ef900b4addf8808145b702d1c28520aec9d938eeaae3d871b99ce4b7e20a37bd8e11e52e30e33efebb4f556214a58a2.
2020-06-08 17:28:41 DEBUG (SyncWorker_17) [msmart.lan] Sending to 192.168.1.130:6444 5a5a0111680020000000000000000000000000001f850200001b0000000000000000000000000000c7ec8e4276f8accc266a4648044169534ef900b4addf8808145b702d1c28520aec9d938eeaae3d871b99ce4b7e20a37b2aa3c0ae20c7311a637cdcff277ce635.
2020-06-08 17:28:41 DEBUG (SyncWorker_7) [msmart.lan] Sending to 192.168.1.136:6444 5a5a011168002000000000000000000000000000e85e020000220000000000000000000000000000c7ec8e4276f8accc266a4648044169534ef900b4addf8808145b702d1c28520aec9d938eeaae3d871b99ce4b7e20a37b45ed13363ac83da9f77862d07955814c.
2020-06-08 17:28:42 DEBUG (SyncWorker_9) [msmart.lan] Received from 192.168.1.131:6444 5a5a011168002000000000000000000000000000e2740200001c0000000000000000000000000000c7ec8e4276f8accc266a4648044169534ef900b4addf8808145b702d1c28520aec9d938eeaae3d871b99ce4b7e20a37bd8e11e52e30e33efebb4f556214a58a2.
2020-06-08 17:28:42 DEBUG (SyncWorker_9) [msmart.device] refresh - Recieved from 192.168.1.131, e2740200001c: aa23ac00000000000203c0004e667f7f00000000006cff1200540000000000000000ad3c
2020-06-08 17:28:42 DEBUG (SyncWorker_9) [msmart.command] Appliance response data: c0004e667f7f00000000006cff1200540000000000000000ad3c
2020-06-08 17:28:51 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.childrenroom_aircondition is taking over 10 seconds
2020-06-08 17:28:51 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.secondaryroom_aircondition is taking over 10 seconds
2020-06-08 17:28:51 INFO (SyncWorker_7) [msmart.lan] Connect the Device 192.168.1.136:6444 TimeOut for 10s. don't care about a small amount of this. if many maybe not support.
2020-06-08 17:28:51 INFO (SyncWorker_17) [msmart.lan] Connect the Device 192.168.1.130:6444 TimeOut for 10s. don't care about a small amount of this. if many maybe not support.
2020-06-08 17:28:51 DEBUG (SyncWorker_7) [msmart.device] refresh - Recieved from 192.168.1.136, e85e02000022:
2020-06-08 17:28:51 DEBUG (SyncWorker_17) [msmart.device] refresh - Recieved from 192.168.1.130, 1f850200001b:
2020-06-08 17:28:57 DEBUG (SyncWorker_13) [msmart.packet_builder] Finalize request data: aa20ac00000000000003410000ff03ff00020000000000000000000000000004e9
2020-06-08 17:28:57 DEBUG (SyncWorker_12) [msmart.packet_builder] Finalize request data: aa20ac00000000000003410000ff03ff00020000000000000000000000000004e9
2020-06-08 17:28:57 DEBUG (SyncWorker_8) [msmart.packet_builder] Finalize request data: aa20ac00000000000003410000ff03ff00020000000000000000000000000004e9
2020-06-08 17:28:57 DEBUG (SyncWorker_13) [msmart.lan] Sending to 192.168.1.131:6444 5a5a011168002000000000000000000000000000e2740200001c0000000000000000000000000000c7ec8e4276f8accc266a4648044169534ef900b4addf8808145b702d1c28520aec9d938eeaae3d871b99ce4b7e20a37bd8e11e52e30e33efebb4f556214a58a2.
2020-06-08 17:28:57 DEBUG (SyncWorker_12) [msmart.lan] Sending to 192.168.1.136:6444 5a5a011168002000000000000000000000000000e85e020000220000000000000000000000000000c7ec8e4276f8accc266a4648044169534ef900b4addf8808145b702d1c28520aec9d938eeaae3d871b99ce4b7e20a37b45ed13363ac83da9f77862d07955814c.
2020-06-08 17:28:57 DEBUG (SyncWorker_8) [msmart.lan] Sending to 192.168.1.130:6444 5a5a0111680020000000000000000000000000001f850200001b0000000000000000000000000000c7ec8e4276f8accc266a4648044169534ef900b4addf8808145b702d1c28520aec9d938eeaae3d871b99ce4b7e20a37b2aa3c0ae20c7311a637cdcff277ce635.
2020-06-08 17:28:58 DEBUG (SyncWorker_13) [msmart.lan] Received from 192.168.1.131:6444 5a5a011168002000000000000000000000000000e2740200001c0000000000000000000000000000c7ec8e4276f8accc266a4648044169534ef900b4addf8808145b702d1c28520aec9d938eeaae3d871b99ce4b7e20a37bd8e11e52e30e33efebb4f556214a58a2.
2020-06-08 17:28:58 DEBUG (SyncWorker_13) [msmart.device] refresh - Recieved from 192.168.1.131, e2740200001c: aa23ac00000000000203c0004e667f7f00000000006cff1200540000000000000000ad3c
2020-06-08 17:28:58 DEBUG (SyncWorker_13) [msmart.command] Appliance response data: c0004e667f7f00000000006cff1200540000000000000000ad3c

之前请大佬看过美的风管机的抓包情况了，目前新增的debug功能，已获取log，麻烦大佬看下能有啥进展。

midea.log

I use this library with Domoticz, it works fine.
But sometimes (1 or 2 times a day) I get strange readings of indoor, outdoor and target temperatures.
It seems that when the device cannot be reached, refresh() gives the values in init.
How to come over this? I am not a Python Expert.

I use the following example and result. How to get the print() statement not executed if the connection fails?
That method we can also use in Domoticz to pass this failed refresh cycle and not updating the values.
The link to the Domoticz plugin (I am not the owner...) https://github.com/awalsum/Qlima

#!/usr/bin/env python3
from msmart.device import device as midea_device
from msmart.device import air_conditioning_device as ac
import logging
logging.basicConfig(level=logging.DEBUG)

# first take device's ip and id
# pip3 install msmart; midea-discover
c = midea_device('192.168.1.55', 21990232569751, 6444 )
device = c.setup()
# Refresh the object with the actual state by querying it
device.refresh()
print({
        'id': device.id,
        'name': device.ip,
        'power_state': device.power_state,
        'prompt_tone': device.prompt_tone,
        'target_temperature': device.target_temperature,
        'operational_mode': device.operational_mode,
        'fan_speed': device.fan_speed,
        'swing_mode': device.swing_mode,
        'eco_mode': device.eco_mode,
        'turbo_mode': device.turbo_mode,
        'indoor_temperature': device.indoor_temperature,
        'outdoor_temperature': device.outdoor_temperature
    })

I get the following Result

DEBUG:msmart.command:Finalize request data: aa20ac00000000000003418100ff03ff0002000000000000000000000000002f3d
INFO:msmart.lan:Couldn't connect with Device 192.168.1.55:6444
DEBUG:msmart.device:refresh - Recieved from 192.168.1.55, 973700000014: 
{'id': '973700000014', 'name': '192.168.1.55', 'power_state': False, 'prompt_tone': True, 'target_temperature': 20.0, 'operational_mode': <operational_mode_enum.auto: 1>, 'fan_speed': <fan_speed_enum.Auto: 102>, 'swing_mode': <swing_mode_enum.Off: 0>, 'eco_mode': False, 'turbo_mode': False, 'indoor_temperature': 0.0, 'outdoor_temperature': 0.0}

I have a split type blanc series model and it has "Frost Protection" mode, any chance that could be implemented?

In the Midea android app, it can be enabled via a simple click on an icon, but if using the aircon remote control it's a bit of a faff.

Set mode to HEAT, set TEMP to 16, and then press "v" twice within one second.

It's the first time I'm trying it on my unit but I believe it stops the room it's in going below 8 degrees.

As an aside, whilst in Frost Protection mode the display in th UI does not show the correct values

BTW Great work so far!

Hello ,

I have an issue with temperature when I set up modes/temperatures or at random refresh time. The tempeture falls down to -22.5C (or other minus number) for 5-10 seconds and then the normal tempeture appears.

LOG:

2020-05-26 11:12:35 DEBUG (SyncWorker_6) [msmart.lan] Received from 192.168.1.17:6444 5a5a01116800200000000000000000000000000031860000000f0000000000000000000000000000c7ec8e4276f8accc266a4648044169534ef900b4addf8808145b702d1c28520aec9d938eeaae3d871b99ce4b7e20a37b951a3cdfd2e8af002178d80ff39f9455.
2020-05-26 11:12:35 DEBUG (SyncWorker_6) [msmart.device] refresh - Recieved from 192.168.1.17, 31860000000f: aa23ac00000000000303c00057507f7f003c00000064ff0b00020000000000000000d149
2020-05-26 11:12:35 DEBUG (SyncWorker_6) [msmart.command] Appliance response data: c00057507f7f003c00000064ff0b00020000000000000000d149
2020-05-26 11:12:35 DEBUG (SyncWorker_9) [msmart.lan] Received from 192.168.1.21:6444 5a5a0111680020000000000000000000000000002d8d000000100000000000000000000000000000c7ec8e4276f8accc266a4648044169534ef900b4addf8808145b702d1c28520aec9d938eeaae3d871b99ce4b7e20a37b302d88a48df0b3d5143d742e56777667.
2020-05-26 11:12:35 DEBUG (SyncWorker_9) [msmart.device] refresh - Recieved from 192.168.1.21, 2d8d00000010: aa23ac00000000000303c00057667f7f000000000064ff0b00040000000000000000ac92
2020-05-26 11:12:35 DEBUG (SyncWorker_9) [msmart.command] Appliance response data: c00057667f7f000000000064ff0b00040000000000000000ac92
2020-05-26 11:12:35 DEBUG (SyncWorker_0) [msmart.lan] Received from 192.168.1.16:6444 5a5a0111680020000000000000000000000000002f8d000000100000000000000000000000000000c7ec8e4276f8accc266a4648044169534ef900b4addf8808145b702d1c28520aec9d938eeaae3d871b99ce4b7e20a37bdf9cb1a2fc169ee1f1b7d550df1e7639.
2020-05-26 11:12:35 DEBUG (SyncWorker_0) [msmart.device] refresh - Recieved from 192.168.1.16, 2f8d00000010: aa2bac00000000000304a100148240000000000037052b645a00001e13fe000000000000000000000000a5b2
2020-05-26 11:12:35 DEBUG (SyncWorker_0) [msmart.command] Appliance response data: a100148240000000000037052b645a00001e13fe000000000000000000000000a5b2
2020-05-26 11:12:35 DEBUG (SyncWorker_0) [msmart.device] Unknown Operational Mode: 0
2020-05-26 11:12:35 DEBUG (SyncWorker_0) [msmart.device] Unknown Fan Speed: 2
2020-05-26 11:12:42 DEBUG (SyncWorker_8) [msmart.packet_builder] Finalize request data: aa23ac000000000000024000a46503ff0000000002000000000000000000000000007072
2020-05-26 11:12:42 DEBUG (SyncWorker_8) [msmart.lan] Sending to 192.168.1.16:6444 5a5a0111680020000000000000000000000000002f8d000000100000000000000000000000000000489d510f20d55a3422c50933fa3b4d0a5bcd628c7e000fa098bb3d63c90f44756ec374d91662b5fdd3d9d06a1ed87e46d27f41362d2a1397abf5b8232c95f1b2.
2020-05-26 11:12:44 DEBUG (SyncWorker_8) [msmart.lan] Received from 192.168.1.16:6444 5a5a0111680020000000000000000000000000002f8d000000100000000000000000000000000000489d510f20d55a3422c50933fa3b4d0a5bcd628c7e000fa098bb3d63c90f44756ec374d91662b5fdd3d9d06a1ed87e46d27f41362d2a1397abf5b8232c95f1b2.
2020-05-26 11:12:44 DEBUG (SyncWorker_8) [msmart.device] apply - Recieved from 192.168.1.16, 2f8d00000010: aa23ac00000000000302c000a4667f7f0000000000645a08001300000000000000003c4f
2020-05-26 11:12:44 DEBUG (SyncWorker_8) [msmart.command] Appliance response data: c000a4667f7f0000000000645a08001300000000000000003c4f
2020-05-26 11:12:44 DEBUG (SyncWorker_7) [msmart.packet_builder] Finalize request data: aa20ac00000000000003410000ff03ff00020000000000000000000000000004e9
2020-05-26 11:12:44 DEBUG (SyncWorker_7) [msmart.lan] Sending to 192.168.1.16:6444 5a5a0111680020000000000000000000000000002f8d000000100000000000000000000000000000c7ec8e4276f8accc266a4648044169534ef900b4addf8808145b702d1c28520aec9d938eeaae3d871b99ce4b7e20a37bdf9cb1a2fc169ee1f1b7d550df1e7639.
2020-05-26 11:12:47 DEBUG (SyncWorker_7) [msmart.lan] Received from 192.168.1.16:6444 5a5a0111680020000000000000000000000000002f8d000000100000000000000000000000000000c7ec8e4276f8accc266a4648044169534ef900b4addf8808145b702d1c28520aec9d938eeaae3d871b99ce4b7e20a37bdf9cb1a2fc169ee1f1b7d550df1e7639.
2020-05-26 11:12:47 DEBUG (SyncWorker_7) [msmart.device] refresh - Recieved from 192.168.1.16, 2f8d00000010: aa23ac00000000000303c000a4667f7f0000000000655a08001600000000000000009de9
2020-05-26 11:12:47 DEBUG (SyncWorker_7) [msmart.command] Appliance response data: c000a4667f7f0000000000655a08001600000000000000009de9
2020-05-26 11:12:49 DEBUG (SyncWorker_5) [msmart.packet_builder] Finalize request data: aa20ac00000000000003410000ff03ff00020000000000000000000000000004e9
2020-05-26 11:12:49 DEBUG (SyncWorker_1) [msmart.packet_builder] Finalize request data: aa20ac00000000000003410000ff03ff00020000000000000000000000000004e9
2020-05-26 11:12:49 DEBUG (SyncWorker_6) [msmart.packet_builder] Finalize request data: aa20ac00000000000003410000ff03ff00020000000000000000000000000004e9
2020-05-26 11:12:49 DEBUG (SyncWorker_6) [msmart.lan] Sending to 192.168.1.16:6444 5a5a0111680020000000000000000000000000002f8d000000100000000000000000000000000000c7ec8e4276f8accc266a4648044169534ef900b4addf8808145b702d1c28520aec9d938eeaae3d871b99ce4b7e20a37bdf9cb1a2fc169ee1f1b7d550df1e7639.
2020-05-26 11:12:49 DEBUG (SyncWorker_1) [msmart.lan] Sending to 192.168.1.17:6444 5a5a01116800200000000000000000000000000031860000000f0000000000000000000000000000c7ec8e4276f8accc266a4648044169534ef900b4addf8808145b702d1c28520aec9d938eeaae3d871b99ce4b7e20a37b951a3cdfd2e8af002178d80ff39f9455.
2020-05-26 11:12:49 DEBUG (SyncWorker_5) [msmart.lan] Sending to 192.168.1.21:6444 5a5a0111680020000000000000000000000000002d8d000000100000000000000000000000000000c7ec8e4276f8accc266a4648044169534ef900b4addf8808145b702d1c28520aec9d938eeaae3d871b99ce4b7e20a37b302d88a48df0b3d5143d742e56777667.

Found a unsupported device - type: '0xe2'

Describe the bug
When setting fan_mode to high, the fan is only at 80%
When setting to 100% with the remote or the app it appears like Auto in HA
When setting to auto in HA it's really auto

Versions

• Home Assistant version: 2020.12.1
• Midea msmart version: 0.1.24

INFO:msmart.cli:Debug mode active
INFO:msmart.cli:msmart version: 0.1.23
INFO:msmart.cli:Sending Device Scan Broadcast...
INFO:msmart.cli:Midea Local Data 192.168.142.170 837000c8200f00005a5a0111b8007a80000000001c2634150b0a1414c822150000930000000000000000018000000000267183c24ba5db6e5b4cce63e715a068cd12cdf578f53a39abc64ce617c6acb82c34bebef0fdd12c9c7c1752d2bfb60279d61bc6ed3ce6429046a4768cb9f8c99b6d9d3c5bddedd5b43bdcfbaec9648bc083b3c640ad7ba255dddf95919675ad4bdfb3e16e33d88768cc4c3d0658937d96fbcce99f70c976413c2f05f60f82e72c2909bfcae62da1ed3f52058c69d195398d6a97a75806510fd5bb9844ea8c77
INFO:msmart.cli:Decrypt Reply: 192.168.142.170 aa8ea8c02c19000030303030303033313132323031323336393039303530353232353830303030300d6d696465615f61635f323538300000830002000000000000000000ac00acac00000000a0681c048a10150015032018000300000000000000000000000000000000000000000000000000000000000000000000
DEBUG:msmart.command:Finalize request data: aa20ac00000000000003418100ff03ff0002000000000000000000000000192e25
DEBUG:msmart.lan:Sending to 192.168.142.170:6444 5a5a01116800200000000000171934150b0a1414c8221500009300000000000000000000000000006b000a76e27eed2c3647e57d8602df8b9981402b1d7f5153d47b03e0e31cd254b1c2205f69843a3c2f9a56fd694277b4651b5c49fbcfc27bd1e6a04e31430c21

INFO:msmart.lan:Couldn't connect with Device 192.168.142.170:6444
DEBUG:msmart.device:refresh - Recieved from 192.168.142.170, c82215000093:
INFO:msmart.cli:*** Found a unsupported device - type: '0xac' - version: V3 - ip: 192.168.142.170 - port: 6444 - id: 161628210668232 - sn: 00000031122012369090505225800000 - ssid: midea_ac_2580
INFO:msmart.cli:Midea Local Data 192.168.142.118 837000c8200f00005a5a0111b8007a8000000000f12634150b0a1414ec221500009300000000000000000180000000001919f0ed0673eee9b4e22f6278439436cd12cdf578f53a39abc64ce617c6acb8d854f3442ed531b1e8a5d5a9a914cc9a8f29037b123de3281cbcfa2365dc75969c45e590fa306ad3c3b6f18ee366bcdd595df4a2a58a7d227078a0864466f8504bdfb3e16e33d88768cc4c3d0658937d96fbcce99f70c976413c2f05f60f82e7c59646189b83d711643ff63b5dd453d689271b4f93c0725cbb46a625f0cde58f
INFO:msmart.cli:Decrypt Reply: 192.168.142.118 768ea8c02c19000030303030303033313132323031323336393039303530353232353832303030300d6d696465615f61635f323538320000830002000000000000000000ac00acac0000000030b237a738a9150015032018000300000000000000000000000000000000000000000000000000000000000000000000
DEBUG:msmart.command:Finalize request data: aa20ac00000000000003418100ff03ff00020000000000000000000000002152f9
DEBUG:msmart.lan:Sending to 192.168.142.118:6444 5a5a01116800200000000000182134150b0a1414ec221500009300000000000000000000000000006b000a76e27eed2c3647e57d8602df8bc24133a0909225f1481c3b73abacf8ec0bdaf60a4e381fb221a9a82463236a1bc1379d9cf6965ccc1fecb72767975c09

INFO:msmart.lan:Couldn't connect with Device 192.168.142.118:6444
DEBUG:msmart.device:refresh - Recieved from 192.168.142.118, ec2215000093:
INFO:msmart.cli:*** Found a unsupported device - type: '0xac' - version: V3 - ip: 192.168.142.118 - port: 6444 - id: 161628210668268 - sn: 00000031122012369090505225820000 - ssid: midea_ac_2582

HA版本0.109.1，空调美的风语者KFR-35GW/BP3DN8Y-FA200
可以正常接入美的APP，美的APP可以控制
通过iPhone提取15位Applianceid，接入HA

HA报错：Update for climate.midea_dd4004000086 fails
无法读取空调状态，无法控制空调

日志如下：

Update for climate.midea_dd4004000086 fails
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 279, in async_update_ha_state
await self.async_device_update()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 470, in async_device_update
await self.async_update()
File "/config/custom_components/midea/climate.py", line 108, in async_update
await self.hass.async_add_executor_job(self._device.refresh)
File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/local/lib/python3.7/site-packages/msmart/device.py", line 170, in refresh
data = self._lan_service.appliance_transparent_send(data)
File "/usr/local/lib/python3.7/site-packages/msmart/lan.py", line 63, in appliance_transparent_send
response = bytearray(self.request(data))[40:88]
File "/usr/local/lib/python3.7/site-packages/msmart/lan.py", line 38, in request
response = sock.recv(256)
socket.timeout: timed out

Hello,
is there a Lovelace (home-assistant) integration?
The "example configuration" you wrote in project home page is in yaml.
Thanks.

Edit:
Ok,
I just used thermostat component. It appears on my dashboard but it doesn't works.
I am unable to turn on/off it via home-assistant.

There is no log in Home-Assistant.

配置后接入HA，控制无效（点什么都是failed to call service）

配置文件如下

climate:
  - platform: midea
    host: 10.0.6.1
    id: 162727721163973

报错log如下

Update for climate.midea_c5dc03000094 fails
1:04:23 PM – custom_components/midea/climate.py (ERROR) - message first occurred at 11:41:37 AM and shows up 313 times
timed out
1:02:02 PM – Home Assistant WebSocket API (ERROR) - message first occurred at 12:58:25 PM and shows up 2 times

2020-05-14 13:01:59 INFO (SyncWorker_6) [pynetgear] Get attached devices
2020-05-14 13:01:59 ERROR (MainThread) [homeassistant.helpers.entity] Update for climate.midea_c5dc03000094 fails
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 279, in async_update_ha_state
    await self.async_device_update()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 470, in async_device_update
    await self.async_update()
  File "/config/custom_components/midea/climate.py", line 104, in async_update
    await self.hass.async_add_executor_job(self._device.apply)
  File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/local/lib/python3.7/site-packages/msmart/device.py", line 192, in apply
    data = self._lan_service.appliance_transparent_send(data)
  File "/usr/local/lib/python3.7/site-packages/msmart/lan.py", line 63, in appliance_transparent_send
    response = bytearray(self.request(data))[40:88]
  File "/usr/local/lib/python3.7/site-packages/msmart/lan.py", line 38, in request
    response = sock.recv(256)
socket.timeout: timed out
2020-05-14 13:02:02 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection.2797989008] timed out
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 130, in handle_call_service
    connection.context(msg),
  File "/usr/src/homeassistant/homeassistant/core.py", line 1247, in async_call
    task.result()
  File "/usr/src/homeassistant/homeassistant/core.py", line 1282, in _execute_service
    await handler.func(service_call)
  File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 213, in handle_service
    self._platforms.values(), func, call, required_features
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 453, in entity_service_call
    future.result()  # pop exception if have
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 596, in async_request_call
    await coro
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 484, in _handle_entity_call
    await result
  File "/config/custom_components/midea/climate.py", line 263, in async_set_hvac_mode
    await self.apply_changes()
  File "/config/custom_components/midea/climate.py", line 95, in apply_changes
    await self.hass.async_add_executor_job(self._device.apply)
  File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/local/lib/python3.7/site-packages/msmart/device.py", line 192, in apply
    data = self._lan_service.appliance_transparent_send(data)
  File "/usr/local/lib/python3.7/site-packages/msmart/lan.py", line 63, in appliance_transparent_send
    response = bytearray(self.request(data))[40:88]
  File "/usr/local/lib/python3.7/site-packages/msmart/lan.py", line 38, in request
    response = sock.recv(256)
socket.timeout: timed out
2020-05-14 13:02:05 DEBUG (MainThread) [queueman.manager] Queue execution finished for 4 tasks finished in 13.61 seconds
2020-05-14 13:02:11 INFO (SyncWorker_12) [pynetgear] Get attached devices
2020-05-14 13:02:15 ERROR (MainThread) [homeassistant.helpers.entity] Update for climate.midea_c5dc03000094 fails
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 279, in async_update_ha_state
    await self.async_device_update()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 470, in async_device_update
    await self.async_update()
  File "/config/custom_components/midea/climate.py", line 104, in async_update
    await self.hass.async_add_executor_job(self._device.apply)
  File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/local/lib/python3.7/site-packages/msmart/device.py", line 192, in apply
    data = self._lan_service.appliance_transparent_send(data)
  File "/usr/local/lib/python3.7/site-packages/msmart/lan.py", line 63, in appliance_transparent_send
    response = bytearray(self.request(data))[40:88]
  File "/usr/local/lib/python3.7/site-packages/msmart/lan.py", line 38, in request
    response = sock.recv(256)
socket.timeout: timed out

Is it possible to show the property/attribute outdoor_temperature in Home Assistant ?

Logger: homeassistant.components.websocket_api.http.connection.178689
Source: helpers/service.py:514
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 6:56:48 PM (1 occurrences)
Last logged: 6:56:48 PM

Unauthorized
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 130, in handle_call_service
connection.context(msg),
File "/usr/src/homeassistant/homeassistant/core.py", line 1253, in async_call
task.result()
File "/usr/src/homeassistant/homeassistant/core.py", line 1288, in _execute_service
await handler.func(service_call)
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 514, in admin_handler
raise Unauthorized(context=call.context)
homeassistant.exceptions.Unauthorized: Unauthorized

HomeKit端能否加入除湿和扫风功能？另外能否加入蜂鸣声

Sorry, wrong repository.
Please delete!
Thanks

Describe the bug （描述一下问题）
There is a message in the logs that ClimateDevice is deprecated

Screenshots / Logs / Pcap File（屏幕截图/日志/抓包文件）
Logger: homeassistant.components.climate
Source: components/climate/init.py:547
Integration: Climate (documentation, issues)
First occurred: 8:16:51 PM (1 occurrences)
Last logged: 8:16:51 PM

ClimateDevice is deprecated, modify MideaClimateACDevice to extend ClimateEntity

Versions (版本信息)

• Home Assistant version: 0.110.1
• Midea msmart version: 0.1.12

Hi I love your work it's great.
Do you think that it possible to add more HVAC?
I have Electra HVAC that work also with a cloud like Midea.
I will send you anything you need.
Please!!!

➜  ~ midea-discover
INFO:msmart.cli:msmart version: 0.1.24
INFO:msmart.cli:Sending Device Scan Broadcast...
INFO:msmart.cli:Midea Local Data 10.10.0.55 837000b8200f041e5a5a0111a8007a800000000000000000000000005d060000001e00000000000000000000000000008c733ad9a7aacbeecd40b44264bdb449daa5b37f0a7007d7ce0f10562cf95daec5a89ad86aff8d85b13a3c77a908c5eb24a01f5d7d95c5c8be32ea58bd6b63b46401c28d356fb7baa29322a917d234ec1fca94541303884c52e880ddefc03190f31443d17c3aac03a7656614ae1dca44982aa3ee9b3ebee64fcfb82f2b917522ceb1207bfbdf702f13449c552920199d
INFO:msmart.cli:Decrypt Reply: 10.10.0.55 37000a0a2c19000030303030303050303030303030305131333042323337343932463530303030300b6e65745f61635f324635300000000001000000040000000000ac0000000000000030b237492f50069fcd0300080103000000000000000000000000000000000000000000
INFO:msmart.lan:Couldn't connect with Device 10.10.0.55:6444
INFO:msmart.cli:*** Found a unsupported device - type: '0xac' - version: V3 - ip: 10.10.0.55 - port: 6444 - id: 32985348834909 - sn: 000000P0000000Q130B237492F500000 - ssid: net_ac_2F50
INFO:msmart.cli:Midea Local Data 10.10.0.64 837000b8200f04155a5a0111a8007a8000000000000000000000000001b70000001c00000000000000000000000000002d7ad6a0c8d03e12577f3e1ea8ff9786daa5b37f0a7007d7ce0f10562cf95dae8581a4326ba8a6168b07623b4d59e4feaea5e5f28c5165de36b3f80844c098a9e67d558d48da1d18482f5c4ce622e2191fca94541303884c52e880ddefc03190f31443d17c3aac03a7656614ae1dca447652668029126cda4caeee86dac09dee4a2c4f0172b7b8d9642f8f36271ce6ea
INFO:msmart.cli:Decrypt Reply: 10.10.0.64 40000a0a2c19000030303030303050303030303030305131333042323337343935314336303030300b6e65745f61635f353143360000000001000000040000000000ac0000000000000030b2374951c6069fcd0300080103000000000000000000000000000000000000000000
INFO:msmart.lan:Couldn't connect with Device 10.10.0.64:6444
INFO:msmart.cli:*** Found a unsupported device - type: '0xac' - version: V3 - ip: 10.10.0.64 - port: 6444 - id: 30786325624577 - sn: 000000P0000000Q130B2374951C60000 - ssid: net_ac_51C6

Versions

• Home Assistant version: OS 5.11, core 2021.2.3, supervisor-2021-02-11
• Midea msmart version: 0.1.24

TypeError: 'NoneType' object is not iterable
2020-05-28 16:36:08 ERROR (MainThread) [homeassistant.helpers.entity] Update for climate.childrenroom_aircondition fails
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 279, in async_update_ha_state
await self.async_device_update()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 470, in async_device_update
await self.async_update()
File "/config/custom_components/midea/climate.py", line 108, in async_update
await self.hass.async_add_executor_job(self._device.refresh)
File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/local/lib/python3.7/site-packages/msmart/device.py", line 173, in refresh
data = self._lan_service.appliance_transparent_send(data)
File "/usr/local/lib/python3.7/site-packages/msmart/lan.py", line 69, in appliance_transparent_send
response = bytearray(self.request(data))[40:88]
TypeError: 'NoneType' object is not iterable

Describe the bug （描述一下问题）
A clear and concise description of what the bug is.
I'm trying to turn on device using call service but Is not working

Screenshots / Logs / Pcap File（屏幕截图/日志/抓包文件）
If applicable, add screenshots or your home-assistant log file or pcap file to help explain your problem.
请提交相关截图，日志，抓包让开发者能够更快的解决问题

Versions (版本信息)

• Home Assistant version:
  Home Assistant Core 0.114.3
• Midea msmart version:
  0.110.2

Describe the bug （描述一下问题）
添加之后提示[Errno 104] Connection reset by peer

Screenshots / Logs / Pcap File（屏幕截图/日志/抓包文件）
Logger: homeassistant.components.websocket_api.http.connection.140300961035472
Source: custom_components/midea_ac/climate.py:95
Integration: websocket_api (documentation, issues)
First occurred: 下午12:24:23 (5 occurrences)
Last logged: 下午12:24:38

[Errno 104] Connection reset by peer
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 134, in handle_call_service
connection.context(msg),
File "/usr/src/homeassistant/homeassistant/core.py", line 1232, in async_call
await asyncio.shield(self._execute_service(handler, service_call))
File "/usr/src/homeassistant/homeassistant/core.py", line 1255, in _execute_service
await handler.func(service_call)
File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 213, in handle_service
self._platforms.values(), func, call, required_features
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 412, in entity_service_call
future.result() # pop exception if have
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 600, in async_request_call
await coro
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 443, in _handle_entity_call
await result
File "/config/custom_components/midea_ac/climate.py", line 263, in async_set_hvac_mode
await self.apply_changes()
File "/config/custom_components/midea_ac/climate.py", line 95, in apply_changes
await self.hass.async_add_executor_job(self._device.apply)
File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/local/lib/python3.7/site-packages/msmart/device.py", line 197, in apply
data = self._lan_service.appliance_transparent_send(data)
File "/usr/local/lib/python3.7/site-packages/msmart/lan.py", line 69, in appliance_transparent_send
response = bytearray(self.request(data))[40:88]
File "/usr/local/lib/python3.7/site-packages/msmart/lan.py", line 41, in request
response = sock.recv(512)
ConnectionResetError: [Errno 104] Connection reset by peer
Versions (版本信息)

• Home Assistant version: 0.108.0
• Midea msmart version: 0.1.15

Describe the bug （描述一下问题）
Hi, Mac.

After the last update to version msmart==0.1.24 (I updated on 12/01/2020), I get constant disappearing of my air conditioners. I see it in Logbook and History. There are no records of this in the Logs. Only once, right after the update:

Log Details (ERROR)
Logger: homeassistant.components.websocket_api.http.connection
Source: core.py:1405
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: December 1, 2020, 9:04:03 AM (1 occurrences)
Last logged: December 1, 2020, 9:04:03 AM

[140718739954560] string value is None for dictionary value @ data['preset_mode']
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 135, in handle_call_service
    await hass.services.async_call(
  File "/usr/src/homeassistant/homeassistant/core.py", line 1405, in async_call
    processed_data = handler.schema(service_data)
  File "/usr/local/lib/python3.8/site-packages/voluptuous/validators.py", line 218, in __call__
    return self._exec((Schema(val) for val in self.validators), v)
  File "/usr/local/lib/python3.8/site-packages/voluptuous/validators.py", line 340, in _exec
    raise e if self.msg is None else AllInvalid(self.msg, path=path)
  File "/usr/local/lib/python3.8/site-packages/voluptuous/validators.py", line 336, in _exec
    v = func(v)
  File "/usr/local/lib/python3.8/site-packages/voluptuous/schema_builder.py", line 272, in __call__
    return self._compiled([], data)
  File "/usr/local/lib/python3.8/site-packages/voluptuous/schema_builder.py", line 817, in validate_callable
    return schema(data)
  File "/usr/local/lib/python3.8/site-packages/voluptuous/schema_builder.py", line 272, in __call__
    return self._compiled([], data)
  File "/usr/local/lib/python3.8/site-packages/voluptuous/schema_builder.py", line 594, in validate_dict
    return base_validate(path, iteritems(data), out)
  File "/usr/local/lib/python3.8/site-packages/voluptuous/schema_builder.py", line 432, in validate_mapping
    raise er.MultipleInvalid(errors)
voluptuous.error.MultipleInvalid: string value is None for dictionary value @ data['preset_mode']

Before that, on version msmart==0.1.23 this was not. Everything worked fine and stable for a few months.

Screenshots / Logs / Pcap File（屏幕截图/日志/抓包文件）

请提交相关截图，日志，抓包让开发者能够更快的解决问题

Versions (版本信息)

• Home Assistant version: 0.118.4
• Midea msmart version: ==0.1.24
• My air conditioners: Midea Midea Mission II MB-09N8D6H-I/MB-09N8D6H-O and Midea Mission II MB-12N8D6H-I/MB-12N8D6H-O
• Wi-Fi module SK-102

Thanks.

ha 的log里面经常出现更新超时，有可能是什么原因导致的？
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 279, in async_update_ha_state
await self.async_device_update()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 470, in async_device_update
await self.async_update()
File "/config/custom_components/midea/climate.py", line 108, in async_update
await self.hass.async_add_executor_job(self._device.refresh)
File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/local/lib/python3.7/site-packages/msmart/device.py", line 171, in refresh
data = self._lan_service.appliance_transparent_send(data)
File "/usr/local/lib/python3.7/site-packages/msmart/lan.py", line 69, in appliance_transparent_send
response = bytearray(self.request(data))
File "/usr/local/lib/python3.7/site-packages/msmart/lan.py", line 33, in request
sock.connect(device_address)
socket.timeout: timed out
2020-05-30 22:14:50 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.primaryroom_aircondition is taking over 10 seconds
2020-05-30 22:14:50 ERROR (MainThread) [homeassistant.helpers.entity] Update for climate.primaryroom_aircondition fails
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 279, in async_update_ha_state
await self.async_device_update()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 470, in async_device_update
await self.async_update()
File "/config/custom_components/midea/climate.py", line 108, in async_update
await self.hass.async_add_executor_job(self._device.refresh)
File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/local/lib/python3.7/site-packages/msmart/device.py", line 171, in refresh
data = self._lan_service.appliance_transparent_send(data)
File "/usr/local/lib/python3.7/site-packages/msmart/lan.py", line 69, in appliance_transparent_send
response = bytearray(self.request(data))
File "/usr/local/lib/python3.7/site-packages/msmart/lan.py", line 33, in request
sock.connect(device_address)
socket.timeout: timed out

作者真心很好很强大，插件非常牛，一整套操作在linux环境下都能完成，甚至不需要用手机，完美接入homekit

Describe the bug （描述一下问题）
Hi

I am using an A/C with WiFi Module OSK102 for more than a year and it was working "Ok" (when it is available...)
We have bought a new A/C same model but the with WiFi Module is OSK103 I found the device id but although it creates a new entity the device show unavailable in Home assistant - in the Midea app is available and working ok - both A/Cs

"Old A/C" midea_ac_81xxx00000xx -> off ->(OSK102 id: 17xx21xx09xx0x)
"New A/C" midea_ac_d3xxx00000xx -> Unavailable ->(OSK103 id: 31xx58xx26xx8x)

If I switch the Wifi modules and put the OSK103 in the "old A/C" and the OSK102 to the "new A/C" I have exactly the opposite
the new A/C is recognized and the old A/C is unavailable

Versions (版本信息)

• Home Assistant version:
• core-2021.1.5
• supervisor-2021.01.7
• Midea msmart version: c1bd84c

Hi I cannot connect my AC to HA, it's always showing up as:
midea_ac_XXXX00000015 (XXXX are numbers) became unavailable

INFO:msmart.lan:Couldn't connect with Device 192.168.1.34:6444
INFO:msmart.cli:*** Found a unsupported device - type: '0xac' - version: V3 - ip: 192.168.1.34 - port: 6444 - id: 2XXXXX44212500 - sn: 000000P0000000QXXXXX71792A50000 - ssid: net_ac_XXXX

Versions (版本信息)

• Home Assistant version: 1.18
• Midea msmart version: 0.1.24

Thanks and Regards
Oliver

这个空调还可以接入吗？大佬

Describe the bug （描述一下问题）
I have this error ERROR (MainThread) [homeassistant.helpers.entity] Update for climate.midea_ac_xxbx00000010 fails
ValueError: byte must be in range(0, 256)

Screenshots / Logs / Pcap File（屏幕截图/日志/抓包文件）
If applicable, add screenshots or your home-assistant log file or pcap file to help explain your problem.
请提交相关截图，日志，抓包让开发者能够更快的解决问题
2020-06-16 10:11:29 ERROR (MainThread) [homeassistant.helpers.entity] Update for climate.midea_ac_xxbx00000010 fails
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 279, in async_update_ha_state
await self.async_device_update()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 470, in async_device_update
await self.async_update()
File "/config/custom_components/midea_ac/climate.py", line 108, in async_update
await self.hass.async_add_executor_job(self._device.refresh)
File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/local/lib/python3.7/site-packages/msmart/device.py", line 178, in refresh
data = pkt_builder.finalize()
File "/usr/local/lib/python3.7/site-packages/msmart/packet_builder.py", line 46, in finalize
self.command.append(self.checksum(self.command[1:]))
ValueError: byte must be in range(0, 256)
2020-06-16 10:21:29 ERROR (MainThread) [homeassistant.helpers.entity] Update for climate.midea_ac_xxbx00000010 fails
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 279, in async_update_ha_state
await self.async_device_update()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 470, in async_device_update
await self.async_update()
File "/config/custom_components/midea_ac/climate.py", line 108, in async_update
await self.hass.async_add_executor_job(self._device.refresh)
File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/local/lib/python3.7/site-packages/msmart/device.py", line 178, in refresh
data = pkt_builder.finalize()
File "/usr/local/lib/python3.7/site-packages/msmart/packet_builder.py", line 46, in finalize
self.command.append(self.checksum(self.command[1:]))
ValueError: byte must be in range(0, 256)

Versions (版本信息)

• Home Assistant version: Home Assistant 0.111.3 System | HassOS 4.10
• Midea msmart version: 35ed4a3

Describe the bug （描述一下问题）
A clear and concise description of what the bug is.

midea_ac_886103000093 不可用

Screenshots / Logs / Pcap File（屏幕截图/日志/抓包文件）
If applicable, add screenshots or your home-assistant log file or pcap file to help explain your problem.
请提交相关截图，日志，抓包让开发者能够更快的解决问题

Update of climate.midea_ac_886103000093 is taking over 10 seconds

Versions (版本信息)

• Home Assistant version:
  版本 | 2021.1.5
  安装类型 | Home Assistant OS
• Midea msmart version:

Current temp is 0c.
It sends commands just throws every time this error. Does not update status.

Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 279, in async_update_ha_state
await self.async_device_update()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 470, in async_device_update
await self.async_update()
File "/config/custom_components/midea_ac/climate.py", line 104, in async_update
await self.hass.async_add_executor_job(self._device.apply)
File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/local/lib/python3.7/site-packages/msmart/device.py", line 205, in apply
data = self._lan_service.appliance_transparent_send(data)
File "/usr/local/lib/python3.7/site-packages/msmart/lan.py", line 78, in appliance_transparent_send
reply = self.decode(self.security.aes_decrypt(response[40:88]))
File "/usr/local/lib/python3.7/site-packages/msmart/security.py", line 26, in aes_decrypt
decrypted = unpad(decrypted, self.blockSize)
File "/usr/local/lib/python3.7/site-packages/Crypto/Util/Padding.py", line 90, in unpad
raise ValueError("Padding is incorrect.")
ValueError: Padding is incorrect.

Versions (版本信息)

• Home Assistant version:
• Midea msmart version:

抓了华菱空调的关机包。希望能适配。。感激涕零

华菱空调关机.zip

has somebody tried to decipher the protocol between the wifi module and the AC? the wifi modules are somewhat unreliable: need to be repaired every month, at least for me. it would be nice to a mini computer (e.g. pi) directly to the AC's usb-like slot.

I got this working on a Carrier Airco (Yay!) through Home assistant on my x64 Intel NUC Router, but I'm wondering if its possible to somehow read/set temperatures and mode through bash so I can make my own script.

Thank you!

Describe the bug （描述一下问题）
Since upgrading to HA 2021.3, the logfile gives a warning on this intergration

Screenshots / Logs / Pcap File（屏幕截图/日志/抓包文件）
WARNING (MainThread) [homeassistant.loader] No 'version' key in the manifest file for custom integration 'midea_ac'. This will not be allowed in a future version of Home Assistant. Please report this to the maintainer of 'midea_ac'
请提交相关截图，日志，抓包让开发者能够更快的解决问题

Versions (版本信息)

• Home Assistant version: 2021.3
• Midea msmart version: c1bd84c

Does this custom component support EVA II PRO WiFi Smart Dehumidifier?
like this https://github.com/barban-dev/midea_inventor_dehumidifier ?

I have 4 Midea AC's but I cannot figure out where the appliance ID is in the MacOS console log, I have this output:

default 11:13:37.623963+0200 Midea OBM Task .<750> resuming, QOS(0x21) Voucher (null)
default 11:13:37.627104+0200 Midea OBM Task .<750> {strength 0, tls 4, ct 0, sub 0, sig 1, ciphers 0, bundle 0, builtin 0}
default 11:13:37.627609+0200 Midea OBM Task .<750> now using Connection 50
default 11:13:37.629738+0200 Midea OBM Task .<750> sent request, body S 192
default 11:13:37.981312+0200 Midea OBM Task .<750> received response, status 200 content C
default 11:13:37.982372+0200 Midea OBM Task .<750> response ended
default 11:13:37.982806+0200 Midea OBM Task .<750> done using Connection 50
default 11:13:37.983136+0200 Midea OBM Task .<750> summary for task success {transaction_duration_ms=357, response_status=200, connection=50, reused=1, request_start_ms=3, request_duration_ms=1, response_start_ms=355, response_duration_ms=2, request_bytes=493, response_bytes=319, cache_hit=1}
default 11:13:37.983817+0200 Midea OBM Task .<750> finished successfully
default 11:13:38.394026+0200 Midea OBM deviceStateChanged:call back
default 11:13:38.394386+0200 Midea OBM deviceStateChanged:call back
default 11:13:38.394969+0200 Midea OBM deviceStateChanged:call back
default 11:13:38.395370+0200 Midea OBM deviceStateChanged:call back
default 11:13:38.395536+0200 Midea OBM
===={-[MasterACViewController handleTransportNotification:]}====[Line 722]QueryResult RETURN= 0
default 11:13:38.396411+0200 Midea OBM
===={+[MDDataResponseOld toObject:deviceStatue:]}====[Line 220]zerobyte 192
default 11:13:38.396687+0200 Midea OBM
===={-[MasterACViewController setIndoorTempture:]}====[Line 345]Indoor:21 - Outdoor:18
default 11:13:38.404870+0200 Midea OBM Task .<751> resuming, QOS(0x21) Voucher (null)
default 11:13:38.405957+0200 Midea OBM
===={-[MasterACViewController setIndoorTempture:]}====[Line 345]Indoor:21 - Outdoor:18
default 11:13:38.407474+0200 Midea OBM Task .<751> {strength 0, tls 4, ct 0, sub 0, sig 1, ciphers 0, bundle 0, builtin 0}
default 11:13:38.407876+0200 Midea OBM
===={-[MasterACViewController updateSetTemp]}====[Line 441]setTemperature Label = 27.5
default 11:13:38.408178+0200 Midea OBM Task .<751> now using Connection 50
default 11:13:38.410077+0200 Midea OBM Task .<751> sent request, body S 346
default 11:13:38.429222+0200 Midea OBM
===={-[MasterACViewController handleErrInfo]}====[Line 1885]水满 0
default 11:13:38.429394+0200 Midea OBM
===={-[MasterACViewController getThisTime]}====[Line 1881]-=-==-timer_on=0,timer_on_hour=0,timer_on_min=0
default 11:13:38.444165+0200 Midea OBM Task .<752> resuming, QOS(0x21) Voucher (null)
default 11:13:38.445240+0200 Midea OBM Task .<752> {strength 0, tls 4, ct 0, sub 0, sig 1, ciphers 0, bundle 0, builtin 0}
default 11:13:38.445425+0200 Midea OBM Task .<752> now using Connection 58
default 11:13:38.445976+0200 Midea OBM Task .<752> sent request, body S 382
default 11:13:38.828306+0200 Midea OBM Task .<751> received response, status 200 content C
default 11:13:38.829317+0200 Midea OBM Task .<751> response ended
default 11:13:38.829693+0200 Midea OBM Task .<751> done using Connection 50
default 11:13:38.830316+0200 Midea OBM Task .<751> summary for task success {transaction_duration_ms=424, response_status=200, connection=50, reused=1, request_start_ms=2, request_duration_ms=2, response_start_ms=422, response_duration_ms=2, request_bytes=689, response_bytes=396, cache_hit=1}
default 11:13:38.831279+0200 Midea OBM Task .<751> finished successfully
default 11:13:38.861679+0200 Midea OBM Task .<752> received response, status 200 content C
default 11:13:38.862610+0200 Midea OBM Task .<752> response ended
default 11:13:38.863434+0200 Midea OBM Task .<752> done using Connection 58
default 11:13:38.866128+0200 Midea OBM Task .<752> summary for task success {transaction_duration_ms=419, response_status=200, connection=58, reused=1, request_start_ms=0, request_duration_ms=0, response_start_ms=416, response_duration_ms=2, request_bytes=729, response_bytes=1036, cache_hit=1}
default 11:13:38.866560+0200 Midea OBM Task .<752> finished successfully
default 11:13:40.641635+0200 Midea OBM
===={-[MasterACViewController sendCommand:withTag:hideLoading:]}====[Line 506]SendCommonData - Length:33 - aa,20,ac,00,00,00,00,00,00,03,41,81,00,ff,03,ff,00,02,00,00,00,00,00,00,00,00,00,00,00,00,03,cd,9c
default 11:13:40.647258+0200 Midea OBM

Is it possible to be able to add an Aircon unit to an Area in the HA UI?

Describe the bug （描述一下问题）
Integration is missing hvac_action in yaml reflecting the current state of a connected Midea AC. So it is impossible to use in automations :-( I see state in Developer tool but not in state attributes?

Screenshots / Logs / Pcap File（屏幕截图/日志/抓包文件）
If applicable, add screenshots or your home-assistant log file or pcap file to help explain your problem.
请提交相关截图，日志，抓包让开发者能够更快的解决问题

Versions (版本信息)

• Home Assistant version: 0.110.6
• Midea msmart version: latest

三台空调均不可用，希望加上支持

以下为msmart扫描信息：

INFO:msmart.cli:msmart version: 0.1.24
INFO:msmart.cli:Sending Device Scan Broadcast...
INFO:msmart.cli:Midea Local Data 192.168.8.219 837000c8200f00005a5a0111b8007a8000000000805d06091a021514cad7150000940000000000000000018000000000b65e9e22dd6b6636d0626003f3ef8a737ce69f2de03e49783c6a9aa4260847bb80fdf1391a336289f6729ade42e4c35ff8ace8191f45db249459a17e0c892e75585b601d14f37d8b3b9cfa3a2b2d372007a16a2c5f149c6e91d461e948d5d0074bdfb3e16e33d88768cc4c3d0658937d96fbcce99f70c976413c2f05f60f82e7f5ebc172601522bfe75a4f0089e477dc0ce4d10e9e69242492aaee07303bb2b4
INFO:msmart.cli:Decrypt Reply: 192.168.8.219 db08a8c02c19000030303030303033313132323235313137313039303830353130323131303030300d6d696465615f61635f303231310000830002000000000000000000ac00acac00000000a0681c272aa7150014032017000300000000000000000000000000000000000000000000000000000000000000000000
INFO:msmart.lan:Couldn't connect with Device 192.168.8.219:6444
INFO:msmart.cli:*** Found a unsupported device - type: '0xac' - version: V3 - ip: 192.168.8.219 - port: 6444 - id: 162727722342346 - sn: 00000031122251171090805102110000 - ssid: midea_ac_0211
INFO:msmart.cli:Midea Local Data 192.168.8.220 837000c8200f00005a5a0111b8007a800000000061af05091a02151407931a000095000000000000000001800000000081e41d859e2617c247c1fcc84d1e452a569d46f535f6b2542816f95477072319448e0e60fd2acf039873fd156f084243457d833e3370b4c50873d0f10ca47b3737f63737b213c853aecb59389e1c3dffaa0b0db18c0822fed2c698933f0e30d64bdfb3e16e33d88768cc4c3d0658937d96fbcce99f70c976413c2f05f60f82e7ff95642781a647b576a9ff98502b04db0656c8555e360361a72d6b9e41977836
INFO:msmart.cli:Decrypt Reply: 192.168.8.220 dc08a8c02c19000030303030303033313132323031323338333039313330353230303338303030300d6d696465615f61635f3030333800009f0002000000100000000000ac00050000000000a0681c25319e150003202027010300000000000000000000000000000000000000000000000000000000000000000000
INFO:msmart.lan:Couldn't connect with Device 192.168.8.220:6444
INFO:msmart.cli:*** Found a unsupported device - type: '0xac' - version: V3 - ip: 192.168.8.220 - port: 6444 - id: 163827234280199 - sn: 00000031122012383091305200380000 - ssid: midea_ac_0038
INFO:msmart.cli:Midea Local Data 192.168.8.221 837000c8200f00005a5a0111b8007a8000000000073105091a0215143c921a00009600000000000000000180000000002089db026367c887045355067362f4a000de1e73701bcfdd35a1209133549af3d393c5af9c95eb567d377445131bc628857ab10ddc0463cdafb2283a463b1c5d82986e6a2f1698fe559f2fc34c4bca45433b6e8687a075f9d4e1aaf80ab6481a4bdfb3e16e33d88768cc4c3d0658937d96fbcce99f70c976413c2f05f60f82e76ed7cd01fd42a228d69b674c3980b3152174373733a053ea7bf09217aed369fe
INFO:msmart.cli:Decrypt Reply: 192.168.8.221 dd08a8c02c19000030303030303033313132323031323338313041313430353231313230303030300d6d696465615f61635f3131323000009f0002000000100000000000ac00050000000000a0681cb8ca1f15000320202701030000000000000000000000000000000000000000000000000000000000000000000
INFO:msmart.lan:Couldn't connect with Device 192.168.8.221:644
INFO:msmart.cli:*** Found a unsupported device - type: '0xac - version: V3 - ip: 192.168.8.221 - port: 6444 - id: 16492645907772 - sn: 000000311220123810A1405211200000 - ssid: mide_ac_1120

Versions (版本信息)

• Home Assistant version: core-2021.2.3
• Midea msmart version: 0.1.24