Skip to content

Proxmox refactor to use UPTIME sensor#169704

Open
erwindouna wants to merge 1 commit intohome-assistant:devfrom
erwindouna:proxmox-refactor-uptime
Open

Proxmox refactor to use UPTIME sensor#169704
erwindouna wants to merge 1 commit intohome-assistant:devfrom
erwindouna:proxmox-refactor-uptime

Conversation

@erwindouna
Copy link
Copy Markdown
Member

@erwindouna erwindouna commented May 3, 2026

Breaking change

Changes the Uptime sensor from duration in seconds to a timestamp uptime sensor. This is done for the node, VMs and containers.

Proposed change

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

  • I understand the code I am submitting and can explain how it works.
  • 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.
  • Any generated code has been carefully reviewed for correctness and compliance with project standards.

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 diff between library versions and ideally a link to the changelog/release notes is added to the PR description.

To help with the load of incoming pull requests:

@home-assistant
Copy link
Copy Markdown
Contributor

home-assistant Bot commented May 3, 2026

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

Code owner commands

Code owners of proxmoxve can trigger bot actions by commenting:

  • @home-assistant close Closes the pull request.
  • @home-assistant mark-draft Mark the pull request as draft.
  • @home-assistant ready-for-review Remove the draft status from the pull request.
  • @home-assistant rename Awesome new title Renames the pull request.
  • @home-assistant reopen Reopen the pull request.
  • @home-assistant unassign proxmoxve Removes the current integration label and assignees on the pull request, add the integration domain after the command.
  • @home-assistant update-branch Update the pull request branch with the base branch.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component, problem in config, problem in device, feature-request) to the pull request.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component, problem in config, problem in device, feature-request) on the pull request.

@erwindouna erwindouna marked this pull request as ready for review May 3, 2026 20:49
@erwindouna erwindouna requested a review from CoMPaTech as a code owner May 3, 2026 20:49
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Refactors the Proxmox VE integration’s uptime sensors to use Home Assistant’s SensorDeviceClass.UPTIME semantics (boot timestamp) instead of reporting a numeric duration, and updates tests/snapshots accordingly.

Changes:

  • Convert node/VM/container uptime sensors from DURATION (seconds/hours) to UPTIME (datetime boot timestamp).
  • Update sensor entity typing to allow datetime native values for VM/container uptime.
  • Stabilize snapshot testing by freezing time and updating the stored snapshots.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File Description
homeassistant/components/proxmoxve/sensor.py Changes uptime sensors to return a boot timestamp (datetime) and sets device_class=UPTIME.
tests/components/proxmoxve/test_sensor.py Freezes time to make uptime-derived timestamps deterministic in snapshots.
tests/components/proxmoxve/snapshots/test_sensor.ambr Updates expected entity registry/state snapshots for new uptime behavior (timestamp states, no units/state_class).

Comment on lines 128 to 140
ProxmoxNodeSensorEntityDescription(
key="node_uptime",
translation_key="node_uptime",
value_fn=lambda data: data.node["uptime"],
device_class=SensorDeviceClass.DURATION,
native_unit_of_measurement=UnitOfTime.SECONDS,
suggested_unit_of_measurement=UnitOfTime.HOURS,
value_fn=(
lambda data: (
(dt_util.utcnow() - timedelta(seconds=data.node["uptime"]))
if data.node["uptime"] is not None
else None
)
),
device_class=SensorDeviceClass.UPTIME,
entity_category=EntityCategory.DIAGNOSTIC,
state_class=SensorStateClass.MEASUREMENT,
),
Comment on lines 128 to 140
ProxmoxNodeSensorEntityDescription(
key="node_uptime",
translation_key="node_uptime",
value_fn=lambda data: data.node["uptime"],
device_class=SensorDeviceClass.DURATION,
native_unit_of_measurement=UnitOfTime.SECONDS,
suggested_unit_of_measurement=UnitOfTime.HOURS,
value_fn=(
lambda data: (
(dt_util.utcnow() - timedelta(seconds=data.node["uptime"]))
if data.node["uptime"] is not None
else None
)
),
device_class=SensorDeviceClass.UPTIME,
entity_category=EntityCategory.DIAGNOSTIC,
state_class=SensorStateClass.MEASUREMENT,
),
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.

3 participants