MQTT Settings

[earthstephen]

I'm a bit confused by the setting for MQTT Message being described as a bitfield. Does this just mean I enter the integers noted in the description (for example: 2=Uptime). I ask because I get no MQTT output for the 1=Sondes selection (even with balloon data flowing) and if I enter 4 the ttgo enters an endless reset loop. There is also a JSON format issue with the uptime message but that's really a separate issue. There is a space in the time parameter that confuses multiple parsers I have tried.

[ckuethe]

It occurs to me that I may have made some incorrect assumptions about the PMU and how to read from it. I've only got TTGO T-Beam 1.0 with OLED display (fingerprint 23) devices. What device do you have, and more importantly what PMU does it have?

You OR the values together, so if you wanted packets, gps, and RF that'd be
0x01 | 0x08 | 0x10 = 0x19 -> 25

[earthstephen]

Thanks for the reply. The board I’m using is a lilygo ttgo v2.1_1.6. I don’t know what it has for a PMU.
I was missing the hex to decimal conversion part of the MQTT packet select. I’ll try changing that.

[ckuethe]

k. I'm sure there's a datasheet and a schematic somewhere.

[hr-ru]

Alright, that explains it. This board does not have a PMU, in which the pmu pointer will be just NULL, so there is a NULL pointer access causing reset. (There is a simple voltage devider on the v2.1_1.6 to a A/D input, so it would be feasible to measure voltage, but nothing else). I'll fix that in the next version.

But for now, there should be a simple solution, just do not active that part. For what you want, it should be fine to use
Sondes + Uptime + Scanner (i.e. 1+2+16 = 19) in the mqtt config field, just do not add 4 to not enable reading PMU values.