Describe the bug
After defining the path to the Repeater, I click "Save Path and endpoint /api/sources/5dbe1554-b8ec-46cc-8b87 -eb65620b3904/meshcore/contacts/053201a9edf496a3e57a183917ec0c33c6823513289d06d223caabd3364cfaf2/out-path—it’s stuck and doesn’t return. After 4.5 minutes, the message “Save failed” appeared.

To Reproduce
Steps to reproduce the behavior:

1. In MeshCore Source, find node
2. Goto provate messages
3. Click "Define path" and create path
4. Click Save Path

Expected behavior
A saved path to node

Screenshots

Environment (please complete the following information):

• Host OS: Debian 13
• Deployment type: Docker? Mac App? Windows App? or Baremetal?
  • docker in 4.11.5, server only in local home network
    docker-compose:
    meshmonitor:
    image: ghcr.io/yeraze/meshmonitor:4.11
    container_name: meshmonitor
    ports:
    • "8080:3001"
      restart: unless-stopped
      volumes:
    • /opt/meshmonitor/data:/data:rw
      environment:
    • ALLOWED_ORIGINS=http://...:8080 # Required for CORS
    • TZ=Europe/Warsaw
      devices:
    • /dev/ttyACM0
• Database backend: SQLite
• Node type: xiao nrf
• Node Connection Type: serial-bridge

Additional context
Add any other context about the problem here. Console Logs, Container Logs, or Screenshots.
[WARN] [MeshCore] set_out_path failed for 053201a9edf496a3e57a183917ec0c33c6823513289d06d223caabd3364cfaf2: Native command timeout: set_out_path
[WARN] [MeshCore] set_out_path failed for 053201a9edf496a3e57a183917ec0c33c6823513289d06d223caabd3364cfaf2: Native command timeout: set_out_path

If you do not follow this template, your issue may be ignored or delayed due to lack of information.

Thanks, for your job !