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

Improvement of power tracking in power devices #10392

New Issue
Closed
opened 2025-12-29 21:30:49 +01:00 by adam · 1 comment
adam commented 2025-12-29 21:30:49 +01:00
Owner
Copy Link

Originally created by @BYT3M3 on GitHub (Oct 22, 2024).

NetBox version

v3.7.4

Feature type

Change to existing functionality

Triage priority

N/A

Proposed functionality

Currently, there is no distinction between power ports for electrical loads and power ports for power supplies and power distribution units. And power outlets have no rated maximum power draw.

Say you have a 115V AC device and a 240V AC power feed and you need to add a transformer in between. The transformer can be rated for 4000 VA, but your load may only require 1000W. In this case, you'd greatly overestimate your power consumption.

Or more commonly: say you have a switchable PDU that is rated at e.g. 32A 240V, with 16 outlets that can each handle a maximum of 16A. It would be great to keep track of how much capacity of that PDU you're using up by plugging several devices into it. Also: it would be nice to have only the power draw from the devices actually plugged into the PDU to count towards the Power Feed utilization.

Use case

This would benefit every NetBox user, as every user needs to distribute power beyond their power feeds and they need to monitor the utilization at every point where power is split from one socket-plug connection to other socket-plug connections. There's a lot to be said for adding limits to the level of nesting, but one or two levels beyond the power feed are necessary for for example power feed->pdu->multiple loads or power feed->UPS->load or power feed -> UPS -> PDU -> multiple loads.

Database changes

This could function through an extension of the Power Port fields or by making a new Component type designated for Power Ports for power redistribution. The Power Outlet would need a maximum power field (or ideally voltage and maximum current). I think it would require a little more in depth discussion as to how the database needs to be extended/changed. I'm very open to that discussion.

External dependencies

No response

Originally created by @BYT3M3 on GitHub (Oct 22, 2024). ### NetBox version v3.7.4 ### Feature type Change to existing functionality ### Triage priority N/A ### Proposed functionality Currently, there is no distinction between power ports for electrical loads and power ports for power supplies and power distribution units. And power outlets have no rated maximum power draw. Say you have a 115V AC device and a 240V AC power feed and you need to add a transformer in between. The transformer can be rated for 4000 VA, but your load may only require 1000W. In this case, you'd greatly overestimate your power consumption. Or more commonly: say you have a switchable PDU that is rated at e.g. 32A 240V, with 16 outlets that can each handle a maximum of 16A. It would be great to keep track of how much capacity of that PDU you're using up by plugging several devices into it. Also: it would be nice to have only the power draw from the devices actually plugged into the PDU to count towards the Power Feed utilization. ### Use case This would benefit every NetBox user, as every user needs to distribute power beyond their power feeds and they need to monitor the utilization at every point where power is split from one socket-plug connection to other socket-plug connections. There's a lot to be said for adding limits to the level of nesting, but one or two levels beyond the power feed are necessary for for example power feed->pdu->multiple loads or power feed->UPS->load or power feed -> UPS -> PDU -> multiple loads. ### Database changes This could function through an extension of the Power Port fields or by making a new Component type designated for Power Ports for power redistribution. The Power Outlet would need a maximum power field (or ideally voltage and maximum current). I think it would require a little more in depth discussion as to how the database needs to be extended/changed. I'm very open to that discussion. ### External dependencies _No response_
adam added the type: featurenetbox labels 2025-12-29 21:30:49 +01:00
adam closed this issue 2025-12-29 21:30:49 +01:00
adam commented 2025-12-29 21:30:51 +01:00
Author
Owner
Copy Link

@BYT3M3 commented on GitHub (Oct 22, 2024):

I see now that I should first have opened a discussion rather than an issue. Might raise as feature request later.

@BYT3M3 commented on GitHub (Oct 22, 2024): I see now that I should first have opened a discussion rather than an issue. Might raise as feature request later.
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 netbox 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#10392
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?