From 7db011cb7809933d0363583348547a0afe59ac74 Mon Sep 17 00:00:00 2001
From: cproudlock <cproudlock@localhost>
Date: Fri, 26 Jun 2026 09:17:15 -0400
Subject: [PATCH] Network device form: use asset statuses instead of legacy
 machine statuses

Last form still reading /api/statuses (MachineStatus); repoint to
assetsApi.statuses so its status dropdown matches the rest of the app.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
---
 frontend/src/views/network/NetworkDeviceForm.vue | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/frontend/src/views/network/NetworkDeviceForm.vue b/frontend/src/views/network/NetworkDeviceForm.vue
index edf5704..4184c46 100644
--- a/frontend/src/views/network/NetworkDeviceForm.vue
+++ b/frontend/src/views/network/NetworkDeviceForm.vue
@@ -226,7 +226,7 @@ import {
   networkApi,
   vendorsApi,
   locationsApi,
-  statusesApi,
+  assetsApi,
   businessunitsApi
 } from '../../api'
 
@@ -307,7 +307,7 @@ async function loadLocations() {
 
 async function loadStatuses() {
   try {
-    const response = await statusesApi.list({ perpage: 100 })
+    const response = await assetsApi.statuses.list()
     statuses.value = response.data.data || []
   } catch (err) {
     console.error('Error loading statuses:', err)