-
Notifications
You must be signed in to change notification settings - Fork 8
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
Call to device time out #7
Comments
May I know what version of Node JS you have installed? Make sure you have Node 6 and above installed. If you still not able to get the token, you may follow the instructions by #3 (comment) |
Hello I was able to get the token but have the same problem: (node:1266) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: Not able to initialize robot vacuum. (node:1240) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 2): Error: Call to device timed out ping to the robot ip works |
What is your Node version? Please make sure you have NodeJS 6 or above installed. |
my version is 6.10.0 |
@Tim2309 I'm sorry, it seems like is a problem from miIO library. May I know which version of miIO you have installed as well? Due to recent firmware update from Mi, the setup have not working perfectly now. |
My Robot is on 3.3.9_003077 If this help How can i Check my milO Version? |
do you mean miio? the problem was a false token, i used an android phone and the mi toolkit to get the right one. |
@seikan any plan to fix the bug? thanks |
@seikan My Nodejs version is 7. |
@Tim2309 Hi, do you mean the guide of miio to get the token cannot get a right one? How to use an android phone to get token? Install mihome and try developer mode? |
I used an android and the mi toolkit All other methods didn‘t work for me (iPhone backup and Terminal command) |
@Tim2309 thx |
The token never comes. Been waiting 20 min now. I'm on Node.js v 6, via Terminal/Mac OS. |
Allright, just managed to get the Token, however I got the same error:
|
I got the token easily, almost instantly in fact, but no control over the vacuum and the same Unhandled promise rejection as being reported here. Vacuum has static DHCP assignment and the correct IP address is listed in the config.json |
Same Problem with node 6.11 |
Same Problem here
|
@seikan , can you solve that problem ? Edit: It's 23:37 , and the robots works again with homekit =) |
I still have this issue, any ideas? |
@adidoes What error message you got? |
I get this:
also this:
Funny thing is that trying to reproduce this it worked once, but I have no idea why. |
Solution for me was the description postet by @Nastra888 in #3
|
I am also getting "Call to device timed out" errors. Here are a few. node: 9.3.0
|
Please update to latest version of miio. |
I followed your introduce step by step, but my homebridge report an error.
(node:461) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: Not able to initialize robot vacuum.
(node:461) DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
(node:461) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 2): Error: Call to device timed out
The text was updated successfully, but these errors were encountered: