Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

API #5

Open
tanchu opened this issue Aug 22, 2020 · 1 comment
Open

API #5

tanchu opened this issue Aug 22, 2020 · 1 comment

Comments

@tanchu
Copy link

tanchu commented Aug 22, 2020

IQAir has official api.
There is no need to do exec smbget or it would be great to do both implementation: if homebridge hardware has internet - do request to api else do exec()

@evanchaney
Copy link

There are some problems with the IQAir service API. In particular:

  • It can’t be used to access data from a specific device unless that device’s data is public or the caller has a paid IQAir API subscription. If you have an indoors device and you want to keep your home’s data private, but don’t want to spend money on a subscription, for example, you’re out of luck.
  • Many of the device’s measurements can’t be accessed unless the caller has a paid IQAir API subscription. Without a subscription the device’s overall AQI reading is available via the service API but the plugin can’t access readings for each individual component. For example, it wouldn’t be able to provide a carbon dioxide sensor because it can’t see the CO2 concentration.

Providing the option to use either direct device access via SMB or retrieving data using the service API would provide the best service for users.

There’s already another Homebridge plugin which provides AirVisual access through the IQAir service API for data retrieval:

https://github.com/qwtel/homebridge-airvisual-2#readme

It seems fairly mature, but doesn’t support direct device access. So it might make sense for this plugin (homebridge-airvisual-pro) to continue to focus on providing service through direct access only.

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

No branches or pull requests

2 participants