Multiple serial devices with bridges

[pfeifferdev]

I use the following configuration to connect two devices to the network using a bridge.

services:
  serial-bridge-1:
    image: ghcr.io/yeraze/meshtastic-serial-bridge:latest
    container_name: lf-bridge-device1
    devices:
      - /dev/ttyACM0:/dev/ttyACM0
    ports:
      - "4403:4403"
    environment:
      - SERIAL_DEVICE=/dev/ttyACM0
      - SERVICE_NAME=Device 1
      - BAUD_RATE=115200
      - TCP_PORT=4403
      

  serial-bridge-2:
    image: ghcr.io/yeraze/meshtastic-serial-bridge:latest
    container_name: mf-bridge-device2
    devices:
      - /dev/ttyACM1:/dev/ttyACM1
    ports:
      - "4404:4404"
    environment:
      - SERIAL_DEVICE=/dev/ttyACM1
      - TCP_PORT=4404
      - SERVICE_NAME=Device 2
      - BAUD_RATE=115200

A call to: meshtestic --host x.x.x.x:4403 --info produces the same output as a call to meshtestic --host x.x.x.x:4404 even though different devices are connected.

peter@peter-asus:~$ meshtastic --host 192.168.11.14:4403 --info
Connected to radio

Owner: FTL-Weissig Base 🏠 (FTLW)
My info: { "myNodeNum": 2291696324, "minAppVersion": 30200, "deviceId": "CGTqAs1ir+3EgpiInyIr/g==", "pioEnv": "seeed_wio_tracker_L1", "nodedbCount": 28, "rebootCount": 0, "firmwareEdition": "VANILLA" }
Metadata: { "firmwareVersion": "2.7.15.567b8ea", "deviceStateVersion": 24, "canShutdown": true, "hasBluetooth": true, "hwModel": "SEEED_WIO_TRACKER_L1", "hasPKC": true, "excludedModules": 21888, "hasWifi": false, "hasEthernet": false, "role": "CLIENT", "positionFlags": 0, "hasRemoteHardware": false }

Nodes in mesh: {
    "!889882c4": {
    "num": 2291696324,
    "user": {
      "id": "!889882c4",
      "longName": "FTL-Weissig Base \ud83c\udfe0",
      "shortName": "FTLW",
      "macaddr": "e2:9f:88:98:82:c4",
      "hwModel": "SEEED_WIO_TRACKER_L1",
      "publicKey": "f8wjEBYyqoTxZeR/G9PAJ6qwZcz//d5v2ZgwMNmnoRw=",
      "isUnmessagable": false
    },
    "position": {
      "latitudeI": 510000181,
      "longitudeI": 136101473,
      "altitude": 332,
      "time": 1769885344,
      "locationSource": "LOC_INTERNAL",
      "latitude": 51.0000181,
      "longitude": 13.6101473
    },
    "lastHeard": 1769885344,
    "deviceMetrics": {
      "batteryLevel": 101,
      "voltage": -0.001,
      "channelUtilization": 18.79,
      "airUtilTx": 0.6834722,
      "uptimeSeconds": 1328
    },
    "isFavorite": true
  },
  "!6c741fdc": {
    "num": 1819549660,

peter@peter-asus:~$ meshtastic --host 192.168.11.14:4403 --info
Connected to radio

Owner: FTL-Weissig Base 🏠 (FTLW)
My info: { "myNodeNum": 2291696324, "minAppVersion": 30200, "deviceId": "CGTqAs1ir+3EgpiInyIr/g==", "pioEnv": "seeed_wio_tracker_L1", "nodedbCount": 28, "rebootCount": 0, "firmwareEdition": "VANILLA" }
Metadata: { "firmwareVersion": "2.7.15.567b8ea", "deviceStateVersion": 24, "canShutdown": true, "hasBluetooth": true, "hwModel": "SEEED_WIO_TRACKER_L1", "hasPKC": true, "excludedModules": 21888, "hasWifi": false, "hasEthernet": false, "role": "CLIENT", "positionFlags": 0, "hasRemoteHardware": false }

Nodes in mesh: {
  "!889882c4": {
    "num": 2291696324,
    "user": {
      "id": "!889882c4",
      "longName": "FTL-Weissig Base \ud83c\udfe0",
      "shortName": "FTLW",
      "macaddr": "e2:9f:88:98:82:c4",
      "hwModel": "SEEED_WIO_TRACKER_L1",
      "publicKey": "f8wjEBYyqoTxZeR/G9PAJ6qwZcz//d5v2ZgwMNmnoRw=",
      "isUnmessagable": false
    },
    "position": {
      "latitudeI": 510000181,
      "longitudeI": 136101473,
      "altitude": 332,
      "time": 1769885344,
      "locationSource": "LOC_INTERNAL",
      "latitude": 51.0000181,
      "longitude": 13.6101473
    },
    "lastHeard": 1769885344,
    "deviceMetrics": {
      "batteryLevel": 101,
      "voltage": -0.001,
      "channelUtilization": 18.79,
      "airUtilTx": 0.6834722,
      "uptimeSeconds": 1328
    },
    "isFavorite": true
  },
  "!6c741fdc": {

[pfeifferdev]

This leads to a total misconfiguration. The same thing happens when the two containers are separated.

[Yeraze]

Maybe a typo in your comment, but when you showed the two outputs you used port 4403 in both. Can you confirm you tried 4404 and 4403 and saw the same result on both ports?

If so, can you attach docker logs from the two containers upon startup and initial connection from the meshtastic cli?

[Yeraze]

Haven't heard from you in a while, is this still an issue?