Add base entity for Dexcom

[joostlek]

Proposed change

Introduce base entity for Dexcom to allow adding device info in follow up PR

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:

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 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:

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

To help with the load of incoming pull requests:

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

[home-assistant]

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

Code owner commands

Code owners of dexcom 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 dexcom Removes the current integration label and assignees on the pull request, add the integration domain after the command.

[gagebenne]

Makes sense, thanks! I've been also curious about making it a Home Assistant device with two associated entity sensors. I'm going to run this branch as a custom component tonight to check your changes out.

[joostlek]

Makes sense, thanks! I've been also curious about making it a Home Assistant device with two associated entity sensors. I'm going to run this branch as a custom component tonight to check your changes out.

Haha that was my next PR going to be after this one got merged :).

Since I don't have this device or integration (as I am just trying to convert every integration), can you maybe take a look at the rest of the info for a device (manufacturer/model/sw version/hw version)?

[gagebenne]

Nothing along those lines unfortunately with the API Dexcom uses 😕. The lack of unique identifier is why I avoided devices originally.

Username is about the most unique we can get.

[joostlek]

We can do entry_id, that gives a unique identifier per entry :)

[gagebenne]

Ran with latest stable and pre-release pydexcom and branch worked. Thanks!

[edenhaus]

Thanks @joostlek 👍