Add concentration level sensor to Aranet #137291

parkerbxyz · 2025-02-04T06:35:59Z

Proposed change

Adds a threshold level sensor so you can see the threshold levels from the Aranet4 and AranetRn+ in Home Assistant.

Type of change

Dependency upgrade
Bugfix (non-breaking change which fixes an issue)
New integration (thank you!)
New feature (which adds functionality to an existing integration)
Deprecation (breaking change to happen in the future)
Breaking change (fix/feature causing existing functionality to break)
Code quality improvements to existing code or addition of tests

Additional information

This PR fixes or closes issue: fixes #
This PR is related to issue:
Link to documentation pull request:
Link to developer documentation pull request:
Link to frontend pull request:

Checklist

The code change is tested and works locally.
Local tests pass. Your PR cannot be merged unless tests pass
There is no commented out code in this PR.
I have followed the development checklist
I have followed the perfect PR recommendations
The code has been formatted using Ruff (ruff format homeassistant tests)
Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

The manifest file has all fields filled out correctly.
Updated and included derived files by running: python3 -m script.hassfest.
New or updated dependencies have been added to requirements_all.txt.
Updated by running python3 -m script.gen_requirements_all.
For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.

To help with the load of incoming pull requests:

I have reviewed two other open pull requests in this repository.

home-assistant · 2025-02-04T06:36:08Z

Hey there @aschmitz, @thecode, @Anrijs, mind taking a look at this pull request as it has been labeled with an integration (aranet) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of aranet can trigger bot actions by commenting:

@home-assistant close Closes the pull request.
@home-assistant rename Awesome new title Renames the pull request.
@home-assistant reopen Reopen the pull request.
@home-assistant unassign aranet Removes the current integration label and assignees on the pull request, add the integration domain after the command.
@home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the pull request.
@home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the pull request.

homeassistant/components/aranet/sensor.py

parkerbxyz · 2025-02-06T05:36:00Z

tests/components/aranet/test_sensor.py

+    status_sensor_attrs = status_sensor.attributes
+    assert status_sensor.state == "GREEN"
+    assert status_sensor_attrs[ATTR_FRIENDLY_NAME] == "Aranet4 12345 Threshold Level"
+    assert set(status_sensor_attrs[ATTR_OPTIONS]) == {"ERROR", "GREEN", "YELLOW", "RED"}


I'd love to map these to more useful values. For example, the CO₂ could have the following mappings:

GREEN → Good

YELLOW → Average

RED → Unhealthy

For the Radon sensor:

GREEN → Normal

YELLOW → Elevated

RED → Unhealthy

I'm just not sure if that would be considered in scope for this integration.

From end-user viewpoint, it would make more sense to map them to more understandable names

In that case, I'll work on implementing this. Thanks for the quick feedback!

OTOH, isn't the user expecting to see "Red/Yellow/Green", based on the official app and device screen?

They are just colors in the app on the device. If you look in the device settings or the manuals/documentation, it explains what those values translate to, which is where I got these values from. I'm still using Aranet's terminology.

Personally, I would view the descriptive (Good/Average/Unhealthy) terms as more useful on a dashboard, so that would be my preference. I understand that they are not necessarily as obvious when looking at the device, though, so if there's a consensus in another direction that's fine too.

