Migrating from testo 300
The testo 330 and testo 320 replace the testo 300 in many trade and service apps. The QR code looks the same and is read the same way, but the JSON inside is a newer format. A parser written for the testo 300 reads wrong timestamps and does not find the channels.
This page lists what stays, what changes and how to support both instruments with little effort.
Different JSON schema
The testo 330 / 320 with the current instrument software (34.0) write
slim-schema-v1.4.0 into $schema. The testo 300 writes measurement-slim-v2.0.0 into
schema. These are two different schemas, not two versions of the same one: the higher number of the
testo 300 does not mean a newer format. A later instrument software may raise the version of
slim-schema, so always read it from $schema.
At a glance
| testo 300 | testo 330 / 320 | |
|---|---|---|
| QR code (testo format) | binary QR, gzip, JSON Lines | same |
| ZIV QR code (DE, AT, CZ, SK) | yes | same IDs except CO in ppm (69 instead of 79); selectable in the settings (example) |
| JSON schema | measurement-slim-v2.0.0 |
slim-schema-v1.4.0 with software 34.0, a different schema; version in $schema (same as testo Smart) |
| Bluetooth LE | service 0x2000, characteristics 0x3000–0x3019, no pairing |
service FC7B, EC01/EC02 with offset, CRC-32, pairing; from 2027 also authorisation through the testo Cloud (details) |
| Remote control over Bluetooth | TOGGLE_MEASUREMENT (0x3100) |
not available |
Own Android app on the instrument (App to App, testot330i://) |
no longer supported | not available; use testo Smart App to App on the phone |
| Wi-Fi / HTTP | discontinued since app 12.7.29 | not offered |
1. QR code: nothing to change in scanning
Reading the bytes, gunzip and splitting into lines work exactly as before. Your scanner configuration, the binary mode and the decompression stay. Only the JSON parsing changes (next section).
2. JSON: the differences
Detect the format from the schema field and keep two parsers. This is how testo Smart itself imports both.
schema = doc.get("$schema") or doc.get("schema", "")
parser = parse_testo300 if "measurement-slim-v2.0.0" in schema else parse_testo330
| Topic | testo 300 | testo 330 / 320 | What to do |
|---|---|---|---|
| Schema field | schema |
$schema |
read both keys |
timeStamp |
milliseconds ("1618395383000") |
seconds ("1794911176") |
do not divide by 1000 for the testo 330; otherwise all dates become 1970 |
startTime / endTime |
— | milliseconds, in additionalMeasurementInformation |
note the different unit |
Channel name type.name |
short label; older firmware: in the instrument language ("Zug", "AT"), newer firmware: English ("Draught", "FT") with the local label in type.description |
language-neutral quantity ("FlueDraught", "Oxygen", "FluegasTemperature") |
map by type.name; use type.description only for display |
| Measurement type | type.name, translated ("Abgas") |
type.id ("T330Fluegas"); type.name translated |
decide by type.id |
properties |
object: {"fuelName": "Heizöl EL", "o2Value": "3,0"} |
array: [{"name": "CurrentFuelName", "values": [{"value": "Light Oil"}]}] |
read as list of name/value pairs |
| Number format in properties | decimal separator of the instrument language ("3,0") |
"3.0" |
|
| Device of a channel | only the instrument in device[] |
instrument and probes in device[]; each channel names its serial in additionalData |
assign channels by serial |
| Invalid value | "status": "invalid", no value |
"status": invalid, overrange, underrange or empty; value is still present (0.0 for empty) |
check status before value |
| Values per channel | one | one: the last reading or the mean | |
| Special results | channels (e.g. "Rußzahl 1") |
appendix, e.g. appendix.smokeNumber |
read smoke numbers from appendix |
| Customer data | customer, organisation, measuringPoint |
same objects, more fields | contact data may become optional in a future version; prefer your own customer records |
3. Example: the same values in both formats
{
"type": { "name": "Abgas" },
"channels": [
{ "type": { "name": "O₂" }, "unit": { "name": "%" },
"values": [ { "timeStamp": "1618395383000", "value": 20.60 } ] }
],
"properties": { "fuelName": "Heizöl EL", "o2Value": "3,0" },
"schema": "https://github.com/testo/tjf/tree/public/schema/measurement-slim-v2.0.0"
}
{
"$schema": "https://github.com/testo/tjf/raw/public/schema/slim-schema-v1.4.0.json",
"type": { "id": "T330Fluegas", "name": "Flue gas" },
"channels": [
{ "type": { "name": "Oxygen", "description": "O₂" }, "unit": { "name": "%" },
"values": [ { "timeStamp": "1794911176", "value": 17.2 } ],
"additionalData": [ { "name": "serial", "value": "65409720" } ] }
],
"properties": [ { "name": "CurrentFuelName", "values": [ { "value": "Wood 15%w" } ] } ]
}
4. Channel mapping for flue gas measurements
testo 300 type.name (older German firmware / newer firmware) |
testo 330 type.name |
ZIV ID |
|---|---|---|
| AT / FT | FluegasTemperature |
41 |
| VT / AT | AmbientTemperature, AmbientTemperatureFix |
40 |
| O₂ / O2 | Oxygen |
50 |
| CO₂ / CO2 | CalcCarbonDioxide |
52 |
| CO | CarbonMonoxide |
69 / 71 (testo 300: 79 / 71) |
| COunv | CalcCOUndiluted |
70 / 72 |
| Zug / Draught | FlueDraught |
80 / 81 |
| λ | CalcAirRatio |
92 |
| qA + / qAgr. | CalcFlueGasLoss, CalcFlueGasLossPlus |
90 |
| η + / Effg | CalcEfficiency, CalcGrossEfficiency |
91 |
| NO | NitrogenMonoxide |
57 / 59 |
| NOx | CalcNOx |
200 / 201 |
| Taupunkt | CalcFlueGasDewPointTemperature |
93 |
Note the trap in the first two rows: in older German testo 300 data "AT" is the flue gas temperature (Abgastemperatur), in newer data "AT" is the ambient temperature and "FT" the flue gas temperature. The testo 330 names are unambiguous.
5. Bluetooth: rewrite the transport
The Bluetooth interface of the testo 330 is new. Reuse only the part after the transfer (gunzip, JSON).
| Step | testo 300 | testo 330 / 320 |
|---|---|---|
| Find | by name | by name prefix T330_ / T320_ |
| Security | none | pairing with numeric comparison (from instrument software version 34.0); from 2027 in addition authorisation of your app through the testo Cloud |
| Size | read 0x3000 = number of characteristics |
read EC01 = {ready, size, crc} |
| Data | read 0x3001 … 0x30nn (500 bytes each), MTU ≥ 500 required |
write offset to EC01, read EC02, repeat; works with any MTU |
| Check | — | CRC-32 over the compressed bytes |
| Content | plain JSON | gzip JSON Lines (same as the QR code) |
| Start/stop measurement | TOGGLE_MEASUREMENT |
not available |
Full description: Bluetooth LE.
6. Checklist
- Parser selected by
$schema/schema. - Timestamps: milliseconds (testo 300) vs. seconds (testo 330).
- Channel mapping by language-neutral
type.namefor the testo 330. -
propertiesread as array for the testo 330. -
statuschecked beforevalue. - Smoke numbers read from
appendix. - Bluetooth: pairing and the EC01/EC02 transfer implemented.
- Bluetooth: room for the authorisation through the testo Cloud from 2027 (separate step before reading).
- Tested with the testo 330 / 320 example and the testo 300 examples.