Drivers 5.3.0 · Device profiles 9.3.0
Published on 2026-09-29.
Breaking changes
An integration reading these points may need to be adapted.
Point fields that change
| Driver | What changes |
|---|---|
nexelec:air-plus:1 | Product Status: batteryVoltage, batteryResistanceThreshold and batteryLowVoltageThreshold removed (use energyStatus), and the batteryVoltage point with them; remainingProductLifetime.Value → remainingProductLifetime.value; magnetDetection added. |
Drivers
eco-adapt
| Driver | Change | What changed |
|---|---|---|
spt-ecoa:power-elec-6:1 | updated | Eco-Adapt Power Elec 6: package accepted by the driver engine — The 5.2.0 package exported its decoder through an unguarded module.exports, which the driver engine does not provide: the engine refused the package, so the driver was not installed. The redundant export is removed; decoding is unchanged. |
kamstrup
| Driver | Change | What changed |
|---|---|---|
kamstrup:generic:1 | updated | Kamstrup: encrypted short-header frames decoded with the context kept from the long-header frame — Security Profile D short-header frames need the serial number, manufacturer, version and device type that the last long-header frame stored in the context; the engine did not keep that context for this driver, so those frames failed ("Context is empty"). The driver moves to signature lora-alliance, for which the engine keeps the context, stores it as plain arrays and exports isContextUsedInPayload (GitHub PR #289). Its decoded { data, errors, warnings } is returned under data, so connections receive the same payload as before (TXIF-4285); frames with errors still fail the decoding as before. |
nexelec
| Driver | Change | What changed |
|---|---|---|
nexelec:air-plus:1 | updated | Nexelec AIR+ / AIR: manufacturer decoder 1.0.2 — The driver runs Nexelec's decoderAir+.js 1.0.2 (it ran their 1.0.0). Fixes: downlinkCounter was half its value, hushStatus returned hardware-fault labels, the SAV Information frame (0x04) is decoded, unmapped codes read Unknown, short payloads are reported. Nexelec removed the battery voltage and thresholds from their public decoder (outside the product's public interface) and recommends energyStatus (High, Medium, Low, Critical), which the Product Status frame keeps carrying: the batteryVoltage point is no longer published. First delivered in 5.0.0; the change is kept under the same protocolId. |
nexelec:flow:1 | added | Nexelec FLOW CORE / FLOW PRO: uplink decoder and downlink encoder — Nexelec's decoderFlow.js 1.0.9 and encoderFlow.js 1.0.0 for the FLOW thermostatic radiator valve heads: periodic data, product status, NODE One remote probe status, configuration and daily heating profiles (frames 0x01 to 0x07, fPort 56), and the revision C downlink commands (setpoints, schedules, open window detection, child lock, boost…). Points: ambient, setpoint and internal temperatures, valve opening, open window and frost protection states, battery voltages, NODE One probe battery and radio level. |
theta
| Driver | Change | What changed |
|---|---|---|
theta:dc-series:1 | updated | Theta DC series: time of flight published in the new unit us — The decoded flightTime (microseconds) is now published as the point duration, unit us (microsecond, added to the ontology), nature Time of flight. Additive: the existing points are unchanged. |
Device profiles
nexelec
| Model | Change | What changed |
|---|---|---|
nexelec:flow-core:1 | added | Nexelec FLOW CORE thermostatic radiator valve head — New model, driver nexelec:flow:1, LoRaWAN 1.0.4 / RP002-1.0.4 class A EU868 profile with RX2 at SF9 (DR3). |
nexelec:flow-pro:1 | added | Nexelec FLOW PRO thermostatic radiator valve head — New model, driver nexelec:flow:1, same LoRaWAN profile as FLOW CORE (1.0.4 / RP002-1.0.4 class A EU868, RX2 at SF9). |