tx16s.lua (v2.4, MK3 800x480 layout) crashes with "bad argument #5 to 'drawGauge'" as soon as INAV telemetry data arrives

[NeoSamuel22]

Using LuaTelemetry v2.4 (the new tx16s.lua 800x480 layout added in PR #202) on a RadioMaster TX16S MK3, EdgeTX 2.12.0, connected to a freshly-configured 9" INAV multirotor/wing via CRSF (ExpressLRS 4.x, internal Gemini-X module).
The script loads fine with no telemetry connected. As soon as real INAV telemetry data starts arriving (link established, sensors populated), the widget immediately crashes:
in refresh(): /SCRIPTS/TELEMETRY/iNav/tx16s.lua:599: bad argument #5 to 'drawGauge' (number has no integer representation)
Note: I also observed a related crash with the same script/error on a Betaflight craft (not the officially supported firmware for this widget), where moving the right stick triggered a cascade of spurious flight-mode voice announcements ("ARMED", "HORIZON MODE", "ANGLE MODE", etc.) followed by the same crash. Mentioning this only as additional context — the INAV crash below is the priority since it's the supported use case and is immediately reproducible.
To reproduce

Flash/boot the TX16S MK3 with EdgeTX 2.12.0 and LuaTelemetry v2.4 (tx16s.lua, 800x480 layout) on the SD card
Set up a fresh model for a 9" INAV craft, CRSF telemetry via ExpressLRS
Open the telemetry screen with the iNav LuaTelemetry widget — confirm it renders with no telemetry connected
Power on / connect the INAV FC so telemetry data starts flowing
Widget crashes almost immediately once real data arrives, throwing the error above

Expected behavior
The widget should render live INAV telemetry data (GPS, attitude, battery, etc.) without crashing once a real data stream begins.
Screenshots
(attached — EdgeTX error screen showing in refresh(): /SCRIPTS/TELEMETRY/iNav/tx16s.lua:599: bad argument #5 to 'drawGauge' (has no integer representation))
Radio and model settings

Additional context

Radio: RadioMaster TX16S MK3 (800x480 color touchscreen)
Firmware: EdgeTX 2.12.0
LuaTelemetry version: v2.4 ("larger screens" release, tx16s.lua from PR #202)
RF link: ExpressLRS 4.x, internal Gemini-X module, CRSF
FC (primary/reproducible case): INAV, 9" craft, freshly configured
FC (secondary observation, unsupported use case): Betaflight
Crash is immediate on real telemetry data arriving — suggests a value from live INAV sensor data (possibly a percentage/fill computation with a fractional result) is being passed to drawGauge's fill argument without being cast to an integer, in the new gauge-rendering code from PR #202
Not present before updating to v2.4's tx16s.lua

[NeoSamuel22]

Found and fixed the drawGauge crash on TX16S MK3
Tested on a RadioMaster TX16S MK3 (800x480, EdgeTX 2.12) with INAV via CRSF. The widget crashed as soon as real telemetry data arrived, with:
in refresh(): /SCRIPTS/TELEMETRY/iNav/tx16s.lua:599: bad argument #5 to 'drawGauge' (number has no integer representation)
Cause: In tx16s.lua, the battery cell voltage gauge (Box 1) passes a raw floating-point calculation as the 5th argument to lcd.drawGauge(), instead of a rounded integer. Under Lua 5.3 (used since EdgeTX 2.11+), drawGauge requires an integer here, so this throws immediately once real (non-zero) battery values come in. The other two gauges right next to it (fuel, RSSI) already pass integer values and are unaffected — this one line was simply missed.
This is present both in the official v2.4 release and in the current state of this feature/800x480-tx16s-support branch (line 565 there).
Line to find (in the release v2.4, it's line 599; in the current branch, line 565):
lualcd.drawGauge(0, TOP + 102, X1, 18, min(max(val - config[3].v + 0.1, 0) * (100 / (4.2 - config[3].v + 0.1)), 99), 100, data.set_flags(0,data.bc))
Fix — wrap the fill-value expression in floor(...) (already available in this file as a local alias for math.floor):
lualcd.drawGauge(0, TOP + 102, X1, 18, floor(min(max(val - config[3].v + 0.1, 0) * (100 / (4.2 - config[3].v + 0.1)), 99)), 100, data.set_flags(0,data.bc))
Tested and confirmed working after this change on my radio

[micahstuh]

I encountered the same error. Thanks to @NeoSamuel22 for locating the source, except a different transmitter file.

Wrapping my value in floor() still resulted in the error. I was able to fix it with the following code:

In tx15.lua:
old:

lcd.drawGauge(0, bottomY(TOP + 68), X1 - 3, 15, min(max(val - config[3].v + 0.1, 0) * (100 / (4.2 - config[3].v + 0.1)), 99), 100, data.set_flags(0,data.bc))

new:

local gauge_fill = floor(min(max(val - config[3].v + 0.1, 0) * (100 / (4.2 - config[3].v + 0.1)), 99))
local gauge_fill_int = 0
if gauge_fill ~= nil then
	gauge_fill_int = gauge_fill
end
lcd.drawGauge(0, bottomY(TOP + 68), X1 - 3, 15, gauge_fill_int, 100, data.set_flags(0,data.bc))

I bet there is a cleaner way of doing that.

Radio: RadioMaster TX15
Firmware: EdgeTX 2.12.2
LuaTelemetry version: v2.4
RF link: RadioMaster RP3 V2 ExpressLRS, CRSF
FC: CoreWing F405 Wing V2, INAV 9.0.1