starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Increase resolution of maximum draw and allocated draw to 3 decimal places e.g 0.001 W #5712

New Issue
Closed
opened 2025-12-29 19:31:42 +01:00 by adam · 3 comments
adam commented 2025-12-29 19:31:42 +01:00
Owner
Copy Link

Originally created by @ypid on GitHub (Nov 25, 2021).

NetBox version

v3.1-beta1

Feature type

Change to existing functionality

Proposed functionality

Maximum draw and allocated draw of power ports (device type, device) should support at least be 1 decimal place e.g 0.1 W. If in doubt, lets increase to 3 decimal place which is the resolution of lab power meters. I run into this limit of 1 W resolution multiple times.

This is what I am proposing in code:

maximum_draw = models.DecimalField(
    max_digits=8,
    decimal_places=3,
    blank=True,
    null=True,
    help_text="Maximum power draw (watts)"
)

Use case

Manufactures and reviews often give power draw with 0.1 W resolution and accuracy. For example HPE OfficeConnect 1820 Switch Series QuickSpecs.pdf.

Database changes

Yes.

External dependencies

No

Originally created by @ypid on GitHub (Nov 25, 2021). ### NetBox version v3.1-beta1 ### Feature type Change to existing functionality ### Proposed functionality Maximum draw and allocated draw of power ports (device type, device) should support at least be 1 decimal place e.g 0.1 W. If in doubt, lets increase to 3 decimal place which is the resolution of lab power meters. I run into this limit of 1 W resolution multiple times. This is what I am proposing in code: ```Python maximum_draw = models.DecimalField( max_digits=8, decimal_places=3, blank=True, null=True, help_text="Maximum power draw (watts)" ) ``` ### Use case Manufactures and reviews often give power draw with 0.1 W resolution and accuracy. For example [HPE OfficeConnect 1820 Switch Series QuickSpecs.pdf](https://www.dsd-dataservice.de/media/products/HPE%201820.pdf). ### Database changes Yes. ### External dependencies No
adam added the type: feature label 2025-12-29 19:31:42 +01:00
adam closed this issue 2025-12-29 19:31:42 +01:00
adam commented 2025-12-29 19:31:43 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 26, 2021):

Manufactures and reviews often give power draw with 0.1 W resolution and accuracy.

Okay, but what's your use case for this degree of granularity? This seems unnecessary to me. One Watt is well within the the margin of error for most power monitoring systems.

@jeremystretch commented on GitHub (Nov 26, 2021): > Manufactures and reviews often give power draw with 0.1 W resolution and accuracy. Okay, but what's _your_ use case for this degree of granularity? This seems unnecessary to me. One Watt is well within the the margin of error for most power monitoring systems.
adam commented 2025-12-29 19:31:43 +01:00
Author
Owner
Copy Link

@ypid commented on GitHub (Nov 26, 2021):

You are right, I missed really giving a use case above. With that sentence, I just wanted to say that when a manufacture gives me the maximum draw in 0.1 W resolution, than I would like that being represented in my device type. I don’t like rounding just because of technical limitations. My use case is for example single board computers that have a very low power consumption. There it makes a difference if we are talking about 0.7 W or 1.4 W. And for tuning devices to be power efficient. Maybe you found out that disabling 2.4 GHz on an AP saves 0.5 W of power and you would like to track that in NetBox. There are also places were you don’t have plenty of power, like in off-grid/RV were people still want to run networks.

@ypid commented on GitHub (Nov 26, 2021): You are right, I missed really giving a use case above. With that sentence, I just wanted to say that when a manufacture gives me the maximum draw in 0.1 W resolution, than I would like that being represented in my device type. I don’t like rounding just because of technical limitations. My use case is for example single board computers that have a very low power consumption. There it makes a difference if we are talking about 0.7 W or 1.4 W. And for tuning devices to be power efficient. Maybe you found out that disabling 2.4 GHz on an AP saves 0.5 W of power and you would like to track that in NetBox. There are also places were you don’t have plenty of power, like in off-grid/RV were people still want to run networks.
adam commented 2025-12-29 19:31:43 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 15, 2021):

I'm going to decline this as I don't think it makes sense to support fractional Watts. As I mentioned, that degree of granularity just isn't relevant for NetBox's intended use.

@jeremystretch commented on GitHub (Dec 15, 2021): I'm going to decline this as I don't think it makes sense to support fractional Watts. As I mentioned, that degree of granularity just isn't relevant for NetBox's intended use.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label type: feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#5712
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?