Skip to content

Add unit µA to eletric current#3025

Open
Phunkafizer wants to merge 1 commit intohome-assistant:masterfrom
Phunkafizer:addmicroamps
Open

Add unit µA to eletric current#3025
Phunkafizer wants to merge 1 commit intohome-assistant:masterfrom
Phunkafizer:addmicroamps

Conversation

@Phunkafizer
Copy link
Copy Markdown

@Phunkafizer Phunkafizer commented Apr 1, 2026

Proposed change

Type of change

  • Document existing features within Home Assistant
  • Document new or changing features for which there is an existing pull request elsewhere
  • Spelling or grammatical corrections, or rewording for improved clarity
  • Changes to the backend of this documentation
  • Remove stale or deprecated documentation

Checklist

  • I have read and followed the documentation guidelines.
  • I have verified that my changes render correctly in the documentation.

Additional information

Summary by CodeRabbit

  • Documentation
    • Updated current measurement device class documentation to include microamps (µA) as a supported unit alongside amperes and milliamperes.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Apr 1, 2026

📝 Walkthrough

Walkthrough

Documentation updates to the CURRENT device class in both number and sensor entity docs, adding µA (microamps) to the list of supported units alongside existing A and mA units.

Changes

Cohort / File(s) Summary
Current Device Class Documentation
docs/core/entity/number.md, docs/core/entity/sensor.md
Added µA to the supported units list for the CURRENT device class in both number and sensor entity documentation.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title 'Add unit µA to eletric current' is directly related to the main change in the pull request, which adds microamps (µA) support to electric current documentation.
Description check ✅ Passed The description follows the template structure with the type of change selected and a link to the related pull request provided, though the 'Proposed change' section and 'I have verified that my changes render correctly' checklist item are incomplete.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@docs/core/entity/number.md`:
- Line 44: The docs entry for NumberDeviceClass.CURRENT incorrectly lists the
microamp unit (µA); edit docs/core/entity/number.md to remove "µA" from the
CURRENT device class supported units (leave only "A, mA"), and search for any
other occurrences of NumberDeviceClass.CURRENT in the same file to remove µA
mentions so docs match Home Assistant Core implementation and the closed issue
status.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 2dfd1dc7-41f0-4024-9bb4-e8b5900962cc

📥 Commits

Reviewing files that changed from the base of the PR and between e36851d and 735a30f.

📒 Files selected for processing (2)
  • docs/core/entity/number.md
  • docs/core/entity/sensor.md

| `NumberDeviceClass.CO` | ppb, ppm, µg/m³, mg/m³ | Concentration of carbon monoxide.
| `NumberDeviceClass.CONDUCTIVITY` | S/cm, mS/cm, µS/cm | Conductivity
| `NumberDeviceClass.CURRENT` | A, mA | Current
| `NumberDeviceClass.CURRENT` | A, mA, µA | Current
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🌐 Web query:

Does Home Assistant Core support microamps (µA) as a unit for the CURRENT device class in version implemented by PR 166786?

💡 Result:

No, Home Assistant Core does not support microamps (µA) as a unit for the CURRENT device class in the version implemented by PR 166786. No such PR exists; searches returned no results for PR 166786 in the home-assistant/core repository. Official documentation lists only A and mA as supported units for current. A feature request (issue #161400) to add µA was closed as "not planned" in January 2026.

Citations:


Remove µA from CURRENT device class—not supported by Home Assistant Core.

Home Assistant Core does not support microamps (µA) as a unit for the CURRENT device class. Official documentation lists only A and mA as supported units. A feature request (issue #161400) to add µA support was closed as "not planned" in January 2026.

The documentation change contradicts the actual implementation and will mislead users. Remove µA from the supported units list.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@docs/core/entity/number.md` at line 44, The docs entry for
NumberDeviceClass.CURRENT incorrectly lists the microamp unit (µA); edit
docs/core/entity/number.md to remove "µA" from the CURRENT device class
supported units (leave only "A, mA"), and search for any other occurrences of
NumberDeviceClass.CURRENT in the same file to remove µA mentions so docs match
Home Assistant Core implementation and the closed issue status.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants