/
2026-01-06 Weekly Executive Report – Sustainability

2026-01-06 Weekly Executive Report – Sustainability

Highlights

  • Device List & Pulse Sensors

    • Updated Device List behavior to surface Pulse Inputs individually (not just the parent Input Device), to keep them discoverable even if the Primary Device is removed from Timestream.

    • Added support for searching Pulse Input devices by the last 5 digits of EUI, explicitly excluding the Primary EUI from results.

    • Verified HasPulseCounter flag is correctly set to true when pulse counters are added and migrated.

  • Migrations & Platform Cleanup

    • Implemented and deployed a migration Lambda hotfix to run migrations every 15 minutes (instead of once per day) without hitting IoT Core rate limits.

    • Disabled the “duplicate misaligned sensors” report and patched wirefree site notifications to exclude devices with unknown sites from KPI reporting.

    • Removed DeviceConfigured from the LoRaWAN platform codebase and purged existing values from LorawanDevicesTableBmsProd and LorawanGatewaysTableBmsProd.

  • Deployment, Testing & Bugfixes

    • Deployed and tested the safe‑reprovisioning feature in Production with dummy devices and gateways.

    • Fixed issues in the gateway certificate download modal (prevented premature auto‑close when certs are available).

    • Corrected provisioning progress bar percentages, removed successfully provisioned devices from the post‑provisioning list (only failed ones remain), and improved LoRaWAN sensor/gateway button styling.

    • Adjusted Conflict Modal mobile layout so the Close button is fully visible and not cut off.

  • Planning & Design

    • Drafted a proposal to locate the platform‑maintenance price point per site and outlined next steps for analysis.

    • Started a document describing existing features and estimated effort to track installation time per device.

    • Created an initial definition for GREF APIs to replace the current email‑bot workflow.

Lowlights / Issues

  • Edge Cases & Reporting Gaps

    • Excluding devices with unknown sites from KPI reports surfaced some data quality issues that will require follow‑up clean‑up work.

    • The Device List refactor to support individual Pulse Inputs highlighted additional edge cases around devices that still need a data flow validation solution beyond the current hotfix behavior.

Overall

  • Advanced Pulse Input visibility, faster migrations, and safer provisioning flows, reducing operational risk and improving install‑team feedback loops.

  • Tightened up platform correctness by cleaning unused attributes, closing UI gaps, and improving reporting accuracy, positioning the platform for more robust automation and analytics.

  • Laid groundwork for future improvements around installation‑time tracking and GREF APIs.