My only concern would be that they would possibly require some care when handling the translation strings (especially because this meaning of "average" isn't necessarily "the mean of some numbers"), but I'd find it more useful to see "Unhealthy" than "Red" on a HA card.

Personally, I would view the descriptive (Good/Average/Unhealthy) terms as more useful on a dashboard, so that would be my preference.

Certainly, a dashboard is where I would want to use those values, too. That was my motivation. However, I'm also open to sticking to the colors.

My only concern would be that they would possibly require some care when handling the translation strings (especially because this meaning of "average" isn't necessarily "the mean of some numbers

This is a good call-out. Perhaps if we do use these more human-friendly values, we should stick with one set (i.e., normal, elevated, and unhealthy) rather than having different values per device type.

homeassistant/components/aranet/sensor.py

abmantis · 2025-02-06T22:03:10Z

homeassistant/components/aranet/sensor.py

@@ -161,7 +166,11 @@ def sensor_update_to_bluetooth_data_update(
        val = getattr(adv.readings, key)
        if val == -1:
            continue
-        val *= desc.scale
+        val = (


Instead of this, can we set the translation_key add add translations for the states?
Also, isn't the user expecting to see "Red/Yellow/Green", based on the official app and device screen?

I agree, I think we should represent it same as the app does, also for the translations (was actually waiting to have time to search for example for the translations later, thanks @abmantis)

Sure, I'll add translations for the states instead.

Also, isn't the user expecting to see "Red/Yellow/Green", based on the official app and device screen?

I'm not sure if this would necessarily be the expectation. See #137291 (comment).

I'm not sure if I did the translations correctly, and I haven't figured out how to test the translations programmatically. Could someone take a look at the latest changes and let me know if you have any further suggestions?

home-assistant · 2025-02-06T22:03:21Z

Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍

Learn more about our pull request process.

Add threshold level sensor description to Aranet component

aee85a8

home-assistant bot added cla-signed integration: aranet new-feature small-pr PRs with less than 30 lines. labels Feb 4, 2025

home-assistant bot assigned thecode Feb 4, 2025

home-assistant bot added the Quality Scale: No score label Feb 4, 2025

parkerbxyz added 4 commits February 6, 2025 02:48

Use Color enum for status options

73226ba

Add threshold level sensor tests for Aranet components

1a7a651

Rename threshold_level key to status

209cd6b

Update test to expect 7 sensors instead of 6

16f7800

parkerbxyz commented Feb 6, 2025

View reviewed changes

homeassistant/components/aranet/sensor.py Outdated Show resolved Hide resolved

Merge branch 'dev' into aranet-threshold-level

c522db9

parkerbxyz marked this pull request as ready for review February 6, 2025 05:23

parkerbxyz requested a review from thecode as a code owner February 6, 2025 05:23

parkerbxyz commented Feb 6, 2025

View reviewed changes

parkerbxyz marked this pull request as draft February 6, 2025 06:35

parkerbxyz added 2 commits February 6, 2025 08:27

Map sensor status to more human-friendly strings

c272a59

Rename threshold_level key to concentration_status

942ba37

parkerbxyz marked this pull request as ready for review February 6, 2025 08:46

Update docstring for function

cbb072a

parkerbxyz changed the title ~~Add threshold level sensor to Aranet~~ Add concentration status sensor to Aranet Feb 6, 2025

Simplify get_friendly_status()

cd71145

parkerbxyz commented Feb 6, 2025

View reviewed changes

homeassistant/components/aranet/sensor.py Outdated Show resolved Hide resolved

Rename concentration_status to concentration_level

5ef98be

parkerbxyz changed the title ~~Add concentration status sensor to Aranet~~ Add concentration level sensor to Aranet Feb 6, 2025

Rename concentration_status to concentration_level in sensor tests

92d8b1c

abmantis requested changes Feb 6, 2025

View reviewed changes

home-assistant bot marked this pull request as draft February 6, 2025 22:03

parkerbxyz added 2 commits February 7, 2025 07:21

Refactor concentration level handling and tests

ad7f512

Normalize concentration level status values to lowercase

67a33c8

parkerbxyz marked this pull request as ready for review February 7, 2025 07:34

home-assistant bot requested a review from abmantis February 7, 2025 07:34

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Add concentration level sensor to Aranet #137291

Add concentration level sensor to Aranet #137291

parkerbxyz commented Feb 4, 2025 •

edited

Loading

home-assistant bot commented Feb 4, 2025

parkerbxyz Feb 6, 2025 •

edited

Loading

Anrijs Feb 6, 2025

parkerbxyz Feb 6, 2025

abmantis Feb 6, 2025

parkerbxyz Feb 7, 2025

aschmitz Feb 7, 2025

parkerbxyz Feb 7, 2025

abmantis Feb 6, 2025

thecode Feb 6, 2025

parkerbxyz Feb 7, 2025

parkerbxyz Feb 7, 2025 •

edited

Loading

home-assistant bot commented Feb 6, 2025

Add concentration level sensor to Aranet #137291

Are you sure you want to change the base?

Add concentration level sensor to Aranet #137291

Conversation

parkerbxyz commented Feb 4, 2025 • edited Loading

Proposed change

Type of change

Additional information

Checklist

home-assistant bot commented Feb 4, 2025

parkerbxyz Feb 6, 2025 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

parkerbxyz Feb 7, 2025 • edited Loading

Choose a reason for hiding this comment

home-assistant bot commented Feb 6, 2025

parkerbxyz commented Feb 4, 2025 •

edited

Loading

parkerbxyz Feb 6, 2025 •

edited

Loading

parkerbxyz Feb 7, 2025 •

edited

Loading