Everything available on MUI alsi published to MQTT?

[Slyke]

Wasn't sure if I should ask this in the Meshtastic UI repo, or this one, but figured here since it involves MQTT.

Are all the details that show up in the MUI also published to MQTT? Obviously things like graphics, maps etc won't be on MQTT, but I mean things like nodes, distances, messages, wifi details etc?

[garthvh]

Not directly from the MUI device as you can't connect WiFi at the same time

[Slyke]

What do you mean? MUI devices connect to Wifi and MQTT (or at least my T-Deck is). They just don't host the WebUI. I'm just wondering if all the details that are visible in MUI are also published to MQTT?

Obviously histograms and that don't publish all their history to MQTT, but just the latest data.

[garthvh]

The MUI uses the api connection that WiFi uses, you can't use WiFi and thus mqtt while using the MUI

[Slyke]

The docs only mention Bluetooth not working, and I can see it connected with an IP address in MUI:

MUI functions as a client, similar to the Android and Apple apps. It runs on one core of the MCU, while the regular Meshtastic firmware runs on the other. MUI communicates with the firmware using the Client API, the same interface used by other Meshtastic clients.

The Client API supports only one active connection at a time, which means Bluetooth cannot be used while MUI is running. Since not all settings can be configured within MUI, Bluetooth Programming Mode allows users to temporarily disable MUI, enabling Bluetooth so the device can be configured via another client app.

https://meshtastic.org/docs/software/meshtastic-ui/

I can also see it connected to my MQTT topic in MUI and this payload appearing in my MQTT server:

  "channel": 0,
  "from": 2651XXXXXX,
  "hop_start": 3,
  "hops_away": 0,
  "id": 3402443YYY,
  "payload": {
    "air_util_tx": 0.0268888883292675,
    "battery_level": 101,
    "channel_utilization": 3.22666645050049,
    "uptime_seconds": 67,
    "voltage": 4.29199981689453
  },
  "sender": "!9e0a0ZZZ",
  "timestamp": 1747429679,
  "to": 4294967295,
  "type": "telemetry"
}

I am confused when you say wifi doesn't work with MUI when it has to be because I can see my TDeck talking to my MQTT server while I'm messing on it with MUI.

What I'm unsure about is how to get all the other details into MQTT too, such as RSSI, SNR of other nodes, Packet Stats, Frequency and bandwidth etc into MQTT, if that's possible to do.

What I can't do is configure it with the Android app using its IP address when MUI is running. I have to first reboot it turning wifi off, reboot it again to put it into programming mode, connect via BLE and configure it, reboot it again to put it into MUI mode, then reboot again to turn wifi back on - as programming mode doesn't automatically turn wifi off when it tries to start Bluetooth.