Skip to main content

Drivers 5.0.0 · Device profiles 9.0.0

Published on 2026-09-14.

Breaking changes​

An integration reading these points may need to be adapted.

DriverWhat changes
mdlna:arrowwan2:1The alarm field of the daily (fPort 1, 2), weekly (fPort 5) and event (fPort 9) frames is renamed errors → alarms, with the same values ("Leakage", "Mechanical Fraud", "NoConsumption"…). On the platforms where frames carrying an alarm were rejected, they are now decoded. The Mixed measurement frame (fPort 6), which answered "Missing decoder for frame on port 6", is decoded. Points follow the ontology: flowRate (m3/h), volume:1 forward and volume:2 reverse (l), batteryVoltage (mV).
abeeway:asset-tracker-3:1The parameter bleBeaconFastSlowInterval is renamed bleBeaconSlowAdvInterval. frameNumber of the extended header is read on 4 bits: values of 8 and above are no longer truncated. New transport values SECURE_TCP and SECURE_UDP, and the AT3 firmware v1.5 fields are decoded.
os1-mile:am107:1Point illuminance:0 is no longer published and illuminance:3 is new; illuminance:1 and illuminance:2 change value and nature. The decoded payload is unchanged.
actility:micropims:1Points distance, temperature:1, temperature:2 and batteryLevel are no longer published; the temperature is published as temperature. The decoded payload is unchanged.
actility:pollutherm:1Point status:1 is no longer published. The decoded payload is unchanged.
thrmkn:joylrw:1Point temperature:1 is renamed temperature. The decoded payload is unchanged.
wika:pgu2x-100:1Point pressure is renamed pressureLevel. The decoded payload is unchanged.
b-meters:hydrodigit:1The uplink field absoluteMeterCounterReverseFlowRatio is no longer published. Frames that ended in driver error 500 are decoded as the specification describes them.
msight:gs101:1New uplink field device_status (e.g. "on").
msight:uc100:1Uplink fields renamed: chn<N> → modbus_chn_<N>, channel_<N>_error → modbus_chn_<N>_alarm, software_version → firmware_version. The field power is no longer published; device_status is new.
msight:uc300:1Uplink fields renamed: chn<N> → modbus_chn_<N>, counter_<N> → gpio_counter_<N>, gpio_in_<N> → gpio_input_<N>, gpio_out_<N> → gpio_output_<N>. New fields: adc_<N>_min/_max/_avg, adv_<N>_min/_max/_avg, modbus_chn_<N>_alarm, device_status, firmware_version, hardware_version, sn, ipso_version.
mclimate:16a-dry-switch:1The uplink field relayState is a boolean: "ON" / "OFF" → true / false.
nexelec:insafe-pilot:1The datalog timestamps datalogEventTimes are computed from the reception time. Point interval:1 is renamed interval.
nke:zcl:1No point is published anymore: BinaryInput:PresentValue:1, Temperature:MeasuredValue:1, OnOff:State:1… were not ontology names. The decoded payload is unchanged.

Drivers​

-​

DriverChangeWhat changed
@actility/ontology-databaseremovedOntology database no longer shipped in the driver catalog (decision of Bruno Régnier) — 4.0.0 shipped @actility/ontology-database, built from ontology/ of device-catalog-private, which is not a driver. The driver catalog now ships drivers only; the removal was decided by Bruno Régnier.

abeeway​

DriverChangeWhat changed
abeeway:asset-tracker-3:1updatedAsset Tracker 3: AT3 firmware v1.5 support and decoding/encoding fixes — Decoder changes made in the public catalog after 4.0.0. TXIF-4158: decoding support for the new features of AT3 firmware v1.5.0 (commit bf4df3ddf). TXIF-4187: 10 encoding/decoding bugs found while reviewing the codec documentation against the AT3 v1.5 reference, among them a missing BLE_STATUS_CONNECTIVITY request, RESET_DEVICE button actions, SECURE_TCP/SECURE_UDP transport values, ANSWER downlinks that crashed decodeDownlink, the SYSTEM_EVENT class enum and the ICCID/IMSI slicing (commit 53ef3f338). TXIF-4181: the frameNumber of the Extended Header was read with a 3-bit mask instead of 4 bits, so values of 8 and above were truncated (commit 6fb0316d9). TXIF-4187 renames the parameter bleBeaconFastSlowInterval to bleBeaconSlowAdvInterval, which its ticket flags as a breaking change for integrations using the old name: accepted as a correction, no new driver version (decision of 2026-09-15).

adeunis​

DriverChangeWhat changed
adeunis:analog:2updateddecoder adds type only when the frame has one; extractPoints tolerates missing alarms; examples state points: null — Changes merged after 4.0.0. The rebuilt adeunis codec bundle adds type to the decoded content only when the frame defines one, which does not change the serialized output (commit 933ae269b, no ticket). extractPoints reads each alarm with optional chaining and requires librairies/extractPoints.js (commits caef6e0c5 and 84a969075, no ticket). Examples say points: null instead of {} for frames without points (TXIF-4088, commit a410ff591, merged after 4.0.0). The bundle also carries the esbuild packaging wrapper (TXIF-4279).
adeunis:breath:1updatedexamples state points: null for frames without ontology points; packaging wrapper only in index.js — Examples regenerated for TXIF-4088 (commit a410ff591, merged after 4.0.0): a frame without points now says points: null instead of {}. The driver code is unchanged: index.js differs from 4.0.0 by the esbuild packaging wrapper only (TXIF-4279).
adeunis:comfort-co2:1updatedextractPoints added: temperature, humidity and CO2 series, daily minimum/maximum/average, alarm values — New extractPoints.js (TXIF-4088, commit a410ff591, merged after 4.0.0), rewritten under TXIF-4280 because the first version yielded no point on any example: it read the decoded { unit, value(s) } objects as numbers. Now published: temperature (Cel), humidity (%RH) and co2Level (ppm) from the periodic frame 0x6a as records; the daily frame 0x30 as temperature/humidity/co2Level :1 minimum, :2 maximum, :3 average with a nature; the value carried by the alarm frame 0x6b with nature "alarm <status>". Examples regenerated. The bundle also carries the esbuild packaging wrapper (TXIF-4279).
adeunis:comfort-serenity:1updatedextractPoints added: temperature, humidity and CO2 series, daily minimum/maximum/average, alarm values (VOC index not published) — New extractPoints.js (TXIF-4088, commit a410ff591, merged after 4.0.0), rewritten under TXIF-4280 because the first version yielded no point on any example: it read the decoded { unit, value(s) } objects as numbers. Now published: temperature (Cel), humidity (%RH) and co2Level (ppm) from the periodic frames 0x6a/0x6f as records; the daily frames 0x30/0x38 as :1 minimum, :2 maximum, :3 average with a nature; the values carried by the alarm frames 0x6b/0x70 with nature "alarm <status>". The VOC index ("index value") has no ontology unit and is not published. Examples regenerated. The bundle also carries the esbuild packaging wrapper (TXIF-4279).
adeunis:comfort:1updatedextractPoints added: temperature and humidity series, and the values of alarm frames — New extractPoints.js (TXIF-4088, commit a410ff591, merged after 4.0.0), rewritten under TXIF-4280 because the first version yielded no point on any example: it read the decoded { unit, value(s) } objects as numbers. Now published: temperature (Cel) and humidity (%RH) from the periodic frame 0x4c as records (t=0, t-1, …), and the value carried by the alarm frame 0x4d with nature "alarm <status>". Examples regenerated. The bundle also carries the esbuild packaging wrapper (TXIF-4279).
adeunis:delta-p:1updatedextractPoints added: differential pressure and 0-10 V input, periodic and alarm values — New extractPoints.js (TXIF-4088, commit a410ff591, merged after 4.0.0), rewritten under TXIF-4280 because the first version yielded no point on any example: it read the decoded { unit, value(s) } objects as numbers. Now published: pressure (Pa, nature "differential") from the periodic frame 0x53 as records and from the alarm frame 0x54; voltage (mV, nature "0-10 V input") from 0x55 and 0x56. The first version used the field deltaPressure in hPa, which is not an ontology field. Examples regenerated. The bundle also carries the esbuild packaging wrapper (TXIF-4279).
adeunis:dry-contacts:2updatedextractPoints added, returning null: the decoded frames carry no ontology point — New extractPoints.js (TXIF-4088, commit a410ff591, merged after 4.0.0) returning null for every frame; examples state points: null. The decoded output is unchanged. The bundle also carries the esbuild packaging wrapper (TXIF-4279).
adeunis:modbus:1updatedextractPoints added, returning null: the decoded frames carry no ontology point — New extractPoints.js (TXIF-4088, commit a410ff591, merged after 4.0.0) returning null for every frame; examples state points: null. The decoded output is unchanged. The bundle also carries the esbuild packaging wrapper (TXIF-4279).
adeunis:modbus:2updatedextractPoints added: the driver now publishes ontology points — New extractPoints.js (TXIF-4088, commit a410ff591, merged after 4.0.0) publishing counter:1, counter:2, counter:3. Examples carry these points, or points: null for frames without any. Additive: the decoded output is unchanged. The bundle also carries the esbuild packaging wrapper (TXIF-4279).
adeunis:motion:1updatedextractPoints added: the driver now publishes ontology points — New extractPoints.js (TXIF-4088, commit a410ff591, merged after 4.0.0) publishing counter. Examples carry these points, or points: null for frames without any. Additive: the decoded output is unchanged. The bundle also carries the esbuild packaging wrapper (TXIF-4279).
adeunis:motion:2updatedextractPoints added: the driver now publishes ontology points — New extractPoints.js (TXIF-4088, commit a410ff591, merged after 4.0.0) publishing counter, illuminance. Examples carry these points, or points: null for frames without any. Additive: the decoded output is unchanged. The bundle also carries the esbuild packaging wrapper (TXIF-4279).
adeunis:pulse:2updatedextractPoints added: the driver now publishes ontology points — New extractPoints.js (TXIF-4088, commit a410ff591, merged after 4.0.0) publishing counter:1, counter:2. Examples carry these points, or points: null for frames without any. Additive: the decoded output is unchanged. The bundle also carries the esbuild packaging wrapper (TXIF-4279).
adeunis:pulse:3updatedextractPoints added: the driver now publishes ontology points — New extractPoints.js (TXIF-4088, commit a410ff591, merged after 4.0.0) publishing counter:1, counter:2. Examples carry these points, or points: null for frames without any. Additive: the decoded output is unchanged. The bundle also carries the esbuild packaging wrapper (TXIF-4279).
adeunis:pulse4:1updatedexamples state points: null for frames without ontology points; packaging wrapper only in index.js — Examples regenerated for TXIF-4088 (commit a410ff591, merged after 4.0.0): a frame without points now says points: null instead of {}. The driver code is unchanged: index.js differs from 4.0.0 by the esbuild packaging wrapper only (TXIF-4279).
adeunis:temp:2updatedextractPoints added: the driver now publishes ontology points — New extractPoints.js (TXIF-4088, commit a410ff591, merged after 4.0.0) publishing temperature:1, temperature:2. Examples carry these points, or points: null for frames without any. Additive: the decoded output is unchanged. The bundle also carries the esbuild packaging wrapper (TXIF-4279).
adeunis:temp:3updatedextractPoints added: the driver now publishes ontology points — New extractPoints.js (TXIF-4088, commit a410ff591, merged after 4.0.0) publishing temperature:1, temperature:2. Examples carry these points, or points: null for frames without any. Additive: the decoded output is unchanged. The bundle also carries the esbuild packaging wrapper (TXIF-4279).
adeunis:temp4:1updatedexamples state points: null for frames without ontology points; packaging wrapper only in index.js — Examples regenerated for TXIF-4088 (commit a410ff591, merged after 4.0.0): a frame without points now says points: null instead of {}. The driver code is unchanged: index.js differs from 4.0.0 by the esbuild packaging wrapper only (TXIF-4279).
adeunis:tic:1updatedextractPoints added: the driver now publishes ontology points — New extractPoints.js (TXIF-4088, commit a410ff591, merged after 4.0.0) publishing energy:1, energy:2, energy:3, energy:4, current:1, current:2. Examples carry these points, or points: null for frames without any. Additive: the decoded output is unchanged. The bundle also carries the esbuild packaging wrapper (TXIF-4279).

advantech​

DriverChangeWhat changed
advantec:eva:1updatedextractPoints publishes points the examples did not carry; driver code unchanged — Points only: the examples are identical to 4.0.0 once their points are set aside, and the bundle differs by index.js: the appended extractPoints. 5 example(s) changed: new points batteryVoltage, current:1, current:2, current:3, temperature, humidity, leak. The extractPoints work of TXIF-4088 touched this driver after the 4.0.0 tag (commits a410ff591, 1eb681a7f, 34b7a1ca2). Recorded under TXIF-4280, the ticket for drivers whose only change is their extractPoints.

arad​

DriverChangeWhat changed
arad:sonata:1updatedextractPoints publishes points the examples did not carry; driver code unchanged — Points only: the examples are identical to 4.0.0 once their points are set aside, and the bundle differs by index.js: the appended extractPoints. 3 example(s) changed: new points batteryLevel; 1 example(s) without point now say points: null instead of {}. The extractPoints work of TXIF-4088 touched this driver after the 4.0.0 tag (commits a410ff591, 1eb681a7f, 34b7a1ca2). Recorded under TXIF-4280, the ticket for drivers whose only change is their extractPoints.

atim​

DriverChangeWhat changed
atim:dinrsm-v2:1updatedpoints updated (extractPoints / examples); driver code unchanged — Points only: the examples are identical to 4.0.0 once their points are set aside, and the bundle differs by index.js: the esbuild wrapper. 2 example(s) changed: 2 example(s) without point now say points: null instead of {}. The extractPoints work of TXIF-4088 touched this driver after the 4.0.0 tag (commit a410ff591). Recorded under TXIF-4280, the ticket for drivers whose only change is their extractPoints.
atim:generic:1updatedpoints updated (extractPoints / examples); driver code unchanged — Points only: the examples are identical to 4.0.0 once their points are set aside, and the bundle differs by index.js: the esbuild wrapper. 21 example(s) changed: 21 example(s) without point now say points: null instead of {}. The extractPoints work of TXIF-4088 touched this driver after the 4.0.0 tag (commit a410ff591). Recorded under TXIF-4280, the ticket for drivers whose only change is their extractPoints.

b-meters​

DriverChangeWhat changed
b-meters:hydrodigit:1updatedHydrodigit S1 codec aligned with the specification (driver error 500) — Commits 83d782955 (align codec with spec) and 4e55cd829 (decode application content), TXIF-4245. Uplink payload: absoluteMeterCounterReverseFlowRatio is no longer published (datapath comparison with 4.0.0, TXIF-4285).
os1-b-me:iwm-lr3:1removedNo longer shipped: no model references this protocolId (commit d0c11e3d3) — The driver is still checked and tested but not packaged since commit d0c11e3d3 (feat(package): ship only what a model points at, 2026-09-10, no ticket): only protocolIds a model.yaml of the public catalog references are shipped. No model references os1-b-me:iwm-lr3:1.

cicicom​

DriverChangeWhat changed
cicicom:s-lg-i3:1updatedpoints updated (extractPoints / examples); driver code unchanged — Points only: the examples are identical to 4.0.0 once their points are set aside, and the bundle differs by index.js: the esbuild wrapper. 5 example(s) changed: changed batteryVoltage (shape). The extractPoints work of TXIF-4088 touched this driver after the 4.0.0 tag (commit a410ff591). Recorded under TXIF-4280, the ticket for drivers whose only change is their extractPoints.

citylone​

DriverChangeWhat changed
citylone:generic:1updatedpoints updated (extractPoints / examples); driver code unchanged — Points only: the examples are identical to 4.0.0 once their points are set aside, and the bundle differs by index.js: the esbuild wrapper. 11 example(s) changed: 11 example(s) without point now say points: null instead of {}. The extractPoints work of TXIF-4088 touched this driver after the 4.0.0 tag (commit a410ff591). Recorded under TXIF-4280, the ticket for drivers whose only change is their extractPoints.

comtac​

DriverChangeWhat changed
os1-comt:lpn-cm4:1updatedpoints updated (extractPoints / examples); driver code unchanged — The driver code is unchanged. What differs from 4.0.0: index.js: the appended extractPoints.
os1-comt:lpn-km:1updatedpoints updated (extractPoints / examples); driver code unchanged — The driver code is unchanged. What differs from 4.0.0: index.js: the appended extractPoints.
os1-comt:lpn-td1:2updatedpoints updated (extractPoints / examples); driver code unchanged — The driver code is unchanged. What differs from 4.0.0: index.js: the appended extractPoints.

dragino​

DriverChangeWhat changed
dragino:sn50v3lbls:1updatedextractPoints publishes points the examples did not carry; driver code unchanged — Points only: the examples are identical to 4.0.0 once their points are set aside, and the bundle differs by index.js: the appended extractPoints. 1 example(s) changed: new points batteryVoltage, voltage. The extractPoints work of TXIF-4088 touched this driver after the 4.0.0 tag (commit a410ff591). Recorded under TXIF-4280, the ticket for drivers whose only change is their extractPoints.

ellenex​

DriverChangeWhat changed
ellenex:pls2-l:1updatedpoints updated (extractPoints / examples); driver code unchanged — What differs from 4.0.0: index.js: appended extractPoints; README.md removed; examples/all.examples.json: points only.
ellenex:pts2-l:1updatedpressure point computed from the device setup; test example with pressure calculation added — The test example "Example with pressure calculation" (commit d7f2aaede) gives the device setup (sensorRange 1000, sensorSpan 1000, sensorZero 0, sensorUnit hPa) from which extractPoints computes the pressure. The setup sat beside input, where neither the driver tester nor the engine read it; it is now in input.thing, and the example publishes pressure 214 hPa next to batteryVoltage, as the Go engine computes it. The two other examples carry no setup and publish batteryVoltage only. index.js differs from 4.0.0 by the packaging wrapper only (TXIF-4279).

elsys​

DriverChangeWhat changed
elsys:generic:1updatedpoints updated (extractPoints / examples); driver code unchanged — What differs from 4.0.0: index.js: appended extractPoints; examples/all.examples.json: points only; uplink.schema.json removed.

elvaco​

DriverChangeWhat changed
elvaco:cmi41xx:1updatedBigInt values published as numbers, so the decoded uplink can be serialized — The customer uplink failed with "Do not know how to serialize a BigInt". The fix (Number(value) instead of the raw bigint) was committed on 2026-04-17 in 084b85ded but never published: the deployed 4.0.0 package still carries the previous line. Driver code is otherwise unchanged.

enless-wireless​

DriverChangeWhat changed
enless-w:600-021:1updatedEnless driver adapted for BACnet (mapping, normalization hook, rebuilt bundle) — Modified during the BACnet adaptations of the Enless drivers (TXIF-4101). What differs from 4.0.0: index.js: index.js source replaced by its bundled build, main.js: rebuilt from that index.js, examples/all.examples.json modified, mapping.json modified. Commits after the 4.0.0 tag on this driver: ef48edf47 (Build Webpack drivers vendors), 63a9d1556 (Build Webpack drivers vendors).
enless-w:600-022:1updatedBACnet mapping and normalization hooks updated; driver code unchanged — What differs from 4.0.0: index.js: esbuild wrapper; main.js: webpack rebuild, sources unchanged; examples/all.examples.json: points only; mapping.json modified.
enless-w:600-023:1updatedBACnet mapping and normalization hooks updated; driver code unchanged — What differs from 4.0.0: index.js: esbuild wrapper; main.js: webpack rebuild, sources unchanged; examples/all.examples.json: points only; mapping.json modified.
enless-w:600-031:1updatedEnless driver adapted for BACnet (mapping, normalization hook, rebuilt bundle) — Modified during the BACnet adaptations of the Enless drivers (TXIF-4101). What differs from 4.0.0: index.js: index.js source replaced by its bundled build, main.js: rebuilt from that index.js, examples/all.examples.json modified, mapping.json modified. Commits after the 4.0.0 tag on this driver: ed75cb527 (Build Webpack drivers vendors), 441941bee (chore(catalog): refresh driver checksums and report).
enless-w:600-032:1updatedBACnet mapping and normalization hooks updated; driver code unchanged — What differs from 4.0.0: index.js: esbuild wrapper; main.js: webpack rebuild, sources unchanged; examples/all.examples.json: points only; mapping.json modified.
enless-w:600-034:1updatedEnless driver adapted for BACnet (mapping, normalization hook, rebuilt bundle) — Modified during the BACnet adaptations of the Enless drivers (TXIF-4101). What differs from 4.0.0: index.js: index.js source replaced by its bundled build, main.js: rebuilt from that index.js, examples/all.examples.json modified, mapping.json modified. Commits after the 4.0.0 tag on this driver: catalog-wide commits only.
enless-w:600-035:1updatedBACnet mapping and normalization hooks updated; driver code unchanged — What differs from 4.0.0: index.js: esbuild wrapper; main.js: webpack rebuild, sources unchanged; examples/all.examples.json: points only; mapping.json modified.
enless-w:600-036:1updatedEnless driver adapted for BACnet (mapping, normalization hook, rebuilt bundle) — Modified during the BACnet adaptations of the Enless drivers (TXIF-4101). What differs from 4.0.0: index.js: identical, main.js: webpack rebuild, examples/all.examples.json modified, mapping.json modified, normalizeUplinkMapping.js added. Commits after the 4.0.0 tag on this driver: ed75cb527 (Build Webpack drivers vendors), 63a9d1556 (Build Webpack drivers vendors).
enless-w:600-037:1updatedEnless driver adapted for BACnet (mapping, normalization hook, rebuilt bundle) — Modified during the BACnet adaptations of the Enless drivers (TXIF-4101). What differs from 4.0.0: index.js: identical, main.js: webpack rebuild, examples/all.examples.json modified, mapping.json modified, normalizeUplinkMapping.js added. Commits after the 4.0.0 tag on this driver: ed75cb527 (Build Webpack drivers vendors).
enless-w:600-038:1updatedEnless driver adapted for BACnet (mapping, normalization hook, rebuilt bundle) — Modified during the BACnet adaptations of the Enless drivers (TXIF-4101). What differs from 4.0.0: index.js: index.js source replaced by its bundled build, main.js: rebuilt from that index.js. Commits after the 4.0.0 tag on this driver: bd8765794 (fix(driver-catalog): align validation and reports).
enless-w:600-039:1updatedEnless driver adapted for BACnet (mapping, normalization hook, rebuilt bundle) — Modified during the BACnet adaptations of the Enless drivers (TXIF-4101). What differs from 4.0.0: index.js: index.js source replaced by its bundled build, main.js: rebuilt from that index.js, examples/all.examples.json modified, mapping.json modified, normalizeUplinkMapping.js added. Commits after the 4.0.0 tag on this driver: bd8765794 (fix(driver-catalog): align validation and reports).
enless-w:600-050:1updatedBACnet mapping and normalization hooks updated; driver code unchanged — What differs from 4.0.0: index.js: esbuild wrapper; main.js: webpack rebuild, sources unchanged; examples/all.examples.json: points only; mapping.json modified.
enless-w:600-051:1updatedBACnet mapping and normalization hooks updated; driver code unchanged — What differs from 4.0.0: index.js: esbuild wrapper; main.js: webpack rebuild, sources unchanged; examples/all.examples.json: points only; mapping.json modified; normalizeUplinkMapping.js added.
enless-w:600-052:1updatedBACnet mapping and normalization hooks updated; driver code unchanged — What differs from 4.0.0: index.js: esbuild wrapper; main.js: webpack rebuild, sources unchanged; examples/all.examples.json: points only; mapping.json modified; normalizeUplinkMapping.js added.
enless-w:600-053:1updatedEnless driver adapted for BACnet (mapping, normalization hook, rebuilt bundle) — Modified during the BACnet adaptations of the Enless drivers (TXIF-4101). What differs from 4.0.0: index.js: index.js source replaced by its bundled build, main.js: rebuilt from that index.js, examples/all.examples.json modified, mapping.json modified, normalizeUplinkMapping.js added. Commits after the 4.0.0 tag on this driver: 441941bee (chore(catalog): refresh driver checksums and report), ac1eaea6a (Fix Enless extractor robustness), c3a053faf (Update Enless driver checksums), 292b266cd (Build Webpack drivers vendors), 3d41024d2 (Build Webpack drivers vendors).
enless-w:600-062:1updatedBACnet mapping and normalization hooks updated; driver code unchanged — What differs from 4.0.0: index.js: esbuild wrapper; main.js: webpack rebuild, sources unchanged; examples/all.examples.json: points only; mapping.json modified; normalizeUplinkMapping.js added.
enless-w:600-065:1updatedBACnet mapping and normalization hooks updated; driver code unchanged — What differs from 4.0.0: index.js: esbuild wrapper; main.js: webpack rebuild, sources unchanged; examples/all.examples.json: points only; mapping.json modified; normalizeUplinkMapping.js added.
enless-w:600-232:1updatedBACnet mapping and normalization hooks updated; driver code unchanged — What differs from 4.0.0: index.js: esbuild wrapper; main.js: webpack rebuild, sources unchanged; examples/all.examples.json: points only; mapping.json modified.

eurecam​

DriverChangeWhat changed
eurecam:comptipix:1updatedextractPoints publishes points the examples did not carry; driver code unchanged — Points only: the examples are identical to 4.0.0 once their points are set aside, and the bundle differs by index.js: the appended extractPoints. 1 example(s) changed: new points counter:1, counter:2, counter:3, counter:4. The extractPoints work of TXIF-4088 touched this driver after the 4.0.0 tag (commits a410ff591, 34b7a1ca2). Recorded under TXIF-4280, the ticket for drivers whose only change is their extractPoints.

fludia​

DriverChangeWhat changed
fludia:fm432e:1updatedpoints updated (extractPoints / examples); driver code unchanged — Points only: the examples are identical to 4.0.0 once their points are set aside, and the bundle differs by index.js: the appended extractPoints. 3 example(s) changed: changed energy:1 (shape), energy:2 (shape), activePower (shape); 1 example(s) without point now say points: null instead of {}. The extractPoints work of TXIF-4088 touched this driver after the 4.0.0 tag (commits a410ff591, 34b7a1ca2). Recorded under TXIF-4280, the ticket for drivers whose only change is their extractPoints.
fludia:fm432g:1updatedpoints updated (extractPoints / examples); driver code unchanged — Points only: the examples are identical to 4.0.0 once their points are set aside, and the bundle differs by index.js: the appended extractPoints. 2 example(s) changed: changed volume:1 (shape), volume:2 (shape); 1 example(s) without point now say points: null instead of {}. The extractPoints work of TXIF-4088 touched this driver after the 4.0.0 tag (commits a410ff591, 34b7a1ca2). Recorded under TXIF-4280, the ticket for drivers whose only change is their extractPoints.
fludia:fm432ir:1updatedpoints updated (extractPoints / examples); driver code unchanged — Points only: the examples are identical to 4.0.0 once their points are set aside, and the bundle differs by index.js: the appended extractPoints. 4 example(s) changed: changed energy:1 (shape), energy:2 (shape), activePower:1 (shape), energy:3 (shape), energy:4 (shape), activePower:2 (shape), activePower (shape); 1 example(s) without point now say points: null instead of {}. The extractPoints work of TXIF-4088 touched this driver after the 4.0.0 tag (commits a410ff591, 34b7a1ca2). Recorded under TXIF-4280, the ticket for drivers whose only change is their extractPoints.
fludia:fm432p:1updatedpoints updated (extractPoints / examples); driver code unchanged — Points only: the examples are identical to 4.0.0 once their points are set aside, and the bundle differs by index.js: the appended extractPoints. 1 example(s) changed: 1 example(s) without point now say points: null instead of {}. The extractPoints work of TXIF-4088 touched this driver after the 4.0.0 tag (commits a410ff591, 34b7a1ca2). Recorded under TXIF-4280, the ticket for drivers whose only change is their extractPoints.

g2misuratori​

DriverChangeWhat changed
g2misura:generic:1updatedpoints updated (extractPoints / examples); driver code unchanged — Points only: the examples are identical to 4.0.0 once their points are set aside, and the bundle differs by index.js: the esbuild wrapper. 1 example(s) changed: 1 example(s) without point now say points: null instead of {}. The extractPoints work of TXIF-4088 touched this driver after the 4.0.0 tag (commit a410ff591). Recorded under TXIF-4280, the ticket for drivers whose only change is their extractPoints.

globalsat​

DriverChangeWhat changed
glbsat:th:1updatedexamples follow the standard output format ({ data }); driver code unchanged — What differs from 4.0.0: index.js: appended extractPoints; examples/all.examples.json: examples in the standard format (output under data); 6 example(s) empty in 4.0.0 now carry their decoded output.

gossenmw​

DriverChangeWhat changed
gossenmw:energymid:1updatedextractPoints added: the driver publishes its points; driver code unchanged — extractPoints.js added on the private side (a410ff591) so the driver reaches the ontology points coverage; the packaged examples move to the standard examples/all.examples.json layout. The decoding code itself is unchanged.

honeywell​

DriverChangeWhat changed
honey-w:HVT-R100:1updatedextractPoints publishes points the examples did not carry; driver code unchanged — Points only: the examples are identical to 4.0.0 once their points are set aside, and the bundle differs by index.js: the appended extractPoints. 1 example(s) changed: new points temperature:1, temperature:2, temperature:3, temperature:4, temperature:5, temperature:6, humidity:1, humidity:2, humidity:3, pressure:1, pressure:2, pressure:3, …. The extractPoints work of TXIF-4088 touched this driver after the 4.0.0 tag (commits a410ff591, 1eb681a7f, 34b7a1ca2). Recorded under TXIF-4280, the ticket for drivers whose only change is their extractPoints.

inbiot​

