[Bug]: Can't set Device Name

[MK-0x41]

🐛 Describe the Bug

When attempting to assign a name to a new device, the system displays a success message indicating that the name has been saved. However, after about a second, the field becomes empty again, making it impossible to set a name.

🔍 Steps to Reproduce

1. Open the interface for assigning a name to a new device.
2. Enter a desired name in the name field.
3. Enter-key to Confirm/save the name.

🌐 Browser

Brave

🔧 Deployment Type

• Docker
• Standalone

✨ Expected Behavior

The name should be saved and remain visible in the field.

📋 ZTNET Logs

docker compose logs 
WARN[0000] /data/ztnet/docker-compose.yml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion 
postgres  | 
postgres  | PostgreSQL Database directory appears to contain a database; Skipping initialization
postgres  | 
postgres  | 2025-01-17 12:12:41.993 UTC [1] LOG:  starting PostgreSQL 15.2 on x86_64-pc-linux-musl, compiled by gcc (Alpine 12.2.1_git20220924-r4) 12.2.1 20220924, 64-bit
postgres  | 2025-01-17 12:12:41.994 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
postgres  | 2025-01-17 12:12:41.994 UTC [1] LOG:  listening on IPv6 address "::", port 5432
postgres  | 2025-01-17 12:12:41.998 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
postgres  | 2025-01-17 12:12:42.006 UTC [24] LOG:  database system was shut down at 2025-01-17 12:12:34 UTC
postgres  | 2025-01-17 12:12:42.020 UTC [1] LOG:  database system is ready to accept connections
postgres  | 2025-01-17 12:12:44.945 UTC [29] LOG:  could not receive data from client: Connection reset by peer
zerotier  | Starting Control Plane...
zerotier  | Starting V6 Control Plane...
ztnet     | Creating .env file...
ztnet     | Applying migrations to the database...
ztnet     | Environment variables loaded from .env
ztnet     | Prisma schema loaded from prisma/schema.prisma
ztnet     | Datasource "db": PostgreSQL database "ztnet", schema "public" at "postgres:5432"
ztnet     | 
ztnet     | 37 migrations found in prisma/migrations
ztnet     | 
ztnet     | 
ztnet     | No pending migrations to apply.
ztnet     | npm notice
ztnet     | npm notice New major version of npm available! 10.7.0 -> 11.0.0
ztnet     | npm notice Changelog: https://github.com/npm/cli/releases/tag/v11.0.0
ztnet     | npm notice To update run: npm install -g [email protected]
ztnet     | npm notice
ztnet     | Migrations applied successfully!
ztnet     | Seeding the database...
ztnet     | Environment variables loaded from .env
ztnet     | Running seed command `ts-node --compiler-options {"module":"CommonJS"} prisma/seed.ts` ...
ztnet     | Seeding:: User Options complete!
ztnet     | Seeding:: Updating user ID complete!
ztnet     | 
ztnet     | 🌱  The seed command has been executed.
ztnet     | ┌─────────────────────────────────────────────────────────┐
ztnet     | │  Update available 6.0.1 -> 6.2.1                        │
ztnet     | │  Run the following to update                            │
ztnet     | │    npm i -g prisma@latest                               │
ztnet     | │    npm i @prisma/client@latest                          │
ztnet     | └─────────────────────────────────────────────────────────┘
ztnet     | Database seeded successfully!
ztnet     | Executing command
ztnet     |    ▲ Next.js 14.1.4
ztnet     |    - Local:        http://d38425bbc0ff:3000
ztnet     |    - Network:      http://172.31.255.4:3000
ztnet     | 
ztnet     |  ✓ Ready in 211ms
ztnet     | Socket is initializing

🖼 Screenshots