-
Notifications
You must be signed in to change notification settings - Fork 7.6k
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
Support for TVOC, eCO2, AQI readings (carbondioxide zigbee device) #11036
Comments
I would add to "wish list" "the air fine dust value" (PM100,PM10,PM5,PM2.5) with unit ppm |
Hi, please take a look there in esp-zigbee-sdk file: Those are currently all available clusters implemented in esp-zigbee-sdk. I see there the PM2.5, but no TVOC or AQU clusters. |
If there are not the clusters you are looking for, I may implement that in the esp-zigbee-sdk and after its merged there and new version gets released do implementation here in Zigbee library. |
Indeed, AQI and TVOC identifiers do not exist on this list. I thought that they would be there as I've seen zigbee devices report them, like Aqara TVOC does. I hope they will be added down the road, if this is common way when updating cluster identifiers on the sdk. |
As Espressif use Zigbee 3.0 specification, so if Aqara uses the same (for 99% percent they does) then yes, they follow the official. If you are willing to add any new clusters that are not supported yet in esp-zigbee-sdk, feel free to also open a feature request there :) |
Related area
Extend carbondioxide device end point of zigbee
Hardware specification
ESP32-C6 with Gravity ENS160 Air Quality board
Is your feature request related to a problem?
Carbondioxide end device and its example supports reporting of CO2 value only.
In case of using a Gravity ENS160 attached via I2C to a ESP32-C6 the values of TVOC and AQI are also available from the ENS160.
Describe the solution you'd like
Extend the carbondioxide end device (+example) to also report TVOC and AQI values through zigbee.
Describe alternatives you've considered
No response
Additional context
No response
I have checked existing list of Feature requests and the Contribution Guide
The text was updated successfully, but these errors were encountered: