-
Notifications
You must be signed in to change notification settings - Fork 36
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
Make it compatible with WAQI. #35
Comments
thanks for letting me know about WAQI. I'll see what sensors are available from this integration. |
Super-quick fix if you don't want to wait.
This is a bodge; there are surely shortcuts and errors but for the moment it works on my config, so I am happy with this. I did my best; I am sure that my code will be gross to watch for some of the experienced chaps in here and I am open to suggestions! I left my Location and Stations of interest in, so for you to quickly try the config with a working configuration; change it accordingly to your location. In the declaration of sensor.waqi_air_pollution_level, the attributes latitude and longitude are commented out. This because I found out these are not strictly necessary for the functionality of AirVisual Card. |
Thanks. I started implementing it but ran into some issues. I'm pretty slow so it's good you wrote a template sensor instead. Thanks for figuring out the values for main pollutant, I will add that to the code. |
I'll leave this with you. Shout if you need any help, closing this now. Cheers |
Hey @Ndrinta , I'm almost done adding WAQI support, but wanted your help on calculating this value (see red circle) Do you know how this value is calculated? Is it possible to calculate with the data from the WAQI sensors? |
I've added in WAQI support, but I'm not going to publish a new release due to insufficient testing. It technically works, and if Airvisual has problems again, I'll probably pick this up again. You can put the .js file in your /www/community/air-visual-card directory |
Amazing, thanks!
As far as I know, the AQI is "calculated" in this way: Also, if I can say, the way in which IQAir derives the Air Quality Index (AQI) is a bit of a mystery:
While WAQI is pretty simple and open (US EPA standard). |
Hi all, I've setup a air visual card using WAQI from a year or so. I worked great but starting from few days values are always shown in english even if my template sensor use my native language: CARD:
SENSOR
Has something changed? |
Hello trying the same thing I get AQI value, face, and main pollutant unit right but I miss air quality "text value", main pollutant and main pollutant value any help appreciated
|
@walkercz Do you see any errors in the developer console in your browser (F12) when the card is rendered? |
OK SORRY GUYS - I realize that I just need to use default waqi value.. 🤦♂️
Do not get me wrong .. the output of the custom sensors is accurate, but the output is displayed only partially in the card itself maybe the card expect different input? |
Could you try to set your template to match these sensors sensors.en.json? |
Hi guys. I've made a little tweak to show main pollutant value when using WAQI sensor (it still doesn't work for AirVisual tho). Can't tell if I did it 100% right (this is my first time tinkering with Lovelace cards tbh) but you all are very welcome to take a look at the code. |
I'm using only WAQI and I have the same problem. Only AQI is shown and nothing else, no text, no pollutant. |
@ngseer even using your repo; I still get: Is this still working for people? |
AirVisual suddenly stopped working for my city for some reason (returns city_not_found) so I switched to the WAQI integration. I was pleasantly surprised that this air-visual-card worked just fine with no extra sensors or modifications required, I just put the same waqi sensor for all 3 air quality entities. |
Given the recent issues with the AirVisual API (#42776), I'd be nice to have a backup when stuff like this happen.
WAQI looks like the only alternative for home assistant right now.
Is this feasible?
The text was updated successfully, but these errors were encountered: