Skip to content
This repository has been archived by the owner on Oct 24, 2024. It is now read-only.

UnhandledPromiseRejectionWarning #24

Open
bogaertterry opened this issue Sep 18, 2018 · 2 comments
Open

UnhandledPromiseRejectionWarning #24

bogaertterry opened this issue Sep 18, 2018 · 2 comments

Comments

@bogaertterry
Copy link

Hello everyone, sorry about my English...

I'm new here, everything work well, the vacuum is detected and work but I got this message in my terminal every time I start the vacuum

((node:587) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: Could not complete call to device
(node:587) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with anon-zero exit code.
(node:587) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 2): Error: Could not complete call to device
(node:587) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 3): Error: Could not complete call to device)

Could you help me ?

Thanks and have a good day,

Terry

@J7mbo
Copy link

J7mbo commented Oct 7, 2018

I also have this problem. Everything works, but I get this in the console.

@ageorgios
Copy link

ageorgios commented Nov 13, 2018

Nov 13 18:39:42 rpi3 homebridge[686]: (node:686) UnhandledPromiseRejectionWarning: Error: Could not complete call to device
Nov 13 18:39:42 rpi3 homebridge[686]:     at checkResult (/usr/lib/node_modules/miio/lib/devices/vacuum.js:13:9)
Nov 13 18:39:42 rpi3 homebridge[686]:     at <anonymous>
Nov 13 18:39:42 rpi3 homebridge[686]: (node:686) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 11)

I also get this, and sometimes I turn on the "Fan" and the command does not propagate until I turn it off and on again.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants