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

Add support for the Ubiquiti SmartPower connector type #6389

New Issue
Closed
opened 2025-12-29 19:40:08 +01:00 by adam · 2 comments
adam commented 2025-12-29 19:40:08 +01:00
Owner
Copy Link

Originally created by @WarriorXK on GitHub (Apr 21, 2022).

Originally assigned to: @WarriorXK on GitHub.

NetBox version

v3.2.1

Feature type

Change to existing functionality

Proposed functionality

Adding the option "Ubiquiti SmartPower" to the power connect type

Use case

It would allow users to be more accurate regarding their power layout with Ubiquiti gear.

Database changes

None

External dependencies

None

Originally created by @WarriorXK on GitHub (Apr 21, 2022). Originally assigned to: @WarriorXK on GitHub. ### NetBox version v3.2.1 ### Feature type Change to existing functionality ### Proposed functionality Adding the option "Ubiquiti SmartPower" to the power connect type ### Use case It would allow users to be more accurate regarding their power layout with Ubiquiti gear. ### Database changes None ### External dependencies None
adam added the status: acceptedtype: feature labels 2025-12-29 19:40:08 +01:00
adam closed this issue 2025-12-29 19:40:08 +01:00
adam commented 2025-12-29 19:40:08 +01:00
Author
Owner
Copy Link

@crouthamela commented on GitHub (May 11, 2022):

@WarriorXK Could you add this for Power Outlets too? (class PowerOutletTypeChoices)

Without that, when you model an RPS device, it won't have the SmartPower connections an Outlet (which in turn should be what connects to a Ubiquiti device on its SmartPower Port).

@crouthamela commented on GitHub (May 11, 2022): @WarriorXK Could you add this for Power Outlets too? (class PowerOutletTypeChoices) Without that, when you model an RPS device, it won't have the SmartPower connections an Outlet (which in turn should be what connects to a Ubiquiti device on its SmartPower Port).
adam commented 2025-12-29 19:40:09 +01:00
Author
Owner
Copy Link

@WarriorXK commented on GitHub (May 12, 2022):

@crouthamela Sure, see #9343

@WarriorXK commented on GitHub (May 12, 2022): @crouthamela Sure, see #9343
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 status: accepted 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#6389
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?