Skip to content
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

Add support to a different unit of measurement(mmol/L) on Nightscout #54898

Conversation

mateusrevoredo
Copy link

@mateusrevoredo mateusrevoredo commented Aug 19, 2021

Breaking change

Proposed change

The existing Nightscout integration only supports one unit of measurement for blood glucose values(mg/dL). Most countries in Europe and Oceania use a different unit of measurement(mmol/L).

This PR introduces an option to chose which unit of measurement the user wants for the Nightscout integration.

nightscout_configuration_01
nightscout_configuration_02

I worked on this feature, but during the creation of the PR I noticed that someone else attempted to do the same thing a while ago on #41382 but it ended up being automatically closed due to inactivity. My changes are similar to the ones proposed on the other PR, but still slightly different.

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)
  • Breaking change (fix/feature causing existing functionality to break)
  • Code quality improvements to existing code or addition of tests

Additional information

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
  • The code has been formatted using Black (black --fast homeassistant tests)
  • Tests have been added to verify that the new code works.

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

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.
  • Untested files have been added to .coveragerc.

The integration reached or maintains the following Integration Quality Scale:

  • No score or internal
  • 🥈 Silver
  • 🥇 Gold
  • 🏆 Platinum

To help with the load of incoming pull requests:

@probot-home-assistant
Copy link

Hey there @marciogranzotto, mind taking a look at this pull request as it has been labeled with an integration (nightscout) you are listed as a code owner for? Thanks!
(message by CodeOwnersMention)

Comment on lines +107 to +110
def _get_bgl(self, value) -> float:
if self._unit_of_measurement == MMOL_L:
return round((value / MMOL_CONVERSION_FACTOR), 1)
return value
Copy link
Member

@frenck frenck Aug 21, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We generally don't want these types of conversions or calculations in Home Assistant.

The reasoning is simple: Before we know it, we will have tons of integrations offering all kinds of conversions. If anything, such a problem needs to be solved globally and not in a case-by-case situation.

So, at this point, we generally hold on to: Provide the uom the device natively provides.

So IMHO, we should not add this.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @frenck,

Unfortunately, the API of this integration only provides data in this specific unit of measure.
It does have an endpoint indicating if the user would like to have the values displayed in a different UOM, but it does not handle the conversion itself. Changing the code on the integration would be much harder, as it is an(although not FDA approved) medical application, so the changes would be more drastic.

I understand your point. Trying to support all different types of UOMs can get overwhelming and out of control, but all the applications that I know of that integrate with Nightscout, provide a way to convert the values since there are two different UOMs used worldwide for this type of data.

I've seen some requests on this repo, on the add-on repo, and also on the forums. That's why I thought it would be a good idea to implement the feature. Links below for reference:

With that said, do you believe those would be legit reasons for the change?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@frenck maybe is best to add this conversion on the py_nightscout lib?

@github-actions
Copy link

There hasn't been any activity on this pull request recently. This pull request has been automatically marked as stale because of that and will be closed if no further activity occurs within 7 days.
Thank you for your contributions.

@github-actions github-actions bot added the stale label Sep 21, 2021
@github-actions github-actions bot closed this Sep 28, 2021
@github-actions github-actions bot locked and limited conversation to collaborators Sep 30, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants