Drivers 5.4.0 · Device profiles 9.4.0
Published on 2026-10-12.
Breaking changes
An integration reading these points may need to be adapted.
| Driver | What changes |
|---|---|
elsys:ers:1 | Device profiles ELSYS/GenericC.1.0.3a_*: LoRaWAN class C becomes A, the ISM bands of ELSYS/GenericC.1.0.3a_ETSI (eu868,cn779,in865,eu433,kr920,ru864) become eu868,in865 and those of ELSYS/GenericC.1.0.3a_FCC (us915,cn470) become us915, the model is renamed ERS |
Drivers
atim
| Driver | Change | What changed |
|---|---|---|
atim:mr2-ex:2 | added | ATIM MR2-EX: separate LoRaWAN indexes from Sigfox deltas |
mcf88
| Driver | Change | What changed |
|---|---|---|
os1-mcf8:mcf-lw06davk:1 | updated | MCF88 / Enginko: time sync frames (0x01) decoded — The decoder called parseTimeSync without defining it, so every time sync frame (uplink 0x01) failed with 'driver internal error: parseTimeSync is not defined'. The frame is now decoded into syncID, syncVersion, applicationType and rfu. Other frames are unchanged. |
os1-mcf8:mcf-lw06davpk:1 | updated | MCF88 / Enginko: time sync frames (0x01) decoded — The decoder called parseTimeSync without defining it, so every time sync frame (uplink 0x01) failed with 'driver internal error: parseTimeSync is not defined'. The frame is now decoded into syncID, syncVersion, applicationType and rfu. Other frames are unchanged. |
os1-mcf8:mcf-lw12co2:1 | updated | MCF88 / Enginko: time sync frames (0x01) decoded — The decoder called parseTimeSync without defining it, so every time sync frame (uplink 0x01) failed with 'driver internal error: parseTimeSync is not defined'. The frame is now decoded into syncID, syncVersion, applicationType and rfu. Other frames are unchanged. |
os1-mcf8:mcf-lw12co2e:1 | updated | MCF88 / Enginko: time sync frames (0x01) decoded — The decoder called parseTimeSync without defining it, so every time sync frame (uplink 0x01) failed with 'driver internal error: parseTimeSync is not defined'. The frame is now decoded into syncID, syncVersion, applicationType and rfu. Other frames are unchanged. |
os1-mcf8:mcf-lw12met:1 | updated | MCF88 / Enginko: time sync frames (0x01) decoded — The decoder called parseTimeSync without defining it, so every time sync frame (uplink 0x01) failed with 'driver internal error: parseTimeSync is not defined'. The frame is now decoded into syncID, syncVersion, applicationType and rfu. Other frames are unchanged. |
os1-mcf8:mcf-lw12plg:1 | updated | MCF88 / Enginko: time sync frames (0x01) decoded — The decoder called parseTimeSync without defining it, so every time sync frame (uplink 0x01) failed with 'driver internal error: parseTimeSync is not defined'. The frame is now decoded into syncID, syncVersion, applicationType and rfu. Other frames are unchanged. |
os1-mcf8:mcf-lw12ter:1 | updated | MCF88 / Enginko: time sync frames (0x01) decoded — The decoder called parseTimeSync without defining it, so every time sync frame (uplink 0x01) failed with 'driver internal error: parseTimeSync is not defined'. The frame is now decoded into syncID, syncVersion, applicationType and rfu. Other frames are unchanged. |
os1-mcf8:mcf-lw12terpm:1 | updated | MCF88 / Enginko: time sync frames (0x01) decoded — The decoder called parseTimeSync without defining it, so every time sync frame (uplink 0x01) failed with 'driver internal error: parseTimeSync is not defined'. The frame is now decoded into syncID, syncVersion, applicationType and rfu. Other frames are unchanged. |
os1-mcf8:mcf-lw12terwp:1 | updated | MCF88 / Enginko: time sync frames (0x01) decoded — The decoder called parseTimeSync without defining it, so every time sync frame (uplink 0x01) failed with 'driver internal error: parseTimeSync is not defined'. The frame is now decoded into syncID, syncVersion, applicationType and rfu. Other frames are unchanged. |
os1-mcf8:mcf-lw12voc:1 | updated | MCF88 / Enginko: time sync frames (0x01) decoded — The decoder called parseTimeSync without defining it, so every time sync frame (uplink 0x01) failed with 'driver internal error: parseTimeSync is not defined'. The frame is now decoded into syncID, syncVersion, applicationType and rfu. Other frames are unchanged. |
os1-mcf8:mcf-lw13io:1 | updated | MCF88 / Enginko: time sync frames (0x01) decoded — The decoder called parseTimeSync without defining it, so every time sync frame (uplink 0x01) failed with 'driver internal error: parseTimeSync is not defined'. The frame is now decoded into syncID, syncVersion, applicationType and rfu. Other frames are unchanged. |
os1-mcf8:mcf-lw13mio:1 | updated | MCF88 / Enginko: time sync frames (0x01) decoded — The decoder called parseTimeSync without defining it, so every time sync frame (uplink 0x01) failed with 'driver internal error: parseTimeSync is not defined'. The frame is now decoded into syncID, syncVersion, applicationType and rfu. Other frames are unchanged. |
os1-mcf8:mcf-lwws00:1 | updated | MCF88 / Enginko: time sync frames (0x01) decoded — The decoder called parseTimeSync without defining it, so every time sync frame (uplink 0x01) failed with 'driver internal error: parseTimeSync is not defined'. The frame is now decoded into syncID, syncVersion, applicationType and rfu. Other frames are unchanged. |
os1-mcf8:mcf-lwws01:1 | updated | MCF88 / Enginko: time sync frames (0x01) decoded — The decoder called parseTimeSync without defining it, so every time sync frame (uplink 0x01) failed with 'driver internal error: parseTimeSync is not defined'. The frame is now decoded into syncID, syncVersion, applicationType and rfu. Other frames are unchanged. |
os1-mcf8:mcf-lwws02:1 | updated | MCF88 / Enginko: time sync frames (0x01) decoded — The decoder called parseTimeSync without defining it, so every time sync frame (uplink 0x01) failed with 'driver internal error: parseTimeSync is not defined'. The frame is now decoded into syncID, syncVersion, applicationType and rfu. Other frames are unchanged. |
os1-mcf8:mcf-lwws03:1 | updated | MCF88 / Enginko: time sync frames (0x01) decoded — The decoder called parseTimeSync without defining it, so every time sync frame (uplink 0x01) failed with 'driver internal error: parseTimeSync is not defined'. The frame is now decoded into syncID, syncVersion, applicationType and rfu. Other frames are unchanged. |
yosensi
| Driver | Change | What changed |
|---|---|---|
yosensi:generic:1 | updated | Yosensi: decoder updated to the manufacturer's 1.0.3 (V1 startup frames, measurement types 40 to 49 and 62 named); new point: velocity (m/s) |
Device profiles
atim
| Model | Change | What changed |
|---|---|---|
atim:acw-mr2:1 | updated | ATIM MR2-EX: make the corrected v2 driver default for new devices |
elsys
| Model | Change | What changed |
|---|---|---|
elsys:elt-2:1 | updated | ELSYS ELT-2: shared RFGroup profiles, short product name — The device profile ids are unchanged. The profiles now come from the shared ELSYS RFGroup profiles, with a maximum TX power of 20 dBm in every region (it was 16 dBm in Europe and 30 dBm in the US and Australia), the ISM bands eu868,in865 in Europe and a shorter product name. |
elsys:elt-lite:1 | updated | ELSYS ELT Lite: shared RFGroup profiles, short product name — The device profile ids are unchanged. The profiles now come from the shared ELSYS RFGroup profiles, with a maximum TX power of 20 dBm in every region (it was 16 dBm in Europe and 30 dBm in the US and Australia), the ISM bands eu868,in865 in Europe and a shorter product name. |
elsys:elt-ultrasonic:1 | updated | ELSYS ELT Ultrasonic: shared RFGroup profiles, short product name — The device profile ids are unchanged. The profiles now come from the shared ELSYS RFGroup profiles, with a maximum TX power of 20 dBm in every region (it was 16 dBm in Europe and 30 dBm in the US and Australia), the ISM bands eu868,in865 in Europe and a shorter product name. |
elsys:ems-desk:1 | updated | ELSYS EMS Desk: shared RFGroup profiles, short product name — The device profile ids are unchanged. The profiles now come from the shared ELSYS RFGroup profiles, with a maximum TX power of 14 dBm in every region (it was 16 dBm in Europe and 30 dBm in the US and Australia), the ISM bands eu868,in865 in Europe and a shorter product name. |
elsys:ems-door:1 | updated | ELSYS EMS DOOR: shared RFGroup profiles, short product name — The device profile ids are unchanged. The profiles now come from the shared ELSYS RFGroup profiles, with a maximum TX power of 14 dBm in every region (it was 16 dBm in Europe and 30 dBm in the US and Australia), the ISM bands eu868,in865 in Europe and a shorter product name. |
elsys:ems-lite:1 | updated | ELSYS EMS Lite: shared RFGroup profiles, short product name — The device profile ids are unchanged. The profiles now come from the shared ELSYS RFGroup profiles, with a maximum TX power of 14 dBm in every region (it was 16 dBm in Europe and 30 dBm in the US and Australia), the ISM bands eu868,in865 in Europe and a shorter product name. |
elsys:ems:1 | updated | ELSYS EMS mini: shared RFGroup profiles, short product name — The device profile ids are unchanged. The profiles now come from the shared ELSYS RFGroup profiles, with a maximum TX power of 14 dBm in every region (it was 16 dBm in Europe and 30 dBm in the US and Australia), the ISM bands eu868,in865 in Europe and a shorter product name. |
elsys:ems2-desk:1 | added | ELSYS EMS2 Desk: added — New ELSYS model on LoRaWAN 1.0.4 profiles, decoded by the existing elsys:generic:1 driver. |
elsys:ems2-door:1 | added | ELSYS EMS2 Door: added — New ELSYS model on LoRaWAN 1.0.4 profiles, decoded by the existing elsys:generic:1 driver. |
elsys:ems2-lite:1 | added | ELSYS EMS2 Lite: added — New ELSYS model on LoRaWAN 1.0.4 profiles, decoded by the existing elsys:generic:1 driver. |
elsys:ems2:1 | added | ELSYS EMS2: added — New ELSYS model on LoRaWAN 1.0.4 profiles, decoded by the existing elsys:generic:1 driver. |
elsys:ers-co2-lite:1 | updated | ELSYS ERS CO2 Lite: shared RFGroup profiles, short product name — The device profile ids are unchanged. The profiles now come from the shared ELSYS RFGroup profiles, with a maximum TX power of 14 dBm in every region (it was 16 dBm in Europe and 30 dBm in the US and Australia), the ISM bands eu868,in865 in Europe and a shorter product name. |
elsys:ers-co2:1 | updated | ELSYS ERS CO2: shared RFGroup profiles, short product name — The device profile ids are unchanged. The profiles now come from the shared ELSYS RFGroup profiles, with a maximum TX power of 14 dBm in every region (it was 16 dBm in Europe and 30 dBm in the US and Australia), the ISM bands eu868,in865 in Europe and a shorter product name. |
elsys:ers-disp-co2:1 | added | ELSYS ERS Display CO2: added — New ELSYS model on LoRaWAN 1.0.4 profiles, decoded by the existing elsys:generic:1 driver. |
elsys:ers-disp-co2lite:1 | added | ELSYS ERS Display CO2 Lite: added — New ELSYS model on LoRaWAN 1.0.4 profiles, decoded by the existing elsys:generic:1 driver. |
elsys:ers-disp-lite:1 | added | ELSYS ERS Display Lite: added — New ELSYS model on LoRaWAN 1.0.4 profiles, decoded by the existing elsys:generic:1 driver. |
elsys:ers-disp-sound:1 | added | ELSYS ERS Display Sound: added — New ELSYS model on LoRaWAN 1.0.4 profiles, decoded by the existing elsys:generic:1 driver. |
elsys:ers-disp-voc:1 | added | ELSYS ERS Display VOC: added — New ELSYS model on LoRaWAN 1.0.4 profiles, decoded by the existing elsys:generic:1 driver. |
elsys:ers-disp:1 | added | ELSYS ERS Display: added — New ELSYS model on LoRaWAN 1.0.4 profiles, decoded by the existing elsys:generic:1 driver. |
elsys:ers-eco-co2:1 | added | ELSYS ERS Eco CO2: added — New ELSYS model on LoRaWAN 1.0.4 profiles, decoded by the existing elsys:generic:1 driver. |
elsys:ers-eco:1 | added | ELSYS ERS Eco: added — New ELSYS model on LoRaWAN 1.0.4 profiles, decoded by the existing elsys:generic:1 driver. |
elsys:ers-eye:1 | updated | ELSYS ERS EYE: shared RFGroup profiles, short product name — The device profile ids are unchanged. The profiles now come from the shared ELSYS RFGroup profiles, with a maximum TX power of 14 dBm in every region (it was 16 dBm in Europe and 30 dBm in the US and Australia), the ISM bands eu868,in865 in Europe and a shorter product name. |
elsys:ers-interactlite:1 | added | ELSYS ERS Interact Lite: added — New ELSYS model on LoRaWAN 1.0.4 profiles, decoded by the existing elsys:generic:1 driver. |
elsys:ers-lite:1 | updated | ELSYS ERS Lite: shared RFGroup profiles, short product name — The device profile ids are unchanged. The profiles now come from the shared ELSYS RFGroup profiles, with a maximum TX power of 14 dBm in every region (it was 16 dBm in Europe and 30 dBm in the US and Australia), the ISM bands eu868,in865 in Europe and a shorter product name. |
elsys:ers-sound:1 | updated | ELSYS ERS SOUND: shared RFGroup profiles, short product name — The device profile ids are unchanged. The profiles now come from the shared ELSYS RFGroup profiles, with a maximum TX power of 14 dBm in every region (it was 16 dBm in Europe and 30 dBm in the US and Australia), the ISM bands eu868,in865 in Europe and a shorter product name. |
elsys:ers-voc:1 | updated | ELSYS ERS VOC: shared RFGroup profiles, short product name — The device profile ids are unchanged. The profiles now come from the shared ELSYS RFGroup profiles, with a maximum TX power of 14 dBm in every region (it was 16 dBm in Europe and 30 dBm in the US and Australia), the ISM bands eu868,in865 in Europe and a shorter product name. |
elsys:ers:1 | updated | ELSYS ERS: shared RFGroup profiles, short product name — The device profile ids are unchanged. The profiles now come from the shared ELSYS RFGroup profiles, with a maximum TX power of 14 dBm in every region (it was 16 dBm in Europe and 30 dBm in the US and Australia), the ISM bands eu868,in865 in Europe and a shorter product name. |
elsys:ers2-co2-lite:1 | added | ELSYS ERS2 CO2 Lite: added — New ELSYS model on LoRaWAN 1.0.4 profiles, decoded by the existing elsys:generic:1 driver. |
elsys:ers2-co2:1 | added | ELSYS ERS2 CO2: added — New ELSYS model on LoRaWAN 1.0.4 profiles, decoded by the existing elsys:generic:1 driver. |
elsys:ers2-eye:1 | added | ELSYS ERS2 Eye: added — New ELSYS model on LoRaWAN 1.0.4 profiles, decoded by the existing elsys:generic:1 driver. |
elsys:ers2-lite:1 | added | ELSYS ERS2 Lite: added — New ELSYS model on LoRaWAN 1.0.4 profiles, decoded by the existing elsys:generic:1 driver. |
elsys:ers2-sound:1 | added | ELSYS ERS2 Sound: added — New ELSYS model on LoRaWAN 1.0.4 profiles, decoded by the existing elsys:generic:1 driver. |
elsys:ers2-voc:1 | added | ELSYS ERS2 VOC: added — New ELSYS model on LoRaWAN 1.0.4 profiles, decoded by the existing elsys:generic:1 driver. |
elsys:ers2:1 | added | ELSYS ERS2: added — New ELSYS model on LoRaWAN 1.0.4 profiles, decoded by the existing elsys:generic:1 driver. |
itron
| Model | Change | What changed |
|---|---|---|
itron:cyble5-v2:1 | updated | Align the Cyble 5 V2 APAC profile with the AS923 regional settings — The APAC 1.0.4 profile now follows the existing AS923 profile for the regional dwell times and TxParamSetup MAC command while retaining the V2-specific LoRaWAN 1.0.4, power and NbTrans settings. |
itron:cyble5-v21:1 | updated | Align the shared Cyble 5 V2.1 APAC profile with the AS923 regional settings — The shared APAC 1.0.4 profile now follows the existing AS923 profile for the regional dwell times and TxParamSetup MAC command while retaining the V2 NbTrans settings. |
yosensi
| Model | Change | What changed |
|---|---|---|
yosensi:agri-pro:1 | added | New Yosensi model (manufacturer contribution, public PR 292) |
yosensi:air-pressure-mon:1 | added | New Yosensi model (manufacturer contribution, public PR 292) |
yosensi:analog:1 | updated | YO Analog: the description names its six 4-20 mA / 0-10 V inputs |
yosensi:atmos:1 | added | New Yosensi model (manufacturer contribution, public PR 292) |
yosensi:meter-reader2:1 | updated | YO Meter Reader 2.0: the description covers the three sensor options (LED pulse, pulse input, IEC 62056-21) |
yosensi:pm-sensor:1 | added | New Yosensi model (manufacturer contribution, public PR 292) |
Across the catalog
| Catalog | What changed |
|---|---|
| drivers | Delivered driver archives contain only release-applicable changelog history — The archive now includes a driver changelog rendered from the requested release, retaining older published history while excluding unreleased history, internal entries, and future versions. The source development changelog is unchanged. |
| devices | Delivered device archives contain only release-applicable changelog history — The device archive changelog is rendered from YAML for the requested release instead of copying unreleased legacy history. Older published history is retained. The IoT-Flow driver documentation links the official manual catalog upload procedure for self-hosted TPE administrators; SaaS catalogs remain managed by Actility. |
| devices | Pyrescom manufacturer contact and logo refreshed — Public PR #290, commit 33a1818a6: the manufacturer contact is now lora@pyres.com and the vendor logo is updated. No model, LoRaWAN profile, or driver contract changes. |