Sensorbee Release Notes
(Updated on 2024/06/06)
Fixed Issues
Issues that were fixed:
- Fixed stuck "unpairing" status bug when unpairing units
- Resolved an issue where attempting to unpair a sensor unit from the cloud service would sometimes result in that unit becoming stuck in an "unpairing" state, even though the unpairing process had completed on the backend. This would prevent users from being able to repair the affected unit or attach it to a different parent device without manual intervention.
- Unable to properly log NO2 value when computing for 03
- This has been corrected to ensure the NO2 values are properly captured and stored whenever O3 levels are derived, improving traceability and data quality for air pollutant reporting
Improvements
Enhancements and improvements made:
- Additional labels in gas parameters tab
- The gas parameters tab in the cloud service UI has been enhanced with additional labeling to provide better clarity and context for users. This tab displays key measurements and settings related to the various gases being monitored, such as O3, NO2, CO2, PM2.5, and SO2.
- Added the option to change concentration in gas parameters (ppb or ug/m3)
- The cloud service now provides users the flexibility to view gas concentration data in either parts per billion (ppb) or micrograms per cubic meter (ug/m3). This option can be selected within the gas parameters section of the user interface.
- Adding NO, H2S, and vibration sensors to the report and push API
- The cloud service has been enhanced to support data ingestion and reporting from nitrogen oxide (NO), hydrogen sulfide (H2S), and vibration sensors. This expansion allows customers to monitor a wider range of environmental conditions and potential pollutants.
- Gas parameter page
- The gas parameter page within the cloud service's user interface has been significantly improved to display a richer set of sensor data, including Alphasense-specific parameters and atmospheric pressure readings.
For any questions or concerns, kindly let us know.