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

Unable to discover the device (zhimi.airpurifier.ma4) #798

Closed
poma opened this issue Aug 15, 2020 · 5 comments
Closed

Unable to discover the device (zhimi.airpurifier.ma4) #798

poma opened this issue Aug 15, 2020 · 5 comments

Comments

@poma
Copy link

poma commented Aug 15, 2020

Describe the bug
Unable to interact with device.

Version information (please complete the following information):

  • OS: Ubuntu 18.04
  • python-miio: 0.5.3

Device information:

  • Model: Air Purifier 3
  • Hardware version: zhimi.airpurifier.ma4
  • Firmware version: 2.1.3.0022

To Reproduce

$ miiocli device --ip 172.16.*** --token *** info
Error: Unable to discover the device 172.16.***
  • I verified that the device ip is correct
  • I'm able to successfully ping this ip address
  • My PC and the device are in the same subnet

Also tried doing this from a Mac (10.15.6, miio 0.5.3):

$ miiocli device --ip 172.16.*** --token *** info
ERROR:miio.miioprotocol:Got error when receiving: timed out
Error: No response from the device
@poma
Copy link
Author

poma commented Sep 3, 2020

So how do I troubleshoot this?

@poma
Copy link
Author

poma commented Sep 9, 2020

I tried to monitor network with wireshark and it looks like the device responds to handhakes:

> 21310020ffffffffffffffffffffffffffffffffffffffffffffffffffffffff
< 2131002000000000123d37c7000007c5ffffffffffffffffffffffffffffffff

@poma
Copy link
Author

poma commented Sep 28, 2020

Found the reason: outdated token

When I used -dd switch I saw errors like Unable to decrypt, returning raw bytes, looks like this is a clear sign that token is incorrect

@rytilahti
Copy link
Owner

The unable to decrypt message also gets printed during the discovery process, normally the incorrect token causes Got checksum error which indicates use of an invalid token error. Are you sure that didn't happen?

Glad you got it working though!

@poma
Copy link
Author

poma commented Oct 1, 2020 via email

@syssi syssi removed the bug label Nov 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants