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.

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.

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.

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.

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.

A smaller maintenance-focused month centered on improving configuration accuracy for supported devices.

Fixed

NTP configuration display and handling - Corrected an issue where NTP configuration values were not represented properly in the device configuration section.

Improved

Device configuration consistency - Cleaned up configuration handling so device settings are displayed and managed more reliably across the UI.

Why it matters

Teams can trust that time synchronization settings shown in CMP reflect the actual device configuration, reducing confusion during setup, troubleshooting, and audits.

Logging and outlet management saw major enhancements, making it easier to organize power workflows, analyze device behavior, and export data for audits or reporting.

New for On-prem Deployments

• Outlet management groups - Create and manage groups of outlets for project-based organization, coordinated control actions, and grouped power and telemetry analysis on supported devices.
• Device connection and disconnection events in event logs- Device online and offline transitions now appear directly in the event log rather than the activity log, making connectivity history easier to audit and filter.

New for Cloud Deployments

• VLAN support for CMP-supported devices - Configure VLAN behavior directly through CMP on supported hardware.
• WAN health signals- Added WAN health indicators to surface connectivity issues more quickly.
• Expanded device and PDU routes - Improved coverage and routing consistency for network-related device pages.

New for All Deployments

• CSV export for event logs - Download event logs directly from the UI, including any filters currently applied, for compliance, troubleshooting, or external analysis.

Improved for All Deployments

• Event log filtering and structure - Added preset time ranges (1 hour, 6 hours, 24 hours, 7 days, 30 days) along with custom date range selection. The event log table has been reorganized with clearer columns and improved filtering controls.
• Device and configuration UX polish - Refined device configuration, details, and inlet and outlet pages with usability and consistency improvements across the UI.

Fixed

• ATS inlet information display - Corrected issues where ATS inlet data was not clearly or accurately represented in the UI.
• Gateway IP information - Corrected issues with gateway ip not correctly showing

Why it matters

Teams can now organize outlets around real-world projects, rely on richer and more actionable event logs, and export data without manual work. Network-level visibility further reduces time to diagnose connectivity issues across fleets.

On-prem deployments received reliability fixes around access control and notifications, while cloud performance was made more predictable through internal consistency improvements.

New

• On-prem: Device offline email notifications Administrators can now receive email alerts when devices go offline, improving visibility for unattended or remote deployments.
• On-prem: Custom outlet metadata fields Additional custom fields can now be associated with individual outlets and are included in logging and telemetry data. This is especially useful for equipment labeling, asset tracking, and downstream reporting.

Improved

• Cloud: Performance consistency Backend request handling has been standardized to reduce intermittent errors and improve overall responsiveness across device operations.

Fixed

• Role-based access issues Resolved edge cases where role permissions were not consistently enforced across devices and configuration pages.

Why it matters

On-prem operators gain better alerting and asset visibility, while cloud users benefit from steadier performance and fewer unexplained errors during device interactions.

Running Synaccess CMP on your own network is now straightforward. You get private image delivery, a drop-in Docker Compose file, and step-by-step docs. Updates are quick, and security teams have clear guidance.

New

• On-prem Docker package — Pull Synaccess CMP from our private registry with customer-specific access keys (no public accounts).
• Copy-paste Compose starter — A ready file and .env template so you can configure and launch in minutes.
• First-time setup guide — Clear prerequisites, architecture, and networking/port requirements for security and IT teams.
• Update playbook — Choose to follow the latest build or pin a specific version; sign up for release emails at [email protected].
• Device pairing guide — Walkthrough for pairing PDUs, including certificate validation options.

Improved

• Security guidance — Best practices for credentials, TLS, and network allow-listing presented in plain language.
• Sizing & topology — Right-sized hardware suggestions and deployment patterns for labs to enterprise.
• Consistency — Unified terms, examples, and URLs across all docs to reduce guesswork.

Fixed

• Outdated examples that caused setup friction have been corrected and simplified.
• Documentation gaps around HTTPS certificates and pairing behavior have been closed.

Why it matters Your team can deploy Syn Cloud on-prem quickly, keep it up to date with minimal effort, and satisfy security reviews without back-and-forth. Faster rollout, predictable updates, and less operational overhead.

Device pages now load instantly, include a unified control center for major configuration task, and support device outlets grouping for alert automations.

New

• Instant status bar for quick device health checks
• Faster, streamlined device loading
• Configuration hub for SMTP, Syslog, global reboot schedules, AutoPing defaults, PDU port controls, and user management
• Device outlet grouping: create groups of outlets and trigger them as an action in alert configurations, with flexible sequencing and timing

Improved

• Page performance keeps focus on the current device instead of waiting for live data to hydrate

Fixed

• Eliminated lag from fetching live state so navigation between devices remains responsive
• Addressed cases where some outlets weren’t visible for certain users depending on assigned roles
• Smoothed out a rare timing issue with how device data was fetched on the frontend
• Corrected activity log links so they consistently point to the right device

Why it matters Operators can confirm device health and adjust settings—from alerts to access—without leaving the page or waiting on spinners.

Activity and device pages surface the right context—from history to network status—without extra clicks.

New: Activity log search with pagination, device overview tiles, and networking callouts (including LTE details and active interface status).
Improved: Event logging now flags Ethernet loss on primary links, and inlet/outlet graphs include adjustable time-frame filters.
Fixed: Tightened device pages so networking insights and summaries populate consistently.
Why it matters: Teams can diagnose issues faster because the key history, network health, and usage charts appear together on the device view.

Device configurations save the first time, large deployments feel quicker, and teams can finally explore a complete event history.

New: Centralized event log that tracks every trigger with filters for device, event type, and status so teams can retrace what happened.
Improved: Front-end fixes that keep configuration changes from failing silently and performance tuning tailored for long-running enterprise fleets.
Why it matters: Operators get trusted records for audits and don’t need to double-check whether their configuration changes actually stuck.

We introduced a new batch firmware update tool.

Improved: Batch firmware updates that help teams roll out versions to groups of devices in one go, plus a unified firmware overview so you can confirm coverage before pressing update.
Fixed: Cleared the lag that occasionally slowed down the device list, keeping it snappy for daily check-ins.

Why it matters
Operators can confirm what needs attention and schedule upgrades in minutes instead of digging through individual devices.