search

joe-ng / homebridge-dyson-link

MIT License
206 stars 40 forks source link

Air quality not working? #80

Open dpyy opened 5 years ago

dpyy commented 5 years ago

In the dyson app it shows as Poor but in the Home app, it shows as Good. Any fix?

jasper-seinhorst commented 5 years ago

Can you check the logs what the value of vact is? It's probably "fail", if thats the case you should clean your fan (both sensor and filter)

I had the same issue, my state was: {"msg":"ENVIRONMENTAL-CURRENT-SENSOR-DATA","time":"2019-05-27T16:12:29.001Z","data":{"tact":"2949","hact":"0044","pact":"0003","vact":"FAIL","sltm":"OFF"}}

ifeign commented 5 years ago

I am having this same issue.

[8/7/2019, 2:17:52 AM] [DysonPlatform] {"msg":"ENVIRONMENTAL-CURRENT-SENSOR-DATA","time":"2019-08-07T02:17:51.002Z","data":{"tact":"2966","hact":"0051","pact":"0004","vact":"0000","sltm":"OFF"}}
[8/7/2019, 2:17:52 AM] [DysonPlatform] Update sensor data from ENVIRONMENTAL-CURRENT-SENSOR-DATA - Air Purifier
jakemauer commented 4 years ago

I'm having the same issue with a brand-new HP04. I just set it up about 10 minutes ago and the UI on the fan itself and the app are reporting good air quality but the home app is saying poor.

{"msg":"ENVIRONMENTAL-CURRENT-SENSOR-DATA","time":"2019-10-15T0
0:31:08.000Z","data":"tact":"2940","hact":"0054","pm25":"0026","pm10":"0015","va10":"INIT","noxl":"INIT","p25r":"0025","p10r":"0023","sltm":"OFF"}}

EDIT: I also want to take this opportunity to thank you for this work, it's really great to be able to drop this fan into my automation setup.

jasper-seinhorst commented 4 years ago

@jakemauer looks like you don't have the vact value. Maybe it is crashing on the missing property.

vwhitteron commented 4 years ago

I had this as well after setting up a brand new HP04. I think the issue is that the math.Max test in DysonEnvironmentState.js is failing on the "INIT" values for va10 and noxl. Perhaps there should be a test on the output of the math.Max and if it is NaN then return 0 for an "unknown" airQuality result.

I did add this on my running instance but unfortunately va10 and noxl started reporting values before I could test it properly.