Skip to content
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

Bug: colmo DA01 powe/lock action got unidentified protocol #299

Closed
wuwentao opened this issue Aug 29, 2024 · 1 comment
Closed

Bug: colmo DA01 powe/lock action got unidentified protocol #299

wuwentao opened this issue Aug 29, 2024 · 1 comment
Labels
bug Something isn't working midea-local library Issue/enanchement in midea-local library

Comments

@wuwentao
Copy link
Owner

HA core version

No response

Current integration version

0.5.7

Last known working integration version

not know

Device type and model

Water Drinking Appliance 63200860 (895)

Working mobile app

Meiju

The description of problem

there is a colmo DA01 device, in default query mode, it works well.

once we click power/lock button, it will received a unidentified protocol.

after check and debug with the packet, the content is the same content as query, and only body_type/message_type is different.

based on midea device protocol, message_type 0x02 should be set packet and used to send it to device, seems this device just response it and homeassistant received this packet.

in first step, we can simple parse it and update the status as query message
in the future step, we can continue check and confirm the power/lock action, as these action may not works for colmo DA01 device.

'message type': '.04'

ff010700400010050201100602400103010103101c05103706102d0b10531150b01b00000012500000000000203000000021505f000000002250000000000023600f1e32000000264000001e00272000002810002910003070000000000000003110003620780037300000000522d40007121c08121f09121f3a4000000000

'message type': '.02':

15020700400010050201100602400103010103101c05103706102d0b10531150b01b00000012500000000000203000000021505f000000002250000000000023600f1e32000000264000001e00272000002810002910003070000000000000003110003620780037300000000522d40007121c08121f09121f3a4000000000

only the first two data is difference.

Solution:

response message parse message_type 02 and body_type 15

The logs

log

2024-08-29 18:38:56.749 DEBUG (管线机) [midealocal.device] [210006727698088] Status update: {'power': False, 'water_consumption': 7.088, 'child_lock': True}
2024-08-29 18:38:57.731 DEBUG (管线机) [midealocal.devices.ed] [210006727698088] Received: {'header': 'aa89ed00000000000004', 'body': 'ff010700400010050201100602400103010103101c05103706102d0b10531150b01b00000012500000000000203000000021505f000000002250000000000023600f1e32000000264000001e00272000002810002910003070000000000000003110003620780037300000000522d40007121c08121e09121f3a4000000000', 'message type': '.04', 'body type': '.ff'}
2024-08-29 18:38:57.732 DEBUG (管线机) [midealocal.device] [210006727698088] Status update: {'power': False, 'water_consumption': 7.088, 'child_lock': True}
2024-08-29 18:38:58.711 DEBUG (SyncWorker_5) [midealocal.device] [210006727698088] Sending: {'header': 'aa0ded00000000000002', 'body': '150100', 'message type': '.02', 'body type': '.15'}
2024-08-29 18:38:58.745 DEBUG (管线机) [midealocal.devices.ed] [210006727698088] Received: {'header': 'aa89ed00000000000004', 'body': 'ff010700400010050201100602400103010103101c05103706102d0b10531150b01b00000012500000000000203000000021505f000000002250000000000023600f1e32000000264000001e00272000002810002910003070000000000000003110003620780037300000000522d40007121c08121f09121f3a4000000000', 'message type': '.04', 'body type': '.ff'}
2024-08-29 18:38:58.746 DEBUG (管线机) [midealocal.device] [210006727698088] Status update: {'power': False, 'water_consumption': 7.088, 'child_lock': True}
2024-08-29 18:38:58.960 DEBUG (管线机) [midealocal.devices.ed] [210006727698088] Received: {'header': 'aa89ed00000000000002', 'body': '15020700400010050201100602400103010103101c05103706102d0b10531150b01b00000012500000000000203000000021505f000000002250000000000023600f1e32000000264000001e00272000002810002910003070000000000000003110003620780037300000000522d40007121c08121f09121f3a4000000000', 'message type': '.02', 'body type': '.15'}
2024-08-29 18:38:58.960 DEBUG (管线机) [midealocal.device] [210006727698088] Unidentified protocol
2024-08-29 18:38:59.735 DEBUG (管线机) [midealocal.devices.ed] [210006727698088] Received: {'header': 'aa89ed00000000000004', 'body': 'ff010700400010050201100602400103010103101c05103706102d0b10531150b01b00000012500000000000203000000021505f000000002250000000000023600f1e32000000264000001e00272000002810002910003070000000000000003110003620780037300000000522d40007121c08121f09121f3a4000000000', 'message type': '.04', 'body type': '.ff'}
2024-08-29 18:38:59.736 DEBUG (管线机) [midealocal.device] [210006727698088] Status update: {'power': False, 'water_consumption': 7.088, 'child_lock': True}
2024-08-29 18:39:01.044 DEBUG (SyncWorker_12) [midealocal.device] [210006727698088] Sending: {'header': 'aa0ded00000000000002', 'body': '150100', 'message type': '.02', 'body type': '.15'}
2024-08-29 18:39:01.270 DEBUG (管线机) [midealocal.devices.ed] [210006727698088] Received: {'header': 'aa89ed00000000000002', 'body': '15020700400010050201100602400103010103101c05103706102d0b10531150b01b00000012500000000000203000000021505f000000002250000000000023600f1e32000000264000001e00272000002810002910003070000000000000003110003620780037300000000522d40007121c08121f09121f3a4000000000', 'message type': '.02', 'body type': '.15'}
2024-08-29 18:39:01.271 DEBUG (管线机) [midealocal.device] [210006727698088] Unidentified protocol
2024-08-29 18:39:01.727 DEBUG (管线机) [midealocal.devices.ed] [210006727698088] Received: {'header': 'aa89ed00000000000004', 'body': 'ff010700400010050201100602400103010103101d05103706102d0b10531150b01b00000012500000000000203000000021505f000000002250000000000023600f1e32000000264000001e00272000002810002910003070000000000000003110003620780037300000000522d40007121d08121f09121f3a4000000000', 'message type': '.04', 'body type': '.ff'}
@wuwentao wuwentao added bug Something isn't working midea-local library Issue/enanchement in midea-local library labels Aug 29, 2024
@wuwentao wuwentao changed the title colmo DA01 powe/lock action got unidentified protocol Bug: colmo DA01 powe/lock action got unidentified protocol Aug 30, 2024
rokam pushed a commit to midea-lan/midea-local that referenced this issue Sep 9, 2024
…#284)

fix #283 
origin from wuwentao/midea_ac_lan#299


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

- **New Features**
	- Introduced a new body type, `X15`, to enhance message categorization.
- Expanded response handling to accommodate a new message type,
improving flexibility in message processing.

- **Improvements**
- Updated initialization parameters for message handling classes to
enhance readability and maintainability.
- Established a comprehensive suite of unit tests for ED message
handling, ensuring robust functionality and correctness.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
@wuwentao
Copy link
Owner Author

wuwentao commented Sep 9, 2024

fixed

@wuwentao wuwentao closed this as completed Sep 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working midea-local library Issue/enanchement in midea-local library
Projects
None yet
Development

No branches or pull requests

1 participant