Summary
daqifi-core#335 (merged, PR #348) surfaces device health telemetry — battery %, board temperature, power status — on the Core device (DeviceHealth on Metadata), data that was previously decoded and dropped. The example CLI does not print it anywhere, so the newly-exposed telemetry is invisible to consumers using the reference app.
Observed
--show-status during streaming prints only sample lines and the connection status; no battery/temp/power fields appear. There is no dedicated flag to read Metadata.* health.
Suggested change
Surface DeviceHealth in the example CLI — e.g. print it under --show-status / a new --health flag after InitializeAsync, reading the fields Core now populates on Metadata. This keeps the consumer reference in step with the Core API it is meant to demonstrate (consumer-first pattern).
Notes
- Verify the exact
DeviceHealth property names against core main (@ time of writing, just merged in #348).
- Bench context: Nq1, FW 3.7.2 over USB — a good target to confirm live values render.
Found during an autonomous live-hardware testing pass.
Summary
daqifi-core#335 (merged, PR #348) surfaces device health telemetry — battery %, board temperature, power status — on the Core device (
DeviceHealthonMetadata), data that was previously decoded and dropped. The example CLI does not print it anywhere, so the newly-exposed telemetry is invisible to consumers using the reference app.Observed
--show-statusduring streaming prints only sample lines and the connection status; no battery/temp/power fields appear. There is no dedicated flag to readMetadata.*health.Suggested change
Surface
DeviceHealthin the example CLI — e.g. print it under--show-status/ a new--healthflag afterInitializeAsync, reading the fields Core now populates onMetadata. This keeps the consumer reference in step with the Core API it is meant to demonstrate (consumer-first pattern).Notes
DeviceHealthproperty names against coremain(@ time of writing, just merged in #348).Found during an autonomous live-hardware testing pass.