-
-
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
Device became unavailable after last MSmartHome app upgrade #11
Comments
It's possible the firmware updated and the protocol has changed. What's interesting is that final byte in each message appears to be a valid checksum Can you enable debug messages and provide logs from that? |
Other users reported similar problems. No solution yet. This one also looks like a checksum Unsure about this one |
It seems thah something changed on firmware, because msmart 0.2.3 worked correctly before the midea app upgrade. Now I'm using with success the package Midea AC LAN, but the next days I will try with debug property. |
msmart 0.2.3 never checked the CRC or checksum on responses from the device. That was introduced in v0.2.4. It looks like midea_ac_lan also doesn't check for CRCs or checksum. So I bet your device FW didn't update, but simply this library did and it's incompatible |
But now I have the same problem with msmart 0.2.3 |
Can you confirm that msmart 0.2.3 is installed? Provide the output of |
I have the same issue with msmart 0.2.5. here is the output from this command:
|
I've got a branch that tries to resolve this issue. Can you give it a shot? Install like so
And then post the output of |
@mill1000
|
Thanks. It's a start! I'll make some changes to properly initialize the object and that should clear up the exception. Can you provide the following info for me?
|
Thanks for the support! The unit is the following:
Update: This is the state of the unit while trying it:
|
Just updated the branch. Try installing again and post the output of midea-discover -d |
YES IT WORKS! finally got no errors and got the id! :D Now i hope it works with the Home Assistant integration :) Here is the output from the debug run
Thanks again @mill1000 |
Cool! Progress! I just noticed a bug and push another change to the branch. Let me know how it goes with HA. Your device sends interesting messages so I'm curious how well it works |
The integration in HA seems to work ok, but when I try to use it in the dashboard, I get an error. I copied this directory to the custom_components then restarted HA
|
Looks like you didn't update the branch since yesterday. I noticed a bug yesterday after your initial success. Try pulling the latest.
|
Are you talking about this repo? |
No, I mean mill1000/midea-msmart. The same one we worked with earlier. So update with the same pip command from #11 (comment) |
Awesome! I'll get these fixes merged in so everyone else gets them too. Feel free to create new issues for any problems you encounter. |
Describe the bug (描述一下问题)
It is unable to get the device available.
Screenshots / Logs / Pcap File(屏幕截图/日志/抓包文件)
This is the output from midea-discover:
ERROR:msmart.device.AC.command:Payload 'c0004a667f7f00000000006b67000000000000c0' failed CRC. Received: 0xC0, Expected: 0xCB.
ERROR:msmart.device.AC.command:Payload 'c0004a667f7f00000000006a67000000000000c1' failed CRC. Received: 0xC1, Expected: 0x88.
ERROR:msmart.device.AC.command:Payload 'c0004a667f7f00000000006967000000000000c2' failed CRC. Received: 0xC2, Expected: 0x4D.
ERROR:msmart.device.AC.command:Payload 'c0004a667f7f00000000006867000000000000c3' failed CRC. Received: 0xC3, Expected: 0xE.
Versions (版本信息)
The text was updated successfully, but these errors were encountered: