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

Allow Devices to be added to Power panels #10798

New Issue
Closed
opened 2025-12-29 21:36:03 +01:00 by adam · 2 comments
adam commented 2025-12-29 21:36:03 +01:00
Owner
Copy Link

Originally created by @Daniel-Dietz on GitHub (Feb 22, 2025).

NetBox version

v4.2.3

Feature type

New functionality

Proposed functionality

Allow Devices to be added to Power panels.
Many devices can be added to Power Panels via a DIN-Rail (https://en.wikipedia.org/wiki/DIN_rail) mount and it is currently not possible to add them to Netbox. Examples are KNX, Power-, Energy Metering or Fuse Monitoring ...

Use case

This would allow a unified approach to documenting modern energy infrastructures where many components are ethernet connected. Currently a duplication of the Power panel must be created as a Cabinet or Rack to allow the documentation of one physical location

Database changes

No response

External dependencies

No response

Originally created by @Daniel-Dietz on GitHub (Feb 22, 2025). ### NetBox version v4.2.3 ### Feature type New functionality ### Proposed functionality Allow Devices to be added to Power panels. Many devices can be added to Power Panels via a DIN-Rail (https://en.wikipedia.org/wiki/DIN_rail) mount and it is currently not possible to add them to Netbox. Examples are KNX, Power-, Energy Metering or Fuse Monitoring ... ### Use case This would allow a unified approach to documenting modern energy infrastructures where many components are ethernet connected. Currently a duplication of the Power panel must be created as a Cabinet or Rack to allow the documentation of one physical location ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featureplugin candidate labels 2025-12-29 21:36:03 +01:00
adam closed this issue 2025-12-29 21:36:03 +01:00
adam commented 2025-12-29 21:36:04 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 6, 2025):

Thank you for submitting your idea. Although the proposed functionality falls outside the current scope of NetBox's core feature set, it may make a good candidate for a NetBox plugin, and we encourage you to pursue its development and a standalone project.

@jeremystretch commented on GitHub (Mar 6, 2025): Thank you for submitting your idea. Although the proposed functionality falls outside the current scope of NetBox's core feature set, it may make a good candidate for a [NetBox plugin](https://netbox.readthedocs.io/en/stable/plugins/), and we encourage you to pursue its development and a standalone project.
adam commented 2025-12-29 21:36:04 +01:00
Author
Owner
Copy Link

@Daniel-Dietz commented on GitHub (Mar 6, 2025):

Don't get me wrong but what is the NetBox's core feature set at the moment?

If the following description is still correct:
"What is NetBox?
NetBox is the source of truth for everything on your network, from physical components like power systems and cabling to virtual assets like IP addresses and VLANs. Network automation and observability tools depend on NetBox’s authoritative data to roll out configurations, monitor changes, and accelerate operations across the enterprise."

.., this feature would pretty much match the entirety of the description. Furthermore it removes a need for duplicated, error prone work that can not be used for automation.

I get the plugin route for a many features and functions but this as it pertains to the core of how to document a system this should not be pushed into one,

@Daniel-Dietz commented on GitHub (Mar 6, 2025): Don't get me wrong but what is the NetBox's core feature set at the moment? If the following description is still correct: "What is NetBox? NetBox is the source of truth for everything on your network, from physical components like power systems and cabling to virtual assets like IP addresses and VLANs. Network automation and observability tools depend on NetBox’s authoritative data to roll out configurations, monitor changes, and accelerate operations across the enterprise." .., this feature would pretty much match the entirety of the description. Furthermore it removes a need for duplicated, error prone work that can not be used for automation. I get the plugin route for a many features and functions but this as it pertains to the core of how to document a system this should not be pushed into one,
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 plugin candidate 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#10798
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?