Skip to content

Use config entry id for unique id if serial number is missing#34154

Merged
balloob merged 8 commits intohome-assistant:devfrom
bdraco:nut_uniqueness
Apr 16, 2020
Merged

Use config entry id for unique id if serial number is missing#34154
balloob merged 8 commits intohome-assistant:devfrom
bdraco:nut_uniqueness

Conversation

@bdraco
Copy link
Copy Markdown
Member

@bdraco bdraco commented Apr 13, 2020

Proposed change

If the device is missing a serial number
we fallback config entry id as
the sensors will not show up on the
integrations page which was confusing.

This turned out to be much more common
then expected. I don't love this solution
and I'd be much happier if there is a better way.

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

Example entry for configuration.yaml:

# Example configuration.yaml

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

The integration reached or maintains the following Integration Quality Scale:

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

Comment thread homeassistant/components/nut/__init__.py Outdated
@bdraco bdraco changed the title Add a fallback unique id for nut Use mac address for nut unique id if serial number is missing Apr 16, 2020
Comment thread homeassistant/components/nut/__init__.py Outdated
bdraco added 5 commits April 16, 2020 01:29
If the device is missing a serial number
we fallback to the host/port/alias as
the sensors will not show up on the
integrations page which was confusing.
@bdraco bdraco changed the title Use mac address for nut unique id if serial number is missing Use config entry id for unique id if serial number is missing Apr 16, 2020
@bdraco bdraco added this to the 0.108.6 milestone Apr 16, 2020
@bdraco
Copy link
Copy Markdown
Member Author

bdraco commented Apr 16, 2020

For 0.108.6 backport, only __init__.py needed. Tests can be skipped

@balloob balloob merged commit abae48c into home-assistant:dev Apr 16, 2020
@balloob balloob mentioned this pull request Apr 17, 2020
@lock lock Bot locked and limited conversation to collaborators Apr 19, 2020
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.

NUT integration introduced in 0.108 only allows adding a single UPS host NUT does not create UPS sensors under integration to QNAP NAS

5 participants