Comments (9)
嗯 虽然插件中给配置 但协议解析中还是仅仅解析整数
需要提交一些log和抓包过来给我看一下
from midea-ac-py.
请升级最新版本,或者直接修改manifest.json中msmart==0.1.13
ha的配置中增加:
logger:
default: info
logs:
custom_components.midea: debug
msmart: debug
再有相关问题 请筛选出相关log反馈过来
from midea-ac-py.
从28度调整为28.5度的log
2020-05-19 19:45:46 DEBUG (SyncWorker_1) [msmart.packet_builder] Finalize request data: aa20ac00000000000003410000ff03ff00020000000000000000000000000004e9
2020-05-19 19:45:46 DEBUG (SyncWorker_1) [msmart.lan] Sending to 192.168.1.114:6444 5a5a011168002000000000000000000000000000e2740200001c0000000000000000000000000000c7ec8e4276f8accc266a4648044169534ef900b4addf8808145b702d1c28520aec9d938eeaae3d871b99ce4b7e20a37bd8e11e52e30e33efebb4f556214a58a2.
2020-05-19 19:45:47 DEBUG (SyncWorker_1) [msmart.lan] Received from 192.168.1.114:6444 5a5a011168002000000000000000000000000000e2740200001c0000000000000000000000000000c7ec8e4276f8accc266a4648044169534ef900b4addf8808145b702d1c28520aec9d938eeaae3d871b99ce4b7e20a37bd8e11e52e30e33efebb4f556214a58a2.
2020-05-19 19:45:47 DEBUG (SyncWorker_1) [msmart.device] refresh - Recieved from 192.168.1.114, e2740200001c: aa23ac00000000000203c0014c667f7f00000000006e6c1000320000000000000000207f
2020-05-19 19:45:47 DEBUG (SyncWorker_1) [msmart.command] Appliance response data: c0014c667f7f00000000006e6c1000320000000000000000207f
2020-05-19 19:45:47 DEBUG (SyncWorker_15) [msmart.packet_builder] Finalize request data: aa23ac0000000000000240014c6503ff000000000000000000000000000000000000fe3d
2020-05-19 19:45:47 DEBUG (SyncWorker_15) [msmart.lan] Sending to 192.168.1.114:6444 5a5a011168002000000000000000000000000000e2740200001c00000000000000000000000000001b25fa2048aa387116fcb25aa0edb7454bdfb3e16e33d88768cc4c3d0658937d82e77c63e5379a91919e4e1e42b891a3b6c5e05289c0710f29b9894cc0bb263d.
2020-05-19 19:45:48 DEBUG (SyncWorker_15) [msmart.lan] Received from 192.168.1.114:6444 5a5a011168002000000000000000000000000000e2740200001c00000000000000000000000000001b25fa2048aa387116fcb25aa0edb7454bdfb3e16e33d88768cc4c3d0658937d82e77c63e5379a91919e4e1e42b891a3b6c5e05289c0710f29b9894cc0bb263d.
2020-05-19 19:45:48 DEBUG (SyncWorker_15) [msmart.device] apply - Recieved from 192.168.1.114, e2740200001c: aa23ac00000000000202c0014c667f7f00000000006e6c10003200000000000000002080
2020-05-19 19:45:48 DEBUG (SyncWorker_15) [msmart.command] Appliance response data: c0014c667f7f00000000006e6c10003200000000000000002080
2020-05-19 19:45:48 DEBUG (SyncWorker_10) [msmart.packet_builder] Finalize request data: aa20ac00000000000003410000ff03ff00020000000000000000000000000004e9
2020-05-19 19:45:48 DEBUG (SyncWorker_10) [msmart.lan] Sending to 192.168.1.114:6444 5a5a011168002000000000000000000000000000e2740200001c0000000000000000000000000000c7ec8e4276f8accc266a4648044169534ef900b4addf8808145b702d1c28520aec9d938eeaae3d871b99ce4b7e20a37bd8e11e52e30e33efebb4f556214a58a2.
2020-05-19 19:45:49 DEBUG (SyncWorker_10) [msmart.lan] Received from 192.168.1.114:6444 5a5a011168002000000000000000000000000000e2740200001c0000000000000000000000000000c7ec8e4276f8accc266a4648044169534ef900b4addf8808145b702d1c28520aec9d938eeaae3d871b99ce4b7e20a37bd8e11e52e30e33efebb4f556214a58a2.
2020-05-19 19:45:49 DEBUG (SyncWorker_10) [msmart.device] refresh - Recieved from 192.168.1.114, e2740200001c: aa23ac00000000000203c0014c667f7f00000000006e6c1000320000000000000000207f
2020-05-19 19:45:49 DEBUG (SyncWorker_10) [msmart.command] Appliance response data: c0014c667f7f00000000006e6c1000320000000000000000207f
2020-05-19 19:46:02 DEBUG (SyncWorker_8) [msmart.packet_builder] Finalize request data: aa20ac00000000000003410000ff03ff00020000000000000000000000000004e9
2020-05-19 19:46:02 DEBUG (SyncWorker_8) [msmart.lan] Sending to 192.168.1.114:6444 5a5a011168002000000000000000000000000000e2740200001c0000000000000000000000000000c7ec8e4276f8accc266a4648044169534ef900b4addf8808145b702d1c28520aec9d938eeaae3d871b99ce4b7e20a37bd8e11e52e30e33efebb4f556214a58a2.
2020-05-19 19:46:03 DEBUG (SyncWorker_8) [msmart.lan] Received from 192.168.1.114:6444 5a5a011168002000000000000000000000000000e2740200001c0000000000000000000000000000c7ec8e4276f8accc266a4648044169534ef900b4addf8808145b702d1c28520aec9d938eeaae3d871b99ce4b7e20a37bd8e11e52e30e33efebb4f556214a58a2.
2020-05-19 19:46:03 DEBUG (SyncWorker_8) [msmart.device] refresh - Recieved from 192.168.1.114, e2740200001c: aa23ac00000000000203c0014c667f7f00000000006e6c1000320000000000000000207f
2020-05-19 19:46:03 DEBUG (SyncWorker_8) [msmart.command] Appliance response data: c0014c667f7f00000000006e6c1000320000000000000000207f
from midea-ac-py.
2020-05-19 19:41:20 INFO (SyncWorker_2) [homeassistant.util.package] Attempting install of msmart==0.1.13
from midea-ac-py.
(self.data[0x02] & 0xf) + 16
>>> bin(0x4c)
'0b1001100'
setSetTemperate: function(p1, p2) {
mdSmart.message.setBits(_messageBodyControl, 2, 0, 3, p1);
mdSmart.message.setBit(_messageBodyControl, 2, 4, p2);
},
bits中的第4位应该是步长的标志位
目前msmart中未设置此标志位,所以发送和得到的温度都是没有标志位的
所以,请在美居app里设置温度28.5
然后给出hass中同步的log
from midea-ac-py.
你可能理解错我的意思了
我的意思是你在app里去操作,等待一会儿 HASS会去同步 这时候应该得到返回的温度
我需要的是hass中的msmart去同步时候的debug log, 我好确认计算方法
from midea-ac-py.
比如 你将空调从28调整到28.5 然后将这期间的hass中msmart相关的log发给我
from midea-ac-py.
IP 是114的空调,美居app温度从28度调整到28.5 后,等了几秒钟后,ha输出的log
2020-05-27 17:30:28 DEBUG (SyncWorker_10) [msmart.packet_builder] Finalize request data: aa20ac00000000000003410000ff03ff00020000000000000000000000000004e9
2020-05-27 17:30:28 DEBUG (SyncWorker_14) [msmart.packet_builder] Finalize request data: aa20ac00000000000003410000ff03ff00020000000000000000000000000004e9
2020-05-27 17:30:28 DEBUG (SyncWorker_8) [msmart.packet_builder] Finalize request data: aa20ac00000000000003410000ff03ff00020000000000000000000000000004e9
2020-05-27 17:30:28 DEBUG (SyncWorker_10) [msmart.lan] Sending to 192.168.1.114:6444 5a5a011168002000000000000000000000000000e2740200001c0000000000000000000000000000c7ec8e4276f8accc266a4648044169534ef900b4addf8808145b702d1c28520aec9d938eeaae3d871b99ce4b7e20a37bd8e11e52e30e33efebb4f556214a58a2.
2020-05-27 17:30:28 DEBUG (SyncWorker_14) [msmart.lan] Sending to 192.168.1.110:6444 5a5a011168002000000000000000000000000000e85e020000220000000000000000000000000000c7ec8e4276f8accc266a4648044169534ef900b4addf8808145b702d1c28520aec9d938eeaae3d871b99ce4b7e20a37b45ed13363ac83da9f77862d07955814c.
2020-05-27 17:30:28 DEBUG (SyncWorker_8) [msmart.lan] Sending to 192.168.1.106:6444 5a5a0111680020000000000000000000000000001f850200001b0000000000000000000000000000c7ec8e4276f8accc266a4648044169534ef900b4addf8808145b702d1c28520aec9d938eeaae3d871b99ce4b7e20a37b2aa3c0ae20c7311a637cdcff277ce635.
2020-05-27 17:30:28 DEBUG (SyncWorker_14) [msmart.lan] Received from 192.168.1.110:6444 5a5a011168002000000000000000000000000000e85e020000220000000000000000000000000000c7ec8e4276f8accc266a4648044169534ef900b4addf8808145b702d1c28520aec9d938eeaae3d871b99ce4b7e20a37b45ed13363ac83da9f77862d07955814c.
2020-05-27 17:30:28 DEBUG (SyncWorker_14) [msmart.device] refresh - Recieved from 192.168.1.110, e85e02000022: aa23ac00000000000203c0004d667f7f00000000006eff1100050000000000000000f840
2020-05-27 17:30:28 DEBUG (SyncWorker_14) [msmart.command] Appliance response data: c0004d667f7f00000000006eff1100050000000000000000f840
2020-05-27 17:30:29 DEBUG (SyncWorker_10) [msmart.lan] Received from 192.168.1.114:6444 5a5a011168002000000000000000000000000000e2740200001c0000000000000000000000000000c7ec8e4276f8accc266a4648044169534ef900b4addf8808145b702d1c28520aec9d938eeaae3d871b99ce4b7e20a37bd8e11e52e30e33efebb4f556214a58a2.
2020-05-27 17:30:29 DEBUG (SyncWorker_10) [msmart.device] refresh - Recieved from 192.168.1.114, e2740200001c: aa23ac00000000000203c0017c657f7f00000000006c6c1000450000000000000000f06f
2020-05-27 17:30:29 DEBUG (SyncWorker_10) [msmart.command] Appliance response data: c0017c657f7f00000000006c6c1000450000000000000000f06f
2020-05-27 17:30:29 DEBUG (SyncWorker_8) [msmart.lan] Received from 192.168.1.106:6444 5a5a0111680020000000000000000000000000001f850200001b0000000000000000000000000000c7ec8e4276f8accc266a4648044169534ef900b4addf8808145b702d1c28520aec9d938eeaae3d871b99ce4b7e20a37b2aa3c0ae20c7311a637cdcff277ce635.
2020-05-27 17:30:29 DEBUG (SyncWorker_8) [msmart.device] refresh - Recieved from 192.168.1.106, 1f850200001b: aa23ac00000000000203c0004a667f7f00000000006eff0e00090000000000000000cb6f
2020-05-27 17:30:29 DEBUG (SyncWorker_8) [msmart.command] Appliance response data: c0004a667f7f00000000006eff0e00090000000000000000cb6f
2020-05-27 17:30:44 DEBUG (SyncWorker_0) [msmart.packet_builder] Finalize request data: aa20ac00000000000003410000ff03ff00020000000000000000000000000004e9
2020-05-27 17:30:44 DEBUG (SyncWorker_18) [msmart.packet_builder] Finalize request data: aa20ac00000000000003410000ff03ff00020000000000000000000000000004e9
2020-05-27 17:30:44 DEBUG (SyncWorker_13) [msmart.packet_builder] Finalize request data: aa20ac00000000000003410000ff03ff00020000000000000000000000000004e9
2020-05-27 17:30:44 DEBUG (SyncWorker_0) [msmart.lan] Sending to 192.168.1.114:6444 5a5a011168002000000000000000000000000000e2740200001c0000000000000000000000000000c7ec8e4276f8accc266a4648044169534ef900b4addf8808145b702d1c28520aec9d938eeaae3d871b99ce4b7e20a37bd8e11e52e30e33efebb4f556214a58a2.
2020-05-27 17:30:44 DEBUG (SyncWorker_18) [msmart.lan] Sending to 192.168.1.110:6444 5a5a011168002000000000000000000000000000e85e020000220000000000000000000000000000c7ec8e4276f8accc266a4648044169534ef900b4addf8808145b702d1c28520aec9d938eeaae3d871b99ce4b7e20a37b45ed13363ac83da9f77862d07955814c.
2020-05-27 17:30:44 DEBUG (SyncWorker_13) [msmart.lan] Sending to 192.168.1.106:6444 5a5a0111680020000000000000000000000000001f850200001b0000000000000000000000000000c7ec8e4276f8accc266a4648044169534ef900b4addf8808145b702d1c28520aec9d938eeaae3d871b99ce4b7e20a37b2aa3c0ae20c7311a637cdcff277ce635.
2020-05-27 17:30:44 DEBUG (SyncWorker_18) [msmart.lan] Received from 192.168.1.110:6444 5a5a011168002000000000000000000000000000e85e020000220000000000000000000000000000c7ec8e4276f8accc266a4648044169534ef900b4addf8808145b702d1c28520aec9d938eeaae3d871b99ce4b7e20a37b45ed13363ac83da9f77862d07955814c.
2020-05-27 17:30:44 DEBUG (SyncWorker_18) [msmart.device] refresh - Recieved from 192.168.1.110, e85e02000022: aa23ac00000000000203c0004d667f7f00000000006eff1100050000000000000000f840
2020-05-27 17:30:44 DEBUG (SyncWorker_18) [msmart.command] Appliance response data: c0004d667f7f00000000006eff1100050000000000000000f840
2020-05-27 17:30:44 DEBUG (SyncWorker_0) [msmart.lan] Received from 192.168.1.114:6444 5a5a011168002000000000000000000000000000e2740200001c0000000000000000000000000000c7ec8e4276f8accc266a4648044169534ef900b4addf8808145b702d1c28520aec9d938eeaae3d871b99ce4b7e20a37bd8e11e52e30e33efebb4f556214a58a2.
2020-05-27 17:30:44 DEBUG (SyncWorker_0) [msmart.device] refresh - Recieved from 192.168.1.114, e2740200001c: aa23ac00000000000203c0017c657f7f00000000006c6c1000450000000000000000f06f
2020-05-27 17:30:44 DEBUG (SyncWorker_0) [msmart.command] Appliance response data: c0017c657f7f00000000006c6c1000450000000000000000f06f
2020-05-27 17:30:45 DEBUG (SyncWorker_13) [msmart.lan] Received from 192.168.1.106:6444 5a5a0111680020000000000000000000000000001f850200001b0000000000000000000000000000c7ec8e4276f8accc266a4648044169534ef900b4addf8808145b702d1c28520aec9d938eeaae3d871b99ce4b7e20a37b2aa3c0ae20c7311a637cdcff277ce635.
2020-05-27 17:30:45 DEBUG (SyncWorker_13) [msmart.device] refresh - Recieved from 192.168.1.106, 1f850200001b: aa23ac00000000000203c0004a667f7f00000000006eff0e00090000000000000000cb6f
2020-05-27 17:30:45 DEBUG (SyncWorker_13) [msmart.command] Appliance response data: c0004a667f7f00000000006eff0e00090000000000000000cb6f
from midea-ac-py.
msmart version 0.1.19 fixed
from midea-ac-py.
Related Issues (20)
- Carrier Infinity
- error when adding multiple midea AC HOT 2
- 我用洗衣机开启时间自动变了,目前还不知道是那个程序。
- entity does not accept name as parameter HOT 1
- 希望支持colmo**空调 HOT 6
- Unable to install package msmart==0.2.4, HOT 1
- Outdoor temperature, 永远是102.5 HOT 3
- No need for logs when devices are off HOT 5
- Rotenso AC msmart.device.AC.appliance HOT 1
- Where do I find the ID number of the unite? HOT 8
- 'Account or Password Incorrect' Issue (probably Midea?) HOT 1
- Qlima AC supported?
- Warning message from HA suggesting alternative call HOT 10
- midea-discover returns code 3004 "value is illegal" HOT 10
- Does this work with Frierich ACs (those use Friedrich Go App) HOT 1
- Device not found HOT 8
- Looking for support? New features? Try my fork!
- Recursion error HOT 4
- Inventor Acc HOT 2
- Midea AG-12NXD1.WIK
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from midea-ac-py.