I own one of these sensors and make it publicly available. Why in the world would I have to pay to get the data from it so I can display it nicely in my home assistant setup when I provide the data free to everyone? Am I missing something?
1 Like
Hello Ganon,
If you’re querying the data for one sensor, the initial one million points can provide several years of data. A user commented about this here: PaymentRequiredError making api calls - #14 by dpattee.
If you never received the initial one million points, please contact us at contact@purpleair.com.
If you are on the same network as the sensor, you can visit its IP address with /json to get the data locally without using the API.
We agree that you shouldn’t have to pay for your personal sensor’s data and are looking for ways to improve and implement this in the future. We appreciate your feedback and welcome any other suggestions.
4 Likes
Appreciate the response!
And sorry, I was a bit grumpy when I posted that apparently. I should’ve known I could hit the sensor locally.
Are you all involved in the HomeAssistant integration at all? I think currently it just uses the API and I’d like it to hit my local sensor. I’d love to make that as easy as possible :-p
2 Likes
I really agree with this - it’s not acceptable to ask users to share their data and then charge to get it back (I cannot access my sensor locally). The limit is large, but it will run out. It should not be difficult to implement a token system linked to a users own account. So please - within the next couple of years! - provide a way for users to get their own data for free.
2 Likes
Hello Ganon,
The HomeAssistant integration was created by a user and is not maintained by PurpleAir. We are looking into directly incorporating data into service like these and hope to have options like that in the future.
3 Likes
Not to be a party pooper, but be sure to read the Terms of Service, especially section 2.6 and all of section 4. The ToS makes it pretty clear who owns the data and what you can do with it.
If you’re doing enough with the sensor to generate a million API calls, then it’s worth it to invest in a Meteobridge (or other compatible datalogger) and store the data yourself.
2 Likes
I also agree with this - I should be able to query my own sensor data without using credits/points. I can get the data required via a local JSON query, but it requires the device to be on the same local network and ideally it would be good to have the PurpleAir isolated for security reasons.
2 Likes
We will figure out a way to make sensor owners able to access their own data for free. We do appreciate all the feedback.
3 Likes
Back two months later because I’ve run out of points - and I still seriously object to having to pay to retrieve my own data. That million points lasted almost exactly two months (the sensor has actually been down for some time, but I assumed it was broken. It’s not: I’ve run out of points so the API calls fail).
Moreover, how on earth have I run out of points? I call the data every ten minutes, generating 100-120 calls per day, but each call uses 155 points? The guide says that each of these calls (get_sensor) should use one point.
Please (a) credit my account immediately with more points and (b) explain what is going on here.
Having looked into this, I’m guessing I am being deducted so many points because I am retrieving all sensor fields, and each one costs points. Is this the case?
Either way, this is still ridiculous for data which I provide myself, to you, for free. Please make good on your promise above and elsewhere to provide free data access - to all personal data - to those who provide it.
Well this is unfortunate. There’s no way my casual use is costing more than the data I’ve been contributing. I’ll be taking all of my sensors offline, and I encourage others who have likewise been cheated to do so as well. I’ll check back in a year or two to see if this is resolved…maybe.