-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature(ED): 厨下式净水器所有传感器都显示 未知 #352
Feature(ED): 厨下式净水器所有传感器都显示 未知 #352
Comments
Title: All sensors of the kitchen water purifier show Unknown |
You log shows:
|
我的空调和洗碗机也遇到这种情况,回退到0.5.7就解决了 |
My air conditioner and dishwasher also encountered this problem, and it was solved by returning to 0.5.7 |
@jesson20121020 提供一下设备的SN信息(可以从美居app设备信息里面复制粘贴),这个需要新增设备的协议解析。当前净水器的协议并不适合你这款设备,所以才会报 |
@jesson20121020 Provide the SN information of the device (you can copy and paste it from the device information of the Meiju app). This requires protocol analysis of the new device. The current protocol of the water purifier is not suitable for your device, so it reports |
可能表面上看,是相同的结果,但是问题的原因并不一定一样。 |
On the surface, the results may appear to be the same, but the causes of the problems are not necessarily the same. |
@wuwentao |
多谢,我自己也有一个colmo的管线机DA01,也是ED类型,也报这个错误,但是功能太简单了,没有净水,滤芯等功能,大部分功能我本地都加了一些,但是还没提交进来,也不确定净水机具体有多少款,后续我加上以后,帮忙测试和反馈一下最新的状态即可。 可以通过首页README的Discord Chat链接加入 |
Thank you. I also have a colmo pipeline machine DA01, which is also an ED type. I also reported this error, but the function is too simple. There is no water purification, filter element and other functions. I have added most of the functions locally, but have not submitted them yet. , I am not sure how many models of water purifiers there are. I will add them later and help test and give feedback on the latest status. |
@jesson20121020 多谢确认,帮忙提供一个你现在修改以后的 debug log吧。 我看看怎么单独加一个if/else的判断和匹配条件来解决吧 |
Thank you for confirming. My local pipeline machine is also X01. I have been debugging it locally for a while, but other functions could not be confirmed, so I did not submit the code. |
2024-10-14 14:14:31.574 DEBUG (厨下式净水机) [midealocal.device] [162727723851771] refresh_status with cmds: [<midealocal.devices.ed.message.MessageQuery object at 0x7f6b9fd53140>], check_protocol False |
多谢,你这个就是query的修改即可。 请试试将midea-local里面 修改为: 看看是不是就解决的问题? |
@jesson20121020 请帮忙抽空确认一下,上面的修改是否能够解决问题,多谢 |
@jesson20121020 Please take the time to confirm whether the above modifications can solve the problem. Thank you. |
不要意思,给忘了; 刚测试了下, 还是有点问题, 因为device.py里refresh_status函数中,在for循环中,如果出现了timeout, 就会添加到unspported_protocol中,导致后面的cmd跳过执行了。 2024-10-16 11:42:07.595 DEBUG (厨下式净水机) [midealocal.device] [162727723851771] refresh_status with cmd: {'_device_type': <DeviceType.ED: 237>, '_message_type': <MessageType.query: 3>, '_body_type': <BodyType.X00: 0>, '_message_protocol_version': 0, 'header': 'aa0ced00000000000003', 'body': '0001', 'message_type': 'query', 'body_type': '00', 'self': <midealocal.devices.ed.message.MessageQuery object at 0x7f89e5391130>}, unsupported protocol, SKIP |
@jesson20121020 是的,但是必须要有一个能够返回结果的query,才能生成后续的数据和刷新状态。 按你的描述,应该就是消息查询和解析的问题,具体字段都是一样的。 |
@jesson20121020 Yes, but there must be a query that can return results in order to generate subsequent data and refresh the status. According to your description, it should be a problem of message query and parsing. The specific fields are the same. |
@jesson20121020 需要提供完整的log,以上log并不能体现任何错误,均是最后已经处于错误状态的log了,无法反应准确的状态和错误。 |
@jesson20121020 A complete log needs to be provided. The above logs cannot reflect any errors. They are all logs that are already in an error state at the end and cannot reflect the exact status and errors. |
@jesson20121020 多谢提供log,请帮忙继续修改一下代码测试一下: 确实2个文件都需要修改,具体修改内容如下: 1. 将
2. 将 之前应该已经修改为: 现在需要修改为:
大概率应该就解决问题了,你的其他修改可能也可以回退了 |
已测试 ok |
@jesson20121020 收到,多谢确认,我提交MR,争取下个版本生效吧 |
@jesson20121020 Received, thank you for confirming, I will submit MR and try to take effect in the next version. |
HA版本
2024.10.1
集成版本
0.6.2
之前可正常使用的集成版本
不确定,大概是半年前
设备类型及型号
Water Drinking Appliance 6321898A (4481)
使用的App
美的美居
问题详细描述
不确定是从哪个版本开始坏的。
The logs
2024-10-08 21:24:27.774 DEBUG (厨下式净水机) [midealocal.device] [162727723851771] refresh_status with cmds: [<midealocal.devices.ed.message.MessageQuery object at 0x7f52b91b7ef0>], check_protocol False
2024-10-08 21:24:27.774 DEBUG (厨下式净水机) [midealocal.device] [162727723851771] refresh_status with cmd: {'_device_type': <DeviceType.ED: 237>, '_message_type': <MessageType.query: 3>, '_body_type': <BodyType.X00: 0>, '_message_protocol_version': 0, 'header': 'aa0ced00000000000003', 'body': '0001', 'message_type': 'query', 'body_type': '00', 'self': <midealocal.devices.ed.message.MessageQuery object at 0x7f52b91b7ef0>}, unsupported protocol, SKIP
2024-10-08 21:24:27.774 DEBUG (厨下式净水机) [midealocal.device] [162727723851771] all the query cmds failed [<midealocal.devices.ed.message.MessageQuery object at 0x7f52b91b7ef0>], please report bug
2024-10-08 21:24:27.774 DEBUG (厨下式净水机) [midealocal.device] [162727723851771] No Supported protocol
2024-10-08 21:24:27.774 DEBUG (厨下式净水机) [midealocal.device] [162727723851771] refresh_status with cmds: [<midealocal.devices.ed.message.MessageQuery object at 0x7f52b91b7ef0>], check_protocol False
2024-10-08 21:24:27.774 DEBUG (厨下式净水机) [midealocal.device] [162727723851771] refresh_status with cmd: {'_device_type': <DeviceType.ED: 237>, '_message_type': <MessageType.query: 3>, '_body_type': <BodyType.X00: 0>, '_message_protocol_version': 0, 'header': 'aa0ced00000000000003', 'body': '0001', 'message_type': 'query', 'body_type': '00', 'self': <midealocal.devices.ed.message.MessageQuery object at 0x7f52b91b7ef0>}, unsupported protocol, SKIP
2024-10-08 21:24:27.774 DEBUG (厨下式净水机) [midealocal.device] [162727723851771] all the query cmds failed [<midealocal.devices.ed.message.MessageQuery object at 0x7f52b91b7ef0>], please report bug
2024-10-08 21:24:27.774 DEBUG (厨下式净水机) [midealocal.device] [162727723851771] No Supported protocol
2024-10-08 21:24:27.774 DEBUG (厨下式净水机) [midealocal.device] [162727723851771] refresh_status with cmds: [<midealocal.devices.ed.message.MessageQuery object at 0x7f52b91b7ef0>], check_protocol False
The text was updated successfully, but these errors were encountered: