February 2026 — Device reliability, event visibility, and operational consistency
February 2026 — Device reliability, event visibility, and operational consistency
Device status tracking and backend event handling were strengthened to make device availability more accurate and reduce noise during normal operations.
New
- Expanded device event logging Device status and method-call behavior now includes more detailed logging, improving auditability when devices reconnect, miss heartbeats, or experience communication issues.
Improved
- Device online/offline accuracy Heartbeat handling, offline thresholds, cache updates, and device sweep behavior were refined to reduce false offline states.
- Backend polling consistency Event polling and device sweep behavior were standardized so background processing behaves more predictably across environments.
- Device cache reliability Device cache handling now better accounts for aliases, stale records, and pre-populated device state.
Fixed
- False offline transitions Failed device method calls no longer incorrectly move devices into an offline state.
- Offline grace timing Offline timing thresholds were adjusted to better reflect real-world device communication delays.
- Development environment polling Background event polling and Event Hub subscriptions are now disabled when event sync is disabled or when running in development mode.
Why it matters
Operators get more trustworthy device status, fewer misleading offline events, and better diagnostic context when investigating connectivity problems. These improvements also reduce unnecessary support noise caused by temporary communication delays.
March 2026 — Custom Functions, Device Shell, diagnostics, and deployment readiness
March expanded CMP’s remote operations capabilities, with new tools for executing device actions, troubleshooting devices, and validating deployments more safely.
New
- Device Shell Added browser-based shell access for supported devices, giving operators a direct troubleshooting path without needing separate remote-access tooling.
- Device diagnostics experience Added diagnostics-focused device views and serial console support to make remote troubleshooting more accessible from the device page.
- Custom Function result logging Custom Function executions now write richer result details into event logs, including operation context and returned device data.
- Packaged Custom Function scripts Added packaged script support, including reboot workflows, so repeatable device actions can be managed more consistently.
- Health and readiness endpoints Added application health, warmup, and readiness checks to support safer deployments and better runtime monitoring.
- Smoke testing framework Added smoke tests for health checks, dashboard loading, device detail access, and outlet mutation flows.
Improved
- Custom Function editing Improved the alert-action editor for Custom Function parameters, making scripts easier to configure and validate.
- Event log clarity Event log handling was updated to show Custom Function results, operation names, and new device event types more clearly.
- Device operation logging Device shell, diagnostics, and event logging now provide better context around remote device actions.
- Deployment workflows Azure deployment workflows were expanded with testing-slot support, smoke test execution, and deployment URL validation.
Fixed
- Custom Function API escaping Improved JSON escaping and script variable handling for Custom Function API calls.
- Deployment slot configuration Corrected workflow configuration for the testing deployment slot.
- Logging stream behavior Restored fatal logs to the expected output stream for operational visibility.
Why it matters
Teams gain stronger remote troubleshooting tools, richer audit trails for automated device actions, and safer deployment validation. Device operations become easier to diagnose, while Custom Functions become more practical for repeatable fleet workflows.