Hello,
I would like to surface the Atmo index using a color code like for the Risque feature that is available here :
It’s possible to fetch the info via Node-RED and send it to MQTT :slight_sm
[quote=« prohand, post:1, topic:8928 »]
I can take care of the development and start testing tomorrow at noon based on what was done
1 Like
Hello,
Here is the PR:
However, I’m encountering a problem: when I assign a value, the device disappears from the dashboard 
I don’t see where the problem could be coming from
I’ve just fixed the issue ^^
I just have a problem with a color that I can’t display:
‹ verypoor-indexatmo ›: ‹ darkred ›,
How can I add darkred?
Second problem: when I run npm test on the front end I get this:
How can I resolve this error?
Thanks
Hi @prohand!
Small question already regarding the feature: we already have AQI in Gladys which looks a lot like this scale, why not just use the AQI which is a more « universal » and international unit? Especially since there are APIs that provide it in France 
I’m saying this to avoid turning Gladys into a purely French product.
When implementing features, we think globally: « What is used as the unit worldwide to represent this value? »
If we read the Wikipedia article on air quality:
We realize that each country has its own scale, sometimes 0 to 8, sometimes 0 to 6, sometimes 0 to 10: basically everyone does their own thing.
In air quality apps, it seems that AQI has become the standard for representing air quality (for example the most well-known app: IQAir AirVisual uses AQI regardless of the country)
In Gladys, we try to have a single unit with conversions for each implementation, so that Gladys can « use » this data regardless of the final implementation.
Example: for smart bulbs, if you use Google Home with Gladys and you say « Make my living room red », it will work directly, even if in the end your bulbs each speak a different unit, because Gladys manages a single unit and does the conversions at the integration level.
For this topic, if for example we add an « Air Quality » widget on the dashboard, or an « Air Quality » layer to the AI part of Gladys, we can’t have the widget do the 10 conversions (Atmo → AQI, « CAQI » → AQI), it’s the integration’s job to do the conversion.
What do you think?
These tests are not used, we should remove them, it causes confusion ^^
We use Cypress on the front
Hello,
Thanks for
1 Like
Ok great
There are air quality APIs that provide the AQI directly in France (and for free):
Example:
1 Like