Module topics 

What info reports, subject by subject.

Each topic names the properties it needs, renders them as report lines, and renders them again as shell assignments. Nothing here touches a device: a topic is a function from fetched octets to text, which is what lets the whole report cost one exchange and lets every rendering be tested without a radio.

Structs

Context

What the renderers know beyond the properties themselves.

Topic

One subject the device can be asked about.

Constants

STAT_FIELDS 🔒

TOPICS

Every subject, in the order a bare report prints them.

Functions

battery_status 🔒

bit 🔒

Booleans in --env output are 0 or 1: [ "$RADIO_ENABLED" = 1 ] is the shell’s natural test, and “on” would only invite string comparison against a word that might change.

capability_list 🔒

capability_name 🔒

The spec mnemonic, or the bare number for a capability this build has never heard of — a device newer than the tool still reports honestly.

charge_state_name 🔒

decode_sint 🔒

Decode the minimal-length signed integer PROP_IDENT_ALTITUDE uses: as many octets as the value needs, big-endian, sign-extended from the first.

default_region 🔒

digest_items 🔒

Split a digest table of fixed-width items. A table whose length is not a multiple of the item width is not one this can read, and saying so beats printing a plausible-looking prefix.

duty_limit 🔒

env_advert 🔒

env_battery 🔒

Kept exactly as it has always been spelled: scripts read these names, and the point of an interface a shell evals is that it does not move.

env_device 🔒

env_gnss 🔒

env_host 🔒

env_identity 🔒

env_radio 🔒

env_repeater 🔒

env_sensors 🔒

env_stats 🔒

env_time 🔒

filter_list 🔒

filters 🔒

host_keys 🔒

identity_keys 🔒

interval 🔒

on_off 🔒

ownership 🔒

Who this device answers to, and whether that is who was expected.

precision_cell 🔒

The approximate cell size one precision names, at the equator. What makes a precision meaningful is how large an area it discloses.

radio_keys 🔒

refusals

A refusal worth reporting rather than passing over in silence.

regions 🔒

render_advert 🔒

render_battery 🔒

render_device 🔒

render_gnss 🔒

render_host 🔒

render_identity 🔒

render_radio 🔒

render_repeater 🔒

render_sensors 🔒

render_stats 🔒

render_time 🔒

shell_quote

Status codes and keys are safe by construction, but a device name is whatever somebody typed into it. Everything that could carry a space or a quote goes through this before a shell sees it.

status_token 🔒

A status as the bare mnemonic, without the Rust path a debug format carries. [ "$DEVICE_STATUS" = RESET_POWER_ON ] is what a script wants to write, and a status this build cannot name still reads as something a script can compare.

topic

The topic of that name, if there is one.

Type Aliases

Line

One line of a report: a label and what it says.