search

Bluebie / homebridge-miio

Xiaomi Mi Home Plugin for Homebridge
112 stars 26 forks source link

TimeoutOverflowWarning with Node 9.10.0 #35

Open Bankaifan opened 6 years ago

Bankaifan commented 6 years ago

After Upgrading to 9.10.0 I had to remove Homebridge-miio since it wrote this message ever millisecond to the log (node:8662) TimeoutOverflowWarning: Infinity does not fit into a 32-bit signed integer. Timeout duration was set to 1.

mensa84 commented 5 years ago

I have the same problem. Is there any solution?

Bluebie commented 5 years ago

I have no idea, I'm using node 11.6 in my home. Is there a compelling reason why this software needs to support such outdated versions of node js?

mensa84 commented 5 years ago

I tried with 10 and 11 and that error is appearing on both.

Bluebie commented 5 years ago

I recently setup a test installation to see if i could reproduce this, aside from my regular home setup, and i'm not seeing it. Can you provide more information about your setups?

mensa84 commented 5 years ago

It's a fresh install on debian 9. Only homebridge + requirements + node are installed.

mensa84 commented 5 years ago

It seems as if this error is only appearing if the homebridge directories "accessories" and "persist" are EMPTY at startup of homebridge with a newer NodeJS version. I can't say which file or entry makes that problem. Maybe that helps you to find?

mensa84 commented 5 years ago

Is it required, that additionally miio is installed? https://www.npmjs.com/package/miio

Bluebie commented 5 years ago

It's absolutely required - it's an npm dependancy, so if you installed homebridge-miio via npm, it will have installed miio along with it.

mensa84 commented 5 years ago

I installed now by that command: npm install -g --unsafe-perm homebridge-miio How can I check if miio is really installed?

psolin commented 5 years ago

This is still a major issue -- totally kills my raspberry pi's logs. Avoid this and all packages dependent on it.

phenomeus commented 4 years ago

i have the same problem but that wasn't the case with pi3. now I'm on a pi4 with node -v v12.16.1

and npm -v 6.14.1

Blindingend commented 2 years ago

I meet the same issue. I'm using: pi4 node v14.17.5 npm v6.14.14