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 new QNAP QSW uptime timestamp sensor #122589

Merged
merged 16 commits into from
Oct 21, 2024

Conversation

Noltari
Copy link
Contributor

@Noltari Noltari commented Jul 25, 2024

Breaking change

QNAP QSW uptime seconds sensor has been replaced by an uptime timestamp sensor.

Proposed change

Add new QNAP QSW uptime timestamp sensor.

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 Ruff (ruff format 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.

To help with the load of incoming pull requests:

Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
@Noltari Noltari changed the title Add new QNAP QSW uptime timestamp sensor. Add new QNAP QSW uptime timestamp sensor Jul 25, 2024
@joostlek
Copy link
Member

Why do we have 2 entities for this now? I prefer the date time one more since it doesn't write state every update

Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
Noltari added 3 commits July 25, 2024 17:16
Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
Comment on lines 53 to 58
"uptime": {
"name": "Uptime"
},
"uptime_timestamp": {
"name": "Uptime timestamp"
}
Copy link
Member

Choose a reason for hiding this comment

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

Hmm, something in me things uptime is viable for both, but I'm not sure what is best here

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I'm happy with both, so I can change it to use uptime for both if you prefer that.

Copy link
Member

Choose a reason for hiding this comment

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

The only downside is that they'll both be called uptime so one will be appended _2

Copy link
Contributor Author

Choose a reason for hiding this comment

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

The only downside is that they'll both be called uptime so one will be appended _2

Ah, you're right, and we won't be able to tell them appart for uptime_seconds_deprecated...

Copy link
Member

Choose a reason for hiding this comment

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

I've asked for a second opinion on this.

But also keep in mind, people could've renamed both the name and entity id, so it could but even be recognizable

Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
@Noltari
Copy link
Contributor Author

Noltari commented Aug 7, 2024

@joostlek deprecation warning is now only shown if used on automations/scripts.
8de5098

@frenck frenck added the smash Indicator this PR is close to finish for merging or closing label Aug 8, 2024
The Unique ID was accidentally changed on 3caffa4:
- Before 3caffa4: the unique ID ends with "_uptime".
- After 3caffa4: the unique ID ends with "_uptime_seconds".

Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
@Noltari Noltari requested a review from joostlek August 11, 2024 16:56
@Noltari
Copy link
Contributor Author

Noltari commented Aug 14, 2024

@joostlek joostlek merged commit 4306b0c into home-assistant:dev Oct 21, 2024
32 checks passed
@Noltari Noltari deleted the qnap-qsw-uptime-timestamp branch October 21, 2024 15:14
@Noltari
Copy link
Contributor Author

Noltari commented Oct 21, 2024

Thanks @joostlek!

@github-actions github-actions bot locked and limited conversation to collaborators Oct 22, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
by-code-owner cla-signed has-tests integration: qnap_qsw new-feature Quality Scale: No score small-pr PRs with less than 30 lines. smash Indicator this PR is close to finish for merging or closing
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants