aanon4 / homebridge-purpleair Goto Github PK

Feature Request: It would be great if there were a custom attribute for the raw AQI. This would make it visible in Eve, for instance, without the obfuscation of Excellent, Good, Poor, etc.

Feature Request: It would be nice to support fakegato-history in order to allow graphing of appropriate attributes in Eve, etc.

Because of a power connector failure, PurpleAir replaced my sensor. I registered the new hardware and it was given a new ID. I changed the ID in the homebridge config, changed nothing else. It is not reading data from the new ID. If I use the old ID I see the residual AQI for that ID in homebridge.

Can't imagine what could be wrong. json status reads to both the IDs at the PurpleAir server seem to work identically, but I may be missing something.

New: https://www.purpleair.com/json?show=97693
Old: https://www.purpleair.com/json?show=54167

This is not important in my life, but if you can identify the issue, it would assuage my curiosity.

With indoor air quality control becoming increasingly important with all the wild fires, many sensitive folks might appreciate the ability to switch on their purification devices at a lower level than the rough triggers Homekit allows (50, 100 etc.). As a feature request to the developers, I suggest to allow the user to set a trigger anywhere between 0 and 50 (or 0 and 100). Obviously, given the Apple restrictions, the Purpleair Bridge would then need to "fool" Homekit by passing on "fake" values: Say a user with asthma wants her/his purifier to kick in at an AQI of 25, Purpleair Bridge would need to tell Homekit that the values equivalent to an AQI of 50 have already been met though they are actually lower. Thank you for your consideration.

PurpleAir has made the change and this plugin will no longer work. There is a workaround here.

As per their Using PurpleAir data document, PurpleAir is migrating all users to a new API at https://api.purpleair.com/, and will soon be blocking all access to purpleair.com/data.json and purpleair.com/json.

Users will also need to contact PurpleAir by email to get a key to access the new API, which would need this plugin to provide a place to provide that key.

Next day edit:
There may be a workaround; the sensor has a webserver open on port 80, and from that the user can find a string of data that gets reported out to PurpleAir (it can be found at http://192.xxx.xxx.xxx/json). I'm not sure how to go about doing this (my java-fu is very weak, and so far I've only got an error log a mile long to show for it), but if this string could be accessed and the readings extracted, then that would eliminate the problem of the API access altogether. There's also the option to expose the PM1.0 reading, dewpoint, and air pressure, and make these available to the user.

There'd be a bit of calculation involved though to make the values match what the PurpleAir map shows; there's the humidity and temperature divergence issues that have already been raised, but also there are two particulate sensors in the device, and this method exposes both of them as-is, so that would need to be taken care of as well (but I'm pretty sure they just average them, unless one of the sensors dies).

HOOBS is throwing the following error upon loading the plugin:

12/8/2020, 4:54:48 PM [12/8/2020, 4:54:48 PM] Plugin 'timjwilkinson/homebridge-purpleair' tried to register with an incorrect plugin identifier: '@timjwilkinson/homebridge-purpleair'. Please report this to the developer!

Not sure if this problem also hits homebridge native, but figured I'd pass it along.

I have a separate weather sensor in the same location as my PurpleAir, and the temperature and humidity sensors are much more accurate than what PurpleAir generates, so I'd like to only publish the AQI sensor to HomeKit. As it stands when I ask Siri for the temperature in the backyard it reports a range.

Ideally there could either be boolean flags in the config to show/hide the individual sensors, or perhaps some sort of option list. Just some way to only publish partial sets of the available sensors would be grand!

"To find your specific "PURPLE_AIR_STATION_ID" (a string):

Use the PurpleAir Map to locate a station (https://www.purpleair.com/map)
Open this URL in a new Window or Tab: (https://www.purpleair.com/json)
Search for the NAME of the station you found in step A (using JSONview in Google Chrome makes this a bit easier)
The Station ID is the first element in the results[:] map - you will enter this ID (1-5 digits) into the preferences for the Air Quality Station
If you have an outdoor sensor, there should be 2 entries in the big JSON file, one for each sensor. Please use only the FIRST entry - the code will find the second and average the values, as done for the PurpleAir map."

These instructions are frustrating and do not work.

Instead, you open the map, find your device, click on your device and look for the numbers after SELECT in the URL.

Just FYI, that temperatures are reporting high (by 8 degrees F).

https://www2.purpleair.com/community/faq#hc-primary-and-secondary-data-header

Tempertautre_F: Temperature inside of the sensor housing in Fahrenheit. On average, this is 8F higher than ambient conditions. (From BME280)