No data form serial port #6

Closed
opened 2026-10-05 03:11:35 +02:00 by adam · 4 comments
Owner

Hi,

I've installed it on my docker, both containers are running, but it seems, that it cannot read from /dev/ttyUSB0
|2026-01-20 08:11:54,616 - __main__ - WARNING - meshcli stderr: ERROR:meshcore:Error while querying device: Event(type=<EventType.ERROR: 'command_error'>, payload={'reason': 'no_event_received'}, attributes={})
when I run:
docker compose exec meshcore-bridge meshcli -s /dev/ttyUSB0 infos
it shows:

INFO:meshcore:Serial Connection started
ERROR:meshcore:Error while querying device: Event(type=<EventType.ERROR: 'command_error'>, payload={'reason': 'no_event_received'}, attributes={})

command: ls -l /dev/serial/by-id/
shows the device:
Jan 20 00:43 usb-Silicon_Labs_CP2102_USB_to_UART_Bridge_Controller_0001-if00-port0 -> ../../ttyUSB0
Lora board is: Helcat v3

Any idea, where is the problem?

Hi, I've installed it on my docker, both containers are running, but it seems, that it cannot read from /dev/ttyUSB0 `|2026-01-20 08:11:54,616 - __main__ - WARNING - meshcli stderr: ERROR:meshcore:Error while querying device: Event(type=<EventType.ERROR: 'command_error'>, payload={'reason': 'no_event_received'}, attributes={})` when I run: `docker compose exec meshcore-bridge meshcli -s /dev/ttyUSB0 infos` it shows: ``` INFO:meshcore:Serial Connection started ERROR:meshcore:Error while querying device: Event(type=<EventType.ERROR: 'command_error'>, payload={'reason': 'no_event_received'}, attributes={}) ``` command: `ls -l /dev/serial/by-id/` shows the device: `Jan 20 00:43 usb-Silicon_Labs_CP2102_USB_to_UART_Bridge_Controller_0001-if00-port0 -> ../../ttyUSB0` Lora board is: **Helcat v3** Any idea, where is the problem? <!-- github-sync-id:3833747229 -->
adam closed this issue 2026-10-05 03:11:35 +02:00
Author
Owner

Could you please post your .env file content?

Could you please post your .env file content? <!-- github-comment-id:3773385092 -->
Author
Owner

sure, .env:

# mc-webui Environment Configuration
# Copy this file to .env and adjust values for your setup

# ============================================
# MeshCore Device Configuration
# ============================================

# Serial port path
# Use "auto" for automatic detection (recommended if only one USB device)
# Or specify manually: /dev/serial/by-id/usb-xxx or /dev/ttyUSB0
# Find available devices: ls /dev/serial/by-id/
MC_SERIAL_PORT=/dev/ttyUSB0

# Your MeshCore device name (used for .msgs file)
# Use "auto" for automatic detection from meshcli (recommended)
# Or specify manually: MarWoj, SP5XYZ, MyNode
MC_DEVICE_NAME=SQ2PPJ_2_TEST

# MeshCore configuration directory (where .msgs and settings files are stored)
# Default: ./data/meshcore (inside project directory)
# This directory is mounted as a Docker volume and shared between both containers
MC_CONFIG_DIR=./data/meshcore

# ============================================
# Application Settings
# ============================================

# Note: Auto-refresh is now intelligent and checks for new messages every 10 seconds
# No configuration needed - the system automatically updates UI only when new messages arrive
# Contact cleanup threshold is set directly in the UI (default: 48 hours)

# ============================================
# Archive Configuration
# ============================================

# Directory for storing archived messages
# Default: ./data/archive (inside project directory)
# This directory is mounted as a Docker volume for mc-webui container
MC_ARCHIVE_DIR=./data/archive

# Enable automatic daily archiving at midnight
MC_ARCHIVE_ENABLED=true

# Number of days to show in live view (older messages available in archives)
MC_ARCHIVE_RETENTION_DAYS=7

# ============================================
# Flask Server Configuration
# ============================================

# Listen on all interfaces (0.0.0.0) or specific IP
FLASK_HOST=0.0.0.0

# Port to expose the web interface
FLASK_PORT=5000

# Debug mode (true/false) - use false in production
FLASK_DEBUG=false

# ============================================
# System Configuration
# ============================================

# Timezone for container logs (default: UTC)
# Examples: Europe/Warsaw, America/New_York, Asia/Tokyo
TZ=Europe/Warsaw

When I changed LoRA board to XIAO it start working. I will try to reflash Heltec and try again.

sure, .env: ``` # mc-webui Environment Configuration # Copy this file to .env and adjust values for your setup # ============================================ # MeshCore Device Configuration # ============================================ # Serial port path # Use "auto" for automatic detection (recommended if only one USB device) # Or specify manually: /dev/serial/by-id/usb-xxx or /dev/ttyUSB0 # Find available devices: ls /dev/serial/by-id/ MC_SERIAL_PORT=/dev/ttyUSB0 # Your MeshCore device name (used for .msgs file) # Use "auto" for automatic detection from meshcli (recommended) # Or specify manually: MarWoj, SP5XYZ, MyNode MC_DEVICE_NAME=SQ2PPJ_2_TEST # MeshCore configuration directory (where .msgs and settings files are stored) # Default: ./data/meshcore (inside project directory) # This directory is mounted as a Docker volume and shared between both containers MC_CONFIG_DIR=./data/meshcore # ============================================ # Application Settings # ============================================ # Note: Auto-refresh is now intelligent and checks for new messages every 10 seconds # No configuration needed - the system automatically updates UI only when new messages arrive # Contact cleanup threshold is set directly in the UI (default: 48 hours) # ============================================ # Archive Configuration # ============================================ # Directory for storing archived messages # Default: ./data/archive (inside project directory) # This directory is mounted as a Docker volume for mc-webui container MC_ARCHIVE_DIR=./data/archive # Enable automatic daily archiving at midnight MC_ARCHIVE_ENABLED=true # Number of days to show in live view (older messages available in archives) MC_ARCHIVE_RETENTION_DAYS=7 # ============================================ # Flask Server Configuration # ============================================ # Listen on all interfaces (0.0.0.0) or specific IP FLASK_HOST=0.0.0.0 # Port to expose the web interface FLASK_PORT=5000 # Debug mode (true/false) - use false in production FLASK_DEBUG=false # ============================================ # System Configuration # ============================================ # Timezone for container logs (default: UTC) # Examples: Europe/Warsaw, America/New_York, Asia/Tokyo TZ=Europe/Warsaw ``` When I changed LoRA board to XIAO it start working. I will try to reflash Heltec and try again. <!-- github-comment-id:3773936264 -->
Author
Owner

Thanks for the update! Also, try MC_SERIAL_PORT=auto (if this is the only USB device connected). I tested that with Heltec V3 and it was discovered just fine.

Thanks for the update! Also, try `MC_SERIAL_PORT=auto` (if this is the only USB device connected). I tested that with Heltec V3 and it was discovered just fine. <!-- github-comment-id:3776535389 -->
Author
Owner

So, is this issue resolved? Can we close the issue?

So, is this issue resolved? Can we close the issue? <!-- github-comment-id:3786501923 -->
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/mc-webui#6