# setTelemetryValue(id, subID, instance, value \[, unit \[, precision \[, name]]]) @status current Introduced in 2.2.0 ## Parameters * `id` Id of the sensor, valid range is from 0 to 0xFFFF * `subID` subID of the sensor, usually 0, valid range is from 0 to 7 * `instance` instance of the sensor (SensorID), valid range is from 0 to 0xFF * `value` fed to the sensor * `unit` unit of the sensor [Full list](https://github.com/opentx/lua-reference-guide/blob/opentx_2.3/part_iii_-_opentx_lua_api_reference/appendix/units.html) * `precision` the precision of the sensor * `0 or not present` no decimal precision. * `!= 0` value is divided by 10^precision, e.g. value=1000, prec=2 => 10.00. * `name` (string) Name of the sensor if it does not yet exist (4 chars). * `not present` Name defaults to the Id. * `present` Sensor takes name of the argument. Argument must have name surrounded by quotes: e.g., "Name" ## Return value * `true,` if the sensor was just added. In this case the value is ignored (subsequent call will set the value) ### Notice All three parameters `id`, `subID` and `instance` can't be zero at the same time. At least one of them must be different from zero. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://doc.open-tx.org/opentx-2-3-lua-reference-guide/part_iii_-_opentx_lua_api_reference/general-functions-less-than-greater-than-luadoc-begin-general/settelemetryvalue.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.