DriverChangeWhat changed
inbiot:inbiot-decoder:1addedinBiot MICA device family (GitHub PR #283)

invirtus​

DriverChangeWhat changed
invirtus:ivtrack-lite:1updatedpoints updated (extractPoints / examples); driver code unchanged — Points only: the examples are identical to 4.0.0 once their points are set aside, and the bundle differs by index.js: the esbuild wrapper. 2 example(s) changed: 2 example(s) without point now say points: null instead of {}. The extractPoints work of TXIF-4088 touched this driver after the 4.0.0 tag (commit a410ff591). Recorded under TXIF-4280, the ticket for drivers whose only change is their extractPoints.

iot-factory​

DriverChangeWhat changed
iot-fact:generic:1updatedextractPoints publishes points the examples did not carry; driver code unchanged — Points only: the examples are identical to 4.0.0 once their points are set aside, and the bundle differs by index.js: the appended extractPoints. 2 example(s) changed: new points batteryLevel. The extractPoints work of TXIF-4088 touched this driver after the 4.0.0 tag (commits a410ff591, 1eb681a7f, 34b7a1ca2). Recorded under TXIF-4280, the ticket for drivers whose only change is their extractPoints.
iot-fact:m-bus-gateway:1updatedextractPoints publishes points the examples did not carry; driver code unchanged — Points only: the examples are identical to 4.0.0 once their points are set aside, and the bundle differs by index.js: the appended extractPoints. 1 example(s) changed: new points batteryLevel. The extractPoints work of TXIF-4088 touched this driver after the 4.0.0 tag (commits a410ff591, 1eb681a7f, 34b7a1ca2). Recorded under TXIF-4280, the ticket for drivers whose only change is their extractPoints.

jri​

DriverChangeWhat changed
jri:lora-spy-th1:1updatedpoints updated (extractPoints / examples); driver code unchanged — Points only: the examples are identical to 4.0.0 once their points are set aside, and the bundle differs by index.js: the appended extractPoints. 4 example(s) changed: changed time:1 (record). Recorded under TXIF-4280, the ticket for drivers whose only change is their extractPoints.

kamstrup​

DriverChangeWhat changed
kamstrup:generic:1updatedKamstrup HC-003-55 Multical support — Commits 66f0d1e54 and 18b92b520 (Kamstrup HC-003-55 support from GitHub PR #284), TXIF-4162.

laird​

DriverChangeWhat changed
laird:ext-multi:1updatedextractPoints publishes points the examples did not carry; driver code unchanged — Points only: the examples are identical to 4.0.0 once their points are set aside, and the bundle differs by index.js: the appended extractPoints. 8 example(s) changed: new points temperature, humidity; 6 example(s) without point now say points: null instead of {}. The extractPoints work of TXIF-4088 touched this driver after the 4.0.0 tag (commits a410ff591, 1eb681a7f, 34b7a1ca2). Recorded under TXIF-4280, the ticket for drivers whose only change is their extractPoints.
laird:ext-temp-rtd:1updatedextractPoints publishes points the examples did not carry; driver code unchanged — Points only: the examples are identical to 4.0.0 once their points are set aside, and the bundle differs by index.js: the appended extractPoints. 6 example(s) changed: new points temperature, batteryVoltage; 4 example(s) without point now say points: null instead of {}. The extractPoints work of TXIF-4088 touched this driver after the 4.0.0 tag (commits a410ff591, 1eb681a7f, 34b7a1ca2). Recorded under TXIF-4280, the ticket for drivers whose only change is their extractPoints.
os1-lair:rs1xx-ext-multi:1removedNo longer shipped: no model references this protocolId (commit d0c11e3d3) — The driver is still checked and tested but not packaged since commit d0c11e3d3 (feat(package): ship only what a model points at, 2026-09-10, no ticket): only protocolIds a model.yaml of the public catalog references are shipped. No model references os1-lair:rs1xx-ext-multi:1.
os1-lair:rs1xx-ext-temp-1:1removedNo longer shipped: no model references this protocolId (commit d0c11e3d3) — The driver is still checked and tested but not packaged since commit d0c11e3d3 (feat(package): ship only what a model points at, 2026-09-10, no ticket): only protocolIds a model.yaml of the public catalog references are shipped. No model references os1-lair:rs1xx-ext-temp-1:1.
os1-lair:rs1xx-ext-temp-r:1removedNo longer shipped: no model references this protocolId (commit d0c11e3d3) — The driver is still checked and tested but not packaged since commit d0c11e3d3 (feat(package): ship only what a model points at, 2026-09-10, no ticket): only protocolIds a model.yaml of the public catalog references are shipped. No model references os1-lair:rs1xx-ext-temp-r:1.
os1-lair:rs1xx-temp-rh-se:1removedNo longer shipped: no model references this protocolId (commit d0c11e3d3) — The driver is still checked and tested but not packaged since commit d0c11e3d3 (feat(package): ship only what a model points at, 2026-09-10, no ticket): only protocolIds a model.yaml of the public catalog references are shipped. No model references os1-lair:rs1xx-temp-rh-se:1.

langyang​

DriverChangeWhat changed
langyang:smart-meter:5updatedpoints updated (extractPoints / examples); driver code unchanged — Points only: the examples are identical to 4.0.0 once their points are set aside, and the bundle differs by index.js: the appended extractPoints. 9 example(s) changed: 9 example(s) without point now say points: null instead of {}. The extractPoints work of TXIF-4088 touched this driver after the 4.0.0 tag (commit a410ff591). Recorded under TXIF-4280, the ticket for drivers whose only change is their extractPoints.

liebearth​

DriverChangeWhat changed
lbearth:generic:1updatedextractPoints publishes points the examples did not carry; driver code unchanged — Points only: the examples are identical to 4.0.0 once their points are set aside, and the bundle differs by index.js: the appended extractPoints. 3 example(s) changed: new points batteryLevel, humidity, humidity:1; 1 example(s) without point now say points: null instead of {}. The extractPoints work of TXIF-4088 touched this driver after the 4.0.0 tag (commits a410ff591, 1eb681a7f, 34b7a1ca2). Recorded under TXIF-4280, the ticket for drivers whose only change is their extractPoints.

lobaro​

DriverChangeWhat changed
lobaro:hyb-ind-gateway:1updatedpoints updated (extractPoints / examples); driver code unchanged — Points only: the examples are identical to 4.0.0 once their points are set aside, and the bundle differs by index.js: the appended extractPoints. 11 example(s) changed: 11 example(s) without point now say points: null instead of {}. The extractPoints work of TXIF-4088 touched this driver after the 4.0.0 tag (commits a410ff591, 34b7a1ca2). Recorded under TXIF-4280, the ticket for drivers whose only change is their extractPoints.

maddalena​

DriverChangeWhat changed
mdlna:arrowwan2:1updateddecoded alarm field errors renamed alarms, Mixed frame (fPort 6) decoded — Requested for the Techem POC on TPE SAAS EU (TXIF-4272). The Node.js driver engine read the alarm names the driver published in data.errors (e.g. "NoConsumption") as decoding errors and rejected the message (com-5000 "driver internal errors"): on that engine every frame carrying an alarm produced no payload at all. The Go driver engine does not have this defect. Fix by Hoang Quy Nguyen (8232cb40e, 2026-09-11), package 1.1.5 injected on TPE SAAS EU on 2026-09-15: the alarm field of the daily (fPort 1, 2), weekly (fPort 5) and event (fPort 9) frames is now data.alarms, same values ("Leakage", "Mechanical Fraud", "NoConsumption"...). Breaking for an integration reading data.errors on a Go-engine platform, where the field used to work; a correction on a Node-engine platform, where those frames used to be rejected. Also in 1.1.5: the Mixed measurement frame (fPort 6, Electo data frames specification v1.9 section 3.1), which 4.0.0 answered with "Missing decoder for frame on port 6", is decoded (battery voltage, RSSI, current and reverse readouts, 6 hourly and 5 weekly readings); the previous-day end-of-day readout and the event current readout are read unsigned as the specification states; extractPoints rewritten on the ontology (flowRate in m3/h, forward and reverse volume, battery voltage). Info frame (fPort 8) unchanged. Known and unchanged since 4.0.0, not addressed here: the timestamps of fPort 1, 2, 5, 8 and 9 carry a fixed +1 h (readings +2 h) and no zone suffix while fPort 6 is UTC; the weekly base readout is still read signed; alarm labels differ from the specification wording.

mclimate​

DriverChangeWhat changed
mclimate:16a-dry-switch:1updatedMClimate driver updated from the manufacturer's driver, with its BACnet overlay — The MClimate range was updated from the manufacturer's drivers, together with its BACnet overlay (TXIF-4101). What differs from 4.0.0: examples/all.examples.json modified, index.js modified, mapping.json added. Commits after the 4.0.0 tag on this driver: e1d7dd50f (chore(mclimate): retire co2-sensor-v2, and record the renamed points), 4517f5548 (feat(mclimate): a protocol mapping for every model that had none), 04de051da (feat(mclimate): name what the indexed points measure). Uplink payload: relayState is now a boolean (true/false) instead of "ON"/"OFF" (datapath comparison with 4.0.0, TXIF-4285).
mclimate:16a-spm:1updatedpoints updated (extractPoints / examples); driver code unchanged — Points only: the examples are identical to 4.0.0 once their points are set aside, and the bundle differs by index.js: the appended extractPoints. 1 example(s) changed: changed temperature (nature). Recorded under TXIF-4280, the ticket for drivers whose only change is their extractPoints.
mclimate:16a-spm:2addedMClimate manufacturer drivers, BACnet and points overlay — Manufacturer drivers for the MClimate devices, with the private extractPoints and BACnet mapping on the manufacturer driver only (the OS1 driver no longer carries the mapping).
mclimate:aqi-sensor:1updatedMClimate driver updated from the manufacturer's driver, with its BACnet overlay — The MClimate range was updated from the manufacturer's drivers, together with its BACnet overlay (TXIF-4101). What differs from 4.0.0: examples/all.examples.json modified, index.js modified. Commits after the 4.0.0 tag on this driver: 8e3709d29 (Correct detected LoRa Alliance driver signatures).
mclimate:co2-display-lite:1updatedMClimate driver updated from the manufacturer's driver, with its BACnet overlay — The MClimate range was updated from the manufacturer's drivers, together with its BACnet overlay (TXIF-4101). What differs from 4.0.0: examples/all.examples.json modified, index.js modified, mapping.json added. Commits after the 4.0.0 tag on this driver: 4517f5548 (feat(mclimate): a protocol mapping for every model that had none).
mclimate:co2-display:2addedMClimate manufacturer drivers, BACnet and points overlay — Manufacturer drivers for the MClimate devices, with the private extractPoints and BACnet mapping on the manufacturer driver only (the OS1 driver no longer carries the mapping).
mclimate:co2-notifier:1updatedMClimate driver updated from the manufacturer's driver, with its BACnet overlay — The MClimate range was updated from the manufacturer's drivers, together with its BACnet overlay (TXIF-4101). What differs from 4.0.0: examples/all.examples.json modified, index.js modified, mapping.json added. Commits after the 4.0.0 tag on this driver: 4517f5548 (feat(mclimate): a protocol mapping for every model that had none).
mclimate:co2-pir-lite:1updatedMClimate driver updated from the manufacturer's driver, with its BACnet overlay — The MClimate range was updated from the manufacturer's drivers, together with its BACnet overlay (TXIF-4101). What differs from 4.0.0: examples/all.examples.json modified, index.js modified, mapping.json added. Commits after the 4.0.0 tag on this driver: 4517f5548 (feat(mclimate): a protocol mapping for every model that had none).
mclimate:fan-coil:1updatedMClimate driver updated from the manufacturer's driver, with its BACnet overlay — The MClimate range was updated from the manufacturer's drivers, together with its BACnet overlay (TXIF-4101). What differs from 4.0.0: examples/all.examples.json modified, index.js modified, mapping.json added. Commits after the 4.0.0 tag on this driver: dde6990a1 (chore(mclimate): record fan-coil's external sensor point), 52a564376 (feat(mclimate): fan-coil publishes its external sensor temperature), 4517f5548 (feat(mclimate): a protocol mapping for every model that had none), 04de051da (feat(mclimate): name what the indexed points measure).
mclimate:flood-sensor:1updatedMClimate driver updated from the manufacturer's driver, with its BACnet overlay — The MClimate range was updated from the manufacturer's drivers, together with its BACnet overlay (TXIF-4101). What differs from 4.0.0: examples/all.examples.json modified, index.js modified, mapping.json added. Commits after the 4.0.0 tag on this driver: 4517f5548 (feat(mclimate): a protocol mapping for every model that had none), 8e3709d29 (Correct detected LoRa Alliance driver signatures).
mclimate:ht-pir-lite:1updatedMClimate driver updated from the manufacturer's driver, with its BACnet overlay — The MClimate range was updated from the manufacturer's drivers, together with its BACnet overlay (TXIF-4101). What differs from 4.0.0: examples/all.examples.json modified, index.js modified, mapping.json added. Commits after the 4.0.0 tag on this driver: 4517f5548 (feat(mclimate): a protocol mapping for every model that had none).
mclimate:ht-sensor:2addedMClimate manufacturer drivers, BACnet and points overlay — Manufacturer drivers for the MClimate devices, with the private extractPoints and BACnet mapping on the manufacturer driver only (the OS1 driver no longer carries the mapping).
mclimate:multipurpose-btn:1updatedMClimate driver updated from the manufacturer's driver, with its BACnet overlay — The MClimate range was updated from the manufacturer's drivers, together with its BACnet overlay (TXIF-4101). What differs from 4.0.0: examples/all.examples.json modified, index.js modified, mapping.json added. Commits after the 4.0.0 tag on this driver: 4517f5548 (feat(mclimate): a protocol mapping for every model that had none).
mclimate:open-close:1updatedpoints updated (extractPoints / examples); driver code unchanged — Points only: the examples are identical to 4.0.0 once their points are set aside, and the bundle differs by index.js: the appended extractPoints. 1 example(s) changed: changed counter (nature). Recorded under TXIF-4280, the ticket for drivers whose only change is their extractPoints.
mclimate:open-close:2addedMClimate manufacturer drivers, BACnet and points overlay — Manufacturer drivers for the MClimate devices, with the private extractPoints and BACnet mapping on the manufacturer driver only (the OS1 driver no longer carries the mapping).
mclimate:pir-mini:1addedMClimate manufacturer drivers, BACnet and points overlay — Manufacturer drivers for the MClimate devices, with the private extractPoints and BACnet mapping on the manufacturer driver only (the OS1 driver no longer carries the mapping).
mclimate:t-valve:1updatedMClimate driver updated from the manufacturer's driver, with its BACnet overlay — The MClimate range was updated from the manufacturer's drivers, together with its BACnet overlay (TXIF-4101). What differs from 4.0.0: examples/all.examples.json modified, index.js modified, mapping.json added. Commits after the 4.0.0 tag on this driver: 46a3f2d3c (chore(mclimate): record the new t-valve and ht-sensor points), 4517f5548 (feat(mclimate): a protocol mapping for every model that had none), 7f0129de2 (fix(mclimate): t-valve's two temperatures are Celsius, and decimal), f58e74614 (feat(mclimate): expose the measurements t-valve and ht-sensor already ).
mclimate:vicki:1updatedpoints updated (extractPoints / examples); driver code unchanged — Points only: the examples are identical to 4.0.0 once their points are set aside, and the bundle differs by index.js: the appended extractPoints. 1 example(s) changed: changed temperature:1 (nature), temperature:2 (nature), angle:1 (nature), angle:2 (nature), status:1 (nature), status:2 (nature), status:3 (nature), status:4 (nature), …. Recorded under TXIF-4280, the ticket for drivers whose only change is their extractPoints.
mclimate:vicki:2addedMClimate manufacturer drivers, BACnet and points overlay — Manufacturer drivers for the MClimate devices, with the private extractPoints and BACnet mapping on the manufacturer driver only (the OS1 driver no longer carries the mapping).
mclimate:w-thermostat:1updatedMClimate driver updated from the manufacturer's driver, with its BACnet overlay — The MClimate range was updated from the manufacturer's drivers, together with its BACnet overlay (TXIF-4101). What differs from 4.0.0: examples/all.examples.json modified, index.js modified, mapping.json added. Commits after the 4.0.0 tag on this driver: e1d7dd50f (chore(mclimate): retire co2-sensor-v2, and record the renamed points), 4517f5548 (feat(mclimate): a protocol mapping for every model that had none).
os1-mcli:aqi-sensor:1removedNo longer shipped: no model references this protocolId (commit d0c11e3d3) — The driver is still checked and tested but not packaged since commit d0c11e3d3 (feat(package): ship only what a model points at, 2026-09-10, no ticket): only protocolIds a model.yaml of the public catalog references are shipped. No model references os1-mcli:aqi-sensor:1; in 4.0.0 vendors/mclimate/models/aqi-sensor did, it has been retargeted since (devices provisioned on os1-mcli:aqi-sensor:1 keep that protocolId).
os1-mcli:fan-coil:1removedNo longer shipped: no model references this protocolId (commit d0c11e3d3) — The driver is still checked and tested but not packaged since commit d0c11e3d3 (feat(package): ship only what a model points at, 2026-09-10, no ticket): only protocolIds a model.yaml of the public catalog references are shipped. No model references os1-mcli:fan-coil:1; in 4.0.0 vendors/mclimate/models/fan-coil did, it has been retargeted since (devices provisioned on os1-mcli:fan-coil:1 keep that protocolId).
os1-mcli:flood-sensor:1removedNo longer shipped: no model references this protocolId (commit d0c11e3d3) — The driver is still checked and tested but not packaged since commit d0c11e3d3 (feat(package): ship only what a model points at, 2026-09-10, no ticket): only protocolIds a model.yaml of the public catalog references are shipped. No model references os1-mcli:flood-sensor:1; in 4.0.0 vendors/mclimate/models/flood-sensor did, it has been retargeted since (devices provisioned on os1-mcli:flood-sensor:1 keep that protocolId).
os1-mcli:t-valve:1removedNo longer shipped: no model references this protocolId (commit d0c11e3d3) — The driver is still checked and tested but not packaged since commit d0c11e3d3 (feat(package): ship only what a model points at, 2026-09-10, no ticket): only protocolIds a model.yaml of the public catalog references are shipped. No model references os1-mcli:t-valve:1; in 4.0.0 vendors/mclimate/models/t-valve did, it has been retargeted since (devices provisioned on os1-mcli:t-valve:1 keep that protocolId).
os1-mcli:vicki:1updatedBACnet mapping carried by the model's first protocolId; driver code unchanged — The driver code is unchanged. What differs from 4.0.0: index.js: the esbuild wrapper; mapping.json removed: the BACnet mapping is carried by the first protocolId of the model (its BACnet owner), not by this driver.

merryiot​

DriverChangeWhat changed
merryiot:cd10:1updatedextractPoints publishes points the examples did not carry; driver code unchanged — Points only: the examples are identical to 4.0.0 once their points are set aside, and the bundle differs by index.js: the appended extractPoints. 1 example(s) changed: new points batteryVoltage, temperature, humidity, co2Level. Recorded under TXIF-4280, the ticket for drivers whose only change is their extractPoints.
merryiot:dw10:1updatedextractPoints publishes points the examples did not carry; driver code unchanged — Points only: the examples are identical to 4.0.0 once their points are set aside, and the bundle differs by index.js: the appended extractPoints. 1 example(s) changed: new points batteryVoltage, temperature, humidity, time, counter. Recorded under TXIF-4280, the ticket for drivers whose only change is their extractPoints.
merryiot:ms10:1updatedextractPoints publishes points the examples did not carry; driver code unchanged — Points only: the examples are identical to 4.0.0 once their points are set aside, and the bundle differs by index.js: the appended extractPoints. 1 example(s) changed: new points batteryVoltage, temperature, humidity, time, counter. Recorded under TXIF-4280, the ticket for drivers whose only change is their extractPoints.
merryiot:wl10:1updatedpoints updated (extractPoints / examples); driver code unchanged — Points only: the examples are identical to 4.0.0 once their points are set aside, and the bundle differs by index.js: the appended extractPoints. 1 example(s) changed: changed temperature (record), humidity (record). Recorded under TXIF-4280, the ticket for drivers whose only change is their extractPoints.

milesight-iot​

DriverChangeWhat changed
msight:am100-series:1updatedBACnet mapping carried by the model's first protocolId; driver code unchanged — The driver code is unchanged. What differs from 4.0.0: index.js: the esbuild wrapper; mapping.json removed: the BACnet mapping is carried by the first protocolId of the model (its BACnet owner), not by this driver.
msight:am102:1updatedMilesight driver realignment on SensorDecoders and encoder fixes — What differs from 4.0.0: driver code changed by e5f3850d3 (Milesight v2, filed as TXIF-4166 by mistake: add Milesight v2 drivers ), e49328bd4 (TXIF-4100: Fix encodeDownlink fPort fallback across all Milesight IoT ); mapping.json removed.
msight:am102:2addedMilesight SensorDecoders v2 drivers, next to the existing v1/TTN implementations — New drivers built on Milesight's current SensorDecoders code (2025), kept beside the v1 drivers so deployed devices stay on the protocolId they were provisioned with. Public examples, private extractPoints, normalization hooks and BACnet mappings.
msight:am102l:1updatedMilesight driver realignment on SensorDecoders and encoder fixes — What differs from 4.0.0: driver code changed by e5f3850d3 (Milesight v2, filed as TXIF-4166 by mistake: add Milesight v2 drivers ), e49328bd4 (TXIF-4100: Fix encodeDownlink fPort fallback across all Milesight IoT ); mapping.json removed.
msight:am102l:2addedMilesight SensorDecoders v2 drivers, next to the existing v1/TTN implementations — New drivers built on Milesight's current SensorDecoders code (2025), kept beside the v1 drivers so deployed devices stay on the protocolId they were provisioned with. Public examples, private extractPoints, normalization hooks and BACnet mappings.
msight:am103:1addedMilesight drivers missing from the 4.0.0 catalog, taken from Milesight's SensorDecoders — Drivers present in Milesight's SensorDecoders repository but absent from the released catalog: decoder, examples, private extractPoints and BACnet mapping.
msight:am103l:1addedMilesight drivers missing from the 4.0.0 catalog, taken from Milesight's SensorDecoders — Drivers present in Milesight's SensorDecoders repository but absent from the released catalog: decoder, examples, private extractPoints and BACnet mapping.
msight:am104:1addedMilesight drivers missing from the 4.0.0 catalog, taken from Milesight's SensorDecoders — Drivers present in Milesight's SensorDecoders repository but absent from the released catalog: decoder, examples, private extractPoints and BACnet mapping.
msight:am107:1addedMilesight drivers missing from the 4.0.0 catalog, taken from Milesight's SensorDecoders — Drivers present in Milesight's SensorDecoders repository but absent from the released catalog: decoder, examples, private extractPoints and BACnet mapping.
msight:am300-series:1updatedexamples replayed on Milesight's current codec; BACnet mapping moved to the owner — Examples regenerated from Milesight's current SensorDecoders payloads (e5f3850d3, whose TXIF-4166 is a typo for TXIF-4099), so their bytes and the points they carry change. mapping.json is gone from the package: the BACnet mapping belongs to the first protocolId of the model (TXIF-4101). index.js differs only by its appended extractPoints; the driver code is unchanged.
msight:am304l:1addedMilesight drivers missing from the 4.0.0 catalog, taken from Milesight's SensorDecoders — Drivers present in Milesight's SensorDecoders repository but absent from the released catalog: decoder, examples, private extractPoints and BACnet mapping.
msight:am305l:1addedMilesight drivers missing from the 4.0.0 catalog, taken from Milesight's SensorDecoders — Drivers present in Milesight's SensorDecoders repository but absent from the released catalog: decoder, examples, private extractPoints and BACnet mapping.
msight:am307:1addedMilesight drivers missing from the 4.0.0 catalog, taken from Milesight's SensorDecoders — Drivers present in Milesight's SensorDecoders repository but absent from the released catalog: decoder, examples, private extractPoints and BACnet mapping.
msight:am307l:1addedMilesight drivers missing from the 4.0.0 catalog, taken from Milesight's SensorDecoders — Drivers present in Milesight's SensorDecoders repository but absent from the released catalog: decoder, examples, private extractPoints and BACnet mapping.
msight:am308:1addedMilesight drivers missing from the 4.0.0 catalog, taken from Milesight's SensorDecoders — Drivers present in Milesight's SensorDecoders repository but absent from the released catalog: decoder, examples, private extractPoints and BACnet mapping.
msight:am308l:1addedMilesight drivers missing from the 4.0.0 catalog, taken from Milesight's SensorDecoders — Drivers present in Milesight's SensorDecoders repository but absent from the released catalog: decoder, examples, private extractPoints and BACnet mapping.
msight:am319-hcho-ir:1addedMilesight drivers missing from the 4.0.0 catalog, taken from Milesight's SensorDecoders — Drivers present in Milesight's SensorDecoders repository but absent from the released catalog: decoder, examples, private extractPoints and BACnet mapping.
msight:am319-hcho-well:1addedMilesight drivers missing from the 4.0.0 catalog, taken from Milesight's SensorDecoders — Drivers present in Milesight's SensorDecoders repository but absent from the released catalog: decoder, examples, private extractPoints and BACnet mapping.
msight:am319-hcho:1addedMilesight drivers missing from the 4.0.0 catalog, taken from Milesight's SensorDecoders — Drivers present in Milesight's SensorDecoders repository but absent from the released catalog: decoder, examples, private extractPoints and BACnet mapping.
msight:am319-o3:1addedMilesight drivers missing from the 4.0.0 catalog, taken from Milesight's SensorDecoders — Drivers present in Milesight's SensorDecoders repository but absent from the released catalog: decoder, examples, private extractPoints and BACnet mapping.
msight:am319l-hcho-ir:1addedMilesight drivers missing from the 4.0.0 catalog, taken from Milesight's SensorDecoders — Drivers present in Milesight's SensorDecoders repository but absent from the released catalog: decoder, examples, private extractPoints and BACnet mapping.
msight:am319l-o3:1addedMilesight drivers missing from the 4.0.0 catalog, taken from Milesight's SensorDecoders — Drivers present in Milesight's SensorDecoders repository but absent from the released catalog: decoder, examples, private extractPoints and BACnet mapping.
msight:at101:1updatedMilesight driver realignment on SensorDecoders and encoder fixes — What differs from 4.0.0: driver code changed by e49328bd4 (TXIF-4100: Fix encodeDownlink fPort fallback across all Milesight IoT ).
msight:at101:2addedMilesight SensorDecoders v2 drivers, next to the existing v1/TTN implementations — New drivers built on Milesight's current SensorDecoders code (2025), kept beside the v1 drivers so deployed devices stay on the protocolId they were provisioned with. Public examples, private extractPoints, normalization hooks and BACnet mappings.
msight:ct101:1updatedMilesight driver realignment on SensorDecoders and encoder fixes — What differs from 4.0.0: driver code changed by e5f3850d3 (Milesight v2, filed as TXIF-4166 by mistake: add Milesight v2 drivers ), e49328bd4 (TXIF-4100: Fix encodeDownlink fPort fallback across all Milesight IoT ); mapping.json removed.
msight:ct101:2addedMilesight SensorDecoders v2 drivers, next to the existing v1/TTN implementations — New drivers built on Milesight's current SensorDecoders code (2025), kept beside the v1 drivers so deployed devices stay on the protocolId they were provisioned with. Public examples, private extractPoints, normalization hooks and BACnet mappings.
msight:ct103:1updatedMilesight driver realignment on SensorDecoders and encoder fixes — What differs from 4.0.0: driver code changed by e5f3850d3 (Milesight v2, filed as TXIF-4166 by mistake: add Milesight v2 drivers ), e49328bd4 (TXIF-4100: Fix encodeDownlink fPort fallback across all Milesight IoT ); mapping.json removed.
msight:ct103:2addedMilesight SensorDecoders v2 drivers, next to the existing v1/TTN implementations — New drivers built on Milesight's current SensorDecoders code (2025), kept beside the v1 drivers so deployed devices stay on the protocolId they were provisioned with. Public examples, private extractPoints, normalization hooks and BACnet mappings.
msight:ct105:1updatedMilesight driver realignment on SensorDecoders and encoder fixes — What differs from 4.0.0: driver code changed by e5f3850d3 (Milesight v2, filed as TXIF-4166 by mistake: add Milesight v2 drivers ), e49328bd4 (TXIF-4100: Fix encodeDownlink fPort fallback across all Milesight IoT ); mapping.json removed.
msight:ct105:2addedMilesight SensorDecoders v2 drivers, next to the existing v1/TTN implementations — New drivers built on Milesight's current SensorDecoders code (2025), kept beside the v1 drivers so deployed devices stay on the protocolId they were provisioned with. Public examples, private extractPoints, normalization hooks and BACnet mappings.
msight:ct303:1updatedMilesight driver realignment on SensorDecoders and encoder fixes — What differs from 4.0.0: driver code changed by e5f3850d3 (Milesight v2, filed as TXIF-4166 by mistake: add Milesight v2 drivers ), e49328bd4 (TXIF-4100: Fix encodeDownlink fPort fallback across all Milesight IoT ); mapping.json removed.
msight:ct303:2addedMilesight SensorDecoders v2 drivers, next to the existing v1/TTN implementations — New drivers built on Milesight's current SensorDecoders code (2025), kept beside the v1 drivers so deployed devices stay on the protocolId they were provisioned with. Public examples, private extractPoints, normalization hooks and BACnet mappings.
msight:ct305:1updatedMilesight driver realignment on SensorDecoders and encoder fixes — What differs from 4.0.0: driver code changed by e5f3850d3 (Milesight v2, filed as TXIF-4166 by mistake: add Milesight v2 drivers ), e49328bd4 (TXIF-4100: Fix encodeDownlink fPort fallback across all Milesight IoT ); mapping.json removed.
msight:ct305:2addedMilesight SensorDecoders v2 drivers, next to the existing v1/TTN implementations — New drivers built on Milesight's current SensorDecoders code (2025), kept beside the v1 drivers so deployed devices stay on the protocolId they were provisioned with. Public examples, private extractPoints, normalization hooks and BACnet mappings.
msight:ct310:1updatedMilesight driver realignment on SensorDecoders and encoder fixes — What differs from 4.0.0: driver code changed by e5f3850d3 (Milesight v2, filed as TXIF-4166 by mistake: add Milesight v2 drivers ), e49328bd4 (TXIF-4100: Fix encodeDownlink fPort fallback across all Milesight IoT ); mapping.json removed.
msight:ct310:2addedMilesight SensorDecoders v2 drivers, next to the existing v1/TTN implementations — New drivers built on Milesight's current SensorDecoders code (2025), kept beside the v1 drivers so deployed devices stay on the protocolId they were provisioned with. Public examples, private extractPoints, normalization hooks and BACnet mappings.
msight:cth01-compress:1addedMilesight SensorDecoders drivers, first publication — Drivers built on Milesight's current SensorDecoders code and never published before: published as v1. Public examples, private extractPoints, normalization hooks and BACnet mappings.
msight:cth01:1addedMilesight SensorDecoders drivers, first publication — Drivers built on Milesight's current SensorDecoders code and never published before: published as v1. Public examples, private extractPoints, normalization hooks and BACnet mappings.
msight:ds3604:1addedMilesight drivers missing from the 4.0.0 catalog, taken from Milesight's SensorDecoders — Drivers present in Milesight's SensorDecoders repository but absent from the released catalog: decoder, examples, private extractPoints and BACnet mapping.
msight:em300-cl:1addedMilesight drivers missing from the 4.0.0 catalog, taken from Milesight's SensorDecoders — Drivers present in Milesight's SensorDecoders repository but absent from the released catalog: decoder, examples, private extractPoints and BACnet mapping.
msight:em300-di-hall:1addedMilesight drivers missing from the 4.0.0 catalog, taken from Milesight's SensorDecoders — Drivers present in Milesight's SensorDecoders repository but absent from the released catalog: decoder, examples, private extractPoints and BACnet mapping.
msight:em300-di:1updatedMilesight driver realignment on SensorDecoders and encoder fixes — What differs from 4.0.0: driver code changed by e5f3850d3 (Milesight v2, filed as TXIF-4166 by mistake: add Milesight v2 drivers ), e49328bd4 (TXIF-4100: Fix encodeDownlink fPort fallback across all Milesight IoT ); mapping.json modified; normalizeDownlinkMapping.js added; normalizeUplinkMapping.js added.
msight:em300-mcs:1updatedMilesight driver realignment on SensorDecoders and encoder fixes — What differs from 4.0.0: driver code changed by e5f3850d3 (Milesight v2, filed as TXIF-4166 by mistake: add Milesight v2 drivers ), 624411b62 (Milesight v2, filed as TXIF-4166 by mistake: add Milesight v2 drivers ), d3ba1d286 (TXIF-4099: Milesight driver catalog realignment — replace TTN drivers ), 765d594be (TXIF-4099 / RDTP-26187: Fix ws202 PIR/daylight BACnet compatibility + ); mapping.json removed.
msight:em300-mcs:2addedMilesight SensorDecoders v2 drivers, next to the existing v1/TTN implementations — New drivers built on Milesight's current SensorDecoders code (2025), kept beside the v1 drivers so deployed devices stay on the protocolId they were provisioned with. Public examples, private extractPoints, normalization hooks and BACnet mappings.
msight:em300-mld:1updatedMilesight driver realignment on SensorDecoders and encoder fixes — What differs from 4.0.0: driver code changed by e5f3850d3 (Milesight v2, filed as TXIF-4166 by mistake: add Milesight v2 drivers ), e49328bd4 (TXIF-4100: Fix encodeDownlink fPort fallback across all Milesight IoT ); mapping.json removed.
msight:em300-mld:2addedMilesight SensorDecoders v2 drivers, next to the existing v1/TTN implementations — New drivers built on Milesight's current SensorDecoders code (2025), kept beside the v1 drivers so deployed devices stay on the protocolId they were provisioned with. Public examples, private extractPoints, normalization hooks and BACnet mappings.
msight:em300-sld:1updatedMilesight driver realignment on SensorDecoders and encoder fixes — What differs from 4.0.0: driver code changed by e5f3850d3 (Milesight v2, filed as TXIF-4166 by mistake: add Milesight v2 drivers ), 624411b62 (Milesight v2, filed as TXIF-4166 by mistake: add Milesight v2 drivers ), d3ba1d286 (TXIF-4099: Milesight driver catalog realignment — replace TTN drivers ), 765d594be (TXIF-4099 / RDTP-26187: Fix ws202 PIR/daylight BACnet compatibility + ); mapping.json removed.
msight:em300-sld:2addedMilesight SensorDecoders v2 drivers, next to the existing v1/TTN implementations — New drivers built on Milesight's current SensorDecoders code (2025), kept beside the v1 drivers so deployed devices stay on the protocolId they were provisioned with. Public examples, private extractPoints, normalization hooks and BACnet mappings.
msight:em300-th:1updatedMilesight driver realignment on SensorDecoders and encoder fixes — What differs from 4.0.0: driver code changed by e5f3850d3 (Milesight v2, filed as TXIF-4166 by mistake: add Milesight v2 drivers ), d3ba1d286 (TXIF-4099: Milesight driver catalog realignment — replace TTN drivers ), a737e75dc (TXIF-4099: Milesight extractPoints, check-signatures and changelogs), 2bd1390a9 (TXIF-4099 / RDTP-26187: Fix extractPoints format + ws202 BACnet PIR fi); mapping.json modified; normalizeDownlinkMapping.js added; normalizeUplinkMapping.js added.
msight:em300-zld:1addedMilesight drivers missing from the 4.0.0 catalog, taken from Milesight's SensorDecoders — Drivers present in Milesight's SensorDecoders repository but absent from the released catalog: decoder, examples, private extractPoints and BACnet mapping.
msight:em310-tilt:1updatedMilesight driver realignment on SensorDecoders and encoder fixes — What differs from 4.0.0: driver code changed by e5f3850d3 (Milesight v2, filed as TXIF-4166 by mistake: add Milesight v2 drivers ), d3ba1d286 (TXIF-4099: Milesight driver catalog realignment — replace TTN drivers ), a737e75dc (TXIF-4099: Milesight extractPoints, check-signatures and changelogs), 2bd1390a9 (TXIF-4099 / RDTP-26187: Fix extractPoints format + ws202 BACnet PIR fi); mapping.json removed.
msight:em310-tilt:2addedMilesight SensorDecoders v2 drivers, next to the existing v1/TTN implementations — New drivers built on Milesight's current SensorDecoders code (2025), kept beside the v1 drivers so deployed devices stay on the protocolId they were provisioned with. Public examples, private extractPoints, normalization hooks and BACnet mappings.
msight:em310-udl:1updatedMilesight driver realignment on SensorDecoders and encoder fixes — What differs from 4.0.0: driver code changed by e5f3850d3 (Milesight v2, filed as TXIF-4166 by mistake: add Milesight v2 drivers ), d3ba1d286 (TXIF-4099: Milesight driver catalog realignment — replace TTN drivers ), e49328bd4 (TXIF-4100: Fix encodeDownlink fPort fallback across all Milesight IoT ); mapping.json modified; normalizeDownlinkMapping.js added; normalizeUplinkMapping.js added.
msight:em320-th:1updatedMilesight driver realignment on SensorDecoders and encoder fixes — What differs from 4.0.0: driver code changed by e5f3850d3 (Milesight v2, filed as TXIF-4166 by mistake: add Milesight v2 drivers ), e49328bd4 (TXIF-4100: Fix encodeDownlink fPort fallback across all Milesight IoT ); mapping.json modified; normalizeDownlinkMapping.js added; normalizeUplinkMapping.js added.
msight:em320-tilt:1updatedMilesight driver realignment on SensorDecoders and encoder fixes — What differs from 4.0.0: driver code changed by e5f3850d3 (Milesight v2, filed as TXIF-4166 by mistake: add Milesight v2 drivers ), d3ba1d286 (TXIF-4099: Milesight driver catalog realignment — replace TTN drivers ), a737e75dc (TXIF-4099: Milesight extractPoints, check-signatures and changelogs), 2bd1390a9 (TXIF-4099 / RDTP-26187: Fix extractPoints format + ws202 BACnet PIR fi); mapping.json removed.
msight:em320-tilt:2addedMilesight SensorDecoders v2 drivers, next to the existing v1/TTN implementations — New drivers built on Milesight's current SensorDecoders code (2025), kept beside the v1 drivers so deployed devices stay on the protocolId they were provisioned with. Public examples, private extractPoints, normalization hooks and BACnet mappings.
msight:em400-mud:1updatedMilesight driver realignment on SensorDecoders and encoder fixes — What differs from 4.0.0: driver code changed by e5f3850d3 (Milesight v2, filed as TXIF-4166 by mistake: add Milesight v2 drivers ), e49328bd4 (TXIF-4100: Fix encodeDownlink fPort fallback across all Milesight IoT ); mapping.json removed.
msight:em400-mud:2addedMilesight SensorDecoders v2 drivers, next to the existing v1/TTN implementations — New drivers built on Milesight's current SensorDecoders code (2025), kept beside the v1 drivers so deployed devices stay on the protocolId they were provisioned with. Public examples, private extractPoints, normalization hooks and BACnet mappings.
msight:em400-tld:1updatedMilesight driver realignment on SensorDecoders and encoder fixes — What differs from 4.0.0: driver code changed by e5f3850d3 (Milesight v2, filed as TXIF-4166 by mistake: add Milesight v2 drivers ), e49328bd4 (TXIF-4100: Fix encodeDownlink fPort fallback across all Milesight IoT ); mapping.json removed.
msight:em400-tld:2addedMilesight SensorDecoders v2 drivers, next to the existing v1/TTN implementations — New drivers built on Milesight's current SensorDecoders code (2025), kept beside the v1 drivers so deployed devices stay on the protocolId they were provisioned with. Public examples, private extractPoints, normalization hooks and BACnet mappings.
msight:em400-udl:1updatedMilesight driver realignment on SensorDecoders and encoder fixes — What differs from 4.0.0: driver code changed by e5f3850d3 (Milesight v2, filed as TXIF-4166 by mistake: add Milesight v2 drivers ), e49328bd4 (TXIF-4100: Fix encodeDownlink fPort fallback across all Milesight IoT ); mapping.json removed.
msight:em400-udl:2addedMilesight SensorDecoders v2 drivers, next to the existing v1/TTN implementations — New drivers built on Milesight's current SensorDecoders code (2025), kept beside the v1 drivers so deployed devices stay on the protocolId they were provisioned with. Public examples, private extractPoints, normalization hooks and BACnet mappings.
msight:em410-rdl:1updatedMilesight driver realignment on SensorDecoders and encoder fixes — What differs from 4.0.0: driver code changed by e5f3850d3 (Milesight v2, filed as TXIF-4166 by mistake: add Milesight v2 drivers ), e49328bd4 (TXIF-4100: Fix encodeDownlink fPort fallback across all Milesight IoT ); mapping.json modified; normalizeDownlinkMapping.js added; normalizeUplinkMapping.js added.
msight:em500-co2:1updatedMilesight driver realignment on SensorDecoders and encoder fixes — What differs from 4.0.0: driver code changed by e5f3850d3 (Milesight v2, filed as TXIF-4166 by mistake: add Milesight v2 drivers ), d3ba1d286 (TXIF-4099: Milesight driver catalog realignment — replace TTN drivers ), a737e75dc (TXIF-4099: Milesight extractPoints, check-signatures and changelogs), 2bd1390a9 (TXIF-4099 / RDTP-26187: Fix extractPoints format + ws202 BACnet PIR fi); mapping.json modified; normalizeDownlinkMapping.js added; normalizeUplinkMapping.js added.
msight:em500-lgt:1updatedMilesight driver realignment on SensorDecoders and encoder fixes — What differs from 4.0.0: driver code changed by e5f3850d3 (Milesight v2, filed as TXIF-4166 by mistake: add Milesight v2 drivers ), d3ba1d286 (TXIF-4099: Milesight driver catalog realignment — replace TTN drivers ), a737e75dc (TXIF-4099: Milesight extractPoints, check-signatures and changelogs), 2bd1390a9 (TXIF-4099 / RDTP-26187: Fix extractPoints format + ws202 BACnet PIR fi); mapping.json modified; normalizeDownlinkMapping.js added; normalizeUplinkMapping.js added.
msight:em500-pp:1updatedMilesight driver realignment on SensorDecoders and encoder fixes — What differs from 4.0.0: driver code changed by e5f3850d3 (Milesight v2, filed as TXIF-4166 by mistake: add Milesight v2 drivers ), d3ba1d286 (TXIF-4099: Milesight driver catalog realignment — replace TTN drivers ), a737e75dc (TXIF-4099: Milesight extractPoints, check-signatures and changelogs), 2bd1390a9 (TXIF-4099 / RDTP-26187: Fix extractPoints format + ws202 BACnet PIR fi); mapping.json modified; normalizeDownlinkMapping.js added; normalizeUplinkMapping.js added.
msight:em500-pt100:1updatedMilesight driver realignment on SensorDecoders and encoder fixes — What differs from 4.0.0: driver code changed by e5f3850d3 (Milesight v2, filed as TXIF-4166 by mistake: add Milesight v2 drivers ), d3ba1d286 (TXIF-4099: Milesight driver catalog realignment — replace TTN drivers ), a737e75dc (TXIF-4099: Milesight extractPoints, check-signatures and changelogs), 2bd1390a9 (TXIF-4099 / RDTP-26187: Fix extractPoints format + ws202 BACnet PIR fi); mapping.json modified; normalizeDownlinkMapping.js added; normalizeUplinkMapping.js added.
msight:em500-smt:1updatedMilesight driver realignment on SensorDecoders and encoder fixes — What differs from 4.0.0: driver code changed by e5f3850d3 (Milesight v2, filed as TXIF-4166 by mistake: add Milesight v2 drivers ), e49328bd4 (TXIF-4100: Fix encodeDownlink fPort fallback across all Milesight IoT ); mapping.json removed.
msight:em500-smtc:1addedMilesight drivers missing from the 4.0.0 catalog, taken from Milesight's SensorDecoders — Drivers present in Milesight's SensorDecoders repository but absent from the released catalog: decoder, examples, private extractPoints and BACnet mapping.
msight:em500-swl:1updatedMilesight driver realignment on SensorDecoders and encoder fixes — What differs from 4.0.0: driver code changed by e5f3850d3 (Milesight v2, filed as TXIF-4166 by mistake: add Milesight v2 drivers ), 624411b62 (Milesight v2, filed as TXIF-4166 by mistake: add Milesight v2 drivers ), d3ba1d286 (TXIF-4099: Milesight driver catalog realignment — replace TTN drivers ), a737e75dc (TXIF-4099: Milesight extractPoints, check-signatures and changelogs); mapping.json removed.
msight:em500-swl:2addedMilesight SensorDecoders v2 drivers, next to the existing v1/TTN implementations — New drivers built on Milesight's current SensorDecoders code (2025), kept beside the v1 drivers so deployed devices stay on the protocolId they were provisioned with. Public examples, private extractPoints, normalization hooks and BACnet mappings.
msight:em500-udl:1updatedMilesight driver realignment on SensorDecoders and encoder fixes — What differs from 4.0.0: driver code changed by e5f3850d3 (Milesight v2, filed as TXIF-4166 by mistake: add Milesight v2 drivers ), d3ba1d286 (TXIF-4099: Milesight driver catalog realignment — replace TTN drivers ), a737e75dc (TXIF-4099: Milesight extractPoints, check-signatures and changelogs), 2bd1390a9 (TXIF-4099 / RDTP-26187: Fix extractPoints format + ws202 BACnet PIR fi); mapping.json modified; normalizeDownlinkMapping.js added; normalizeUplinkMapping.js added.
msight:ft101:1updated9d392adb4, TXIF-4281 | version bytes read as BCD, not decimal — firmware, hardware and ipso versions were decoded from the raw byte value, so 0x11 read as 17 instead of 1.1: the bytes are BCD and are now read as hexadecimal digits (9d392adb4, 2026-09-02, no Jira ticket). The examples also follow the standard output format ({ data }).
msight:gs101:1updatedMilesight driver realignment on SensorDecoders and encoder fixes — What differs from 4.0.0: driver code changed by e5f3850d3 (Milesight v2, filed as TXIF-4166 by mistake: add Milesight v2 drivers ), d3ba1d286 (TXIF-4099: Milesight driver catalog realignment — replace TTN drivers ), 765d594be (TXIF-4099 / RDTP-26187: Fix ws202 PIR/daylight BACnet compatibility + ), a737e75dc (TXIF-4099: Milesight extractPoints, check-signatures and changelogs); mapping.json modified; normalizeDownlinkMapping.js added; normalizeUplinkMapping.js added. Uplink payload: device_status added (datapath comparison with 4.0.0, TXIF-4285).
msight:gs301:1updatedMilesight driver realignment on SensorDecoders and encoder fixes — What differs from 4.0.0: driver code changed by e5f3850d3 (Milesight v2, filed as TXIF-4166 by mistake: add Milesight v2 drivers ), e49328bd4 (TXIF-4100: Fix encodeDownlink fPort fallback across all Milesight IoT ); mapping.json modified; normalizeDownlinkMapping.js added; normalizeUplinkMapping.js added.
msight:gs524n:1addedMilesight drivers missing from the 4.0.0 catalog, taken from Milesight's SensorDecoders — Drivers present in Milesight's SensorDecoders repository but absent from the released catalog: decoder, examples, private extractPoints and BACnet mapping.
msight:gs601:1updatedMilesight driver realignment on SensorDecoders and encoder fixes — What differs from 4.0.0: driver code changed by e5f3850d3 (Milesight v2, filed as TXIF-4166 by mistake: add Milesight v2 drivers ), e49328bd4 (TXIF-4100: Fix encodeDownlink fPort fallback across all Milesight IoT ); mapping.json removed.
msight:gs601:2addedMilesight GS601, WT303 and WT304 v2 — Milesight's current downlink encoder (BREAKING) — Downlink requests take the shape of Milesight's codec: field names follow it and values are numbers. BACnet mappings use Milesight's names, link groups are rebuilt so that every write carries its complete command.
msight:ts101:1updatedMilesight driver realignment on SensorDecoders and encoder fixes — What differs from 4.0.0: driver code changed by e5f3850d3 (Milesight v2, filed as TXIF-4166 by mistake: add Milesight v2 drivers ), e49328bd4 (TXIF-4100: Fix encodeDownlink fPort fallback across all Milesight IoT ); mapping.json removed.
msight:ts101:2addedMilesight SensorDecoders v2 drivers, next to the existing v1/TTN implementations — New drivers built on Milesight's current SensorDecoders code (2025), kept beside the v1 drivers so deployed devices stay on the protocolId they were provisioned with. Public examples, private extractPoints, normalization hooks and BACnet mappings.
msight:ts201:1updatedMilesight driver realignment on SensorDecoders and encoder fixes — What differs from 4.0.0: driver code changed by e5f3850d3 (Milesight v2, filed as TXIF-4166 by mistake: add Milesight v2 drivers ), e49328bd4 (TXIF-4100: Fix encodeDownlink fPort fallback across all Milesight IoT ); mapping.json removed.
msight:ts201:2addedMilesight SensorDecoders v2 drivers, next to the existing v1/TTN implementations — New drivers built on Milesight's current SensorDecoders code (2025), kept beside the v1 drivers so deployed devices stay on the protocolId they were provisioned with. Public examples, private extractPoints, normalization hooks and BACnet mappings.
msight:ts301:1addedMilesight SensorDecoders drivers, first publication — Drivers built on Milesight's current SensorDecoders code and never published before: published as v1. Public examples, private extractPoints, normalization hooks and BACnet mappings.
msight:ts302:1addedMilesight SensorDecoders drivers, first publication — Drivers built on Milesight's current SensorDecoders code and never published before: published as v1. Public examples, private extractPoints, normalization hooks and BACnet mappings.
msight:ts30x:1updatedBACnet mapping carried by the model's first protocolId; points updated; driver code unchanged — The driver code is unchanged. What differs from 4.0.0: index.js: the appended extractPoints; examples/all.examples.json: points only; mapping.json removed: the BACnet mapping is carried by the first protocolId of the model (its BACnet owner), not by this driver.
msight:ts601:1addedMilesight drivers missing from the 4.0.0 catalog, taken from Milesight's SensorDecoders — Drivers present in Milesight's SensorDecoders repository but absent from the released catalog: decoder, examples, private extractPoints and BACnet mapping.
msight:ts602:1addedMilesight drivers missing from the 4.0.0 catalog, taken from Milesight's SensorDecoders — Drivers present in Milesight's SensorDecoders repository but absent from the released catalog: decoder, examples, private extractPoints and BACnet mapping.
msight:uc100:1updatedMilesight driver realignment on SensorDecoders and encoder fixes — What differs from 4.0.0: driver code changed by e5f3850d3 (Milesight v2, filed as TXIF-4166 by mistake: add Milesight v2 drivers ), d3ba1d286 (TXIF-4099: Milesight driver catalog realignment — replace TTN drivers ), e49328bd4 (TXIF-4100: Fix encodeDownlink fPort fallback across all Milesight IoT ); mapping.json removed. Uplink payload fields renamed or removed: software_version became firmware_version, chn2 became modbus_chn_2, power removed, device_status added (datapath comparison with 4.0.0, TXIF-4285).
msight:uc100:2addedMilesight SensorDecoders v2 drivers, next to the existing v1/TTN implementations — New drivers built on Milesight's current SensorDecoders code (2025), kept beside the v1 drivers so deployed devices stay on the protocolId they were provisioned with. Public examples, private extractPoints, normalization hooks and BACnet mappings.
msight:uc11-n1:1updatedMilesight driver realignment on SensorDecoders and encoder fixes — What differs from 4.0.0: driver code changed by e49328bd4 (TXIF-4100: Fix encodeDownlink fPort fallback across all Milesight IoT ).
msight:uc11-n1:2addedMilesight SensorDecoders v2 drivers, next to the existing v1/TTN implementations — New drivers built on Milesight's current SensorDecoders code (2025), kept beside the v1 drivers so deployed devices stay on the protocolId they were provisioned with. Public examples, private extractPoints, normalization hooks and BACnet mappings.
msight:uc11-t1:1updatedMilesight driver realignment on SensorDecoders and encoder fixes — What differs from 4.0.0: driver code changed by e49328bd4 (TXIF-4100: Fix encodeDownlink fPort fallback across all Milesight IoT ).
msight:uc11-t1:2addedMilesight SensorDecoders v2 drivers, next to the existing v1/TTN implementations — New drivers built on Milesight's current SensorDecoders code (2025), kept beside the v1 drivers so deployed devices stay on the protocolId they were provisioned with. Public examples, private extractPoints, normalization hooks and BACnet mappings.
msight:uc11xx:1updatedMilesight driver realignment on SensorDecoders and encoder fixes — What differs from 4.0.0: driver code changed by e49328bd4 (TXIF-4100: Fix encodeDownlink fPort fallback across all Milesight IoT ); mapping.json added; normalizeUplinkMapping.js added.
msight:uc11xx:2addedMilesight SensorDecoders v2 drivers, next to the existing v1/TTN implementations — New drivers built on Milesight's current SensorDecoders code (2025), kept beside the v1 drivers so deployed devices stay on the protocolId they were provisioned with. Public examples, private extractPoints, normalization hooks and BACnet mappings.
msight:uc300:1updatedMilesight driver realignment on SensorDecoders and encoder fixes — What differs from 4.0.0: driver code changed by e5f3850d3 (Milesight v2, filed as TXIF-4166 by mistake: add Milesight v2 drivers ), d3ba1d286 (TXIF-4099: Milesight driver catalog realignment — replace TTN drivers ), a737e75dc (TXIF-4099: Milesight extractPoints, check-signatures and changelogs), 2bd1390a9 (TXIF-4099 / RDTP-26187: Fix extractPoints format + ws202 BACnet PIR fi); mapping.json modified; normalizeDownlinkMapping.js added; normalizeUplinkMapping.js added. Uplink payload fields renamed or removed, among them chn1/chn2, counter_1/counter_2, gpio_in_3/gpio_in_4 (datapath comparison with 4.0.0, TXIF-4285).
msight:uc500-series:1updatedBACnet mapping carried by the model's first protocolId; points updated; driver code unchanged — The driver code is unchanged. What differs from 4.0.0: index.js: the appended extractPoints; examples/all.examples.json: points only; mapping.json removed: the BACnet mapping is carried by the first protocolId of the model (its BACnet owner), not by this driver.
msight:uc501:1addedMilesight drivers missing from the 4.0.0 catalog, taken from Milesight's SensorDecoders — Drivers present in Milesight's SensorDecoders repository but absent from the released catalog: decoder, examples, private extractPoints and BACnet mapping.
msight:uc502:1addedMilesight drivers missing from the 4.0.0 catalog, taken from Milesight's SensorDecoders — Drivers present in Milesight's SensorDecoders repository but absent from the released catalog: decoder, examples, private extractPoints and BACnet mapping.
msight:uc511:1addedMilesight drivers missing from the 4.0.0 catalog, taken from Milesight's SensorDecoders — Drivers present in Milesight's SensorDecoders repository but absent from the released catalog: decoder, examples, private extractPoints and BACnet mapping.
msight:uc512:1addedMilesight drivers missing from the 4.0.0 catalog, taken from Milesight's SensorDecoders — Drivers present in Milesight's SensorDecoders repository but absent from the released catalog: decoder, examples, private extractPoints and BACnet mapping.
msight:uc51x-series:1updatedBACnet mapping carried by the model's first protocolId; points updated; driver code unchanged — The driver code is unchanged. What differs from 4.0.0: index.js: the appended extractPoints; examples/all.examples.json: points only; mapping.json removed: the BACnet mapping is carried by the first protocolId of the model (its BACnet owner), not by this driver.
msight:uc521:1addedMilesight drivers missing from the 4.0.0 catalog, taken from Milesight's SensorDecoders — Drivers present in Milesight's SensorDecoders repository but absent from the released catalog: decoder, examples, private extractPoints and BACnet mapping.
msight:vs121:1updatedMilesight driver realignment on SensorDecoders and encoder fixes — What differs from 4.0.0: driver code changed by e5f3850d3 (Milesight v2, filed as TXIF-4166 by mistake: add Milesight v2 drivers ), e49328bd4 (TXIF-4100: Fix encodeDownlink fPort fallback across all Milesight IoT ); mapping.json removed.
msight:vs121:2addedMilesight SensorDecoders v2 drivers, next to the existing v1/TTN implementations — New drivers built on Milesight's current SensorDecoders code (2025), kept beside the v1 drivers so deployed devices stay on the protocolId they were provisioned with. Public examples, private extractPoints, normalization hooks and BACnet mappings.
msight:vs132:1updatedMilesight driver realignment on SensorDecoders and encoder fixes — What differs from 4.0.0: driver code changed by d3ba1d286 (TXIF-4099: Milesight driver catalog realignment — replace TTN drivers ), e49328bd4 (TXIF-4100: Fix encodeDownlink fPort fallback across all Milesight IoT ); mapping.json added; normalizeUplinkMapping.js added.
msight:vs133:1updatedMilesight driver realignment on SensorDecoders and encoder fixes — What differs from 4.0.0: driver code changed by e5f3850d3 (Milesight v2, filed as TXIF-4166 by mistake: add Milesight v2 drivers ), e49328bd4 (TXIF-4100: Fix encodeDownlink fPort fallback across all Milesight IoT ); mapping.json modified; normalizeDownlinkMapping.js added; normalizeUplinkMapping.js added.
msight:vs135:1updatedMilesight driver realignment on SensorDecoders and encoder fixes — What differs from 4.0.0: driver code changed by e5f3850d3 (Milesight v2, filed as TXIF-4166 by mistake: add Milesight v2 drivers ), e49328bd4 (TXIF-4100: Fix encodeDownlink fPort fallback across all Milesight IoT ); mapping.json modified; normalizeDownlinkMapping.js added; normalizeUplinkMapping.js added.
msight:vs321:1updatedMilesight driver realignment on SensorDecoders and encoder fixes — What differs from 4.0.0: driver code changed by e5f3850d3 (Milesight v2, filed as TXIF-4166 by mistake: add Milesight v2 drivers ), e49328bd4 (TXIF-4100: Fix encodeDownlink fPort fallback across all Milesight IoT ); mapping.json modified; normalizeDownlinkMapping.js added; normalizeUplinkMapping.js added.
msight:vs330:1updatedMilesight driver realignment on SensorDecoders and encoder fixes — What differs from 4.0.0: driver code changed by e5f3850d3 (Milesight v2, filed as TXIF-4166 by mistake: add Milesight v2 drivers ), e49328bd4 (TXIF-4100: Fix encodeDownlink fPort fallback across all Milesight IoT ); mapping.json modified; normalizeDownlinkMapping.js added; normalizeUplinkMapping.js added.
msight:vs340:1updatedMilesight driver realignment on SensorDecoders and encoder fixes — What differs from 4.0.0: driver code changed by e5f3850d3 (Milesight v2, filed as TXIF-4166 by mistake: add Milesight v2 drivers ), e49328bd4 (TXIF-4100: Fix encodeDownlink fPort fallback across all Milesight IoT ); mapping.json removed.
msight:vs340:2addedMilesight SensorDecoders v2 drivers, next to the existing v1/TTN implementations — New drivers built on Milesight's current SensorDecoders code (2025), kept beside the v1 drivers so deployed devices stay on the protocolId they were provisioned with. Public examples, private extractPoints, normalization hooks and BACnet mappings.
msight:vs341:1updatedMilesight driver realignment on SensorDecoders and encoder fixes — What differs from 4.0.0: driver code changed by e5f3850d3 (Milesight v2, filed as TXIF-4166 by mistake: add Milesight v2 drivers ), e49328bd4 (TXIF-4100: Fix encodeDownlink fPort fallback across all Milesight IoT ); mapping.json removed.
msight:vs341:2addedMilesight SensorDecoders v2 drivers, next to the existing v1/TTN implementations — New drivers built on Milesight's current SensorDecoders code (2025), kept beside the v1 drivers so deployed devices stay on the protocolId they were provisioned with. Public examples, private extractPoints, normalization hooks and BACnet mappings.
msight:vs350:1updatedMilesight driver realignment on SensorDecoders and encoder fixes — What differs from 4.0.0: driver code changed by e5f3850d3 (Milesight v2, filed as TXIF-4166 by mistake: add Milesight v2 drivers ), e49328bd4 (TXIF-4100: Fix encodeDownlink fPort fallback across all Milesight IoT ); mapping.json modified; normalizeDownlinkMapping.js added; normalizeUplinkMapping.js added.
msight:vs351:1updatedMilesight driver realignment on SensorDecoders and encoder fixes — What differs from 4.0.0: driver code changed by e5f3850d3 (Milesight v2, filed as TXIF-4166 by mistake: add Milesight v2 drivers ), e49328bd4 (TXIF-4100: Fix encodeDownlink fPort fallback across all Milesight IoT ); mapping.json removed.
msight:vs351:2addedMilesight SensorDecoders v2 drivers, next to the existing v1/TTN implementations — New drivers built on Milesight's current SensorDecoders code (2025), kept beside the v1 drivers so deployed devices stay on the protocolId they were provisioned with. Public examples, private extractPoints, normalization hooks and BACnet mappings.
msight:vs360:1updatedMilesight driver realignment on SensorDecoders and encoder fixes — What differs from 4.0.0: driver code changed by e5f3850d3 (Milesight v2, filed as TXIF-4166 by mistake: add Milesight v2 drivers ), e49328bd4 (TXIF-4100: Fix encodeDownlink fPort fallback across all Milesight IoT ); mapping.json removed.
msight:vs360:2addedMilesight SensorDecoders v2 drivers, next to the existing v1/TTN implementations — New drivers built on Milesight's current SensorDecoders code (2025), kept beside the v1 drivers so deployed devices stay on the protocolId they were provisioned with. Public examples, private extractPoints, normalization hooks and BACnet mappings.
msight:vs370:1updatedMilesight driver realignment on SensorDecoders and encoder fixes — What differs from 4.0.0: driver code changed by e5f3850d3 (Milesight v2, filed as TXIF-4166 by mistake: add Milesight v2 drivers ), e49328bd4 (TXIF-4100: Fix encodeDownlink fPort fallback across all Milesight IoT ); mapping.json modified; normalizeDownlinkMapping.js added; normalizeUplinkMapping.js added.
msight:vs373:1updatedMilesight driver realignment on SensorDecoders and encoder fixes — What differs from 4.0.0: driver code changed by e5f3850d3 (Milesight v2, filed as TXIF-4166 by mistake: add Milesight v2 drivers ), e49328bd4 (TXIF-4100: Fix encodeDownlink fPort fallback across all Milesight IoT ); mapping.json modified; normalizeDownlinkMapping.js added; normalizeUplinkMapping.js added.
msight:ws101:1updatedMilesight driver realignment on SensorDecoders and encoder fixes — What differs from 4.0.0: driver code changed by e5f3850d3 (Milesight v2, filed as TXIF-4166 by mistake: add Milesight v2 drivers ), d3ba1d286 (TXIF-4099: Milesight driver catalog realignment — replace TTN drivers ), a737e75dc (TXIF-4099: Milesight extractPoints, check-signatures and changelogs), 2bd1390a9 (TXIF-4099 / RDTP-26187: Fix extractPoints format + ws202 BACnet PIR fi); mapping.json removed.
msight:ws101:2addedMilesight SensorDecoders v2 drivers, next to the existing v1/TTN implementations — New drivers built on Milesight's current SensorDecoders code (2025), kept beside the v1 drivers so deployed devices stay on the protocolId they were provisioned with. Public examples, private extractPoints, normalization hooks and BACnet mappings.
msight:ws136:1addedMilesight drivers missing from the 4.0.0 catalog, taken from Milesight's SensorDecoders — Drivers present in Milesight's SensorDecoders repository but absent from the released catalog: decoder, examples, private extractPoints and BACnet mapping.
msight:ws136ws156:1updatedMilesight driver realignment on SensorDecoders and encoder fixes — What differs from 4.0.0: driver code changed by e5f3850d3 (Milesight v2, filed as TXIF-4166 by mistake: add Milesight v2 drivers ), e49328bd4 (TXIF-4100: Fix encodeDownlink fPort fallback across all Milesight IoT ); mapping.json removed.
msight:ws156:1addedMilesight drivers missing from the 4.0.0 catalog, taken from Milesight's SensorDecoders — Drivers present in Milesight's SensorDecoders repository but absent from the released catalog: decoder, examples, private extractPoints and BACnet mapping.
msight:ws201:1updatedMilesight driver realignment on SensorDecoders and encoder fixes — What differs from 4.0.0: driver code changed by e5f3850d3 (Milesight v2, filed as TXIF-4166 by mistake: add Milesight v2 drivers ), e49328bd4 (TXIF-4100: Fix encodeDownlink fPort fallback across all Milesight IoT ); mapping.json modified; normalizeDownlinkMapping.js added; normalizeUplinkMapping.js added.
msight:ws202:1updatedMilesight driver realignment on SensorDecoders and encoder fixes — What differs from 4.0.0: driver code changed by e5f3850d3 (Milesight v2, filed as TXIF-4166 by mistake: add Milesight v2 drivers ), 624411b62 (Milesight v2, filed as TXIF-4166 by mistake: add Milesight v2 drivers ), d3ba1d286 (TXIF-4099: Milesight driver catalog realignment — replace TTN drivers ), 765d594be (TXIF-4099 / RDTP-26187: Fix ws202 PIR/daylight BACnet compatibility + ); mapping.json removed.
msight:ws202:2addedMilesight SensorDecoders v2 drivers, next to the existing v1/TTN implementations — New drivers built on Milesight's current SensorDecoders code (2025), kept beside the v1 drivers so deployed devices stay on the protocolId they were provisioned with. Public examples, private extractPoints, normalization hooks and BACnet mappings.
msight:ws203:1updatedMilesight driver realignment on SensorDecoders and encoder fixes — What differs from 4.0.0: driver code changed by e5f3850d3 (Milesight v2, filed as TXIF-4166 by mistake: add Milesight v2 drivers ), e49328bd4 (TXIF-4100: Fix encodeDownlink fPort fallback across all Milesight IoT ); mapping.json removed.
msight:ws203:2addedMilesight SensorDecoders v2 drivers, next to the existing v1/TTN implementations — New drivers built on Milesight's current SensorDecoders code (2025), kept beside the v1 drivers so deployed devices stay on the protocolId they were provisioned with. Public examples, private extractPoints, normalization hooks and BACnet mappings.
msight:ws301:1updatedMilesight driver realignment on SensorDecoders and encoder fixes — What differs from 4.0.0: driver code changed by e5f3850d3 (Milesight v2, filed as TXIF-4166 by mistake: add Milesight v2 drivers ), e49328bd4 (TXIF-4100: Fix encodeDownlink fPort fallback across all Milesight IoT ); mapping.json removed.
msight:ws301:2addedMilesight SensorDecoders v2 drivers, next to the existing v1/TTN implementations — New drivers built on Milesight's current SensorDecoders code (2025), kept beside the v1 drivers so deployed devices stay on the protocolId they were provisioned with. Public examples, private extractPoints, normalization hooks and BACnet mappings.
msight:ws302:1updatedMilesight driver realignment on SensorDecoders and encoder fixes — What differs from 4.0.0: driver code changed by e5f3850d3 (Milesight v2, filed as TXIF-4166 by mistake: add Milesight v2 drivers ), e49328bd4 (TXIF-4100: Fix encodeDownlink fPort fallback across all Milesight IoT ); mapping.json removed.
msight:ws302:2addedMilesight SensorDecoders v2 drivers, next to the existing v1/TTN implementations — New drivers built on Milesight's current SensorDecoders code (2025), kept beside the v1 drivers so deployed devices stay on the protocolId they were provisioned with. Public examples, private extractPoints, normalization hooks and BACnet mappings.
msight:ws303:1updatedMilesight driver realignment on SensorDecoders and encoder fixes — What differs from 4.0.0: driver code changed by e5f3850d3 (Milesight v2, filed as TXIF-4166 by mistake: add Milesight v2 drivers ), e49328bd4 (TXIF-4100: Fix encodeDownlink fPort fallback across all Milesight IoT ); mapping.json removed.
msight:ws303:2addedMilesight SensorDecoders v2 drivers, next to the existing v1/TTN implementations — New drivers built on Milesight's current SensorDecoders code (2025), kept beside the v1 drivers so deployed devices stay on the protocolId they were provisioned with. Public examples, private extractPoints, normalization hooks and BACnet mappings.
msight:ws501-cn:1addedMilesight drivers missing from the 4.0.0 catalog, taken from Milesight's SensorDecoders — Drivers present in Milesight's SensorDecoders repository but absent from the released catalog: decoder, examples, private extractPoints and BACnet mapping.
msight:ws501-eu:1addedMilesight drivers missing from the 4.0.0 catalog, taken from Milesight's SensorDecoders — Drivers present in Milesight's SensorDecoders repository but absent from the released catalog: decoder, examples, private extractPoints and BACnet mapping.
msight:ws501-us:1addedMilesight drivers missing from the 4.0.0 catalog, taken from Milesight's SensorDecoders — Drivers present in Milesight's SensorDecoders repository but absent from the released catalog: decoder, examples, private extractPoints and BACnet mapping.
msight:ws501:1addedMilesight WS513, WS515, WS501, WS502, WS503 on Milesight's current codec — First publication of a per-model driver for these sockets and switches, on Milesight's current SensorDecoders codec (the codec of the hardware Milesight ships today). Public examples, private extractPoints, normalization hooks and BACnet mapping.
msight:ws502-cn:1addedMilesight drivers missing from the 4.0.0 catalog, taken from Milesight's SensorDecoders — Drivers present in Milesight's SensorDecoders repository but absent from the released catalog: decoder, examples, private extractPoints and BACnet mapping.
msight:ws502-eu:1addedMilesight drivers missing from the 4.0.0 catalog, taken from Milesight's SensorDecoders — Drivers present in Milesight's SensorDecoders repository but absent from the released catalog: decoder, examples, private extractPoints and BACnet mapping.
msight:ws502:1addedMilesight WS513, WS515, WS501, WS502, WS503 on Milesight's current codec — First publication of a per-model driver for these sockets and switches, on Milesight's current SensorDecoders codec (the codec of the hardware Milesight ships today). Public examples, private extractPoints, normalization hooks and BACnet mapping.
msight:ws503-cn:1addedMilesight drivers missing from the 4.0.0 catalog, taken from Milesight's SensorDecoders — Drivers present in Milesight's SensorDecoders repository but absent from the released catalog: decoder, examples, private extractPoints and BACnet mapping.
msight:ws503:1addedMilesight WS513, WS515, WS501, WS502, WS503 on Milesight's current codec — First publication of a per-model driver for these sockets and switches, on Milesight's current SensorDecoders codec (the codec of the hardware Milesight ships today). Public examples, private extractPoints, normalization hooks and BACnet mapping.
msight:ws50x:1updatedBACnet mapping carried by the model's first protocolId; points updated; driver code unchanged — The driver code is unchanged. What differs from 4.0.0: index.js: the appended extractPoints; examples/all.examples.json: points only; mapping.json removed: the BACnet mapping is carried by the first protocolId of the model (its BACnet owner), not by this driver.
msight:ws513:1addedMilesight WS513, WS515, WS501, WS502, WS503 on Milesight's current codec — First publication of a per-model driver for these sockets and switches, on Milesight's current SensorDecoders codec (the codec of the hardware Milesight ships today). Public examples, private extractPoints, normalization hooks and BACnet mapping.
msight:ws515:1addedMilesight WS513, WS515, WS501, WS502, WS503 on Milesight's current codec — First publication of a per-model driver for these sockets and switches, on Milesight's current SensorDecoders codec (the codec of the hardware Milesight ships today). Public examples, private extractPoints, normalization hooks and BACnet mapping.
msight:ws51x:1updatedMilesight driver realignment on SensorDecoders and encoder fixes — What differs from 4.0.0: driver code changed by e5f3850d3 (Milesight v2, filed as TXIF-4166 by mistake: add Milesight v2 drivers ), e49328bd4 (TXIF-4100: Fix encodeDownlink fPort fallback across all Milesight IoT ); mapping.json removed.
msight:ws523:1addedMilesight drivers missing from the 4.0.0 catalog, taken from Milesight's SensorDecoders — Drivers present in Milesight's SensorDecoders repository but absent from the released catalog: decoder, examples, private extractPoints and BACnet mapping.
msight:ws525:1addedMilesight drivers missing from the 4.0.0 catalog, taken from Milesight's SensorDecoders — Drivers present in Milesight's SensorDecoders repository but absent from the released catalog: decoder, examples, private extractPoints and BACnet mapping.
msight:ws52x:1updatedBACnet mapping carried by the model's first protocolId; points updated; driver code unchanged — The driver code is unchanged. What differs from 4.0.0: index.js: the appended extractPoints; examples/all.examples.json: points only; mapping.json removed: the BACnet mapping is carried by the first protocolId of the model (its BACnet owner), not by this driver.
msight:ws558:1updatedMilesight driver realignment on SensorDecoders and encoder fixes — What differs from 4.0.0: driver code changed by e5f3850d3 (Milesight v2, filed as TXIF-4166 by mistake: add Milesight v2 drivers ), d3ba1d286 (TXIF-4099: Milesight driver catalog realignment — replace TTN drivers ), e49328bd4 (TXIF-4100: Fix encodeDownlink fPort fallback across all Milesight IoT ); mapping.json modified; normalizeDownlinkMapping.js added; normalizeUplinkMapping.js added.
msight:wt101:1updatedMilesight driver realignment on SensorDecoders and encoder fixes — What differs from 4.0.0: driver code changed by e5f3850d3 (Milesight v2, filed as TXIF-4166 by mistake: add Milesight v2 drivers ), e49328bd4 (TXIF-4100: Fix encodeDownlink fPort fallback across all Milesight IoT ); mapping.json modified; normalizeDownlinkMapping.js added; normalizeUplinkMapping.js added.
msight:wt102:1addedMilesight WT102 driver
msight:wt201:1updatedMilesight driver realignment on SensorDecoders and encoder fixes — What differs from 4.0.0: driver code changed by e5f3850d3 (Milesight v2, filed as TXIF-4166 by mistake: add Milesight v2 drivers ), e49328bd4 (TXIF-4100: Fix encodeDownlink fPort fallback across all Milesight IoT ); mapping.json removed.
msight:wt201:2addedMilesight SensorDecoders v2 drivers, next to the existing v1/TTN implementations — New drivers built on Milesight's current SensorDecoders code (2025), kept beside the v1 drivers so deployed devices stay on the protocolId they were provisioned with. Public examples, private extractPoints, normalization hooks and BACnet mappings.
msight:wt211:1addedMilesight SensorDecoders drivers, first publication — Drivers built on Milesight's current SensorDecoders code and never published before: published as v1. Public examples, private extractPoints, normalization hooks and BACnet mappings.
msight:wt301-wt302:1updatedMilesight driver realignment on SensorDecoders and encoder fixes — What differs from 4.0.0: driver code changed by e5f3850d3 (Milesight v2, filed as TXIF-4166 by mistake: add Milesight v2 drivers ), e49328bd4 (TXIF-4100: Fix encodeDownlink fPort fallback across all Milesight IoT ).
msight:wt301:1addedMilesight drivers missing from the 4.0.0 catalog, taken from Milesight's SensorDecoders — Drivers present in Milesight's SensorDecoders repository but absent from the released catalog: decoder, examples, private extractPoints and BACnet mapping.
msight:wt302:1addedMilesight drivers missing from the 4.0.0 catalog, taken from Milesight's SensorDecoders — Drivers present in Milesight's SensorDecoders repository but absent from the released catalog: decoder, examples, private extractPoints and BACnet mapping.
msight:wt303:1updatedMilesight driver realignment on SensorDecoders and encoder fixes — What differs from 4.0.0: driver code changed by e5f3850d3 (Milesight v2, filed as TXIF-4166 by mistake: add Milesight v2 drivers ), e49328bd4 (TXIF-4100: Fix encodeDownlink fPort fallback across all Milesight IoT ).
msight:wt303:2addedMilesight GS601, WT303 and WT304 v2 — Milesight's current downlink encoder (BREAKING) — Downlink requests take the shape of Milesight's codec: field names follow it and values are numbers. BACnet mappings use Milesight's names, link groups are rebuilt so that every write carries its complete command.
msight:wt304:1updatedMilesight driver realignment on SensorDecoders and encoder fixes — What differs from 4.0.0: driver code changed by e5f3850d3 (Milesight v2, filed as TXIF-4166 by mistake: add Milesight v2 drivers ), e49328bd4 (TXIF-4100: Fix encodeDownlink fPort fallback across all Milesight IoT ).
msight:wt304:2addedMilesight GS601, WT303 and WT304 v2 — Milesight's current downlink encoder (BREAKING) — Downlink requests take the shape of Milesight's codec: field names follow it and values are numbers. BACnet mappings use Milesight's names, link groups are rebuilt so that every write carries its complete command.
msight:wt401:1addedMilesight drivers missing from the 4.0.0 catalog, taken from Milesight's SensorDecoders — Drivers present in Milesight's SensorDecoders repository but absent from the released catalog: decoder, examples, private extractPoints and BACnet mapping.
msight:wts506:1addedMilesight drivers missing from the 4.0.0 catalog, taken from Milesight's SensorDecoders — Drivers present in Milesight's SensorDecoders repository but absent from the released catalog: decoder, examples, private extractPoints and BACnet mapping.
os1-mile:am107:1updatedextractPoints publishes points the examples did not carry; driver code unchanged — Points only: the examples are identical to 4.0.0 once their points are set aside, and the bundle differs by index.js: the appended extractPoints. 1 example(s) changed: new points illuminance:3; points no longer published illuminance:0; changed illuminance:1 (record/nature), illuminance:2 (record/nature). Recorded under TXIF-4280, the ticket for drivers whose only change is their extractPoints.
os1-mile:em300-th:1updatedpoints updated (extractPoints / examples); driver code unchanged — The driver code is unchanged. What differs from 4.0.0: index.js: the appended extractPoints.

nanosense​

DriverChangeWhat changed
nanosens:ep5000:1updatedpoints updated (extractPoints / examples); driver code unchanged — Points only: the examples are identical to 4.0.0 once their points are set aside, and the bundle differs by index.js: the appended extractPoints. 1 example(s) changed: changed temperature:1 (unitId/record/nature), concentration:1 (nature), concentration:2 (record/nature), concentration:3 (nature), concentration:4 (record/nature), concentration:5 (nature), concentration:6 (nature), temperature:2 (unitId/record/nature), …. Recorded under TXIF-4280, the ticket for drivers whose only change is their extractPoints.
nanosens:qaa:1updatedpoints updated (extractPoints / examples); driver code unchanged — Points only: the examples are identical to 4.0.0 once their points are set aside, and the bundle differs by index.js: the appended extractPoints. 1 example(s) changed: changed concentration:1 (records/nature), concentration:2 (records/nature), concentration:3 (nature). Recorded under TXIF-4280, the ticket for drivers whose only change is their extractPoints.

netvox​

DriverChangeWhat changed
os1-netv:r718ma:10removedNo longer shipped: no model references this protocolId (commit d0c11e3d3) — The driver is still checked and tested but not packaged since commit d0c11e3d3 (feat(package): ship only what a model points at, 2026-09-10, no ticket): only protocolIds a model.yaml of the public catalog references are shipped. No model references os1-netv:r718ma:10.
os1-netv:rb11e:10removedNo longer shipped: no model references this protocolId (commit d0c11e3d3) — The driver is still checked and tested but not packaged since commit d0c11e3d3 (feat(package): ship only what a model points at, 2026-09-10, no ticket): only protocolIds a model.yaml of the public catalog references are shipped. No model references os1-netv:rb11e:10.

nexelec​

DriverChangeWhat changed
nexelec:air-plus:1addedNexelec Air Plus, Track Plus and X2 drivers — Webpack-built drivers from the Nexelec decoders; no ticket found in git or Jira (TXIF-4168 covers the WAVE model only).
nexelec:generic:1updatedpoints updated (extractPoints / examples); driver code unchanged — The driver code is unchanged. What differs from 4.0.0: index.js: the appended extractPoints.
nexelec:generic2:1updatedpoints updated (extractPoints / examples); driver code unchanged — The driver code is unchanged. What differs from 4.0.0: index.js: the appended extractPoints.
nexelec:generic3:1updatedextractPoints publishes points the examples did not carry; driver code unchanged — Points only: the examples are identical to 4.0.0 once their points are set aside, and the bundle differs by index.js: the appended extractPoints. 6 example(s) changed: new points batteryVoltage:1, age:1, interval:1, temperature, age:2, temperature:1, temperature:2, temperature:3, humidity:1, humidity:2, humidity:3, humidity, …. Recorded under TXIF-4280, the ticket for drivers whose only change is their extractPoints.
nexelec:insafe-origin:1updatedextractPoints publishes points the examples did not carry; driver code unchanged — Points only: the examples are identical to 4.0.0 once their points are set aside, and the bundle differs by index.js: the appended extractPoints. 9 example(s) changed: new points batteryVoltage:1, batteryVoltage:2, age:1, age:2, interval:1, interval:2, age:3, temperature:1, temperature:2, temperature:3, humidity:1, humidity:2, …; 1 example(s) without point now say points: null instead of {}. Recorded under TXIF-4280, the ticket for drivers whose only change is their extractPoints.
nexelec:insafe-pilot:1updateda771af588, 0ab613bff | datalog timestamps computed from recvTime, which the engine provides — The datalog frame carries five readings without their timestamps, and input.time is not available to a driver: datalogEventTimes is now derived from input.recvTime and timeBetweenMeasurements. No Jira ticket: fixed directly on 2026-09-07 (public a771af588, private 0ab613bff). The point interval:1 becomes interval.
nexelec:track-plus:1addedNexelec Air Plus, Track Plus and X2 drivers — Webpack-built drivers from the Nexelec decoders; no ticket found in git or Jira (TXIF-4168 covers the WAVE model only).
nexelec:x2:1addedNexelec Air Plus, Track Plus and X2 drivers — Webpack-built drivers from the Nexelec decoders; no ticket found in git or Jira (TXIF-4168 covers the WAVE model only).
os1-nexe:carbon:1updated3efc5e106 | ttn signature restored: the lora-alliance wrappers are removed — This driver is a ttn driver, not a lora-alliance one: the decodeUplink / encodeDownlink / decodeDownlink wrappers and their exports are removed so the engine calls the ttn entry points (3efc5e106, 2026-09-08). No Jira ticket. Decoding itself is unchanged.

nke​

DriverChangeWhat changed
nke:zcl:1updatedextractPoints dropped: the points it produced did not follow the ontology — The driver moved from vendors/watteco/drivers/zcl to vendors/nke/drivers/zcl (7979140eb) without its extractPoints.js, and the old copy went with the folder (3609aa2f2). The loss is assumed: the points it published were named after the ZCL wire fields (BinaryInput:PresentValue:1, Temperature:MeasuredValue:1, OnOff:State:1 ...), which the ontology does not define. The decoding code itself is unchanged; the package ships its webpack output.

onesitu​

DriverChangeWhat changed
spt-ones:os110:1addedOneSitu OS110 and Tekelek TEK766 — SPOT migration drivers — SPOT drivers now referenced by the public OneSitu OS110 and Tekelek TEK766 models.

pmx​

DriverChangeWhat changed
pmx:pmx-tcr-protocol:1updatedextractPoints publishes points the examples did not carry; driver code unchanged — Points only: the examples are identical to 4.0.0 once their points are set aside, and the bundle differs by index.js: the appended extractPoints. 6 example(s) changed: new points voltage; 1 example(s) without point now say points: null instead of {}. The extractPoints work of TXIF-4088 touched this driver after the 4.0.0 tag (commits a410ff591, 1eb681a7f, 34b7a1ca2). Recorded under TXIF-4280, the ticket for drivers whose only change is their extractPoints.

quandify​

DriverChangeWhat changed
quandify:cubicmeter-1-1:1updatedextractPoints publishes points the examples did not carry; driver code unchanged — Points only: the examples are identical to 4.0.0 once their points are set aside, and the bundle differs by index.js: the appended extractPoints. 3 example(s) changed: new points temperature:1, temperature:2, temperature:3, batteryVoltage, volume; 2 example(s) without point now say points: null instead of {}. The extractPoints work of TXIF-4088 touched this driver after the 4.0.0 tag (commits a410ff591, 1eb681a7f, 34b7a1ca2). Recorded under TXIF-4280, the ticket for drivers whose only change is their extractPoints.

sample-vendor​

DriverChangeWhat changed
sample-vendor:sample-model-protocol:1removedSample driver of the catalog template removed: not a device driver — template/sample-vendor/drivers/sample-driver (device-catalog) is the template for new drivers; 4.0.0 shipped it as @actility/sample-model-driver. No model references sample-vendor:sample-model-protocol:1, and the build only assembles vendors/.

senlab​

DriverChangeWhat changed
senlab:a:1updatedextractPoints publishes points the examples did not carry; driver code unchanged — Points only: the examples are identical to 4.0.0 once their points are set aside, and the bundle differs by index.js: the appended extractPoints. 3 example(s) changed: new points current, batteryLevel; 2 example(s) without point now say points: null instead of {}. The extractPoints work of TXIF-4088 touched this driver after the 4.0.0 tag (commit a410ff591). Recorded under TXIF-4280, the ticket for drivers whose only change is their extractPoints.
senlab:d:1updatedextractPoints publishes points the examples did not carry; driver code unchanged — Points only: the examples are identical to 4.0.0 once their points are set aside, and the bundle differs by index.js: the appended extractPoints. 3 example(s) changed: new points batteryLevel, status; 1 example(s) without point now say points: null instead of {}. The extractPoints work of TXIF-4088 touched this driver after the 4.0.0 tag (commit a410ff591). Recorded under TXIF-4280, the ticket for drivers whose only change is their extractPoints.
senlab:h:1updatedextractPoints publishes points the examples did not carry; driver code unchanged — Points only: the examples are identical to 4.0.0 once their points are set aside, and the bundle differs by index.js: the appended extractPoints. 3 example(s) changed: new points temperature, humidity, batteryLevel; 2 example(s) without point now say points: null instead of {}. The extractPoints work of TXIF-4088 touched this driver after the 4.0.0 tag (commit a410ff591). Recorded under TXIF-4280, the ticket for drivers whose only change is their extractPoints.
senlab:m:1updatedextractPoints publishes points the examples did not carry; driver code unchanged — Points only: the examples are identical to 4.0.0 once their points are set aside, and the bundle differs by index.js: the appended extractPoints. 2 example(s) changed: new points counter, batteryLevel; 1 example(s) without point now say points: null instead of {}. The extractPoints work of TXIF-4088 touched this driver after the 4.0.0 tag (commit a410ff591). Recorded under TXIF-4280, the ticket for drivers whose only change is their extractPoints.
senlab:o:1updatedextractPoints publishes points the examples did not carry; driver code unchanged — Points only: the examples are identical to 4.0.0 once their points are set aside, and the bundle differs by index.js: the appended extractPoints. 3 example(s) changed: new points humidity, presence, illuminance, temperature, batteryLevel; 2 example(s) without point now say points: null instead of {}. The extractPoints work of TXIF-4088 touched this driver after the 4.0.0 tag (commit a410ff591). Recorded under TXIF-4280, the ticket for drivers whose only change is their extractPoints.
senlab:p:1updatedextractPoints publishes points the examples did not carry; driver code unchanged — Points only: the examples are identical to 4.0.0 once their points are set aside, and the bundle differs by index.js: the appended extractPoints. 2 example(s) changed: new points counter, batteryLevel; 1 example(s) without point now say points: null instead of {}. The extractPoints work of TXIF-4088 touched this driver after the 4.0.0 tag (commit a410ff591). Recorded under TXIF-4280, the ticket for drivers whose only change is their extractPoints.
senlab:t:1updatedextractPoints publishes points the examples did not carry; driver code unchanged — Points only: the examples are identical to 4.0.0 once their points are set aside, and the bundle differs by index.js: the appended extractPoints. 4 example(s) changed: new points temperature:1, batteryLevel, temperature:2; 2 example(s) without point now say points: null instead of {}. The extractPoints work of TXIF-4088 touched this driver after the 4.0.0 tag (commit a410ff591). Recorded under TXIF-4280, the ticket for drivers whose only change is their extractPoints.
senlab:v:1updatedextractPoints publishes points the examples did not carry; driver code unchanged — Points only: the examples are identical to 4.0.0 once their points are set aside, and the bundle differs by index.js: the appended extractPoints. 2 example(s) changed: new points batteryLevel, status:1, status:2, counter; 1 example(s) without point now say points: null instead of {}. The extractPoints work of TXIF-4088 touched this driver after the 4.0.0 tag (commit a410ff591). Recorded under TXIF-4280, the ticket for drivers whose only change is their extractPoints.

sensative​

DriverChangeWhat changed
sensativ:square-air:1updatedpoints updated (extractPoints / examples); driver code unchanged — The driver code is unchanged. What differs from 4.0.0: index.js: the appended extractPoints.
sensativ:square-comfort:1updatedpoints updated (extractPoints / examples); driver code unchanged — The driver code is unchanged. What differs from 4.0.0: index.js: the appended extractPoints.
sensativ:square-sound:1updatedpoints updated (extractPoints / examples); driver code unchanged — The driver code is unchanged. What differs from 4.0.0: index.js: the appended extractPoints.
sensativ:strips:1updatedf79ff042a, be52b17d5, TXIF-4281 | no longer a webpack driver: index.js carries the decoder — The driver was simplified out of its webpack build (strips-translate.js, webpack.config.js removed): the package no longer ships main.js, and index.js now carries the decoder that the bundle held (f79ff042a, be52b17d5, no Jira ticket). The examples follow the standard output format ({ data }), which is why they gain their data block.

sensecap​

DriverChangeWhat changed
sensecap:s210x:1updatedpoints updated (extractPoints / examples); driver code unchanged — The driver code is unchanged. What differs from 4.0.0: index.js: the appended extractPoints.
sensecap:t1000:1updatedextractPoints publishes points the examples did not carry; driver code unchanged — Points only: the examples are identical to 4.0.0 once their points are set aside, and the bundle differs by index.js: the appended extractPoints. 7 example(s) changed: new points batteryLevel, temperature, light, location; 2 example(s) without point now say points: null instead of {}. The extractPoints work of TXIF-4088 touched this driver after the 4.0.0 tag (commits a410ff591, 1eb681a7f, 34b7a1ca2). Recorded under TXIF-4280, the ticket for drivers whose only change is their extractPoints.

sensor-networks-inc​

DriverChangeWhat changed
actility:micropims:1updatedextractPoints publishes points the examples did not carry; driver code unchanged — Points only: the examples are identical to 4.0.0 once their points are set aside, and the bundle differs by index.js: the appended extractPoints. 1 example(s) changed: new points temperature; points no longer published distance, temperature:1, temperature:2, batteryLevel. The extractPoints work of TXIF-4088 touched this driver after the 4.0.0 tag (commits a410ff591, 34b7a1ca2, 2bc7114f7). Recorded under TXIF-4280, the ticket for drivers whose only change is their extractPoints.

sensus​

DriverChangeWhat changed
actility:pollutherm:1updatedpoints updated (extractPoints / examples); driver code unchanged — Points only: the examples are identical to 4.0.0 once their points are set aside, and the bundle differs by index.js: the appended extractPoints. 1 example(s) changed: points no longer published status:1. Recorded under TXIF-4280, the ticket for drivers whose only change is their extractPoints.

smart-parks​

DriverChangeWhat changed
os1-smar:opencollar:1removedNo longer shipped: no model references this protocolId (commit d0c11e3d3) — The driver is still checked and tested but not packaged since commit d0c11e3d3 (feat(package): ship only what a model points at, 2026-09-10, no ticket): only protocolIds a model.yaml of the public catalog references are shipped. No model references os1-smar:opencollar:1.

socomec​

DriverChangeWhat changed
socomec:diris-b-10l:1updatedpoints updated (extractPoints / examples); driver code unchanged — The driver code is unchanged. What differs from 4.0.0: index.js: the appended extractPoints.

swisscom​

DriverChangeWhat changed
swisscom:multisense:1updatedexamples follow the standard output format ({ data }); driver code unchanged — What differs from 4.0.0: index.js: appended extractPoints; examples/all.examples.json: examples in the standard format (output under data); 10 example(s) empty in 4.0.0 now carry their decoded output.

tekelek​

DriverChangeWhat changed
spt-teke:tek-766-inc:1addedOneSitu OS110 and Tekelek TEK766 — SPOT migration drivers — SPOT drivers now referenced by the public OneSitu OS110 and Tekelek TEK766 models.

tektelic​

DriverChangeWhat changed
tektelic:agro:1updatedextractPoints publishes points the examples did not carry; driver code unchanged — Points only: the examples are identical to 4.0.0 once their points are set aside, and the bundle differs by index.js: the appended extractPoints. 4 example(s) changed: new points frequency; 3 example(s) without point now say points: null instead of {}. The extractPoints work of TXIF-4088 touched this driver after the 4.0.0 tag (commits a410ff591, 1eb681a7f, 34b7a1ca2). Recorded under TXIF-4280, the ticket for drivers whose only change is their extractPoints.
tektelic:industrial-trans:1updatedextractPoints publishes points the examples did not carry; driver code unchanged — Points only: the examples are identical to 4.0.0 once their points are set aside, and the bundle differs by index.js: the appended extractPoints. 2 example(s) changed: new points temperature, counter. The extractPoints work of TXIF-4088 touched this driver after the 4.0.0 tag (commits a410ff591, 1eb681a7f, 34b7a1ca2). Recorded under TXIF-4280, the ticket for drivers whose only change is their extractPoints.
tektelic:t0008781-stork:1updatedextractPoints publishes points the examples did not carry; driver code unchanged — Points only: the examples are identical to 4.0.0 once their points are set aside, and the bundle differs by index.js: the appended extractPoints. 12 example(s) changed: new points batteryLevel; 11 example(s) without point now say points: null instead of {}. The extractPoints work of TXIF-4088 touched this driver after the 4.0.0 tag (commits a410ff591, 1eb681a7f, 34b7a1ca2). Recorded under TXIF-4280, the ticket for drivers whose only change is their extractPoints.
tektelic:tundra:1updatedextractPoints publishes points the examples did not carry; driver code unchanged — Points only: the examples are identical to 4.0.0 once their points are set aside, and the bundle differs by index.js: the appended extractPoints. 3 example(s) changed: new points temperature, batteryVoltage, counter. The extractPoints work of TXIF-4088 touched this driver after the 4.0.0 tag (commits a410ff591, 1eb681a7f, 34b7a1ca2). Recorded under TXIF-4280, the ticket for drivers whose only change is their extractPoints.

terabee​

DriverChangeWhat changed
terabee:pc-l-xl:1updatedextractPoints publishes points the examples did not carry; driver code unchanged — Points only: the examples are identical to 4.0.0 once their points are set aside, and the bundle differs by index.js: the appended extractPoints. 10 example(s) changed: new points counter, counter:1; 8 example(s) without point now say points: null instead of {}. The extractPoints work of TXIF-4088 touched this driver after the 4.0.0 tag (commits a410ff591, 1eb681a7f, 34b7a1ca2). Recorded under TXIF-4280, the ticket for drivers whose only change is their extractPoints.
terabee:tb-pcm:1updatedextractPoints publishes points the examples did not carry; driver code unchanged — Points only: the examples are identical to 4.0.0 once their points are set aside, and the bundle differs by index.js: the appended extractPoints. 10 example(s) changed: new points counter, counter:1; 8 example(s) without point now say points: null instead of {}. The extractPoints work of TXIF-4088 touched this driver after the 4.0.0 tag (commits a410ff591, 1eb681a7f, 34b7a1ca2). Recorded under TXIF-4280, the ticket for drivers whose only change is their extractPoints.
terabee:tb-poc:1updatedextractPoints publishes points the examples did not carry; driver code unchanged — Points only: the examples are identical to 4.0.0 once their points are set aside, and the bundle differs by index.js: the appended extractPoints. 19 example(s) changed: new points counter:1, counter:2, counter:3, counter:4, counter:5, counter, counter:6, counter:7, counter:8; 15 example(s) without point now say points: null instead of {}. The extractPoints work of TXIF-4088 touched this driver after the 4.0.0 tag (commits a410ff591, 1eb681a7f, 34b7a1ca2). Recorded under TXIF-4280, the ticket for drivers whose only change is their extractPoints.

thermokon​

DriverChangeWhat changed
thrmkn:generic:1updatedBACnet mapping and normalization hooks updated; driver code unchanged — What differs from 4.0.0: index.js: esbuild wrapper; mapping.json modified; normalizeUplinkMapping.js added.
thrmkn:joylrw:1updatedextractPoints publishes points the examples did not carry; driver code unchanged — Points only: the examples are identical to 4.0.0 once their points are set aside, and the bundle differs by index.js: the esbuild wrapper. 3 example(s) changed: new points temperature; points no longer published temperature:1; 1 example(s) without point now say points: null instead of {}. The extractPoints work of TXIF-4088 touched this driver after the 4.0.0 tag (commits a410ff591, 34b7a1ca2, f49143077). Recorded under TXIF-4280, the ticket for drivers whose only change is their extractPoints.
thrmkn:sab07:1updatedBACnet mapping and normalization hooks updated; driver code unchanged — What differs from 4.0.0: index.js: esbuild wrapper; mapping.json modified.

tpl-sys​

DriverChangeWhat changed
tpl-sys:birdy-slim-iot:1updatedpoints updated (extractPoints / examples); driver code unchanged — Points only: the examples are identical to 4.0.0 once their points are set aside, and the bundle differs by index.js: the appended extractPoints. 1 example(s) changed: 1 example(s) without point now say points: null instead of {}. The extractPoints work of TXIF-4088 touched this driver after the 4.0.0 tag (commits a410ff591, 34b7a1ca2). Recorded under TXIF-4280, the ticket for drivers whose only change is their extractPoints.

twtg​

DriverChangeWhat changed
twtg:neon-vb:4updatedextractPoints publishes points the examples did not carry; driver code unchanged — Points only: the examples are identical to 4.0.0 once their points are set aside, and the bundle differs by index.js: the appended extractPoints. 14 example(s) changed: new points temperature:2, temperature:3, temperature:1, acceleration:1, acceleration:2, speed; 11 example(s) without point now say points: null instead of {}. The extractPoints work of TXIF-4088 touched this driver after the 4.0.0 tag (commits a410ff591, 34b7a1ca2). Recorded under TXIF-4280, the ticket for drivers whose only change is their extractPoints.

volley-boast​

DriverChangeWhat changed
vobo:generic:2updatedpoints updated (extractPoints / examples); driver code unchanged — Points only: the examples are identical to 4.0.0 once their points are set aside, and the bundle differs by index.js: the esbuild wrapper. 48 example(s) changed: 48 example(s) without point now say points: null instead of {}. The extractPoints work of TXIF-4088 touched this driver after the 4.0.0 tag (commit a410ff591). Recorded under TXIF-4280, the ticket for drivers whose only change is their extractPoints.

vutility​

DriverChangeWhat changed
vutility:hotdrop-direct:1updatedextractPoints publishes points the examples did not carry; driver code unchanged — Points only: the examples are identical to 4.0.0 once their points are set aside, and the bundle differs by index.js: the appended extractPoints. 4 example(s) changed: new points voltage, temperature. The extractPoints work of TXIF-4088 touched this driver after the 4.0.0 tag (commits a410ff591, 1eb681a7f, 34b7a1ca2). Recorded under TXIF-4280, the ticket for drivers whose only change is their extractPoints.

watteco​

DriverChangeWhat changed
watteco:atmo:4updatedBACnet mapping carried by the model's first protocolId; driver code unchanged — The driver code is unchanged. What differs from 4.0.0: index.js: a webpack rebuild, sources unchanged; main.js: the esbuild wrapper; mapping.json removed: the BACnet mapping is carried by the first protocolId of the model (its BACnet owner), not by this driver.
watteco:atmo:5updatedBACnet mapping and normalization hooks updated; driver code unchanged — What differs from 4.0.0: index.js: esbuild wrapper; main.js: esbuild wrapper; mapping.json modified.
watteco:climo:5updatedBACnet mapping and normalization hooks updated; driver code unchanged — What differs from 4.0.0: index.js: esbuild wrapper; main.js: esbuild wrapper; mapping.json modified.
watteco:closo:4updatedBACnet mapping carried by the model's first protocolId; driver code unchanged — The driver code is unchanged. What differs from 4.0.0: index.js: a webpack rebuild, sources unchanged; main.js: the esbuild wrapper; mapping.json removed: the BACnet mapping is carried by the first protocolId of the model (its BACnet owner), not by this driver.
watteco:closo:5updatedBACnet mapping and normalization hooks updated; driver code unchanged — What differs from 4.0.0: index.js: esbuild wrapper; main.js: esbuild wrapper; mapping.json modified.
watteco:flasho:4updatedBACnet mapping carried by the model's first protocolId; driver code unchanged — The driver code is unchanged. What differs from 4.0.0: index.js: a webpack rebuild, sources unchanged; main.js: the esbuild wrapper; mapping.json removed: the BACnet mapping is carried by the first protocolId of the model (its BACnet owner), not by this driver.
watteco:flasho:5updatedBACnet mapping and normalization hooks updated; driver code unchanged — What differs from 4.0.0: index.js: esbuild wrapper; main.js: esbuild wrapper; mapping.json modified.
watteco:hygrotemp-remote:5updatedBACnet mapping and normalization hooks updated; driver code unchanged — What differs from 4.0.0: index.js: esbuild wrapper; mapping.json modified.
watteco:hygrotempo:4updatedBACnet mapping carried by the model's first protocolId; driver code unchanged — The driver code is unchanged. What differs from 4.0.0: index.js: a webpack rebuild, sources unchanged; main.js: the esbuild wrapper; mapping.json removed: the BACnet mapping is carried by the first protocolId of the model (its BACnet owner), not by this driver.
watteco:hygrotempo:5updatedBACnet mapping and normalization hooks updated; driver code unchanged — What differs from 4.0.0: index.js: esbuild wrapper; main.js: esbuild wrapper; mapping.json modified.
watteco:inclino:4updatedBACnet mapping carried by the model's first protocolId; driver code unchanged — The driver code is unchanged. What differs from 4.0.0: index.js: a webpack rebuild, sources unchanged; main.js: the esbuild wrapper; mapping.json removed: the BACnet mapping is carried by the first protocolId of the model (its BACnet owner), not by this driver.
watteco:inclino:5updatedBACnet mapping and normalization hooks updated; driver code unchanged — What differs from 4.0.0: index.js: esbuild wrapper; main.js: esbuild wrapper; mapping.json modified.
watteco:indoor-temp:4updatedBACnet mapping carried by the model's first protocolId; driver code unchanged — The driver code is unchanged. What differs from 4.0.0: index.js: a webpack rebuild, sources unchanged; main.js: the esbuild wrapper; mapping.json removed: the BACnet mapping is carried by the first protocolId of the model (its BACnet owner), not by this driver.
watteco:indoor-temp:5updatedBACnet mapping and normalization hooks updated; driver code unchanged — What differs from 4.0.0: index.js: esbuild wrapper; main.js: esbuild wrapper; mapping.json modified.
watteco:ino:4updatedBACnet mapping carried by the model's first protocolId; driver code unchanged — The driver code is unchanged. What differs from 4.0.0: index.js: a webpack rebuild, sources unchanged; main.js: the esbuild wrapper; mapping.json removed: the BACnet mapping is carried by the first protocolId of the model (its BACnet owner), not by this driver.
watteco:ino:5updatedBACnet mapping and normalization hooks updated; driver code unchanged — What differs from 4.0.0: index.js: esbuild wrapper; main.js: esbuild wrapper; mapping.json modified.
watteco:intenso:4updatedBACnet mapping carried by the model's first protocolId; driver code unchanged — The driver code is unchanged. What differs from 4.0.0: index.js: a webpack rebuild, sources unchanged; main.js: the esbuild wrapper; mapping.json removed: the BACnet mapping is carried by the first protocolId of the model (its BACnet owner), not by this driver.
watteco:intenso:5updatedBACnet mapping and normalization hooks updated; driver code unchanged — What differs from 4.0.0: index.js: esbuild wrapper; main.js: esbuild wrapper; mapping.json modified.
watteco:levo:4updatedBACnet mapping carried by the model's first protocolId; driver code unchanged — The driver code is unchanged. What differs from 4.0.0: index.js: a webpack rebuild, sources unchanged; main.js: the esbuild wrapper; mapping.json removed: the BACnet mapping is carried by the first protocolId of the model (its BACnet owner), not by this driver.
watteco:levo:5updatedBACnet mapping and normalization hooks updated; driver code unchanged — What differs from 4.0.0: index.js: esbuild wrapper; main.js: esbuild wrapper; mapping.json modified.
watteco:modbus:4updatedBACnet mapping carried by the model's first protocolId; driver code unchanged — The driver code is unchanged. What differs from 4.0.0: index.js: a webpack rebuild, sources unchanged; main.js: the esbuild wrapper; mapping.json removed: the BACnet mapping is carried by the first protocolId of the model (its BACnet owner), not by this driver.
watteco:modbus:5updatedBACnet mapping and normalization hooks updated; driver code unchanged — What differs from 4.0.0: index.js: esbuild wrapper; main.js: esbuild wrapper; mapping.json modified.
watteco:monito:4updatedBACnet mapping carried by the model's first protocolId; driver code unchanged — The driver code is unchanged. What differs from 4.0.0: index.js: a webpack rebuild, sources unchanged; main.js: the esbuild wrapper; mapping.json removed: the BACnet mapping is carried by the first protocolId of the model (its BACnet owner), not by this driver.
watteco:monito:5updatedBACnet mapping and normalization hooks updated; driver code unchanged — What differs from 4.0.0: index.js: esbuild wrapper; main.js: esbuild wrapper; mapping.json modified.
watteco:moveo-lite:5updatedBACnet mapping and normalization hooks updated; driver code unchanged — What differs from 4.0.0: index.js: esbuild wrapper; main.js: esbuild wrapper; mapping.json modified; normalizeUplinkMapping.js added.
watteco:moveo:4updatedBACnet mapping carried by the model's first protocolId; driver code unchanged — The driver code is unchanged. What differs from 4.0.0: index.js: a webpack rebuild, sources unchanged; main.js: a webpack rebuild, sources unchanged; mapping.json removed: the BACnet mapping is carried by the first protocolId of the model (its BACnet owner), not by this driver.
watteco:outdoor-temp:4updatedBACnet mapping carried by the model's first protocolId; driver code unchanged — The driver code is unchanged. What differs from 4.0.0: index.js: a webpack rebuild, sources unchanged; main.js: the esbuild wrapper; mapping.json removed: the BACnet mapping is carried by the first protocolId of the model (its BACnet owner), not by this driver.
watteco:pilot-wire:4updatedBACnet mapping carried by the model's first protocolId; driver code unchanged — The driver code is unchanged. What differs from 4.0.0: index.js: a webpack rebuild, sources unchanged; main.js: the esbuild wrapper; mapping.json removed: the BACnet mapping is carried by the first protocolId of the model (its BACnet owner), not by this driver.
watteco:presso:4updatedBACnet mapping carried by the model's first protocolId; driver code unchanged — The driver code is unchanged. What differs from 4.0.0: index.js: a webpack rebuild, sources unchanged; main.js: the esbuild wrapper; mapping.json removed: the BACnet mapping is carried by the first protocolId of the model (its BACnet owner), not by this driver.
watteco:presso:5updatedBACnet mapping and normalization hooks updated; driver code unchanged — What differs from 4.0.0: index.js: esbuild wrapper; main.js: esbuild wrapper; mapping.json modified.
watteco:pulse-senso-atex:4updatedBACnet mapping carried by the model's first protocolId; driver code unchanged — The driver code is unchanged. What differs from 4.0.0: index.js: a webpack rebuild, sources unchanged; main.js: the esbuild wrapper; mapping.json removed: the BACnet mapping is carried by the first protocolId of the model (its BACnet owner), not by this driver.
watteco:pulse-senso-atex:5updatedBACnet mapping and normalization hooks updated; driver code unchanged — What differs from 4.0.0: index.js: esbuild wrapper; main.js: esbuild wrapper; mapping.json modified.
watteco:pulse-senso:4updatedBACnet mapping carried by the model's first protocolId; driver code unchanged — The driver code is unchanged. What differs from 4.0.0: index.js: a webpack rebuild, sources unchanged; main.js: a webpack rebuild, sources unchanged; mapping.json removed: the BACnet mapping is carried by the first protocolId of the model (its BACnet owner), not by this driver.
watteco:pulse-senso:5updatedBACnet mapping and normalization hooks updated; driver code unchanged — What differs from 4.0.0: index.js: esbuild wrapper; main.js: esbuild wrapper; mapping.json modified.
watteco:remote-temp:4updatedBACnet mapping carried by the model's first protocolId; driver code unchanged — The driver code is unchanged. What differs from 4.0.0: index.js: a webpack rebuild, sources unchanged; main.js: the esbuild wrapper; mapping.json removed: the BACnet mapping is carried by the first protocolId of the model (its BACnet owner), not by this driver.
watteco:remote-temp2:4updatedBACnet mapping carried by the model's first protocolId; driver code unchanged — The driver code is unchanged. What differs from 4.0.0: index.js: a webpack rebuild, sources unchanged; main.js: the esbuild wrapper; mapping.json removed: the BACnet mapping is carried by the first protocolId of the model (its BACnet owner), not by this driver.
watteco:smart-plug:4updatedBACnet mapping carried by the model's first protocolId; driver code unchanged — The driver code is unchanged. What differs from 4.0.0: index.js: a webpack rebuild, sources unchanged; main.js: the esbuild wrapper; mapping.json removed: the BACnet mapping is carried by the first protocolId of the model (its BACnet owner), not by this driver.
watteco:smart-plug:5updatedBACnet mapping and normalization hooks updated; driver code unchanged — What differs from 4.0.0: index.js: esbuild wrapper; main.js: esbuild wrapper; mapping.json modified.
watteco:smartpilot-wire:5updatedBACnet mapping and normalization hooks updated; driver code unchanged — What differs from 4.0.0: index.js: esbuild wrapper; main.js: esbuild wrapper; mapping.json modified.
watteco:temp-remte-1-prb:5updatedBACnet mapping and normalization hooks updated; driver code unchanged — What differs from 4.0.0: index.js: esbuild wrapper; main.js: esbuild wrapper; mapping.json modified.
watteco:temp-remte-2-prb:5updatedBACnet mapping and normalization hooks updated; driver code unchanged — What differs from 4.0.0: index.js: esbuild wrapper; main.js: esbuild wrapper; mapping.json modified.
watteco:tempo-outdoor:5updatedBACnet mapping and normalization hooks updated; driver code unchanged — What differs from 4.0.0: index.js: esbuild wrapper; main.js: esbuild wrapper; mapping.json modified.
watteco:tempo:5updatedBACnet mapping and normalization hooks updated; driver code unchanged — What differs from 4.0.0: index.js: esbuild wrapper; mapping.json modified.
watteco:th:4updatedBACnet mapping and normalization hooks updated; driver code unchanged — What differs from 4.0.0: index.js: webpack rebuild, sources unchanged; main.js: esbuild wrapper; README.md removed; mapping.json removed.
watteco:th:5updatedBACnet mapping and normalization hooks updated; driver code unchanged — What differs from 4.0.0: index.js: esbuild wrapper; main.js: esbuild wrapper; README.md removed; mapping.json modified.
watteco:ticso:4updatedBACnet mapping carried by the model's first protocolId; driver code unchanged — The driver code is unchanged. What differs from 4.0.0: index.js: a webpack rebuild, sources unchanged; main.js: the esbuild wrapper; mapping.json removed: the BACnet mapping is carried by the first protocolId of the model (its BACnet owner), not by this driver.
watteco:ticso:5updatedBACnet mapping and normalization hooks updated; driver code unchanged — What differs from 4.0.0: index.js: esbuild wrapper; mapping.json modified.
watteco:torano-atex:4updatedBACnet mapping carried by the model's first protocolId; driver code unchanged — The driver code is unchanged. What differs from 4.0.0: index.js: a webpack rebuild, sources unchanged; main.js: the esbuild wrapper; mapping.json removed: the BACnet mapping is carried by the first protocolId of the model (its BACnet owner), not by this driver.
watteco:torano-atex:5updatedBACnet mapping and normalization hooks updated; driver code unchanged — What differs from 4.0.0: index.js: esbuild wrapper; main.js: esbuild wrapper; mapping.json modified.
watteco:triphaso:4updatedBACnet mapping carried by the model's first protocolId; driver code unchanged — The driver code is unchanged. What differs from 4.0.0: index.js: a webpack rebuild, sources unchanged; main.js: the esbuild wrapper; mapping.json removed: the BACnet mapping is carried by the first protocolId of the model (its BACnet owner), not by this driver.
watteco:triphaso:5updatedBACnet mapping and normalization hooks updated; driver code unchanged — What differs from 4.0.0: index.js: esbuild wrapper; main.js: esbuild wrapper; mapping.json modified.
watteco:vaqao-lite:5updatedBACnet mapping and normalization hooks updated; driver code unchanged — What differs from 4.0.0: index.js: esbuild wrapper; main.js: esbuild wrapper; mapping.json modified; normalizeUplinkMapping.js added.
watteco:vaqao-lt:4updatedBACnet mapping and normalization hooks updated; driver code unchanged — What differs from 4.0.0: index.js: webpack rebuild, sources unchanged; main.js: esbuild wrapper; mapping.json modified.
watteco:vaqao-plus:4updatedpoints follow the ontology units; BACnet mapping work — The private extractPoints.js was normalised so every unit is an ontology id (baee21505), alongside the Watteco BACnet and Modbus mapping work (b52998614, 167b3462a). The decoding code is unchanged; driver.yaml also regained its manufacturer codec version (ca1058c6a, TXIF-4282), which the packaging reads but the comparison ignores.
watteco:vaqao:4updatedBACnet mapping carried by the model's first protocolId; driver code unchanged — The driver code is unchanged. What differs from 4.0.0: index.js: a webpack rebuild, sources unchanged; main.js: the esbuild wrapper; mapping.json removed: the BACnet mapping is carried by the first protocolId of the model (its BACnet owner), not by this driver.
watteco:ventilo:4updatedBACnet mapping carried by the model's first protocolId; driver code unchanged — The driver code is unchanged. What differs from 4.0.0: index.js: a webpack rebuild, sources unchanged; main.js: the esbuild wrapper; mapping.json removed: the BACnet mapping is carried by the first protocolId of the model (its BACnet owner), not by this driver.
watteco:ventilo:5updatedBACnet mapping and normalization hooks updated; driver code unchanged — What differs from 4.0.0: index.js: esbuild wrapper; main.js: esbuild wrapper; mapping.json modified.

wavetrend​

DriverChangeWhat changed
wavetrnd:sd01-l:1updatedpoints updated (extractPoints / examples); driver code unchanged — Points only: the examples are identical to 4.0.0 once their points are set aside, and the bundle differs by index.js: a webpack rebuild. 1 example(s) changed: changed temperature:10 (records), temperature:11 (records). Recorded under TXIF-4280, the ticket for drivers whose only change is their extractPoints.

wika​

DriverChangeWhat changed
wika:pgu2x-100:1updatedextractPoints publishes points the examples did not carry; driver code unchanged — Points only: the examples are identical to 4.0.0 once their points are set aside, and the bundle differs by index.js: the appended extractPoints. 1 example(s) changed: new points pressureLevel; points no longer published pressure. The extractPoints work of TXIF-4088 touched this driver after the 4.0.0 tag (commits a410ff591, 5be3e6d5f). Recorded under TXIF-4280, the ticket for drivers whose only change is their extractPoints.

yobiiq​

DriverChangeWhat changed
yobiiq:em2101:1updatedextractPoints publishes points the examples did not carry; driver code unchanged — Points only: the examples are identical to 4.0.0 once their points are set aside, and the bundle differs by index.js: the appended extractPoints. 8 example(s) changed: new points energy:1, energy:2; 7 example(s) without point now say points: null instead of {}. The extractPoints work of TXIF-4088 touched this driver after the 4.0.0 tag (commits a410ff591, 1eb681a7f, 34b7a1ca2). Recorded under TXIF-4280, the ticket for drivers whose only change is their extractPoints.
yobiiq:em4301:1updatedextractPoints publishes points the examples did not carry; driver code unchanged — Points only: the examples are identical to 4.0.0 once their points are set aside, and the bundle differs by index.js: the appended extractPoints. 6 example(s) changed: new points current, voltage; 5 example(s) without point now say points: null instead of {}. The extractPoints work of TXIF-4088 touched this driver after the 4.0.0 tag (commits a410ff591, 1eb681a7f, 34b7a1ca2). Recorded under TXIF-4280, the ticket for drivers whose only change is their extractPoints.
yobiiq:iq-rm200-lrw:2updatedextractPoints publishes points the examples did not carry; driver code unchanged — Points only: the examples are identical to 4.0.0 once their points are set aside, and the bundle differs by index.js: the appended extractPoints. 10 example(s) changed: new points batteryLevel, batteryVoltage; 9 example(s) without point now say points: null instead of {}. The extractPoints work of TXIF-4088 touched this driver after the 4.0.0 tag (commits a410ff591, 1eb681a7f, 34b7a1ca2). Recorded under TXIF-4280, the ticket for drivers whose only change is their extractPoints.
yobiiq:sd-1001:1updatedextractPoints publishes points the examples did not carry; driver code unchanged — Points only: the examples are identical to 4.0.0 once their points are set aside, and the bundle differs by index.js: the appended extractPoints. 6 example(s) changed: new points batteryLevel; 5 example(s) without point now say points: null instead of {}. The extractPoints work of TXIF-4088 touched this driver after the 4.0.0 tag (commits a410ff591, 1eb681a7f, 34b7a1ca2). Recorded under TXIF-4280, the ticket for drivers whose only change is their extractPoints.

yokogawa​

DriverChangeWhat changed
yokogawa:sushi:1updatedexamples follow the standard output format ({ data }); driver code unchanged — What differs from 4.0.0: index.js: appended extractPoints; examples/all.examples.json: examples in the standard format (output under data); 4 example(s) empty in 4.0.0 now carry their decoded output.

zenner​

DriverChangeWhat changed
zenner:co2-ind-ID-A:1updatedpoints updated (extractPoints / examples); driver code unchanged — What differs from 4.0.0: index.js: esbuild wrapper; README.md removed; examples/all.examples.json: points only.
zenner:zelsius-c5-cmf:1updatedpoints updated (extractPoints / examples); driver code unchanged — Points only: the examples are identical to 4.0.0 once their points are set aside, and the bundle differs by index.js: the esbuild wrapper. 1 example(s) changed: 1 example(s) without point now say points: null instead of {}. The extractPoints work of TXIF-4088 touched this driver after the 4.0.0 tag (commit a410ff591). Recorded under TXIF-4280, the ticket for drivers whose only change is their extractPoints.

Device profiles​

adeunis​

ModelChangeWhat changed
adeunis:demonstrator:1updatedDevice profiles added or removed for this model — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.

birdz​

ModelChangeWhat changed
birdz:api-bi:10addedBirdz device models for the Senet to ThingPark Enterprise migration — 30 models linked to the new Birdz EU868 Class A profiles. No protocolId is linked: the request covers device profiles only, without payload decoding.
birdz:api-vanne:10addedBirdz device models for the Senet to ThingPark Enterprise migration — 30 models linked to the new Birdz EU868 Class A profiles. No protocolId is linked: the request covers device profiles only, without payload decoding.
birdz:apilinkv2:20addedBirdz device models for the Senet to ThingPark Enterprise migration — 30 models linked to the new Birdz EU868 Class A profiles. No protocolId is linked: the request covers device profiles only, without payload decoding.
birdz:bridgev1-0:10addedBirdz device models for the Senet to ThingPark Enterprise migration — 30 models linked to the new Birdz EU868 Class A profiles. No protocolId is linked: the request covers device profiles only, without payload decoding.
birdz:bridgev1-5:15addedBirdz device models for the Senet to ThingPark Enterprise migration — 30 models linked to the new Birdz EU868 Class A profiles. No protocolId is linked: the request covers device profiles only, without payload decoding.
birdz:bridgev2-0:20addedBirdz device models for the Senet to ThingPark Enterprise migration — 30 models linked to the new Birdz EU868 Class A profiles. No protocolId is linked: the request covers device profiles only, without payload decoding.
birdz:bridgev2-1:21addedBirdz device models for the Senet to ThingPark Enterprise migration — 30 models linked to the new Birdz EU868 Class A profiles. No protocolId is linked: the request covers device profiles only, without payload decoding.
birdz:bridgev2-3:23addedBirdz device models for the Senet to ThingPark Enterprise migration — 30 models linked to the new Birdz EU868 Class A profiles. No protocolId is linked: the request covers device profiles only, without payload decoding.
birdz:bridgev2-4:24addedBirdz device models for the Senet to ThingPark Enterprise migration — 30 models linked to the new Birdz EU868 Class A profiles. No protocolId is linked: the request covers device profiles only, without payload decoding.
birdz:btoolz:1addedBirdz device models for the Senet to ThingPark Enterprise migration — 30 models linked to the new Birdz EU868 Class A profiles. No protocolId is linked: the request covers device profiles only, without payload decoding.
birdz:custom-customg3r:1addedBirdz device models for the Senet to ThingPark Enterprise migration — 30 models linked to the new Birdz EU868 Class A profiles. No protocolId is linked: the request covers device profiles only, without payload decoding.
birdz:custom-customsf1:1addedBirdz device models for the Senet to ThingPark Enterprise migration — 30 models linked to the new Birdz EU868 Class A profiles. No protocolId is linked: the request covers device profiles only, without payload decoding.
birdz:deporte-g3v1:10addedBirdz device models for the Senet to ThingPark Enterprise migration — 30 models linked to the new Birdz EU868 Class A profiles. No protocolId is linked: the request covers device profiles only, without payload decoding.
birdz:deporte-g3v2:20addedBirdz device models for the Senet to ThingPark Enterprise migration — 30 models linked to the new Birdz EU868 Class A profiles. No protocolId is linked: the request covers device profiles only, without payload decoding.
birdz:deporte-sm4-3:10addedBirdz device models for the Senet to ThingPark Enterprise migration — 30 models linked to the new Birdz EU868 Class A profiles. No protocolId is linked: the request covers device profiles only, without payload decoding.
birdz:fillink:10addedBirdz device models for the Senet to ThingPark Enterprise migration — 30 models linked to the new Birdz EU868 Class A profiles. No protocolId is linked: the request covers device profiles only, without payload decoding.
birdz:g3v1:10addedBirdz device models for the Senet to ThingPark Enterprise migration — 30 models linked to the new Birdz EU868 Class A profiles. No protocolId is linked: the request covers device profiles only, without payload decoding.
birdz:g3v2-ja-delay-15:20addedBirdz device models for the Senet to ThingPark Enterprise migration — 30 models linked to the new Birdz EU868 Class A profiles. No protocolId is linked: the request covers device profiles only, without payload decoding.
birdz:g3v2:20addedBirdz device models for the Senet to ThingPark Enterprise migration — 30 models linked to the new Birdz EU868 Class A profiles. No protocolId is linked: the request covers device profiles only, without payload decoding.
birdz:g3v3:30addedBirdz device models for the Senet to ThingPark Enterprise migration — 30 models linked to the new Birdz EU868 Class A profiles. No protocolId is linked: the request covers device profiles only, without payload decoding.
birdz:g3v4:50addedBirdz device models for the Senet to ThingPark Enterprise migration — 30 models linked to the new Birdz EU868 Class A profiles. No protocolId is linked: the request covers device profiles only, without payload decoding.
birdz:g3v5:50addedBirdz device models for the Senet to ThingPark Enterprise migration — 30 models linked to the new Birdz EU868 Class A profiles. No protocolId is linked: the request covers device profiles only, without payload decoding.
birdz:luka:10addedBirdz device models for the Senet to ThingPark Enterprise migration — 30 models linked to the new Birdz EU868 Class A profiles. No protocolId is linked: the request covers device profiles only, without payload decoding.
birdz:minotaure-c:10addedBirdz device models for the Senet to ThingPark Enterprise migration — 30 models linked to the new Birdz EU868 Class A profiles. No protocolId is linked: the request covers device profiles only, without payload decoding.
birdz:minotaure-vt:10addedBirdz device models for the Senet to ThingPark Enterprise migration — 30 models linked to the new Birdz EU868 Class A profiles. No protocolId is linked: the request covers device profiles only, without payload decoding.
birdz:relay:10addedBirdz device models for the Senet to ThingPark Enterprise migration — 30 models linked to the new Birdz EU868 Class A profiles. No protocolId is linked: the request covers device profiles only, without payload decoding.
birdz:sewerin:10addedBirdz device models for the Senet to ThingPark Enterprise migration — 30 models linked to the new Birdz EU868 Class A profiles. No protocolId is linked: the request covers device profiles only, without payload decoding.
birdz:sm4-1:10addedBirdz device models for the Senet to ThingPark Enterprise migration — 30 models linked to the new Birdz EU868 Class A profiles. No protocolId is linked: the request covers device profiles only, without payload decoding.
birdz:sm4-2:10addedBirdz device models for the Senet to ThingPark Enterprise migration — 30 models linked to the new Birdz EU868 Class A profiles. No protocolId is linked: the request covers device profiles only, without payload decoding.
birdz:sm4-3:10addedBirdz device models for the Senet to ThingPark Enterprise migration — 30 models linked to the new Birdz EU868 Class A profiles. No protocolId is linked: the request covers device profiles only, without payload decoding.

elvaco​

ModelChangeWhat changed
elvaco:cmi4160:1updatedDevice profiles added or removed for this model — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
elvaco:cmi4170:1updatedDevice profiles added or removed for this model — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.

embit​

ModelChangeWhat changed
embit:emb-lr1280-mpci:1updatedDevice profiles added or removed for this model — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
embit:emb-lr1302-mpci:1updatedDevice profiles added or removed for this model — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
embit:emb-lrwl55:1updatedDevice profiles added or removed for this model — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.

generic​

ModelChangeWhat changed
generic:lora:1updatedDevice profiles added or removed for this model — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.

globalsat​

ModelChangeWhat changed
glbsat:lt-501:1updatedDevice profiles added or removed for this model — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
glbsat:lw-360hr:1updatedDevice profiles added or removed for this model — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.

inbiot​

ModelChangeWhat changed
inbiot:mica:1addedinBiot MICA device family (GitHub PR #283) — MICA, MICA MINI, MICA PLUS and MICA WELL, all linked to inbiot:inbiot-decoder:1, with ontology-compliant sensor declarations.
inbiot:mini:1addedinBiot MICA device family (GitHub PR #283) — MICA, MICA MINI, MICA PLUS and MICA WELL, all linked to inbiot:inbiot-decoder:1, with ontology-compliant sensor declarations.
inbiot:plus:1addedinBiot MICA device family (GitHub PR #283) — MICA, MICA MINI, MICA PLUS and MICA WELL, all linked to inbiot:inbiot-decoder:1, with ontology-compliant sensor declarations.
inbiot:well:1addedinBiot MICA device family (GitHub PR #283) — MICA, MICA MINI, MICA PLUS and MICA WELL, all linked to inbiot:inbiot-decoder:1, with ontology-compliant sensor declarations.

itron​

ModelChangeWhat changed
itron:cyble-5:1updatedDevice profiles added or removed for this model — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.

kamstrup​

ModelChangeWhat changed
kamstrup:hc-003-55-mc:1addedKamstrup HC-003-55 Multical (GitHub PR #284)

mclimate​

ModelChangeWhat changed
mclimate:16a-dry-switch:1updatedMClimate range aligned on the manufacturer drivers
mclimate:16a-spm:1updatedMClimate range aligned on the manufacturer drivers
mclimate:aqi-sensor:1deprecatedmodel deprecated, kept for the devices already provisioned on it — Superseded by the MClimate range rebuilt from the manufacturer drivers.
mclimate:co2-display-lite:1updatedMClimate range aligned on the manufacturer drivers
mclimate:co2-display:1updatedMClimate range aligned on the manufacturer drivers
mclimate:co2-notifier:1updatedMClimate range aligned on the manufacturer drivers
mclimate:co2-pir-lite:1updatedMClimate range aligned on the manufacturer drivers
mclimate:co2-sensor:1deprecatedmodel deprecated, kept for the devices already provisioned on it — Superseded by the MClimate range rebuilt from the manufacturer drivers.
mclimate:fan-coil:1updateddevice profiles realigned with the manufacturer drivers — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
mclimate:flood-sensor:1updateddevice profiles realigned with the manufacturer drivers — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
mclimate:ht-pir-lite:1updatedMClimate range aligned on the manufacturer drivers
mclimate:ht-sensor:1updateddevice profiles realigned with the manufacturer drivers — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
mclimate:multipurpose-btn:1updatedMClimate range aligned on the manufacturer drivers
mclimate:open-close:1updateddevice profiles realigned with the manufacturer drivers — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
mclimate:pir-mini:1addedMClimate range aligned on the manufacturer drivers
mclimate:t-valve:1updateddevice profiles realigned with the manufacturer drivers — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
mclimate:vicki:1updateddevice profiles realigned with the manufacturer drivers — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
mclimate:w-thermostat:1updatedMClimate range aligned on the manufacturer drivers

merryiot​

ModelChangeWhat changed
merryiot:ms10:1updatedDevice profiles added or removed for this model — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.

micropelt​

ModelChangeWhat changed
microplt:mlrtps:1updatedDevice profiles added or removed for this model — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.

milesight-iot​

ModelChangeWhat changed
msight:am102:1updateddevice profiles realigned with the official Milesight SensorDecoders drivers — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
msight:am102l:1updateddevice profiles realigned with the official Milesight SensorDecoders drivers — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
msight:am103:1addedMilesight catalog realignment on the official SensorDecoders reference
msight:am103am103l:1deprecatedmodel deprecated, kept for the devices already provisioned on it — Combined model, superseded by the individual AM103 and AM103L models.
msight:am103l:1addedMilesight catalog realignment on the official SensorDecoders reference
msight:am104:1updateddevice profiles realigned with the official Milesight SensorDecoders drivers — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
msight:am107:1updateddevice profiles realigned with the official Milesight SensorDecoders drivers — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
msight:am304l:1addedmodel declared for a driver the catalog already shipped
msight:am305l:1addedmodel declared for a driver the catalog already shipped
msight:am307:1updateddevice profiles realigned with the official Milesight SensorDecoders drivers — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
msight:am307l:1addedmodel declared for a driver the catalog already shipped
msight:am308:1updateddevice profiles realigned with the official Milesight SensorDecoders drivers — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
msight:am308l:1addedmodel declared for a driver the catalog already shipped
msight:am319-hcho-ir:1addedMilesight catalog realignment on the official SensorDecoders reference
msight:am319-hcho-well:1addedMilesight catalog realignment on the official SensorDecoders reference
msight:am319-hcho:1addedMilesight catalog realignment on the official SensorDecoders reference
msight:am319-o3:1addedMilesight catalog realignment on the official SensorDecoders reference
msight:am319:1deprecatedmodel deprecated, kept for the devices already provisioned on it — Combined model, superseded by the individual AM319 variant models.
msight:am319l-hcho-ir:1addedMilesight catalog realignment on the official SensorDecoders reference
msight:am319l-o3:1addedMilesight catalog realignment on the official SensorDecoders reference
msight:at101:1updateddevice profiles realigned with the official Milesight SensorDecoders drivers — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
msight:ct101:1updateddevice profiles realigned with the official Milesight SensorDecoders drivers — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
msight:ct103:1updateddevice profiles realigned with the official Milesight SensorDecoders drivers — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
msight:ct105:1updateddevice profiles realigned with the official Milesight SensorDecoders drivers — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
msight:ct303:1updateddevice profiles realigned with the official Milesight SensorDecoders drivers — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
msight:ct305:1updateddevice profiles realigned with the official Milesight SensorDecoders drivers — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
msight:ct310:1updateddevice profiles realigned with the official Milesight SensorDecoders drivers — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
msight:cth01-compress:1addedMilesight catalog realignment on the official SensorDecoders reference
msight:cth01:1addedMilesight catalog realignment on the official SensorDecoders reference
msight:ds3604:1addedmodel declared for a driver the catalog already shipped
msight:em300-cl:1updateddevice profiles realigned with the official Milesight SensorDecoders drivers — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
msight:em300-di-hall:1addedmodel declared for a driver the catalog already shipped
msight:em300-mcs:1updateddevice profiles realigned with the official Milesight SensorDecoders drivers — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
msight:em300-mld:1updateddevice profiles realigned with the official Milesight SensorDecoders drivers — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
msight:em300-sld:1updateddevice profiles realigned with the official Milesight SensorDecoders drivers — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
msight:em300-zld:1updateddevice profiles realigned with the official Milesight SensorDecoders drivers — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
msight:em310-tilt:1updateddevice profiles realigned with the official Milesight SensorDecoders drivers — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
msight:em320-tilt:1updateddevice profiles realigned with the official Milesight SensorDecoders drivers — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
msight:em400-mud:1updateddevice profiles realigned with the official Milesight SensorDecoders drivers — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
msight:em400-tld:1updateddevice profiles realigned with the official Milesight SensorDecoders drivers — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
msight:em400-udl:1updateddevice profiles realigned with the official Milesight SensorDecoders drivers — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
msight:em500-smt:1deprecatedmodel deprecated, kept for the devices already provisioned on it — TTN-only codec; the Milesight reference publishes EM500-SMTC, a different sensor.
msight:em500-smtc:1updateddevice profiles realigned with the official Milesight SensorDecoders drivers — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
msight:em500-swl:1updateddevice profiles realigned with the official Milesight SensorDecoders drivers — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
msight:gs524n:1addedmodel declared for a driver the catalog already shipped
msight:gs601:1updateddevice profiles realigned with the official Milesight SensorDecoders drivers — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
msight:ts101:1updateddevice profiles realigned with the official Milesight SensorDecoders drivers — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
msight:ts201:1updateddevice profiles realigned with the official Milesight SensorDecoders drivers — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
msight:ts301:1updateddevice profiles realigned with the official Milesight SensorDecoders drivers — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
msight:ts302:1updateddevice profiles realigned with the official Milesight SensorDecoders drivers — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
msight:ts601:1addedmodel declared for a driver the catalog already shipped
msight:ts602:1addedmodel declared for a driver the catalog already shipped
msight:uc100:1updateddevice profiles realigned with the official Milesight SensorDecoders drivers — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
msight:uc11-n1:1addedMilesight catalog realignment on the official SensorDecoders reference
msight:uc11-t1:1addedMilesight catalog realignment on the official SensorDecoders reference
msight:uc1114:1deprecatedmodel deprecated, kept for the devices already provisioned on it — TTN-specific UC11 naming, superseded by UC11-N1, UC11-T1 and UC11xx.
msight:uc1122:1deprecatedmodel deprecated, kept for the devices already provisioned on it — TTN-specific UC11 naming, superseded by UC11-N1, UC11-T1 and UC11xx.
msight:uc1152:1deprecatedmodel deprecated, kept for the devices already provisioned on it — TTN-specific UC11 naming, superseded by UC11-N1, UC11-T1 and UC11xx.
msight:uc11xx:1addedMilesight catalog realignment on the official SensorDecoders reference
msight:uc3xxx:1addedmodel declared for a driver the catalog already shipped
msight:uc501:1addedMilesight catalog realignment on the official SensorDecoders reference
msight:uc502:1addedMilesight catalog realignment on the official SensorDecoders reference
msight:uc50x:1deprecatedmodel deprecated, kept for the devices already provisioned on it — Combined model, superseded by UC501 and UC502.
msight:uc511:1addedMilesight catalog realignment on the official SensorDecoders reference
msight:uc512:1addedMilesight catalog realignment on the official SensorDecoders reference
msight:uc51x:1deprecatedmodel deprecated, kept for the devices already provisioned on it — Combined model, superseded by UC511, UC512 and UC521.
msight:uc521:1addedMilesight catalog realignment on the official SensorDecoders reference
msight:vs121:1updateddevice profiles realigned with the official Milesight SensorDecoders drivers — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
msight:vs340:1updateddevice profiles realigned with the official Milesight SensorDecoders drivers — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
msight:vs341:1updateddevice profiles realigned with the official Milesight SensorDecoders drivers — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
msight:vs351:1updateddevice profiles realigned with the official Milesight SensorDecoders drivers — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
msight:vs360:1updateddevice profiles realigned with the official Milesight SensorDecoders drivers — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
msight:ws101:1updateddevice profiles realigned with the official Milesight SensorDecoders drivers — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
msight:ws136:1addedMilesight catalog realignment on the official SensorDecoders reference
msight:ws136ws156:1deprecatedmodel deprecated, kept for the devices already provisioned on it — Combined model, superseded by the individual WS136 and WS156 models.
msight:ws156:1addedMilesight catalog realignment on the official SensorDecoders reference
msight:ws202:1updateddevice profiles realigned with the official Milesight SensorDecoders drivers — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
msight:ws203:1updateddevice profiles realigned with the official Milesight SensorDecoders drivers — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
msight:ws301:1updateddevice profiles realigned with the official Milesight SensorDecoders drivers — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
msight:ws302:1updateddevice profiles realigned with the official Milesight SensorDecoders drivers — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
msight:ws303:1updateddevice profiles realigned with the official Milesight SensorDecoders drivers — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
msight:ws501-cn:1addedMilesight catalog realignment on the official SensorDecoders reference
msight:ws501-eu:1addedMilesight catalog realignment on the official SensorDecoders reference
msight:ws501-us:1addedMilesight catalog realignment on the official SensorDecoders reference
msight:ws501-v4:1addedMilesight catalog realignment on the official SensorDecoders reference
msight:ws501:1addedMilesight catalog realignment on the official SensorDecoders reference
msight:ws502-cn:1addedMilesight catalog realignment on the official SensorDecoders reference
msight:ws502-eu:1addedMilesight catalog realignment on the official SensorDecoders reference
msight:ws502-v4:1addedMilesight catalog realignment on the official SensorDecoders reference
msight:ws502:1addedMilesight catalog realignment on the official SensorDecoders reference
msight:ws503-cn:1addedMilesight catalog realignment on the official SensorDecoders reference
msight:ws503-v4:1addedMilesight catalog realignment on the official SensorDecoders reference
msight:ws503:1addedMilesight catalog realignment on the official SensorDecoders reference
msight:ws50x:1deprecatedmodel deprecated, kept for the devices already provisioned on it — TTN legacy generic model, superseded by WS501, WS502 and WS503.
msight:ws513-eu:1updateddevice profiles realigned with the official Milesight SensorDecoders drivers — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
msight:ws513-v3:1addedMilesight catalog realignment on the official SensorDecoders reference
msight:ws513:1addedMilesight catalog realignment on the official SensorDecoders reference
msight:ws515-v3:1addedMilesight catalog realignment on the official SensorDecoders reference
msight:ws515:1updateddevice profiles realigned with the official Milesight SensorDecoders drivers — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
msight:ws51x:1updateddevice profiles realigned with the official Milesight SensorDecoders drivers — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
msight:ws523:1updateddevice profiles realigned with the official Milesight SensorDecoders drivers — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
msight:ws525:1addedmodel declared for a driver the catalog already shipped
msight:ws52x:1deprecatedmodel deprecated, kept for the devices already provisioned on it — TTN legacy generic driver, superseded by the individual WS523 and WS525 models.
msight:wt102:1addedMilesight catalog realignment on the official SensorDecoders reference
msight:wt201:1updateddevice profiles realigned with the official Milesight SensorDecoders drivers — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
msight:wt211:1addedMilesight catalog realignment on the official SensorDecoders reference
msight:wt301-wt302:1deprecatedmodel deprecated, kept for the devices already provisioned on it — Combined model, superseded by the individual WT301 and WT302 models.
msight:wt301:1addedMilesight catalog realignment on the official SensorDecoders reference
msight:wt302:1addedMilesight catalog realignment on the official SensorDecoders reference
msight:wt303:1updateddevice profiles realigned with the official Milesight SensorDecoders drivers — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
msight:wt304:1updateddevice profiles realigned with the official Milesight SensorDecoders drivers — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
msight:wt401:1addedmodel declared for a driver the catalog already shipped
msight:wts305:1deprecatedmodel deprecated, kept for the devices already provisioned on it — Absent from the official Milesight SensorDecoders reference, with no equivalent modern driver.
msight:wts506:1updateddevice profiles realigned with the official Milesight SensorDecoders drivers — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.

nexelec​

ModelChangeWhat changed
nexelec:air-plus:1addedNexelec models linked to their renamed device profile
nexelec:atmo-plus:1addedNexelec models linked to their renamed device profile
nexelec:feel-plus:1addedNexelec models linked to their renamed device profile
nexelec:move-plus:1addedNexelec models linked to their renamed device profile
nexelec:rise-plus:1addedNexelec models linked to their renamed device profile
nexelec:sense-plus:1addedNexelec models linked to their renamed device profile
nexelec:sign-plus:1addedNexelec models linked to their renamed device profile
nexelec:track-plus:1addedNexelec models linked to their renamed device profile
nexelec:wave-plus:1addedNexelec models linked to their renamed device profile

onesitu​

ModelChangeWhat changed
onesitu:os110:1addedOneSitu OS110 imported for the SPOT to ThingPark migration — Linked to the imported SPOT protocolId spt-ones:os110:1, with an EU868 LoRaWAN 1.0.2 revB class A fallback profile pending confirmed vendor data.

rakwireless​

ModelChangeWhat changed
rakwirel:rak2560:1updatedDevice profiles added or removed for this model — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
rakwirel:rak7431:1updatedDevice profiles added or removed for this model — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.

ruixinghengfang-network​

ModelChangeWhat changed
ruixingh:rhf0m003:1updatedDevice profiles added or removed for this model — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
ruixingh:rhf0m0e5:1updatedDevice profiles added or removed for this model — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
ruixingh:rhf1s052:1updatedDevice profiles added or removed for this model — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
ruixingh:rhf3mr01:1updatedDevice profiles added or removed for this model — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.

senlab​

ModelChangeWhat changed
senlab:svc-lab-13ns:1addedSenlab V outdoor DC LATCH solenoid model SVC-LAB-13NS

sensaio​

ModelChangeWhat changed
sensaio:sensaio-press:1updatedDevice profiles added or removed for this model — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
sensaio:sensaio-temp:1updatedDevice profiles added or removed for this model — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
sensaio:sensaio-valv:1updatedDevice profiles added or removed for this model — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.

sensecap​

ModelChangeWhat changed
sensecap:loramodule-e5:2updatedDevice profiles added or removed for this model — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.

swisscom​

ModelChangeWhat changed
swisscom:multisense:1updatedDevice profiles added or removed for this model — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.

tekelek​

ModelChangeWhat changed
tekelek:tek-766:1addedTekelek TEK766 imported for the SPOT to ThingPark migration — Linked to the imported SPOT protocolId spt-teke:tek-766-inc:1, with an EU868 LoRaWAN 1.0.2 revB class A fallback profile pending confirmed vendor data.

twtg​

ModelChangeWhat changed
twtg:neon-pg:1updatedDevice profiles added or removed for this model — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
twtg:neon-ps:1updatedDevice profiles added or removed for this model — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
twtg:neon-ts:1updatedDevice profiles added or removed for this model — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
twtg:neon-tt:3updatedDevice profiles added or removed for this model — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
twtg:neon-tt:4updatedDevice profiles added or removed for this model — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.
twtg:neon-vb:3updatedDevice profiles added or removed for this model — Compared with device-profiles-8.0.0, the profile rows this model carries changed: profiles were added or removed. No other field of the model differs.

Across the catalog​

CatalogWhat changed
devicesloRaAllianceVendorID filled from the LoRa Alliance April 2026 list — 163 vendor.yaml files reviewed: 35 identifiers added, abeeway corrected from 000E to 0007, gossenmw and pmx cleared as absent from the list. 93 vendors now carry a valid identifier.
devicesmaxNbtransPerSF and SupportedDataRates carried through to the CSV
devicesVendors kddi, neon and subreach removed from the catalog — Orphaned vendors with no model left in the public catalog; removed on 2026-07-23 (9fa36427d, 1eae246d8).
Last updated on