Modules in devices: use device type as first selection field #248

New Issue

MrUnknownDE · 2026-04-05T16:23:32+02:00

MrUnknownDE commented

2026-04-05 16:23:32 +02:00

Originally created by @Crubumble on 3/3/2026

NetBox version

v4.5.3

Feature type

Data model extension

Proposed functionality

Devices in manufacturing plants or in the process industry are different from server racks. If you have a Siemens SIPLUS ET 200SP as device type. It is the same for each device. Of course, the installed software or hardware version could differ. However, this does not justify the general approach of treating each device individually. In case of hardware and firmware version, this can be handled in the device type as well. With the feature of having modules, this becomes even more convenient. Therefore, the following design should be take into consideration when use devices industrial environment.

Use case

Expected behavior

Under Device Types there are

device type [A, B]
module types [AC/DC, I/O, Interface Module (IM)]

Under Device components

Generate a module bay for a device type NOT device

Under Devices

Add a module under modules. Instead of device as first field device type list is given
- Case A (bays are determined to a specific module)
  - Select a device type
  - Choose module bay and module type
  - Select a bundle of devices (that have the given device type)
- Case B (bays are arbitrary)
  - select a device
  - According to corresponding device type choose a module bay and module type

Observed behavior

Device Types

device type [A, B]
module types [AC/DC, I/O, Interface Module (IM)]

Device components

Generate module bay for ONE device

Devices

Select add module
Select a device
Choose module bay and module type
Repeat this for every device

Database changes

Modules in devices use device type as first selection field and device at the end of the required fields.

In case A the device selection has to be modified in order to handle several selections

External dependencies

No response

*Originally created by @Crubumble on 3/3/2026* ### NetBox version v4.5.3 ### Feature type Data model extension ### Proposed functionality Devices in manufacturing plants or in the process industry are different from server racks. If you have a `Siemens SIPLUS ET 200SP` as device type. It is the same for each device. Of course, the installed software or hardware version could differ. However, this does not justify the general approach of treating each device individually. In case of hardware and firmware version, this can be handled in the device type as well. With the feature of having modules, this becomes even more convenient. Therefore, the following design should be take into consideration when use devices industrial environment. <img width="1297" height="561" alt="Image" src="https://github.com/user-attachments/assets/13596860-e482-4460-88a1-e32cfd8355ff" /> ### Use case ## Expected behavior 1. Under Device Types there are - device type [A, B] - module types [AC/DC, I/O, Interface Module (IM)] 2. Under Device components - Generate a module bay for a device type NOT device 3. Under Devices - Add a module under modules. Instead of device as first field device type list is given - Case A (bays are determined to a specific module) - Select a device type - Choose module bay and module type - Select a bundle of devices (that have the given device type) - Case B (bays are arbitrary) - select a device - According to corresponding device type choose a module bay and module type ### Observed behavior 1. Device Types - device type [A, B] - module types [AC/DC, I/O, Interface Module (IM)] 2. Device components - Generate module bay for ONE device 3. Devices - Select add module - Select a device - Choose module bay and module type - Repeat this for every device ### Database changes Modules in devices use device type as first selection field and device at the end of the required fields. In case A the device selection has to be modified in order to handle several selections ### External dependencies _No response_

Sign in to join this conversation.

Branches Tags

main

21455-sql-indexes-audit

21357-register-model-actions

feature

20924-plugin-ui-components

21766-improve-test-coverage-for-sortable-table-columns

21157-export-template-public-models

21025-pre-render-config-contexts

21364-swagger

feature-ip-prefix-link

20911-dropdown-3

fix_module_substitution

21160-filterset

20911-dropdown-2

20044-elevation-stuck-lightmode

7604-filter-modifiers-v3

20660-script-load

19724-graphql

14884-script

19720-macaddress-interface-generic-relation

fix-19669-api-image-download

7604-filter-modifiers

19275-fixes-interface-bulk-edit

fix-17794-get_field_value_return_list

11507-show-aggregate-and-rir-on-api

9583-add_column_specific_search_field_to_tables

No Label complexity: medium complexity: medium complexity: medium complexity: medium complexity: medium complexity: medium complexity: medium complexity: medium complexity: medium complexity: medium netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox status: needs owner status: needs owner status: needs owner status: needs owner status: needs owner status: needs owner status: needs owner status: needs owner status: needs owner status: needs owner status: needs owner status: needs owner status: needs owner type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/netbox#248