Harry
Harry
Hi @rondemena, This PR can now be closed as pynetbox has been updated to 7.4.0 from latest PR merge
Please raise a PR for to fix this issue or explain what needs to be changed so someone else can create a PR for it.
Hi @segachan The correct way for this to be modeled, is the added them as `module-bays` on the device. Then create the required AC and DC PSUs as a module....
Hi @segachan Yes that would be correct with 4 module-bays within that power tray. Yes nested modules are supported as of 4.1 and are also now supported by this repository.
Hi @arthanson Hope that makes more sense.
Hi Arthanson, Hope this works. ``` { "name": "Expansion card", "schema": { "properties": { "Connector type": { "type": "string", "description": "Connector type e.g. PCIe x4" }, "bandwidth": { "type": "integer",...
Hi @danner26 Is this a normal media converter? Then shouldn't it be a device type rather than the module type?
Hi @marmalodak I would recommend posting this issue on the netbox-community/Device-Type-Library-Import repo
Yes, this was as discussed in the issue #19571
> @harryajc , apologies for letting this languish. > > We need to add `exapansion_card.json` to the `initial_profiles` tuple in `0206_load_module_type_profiles.load_initial_data`, otherwise the migration will not pick the new profile...