Skip to content

Connectivity

The transition to the new Xcelerator gateway affects connectivity for MindConnect agents such as MindConnect Nano, IoT2040, IoT2050, and Software Agent.

The impact differs by connectivity mechanisms:

Standard Connectivity Mechanisms

Overview

MindConnect devices are migrated from the existing Insights Hub connectivity endpoint to a new Siemens Xcelerator connectivity endpoint.

To enable a seamless transition, Siemens provides firmware updates that allow devices to communicate with both the existing Insights Hub URLs and the new Xcelerator URLs. This ensures that devices remain operational during migration.

Migration is executed automatically by the platform. Devices must complete a preparation phase before migration can be executed.

The following devices are included in this migration:

  • MindConnect Nano
  • MindConnect IoT2040
  • MindConnect IoT2050
  • MindConnect Software Agent

Preparation Phase

Before the scheduled migration date, devices have to complete a preparation phase to ensure readiness for the connectivity transition.

Firmware Update

Siemens provides a firmware update that enables devices to communicate with both the existing connectivity URLs and the new Siemens Xcelerator connectivity URLs and authentication support for the new Xcelerator IAM.

  • If automatic firmware approval is enabled, the firmware is installed automatically.
  • If automatic firmware approval is disabled, the firmware update have to be triggered manually by the user.

Devices must successfully install this firmware before they can proceed to the next migration steps.

Network Accessibility

You have to ensure that the required connectivity domains are accessible from the network where your device is deployed.

Ensure that devices can reach the following domains:

Required Domains

  • api.eu1.siemens.app
  • bootstrap.connectivity.siemens.com
  • ota-update.connectivity.siemens.com
  • mqtt.connectivity.siemens.com
  • proxy.connectivity.siemens.com
  • registry.connectivity.siemens.com

Note

Ensure to configure network policies, firewalls, and proxies so that your device can access the required domains. If your device cannot reach any of the domains listed above, it cannot complete this step.

Retry Mechanism during Preparation

If a device fails to complete any preparation step (for example, firmware update or network validation), the platform automatically creates tasks to retry the failed step.

These tasks are generated daily until the step succeeds.

Once all preparation steps are completed successfully, the device is considered ready for migration.

Migration Execution

On the scheduled migration date, the platform triggers a gateway switch command for devices that have successfully completed the preparation phase.

This command switches device connectivity to the new Xcelerator connectivity endpoint.

The gateway switch is considered successful only if the device is able to obtain a new authentication token from the new gateway.

If the device cannot obtain the new token, the migration step is considered Failed. In this case, the platform automatically retries migration by creating a new task the following day.

Migration Scenarios

Device Online During Migration

If the device is online when the migration command is issued:

  1. The gateway switch command is executed.
  2. The device attempts to obtain a new authentication token.
  3. If the token is obtained successfully, the device switches to the new connectivity endpoint.
  4. Device communication continues through the new endpoint.

If the token request fails, the migration step is marked as failed and retried on the following day.

Device Offline During Migration

If the device is offline during the migration window:

  1. The gateway switch command cannot be executed immediately.
  2. The command is executed the next time the device connects to the platform.
  3. The device attempts to obtain a new authentication token.
  4. If successful, the device switches to the new connectivity endpoint.

If the token request fails, the migration step is retried on the following day.

Device Without Updated Firmware

If a device does not have the required firmware when tenant migration occurs:

  • The firmware can still be upgraded using the automated update mechanism until September 2026.
  • Once the firmware update is installed successfully, the device is picked up automatically by the system to proceed with the next steps on the following day.

Important Timeline

Note

To avoid service interruption, ensure that all devices are upgraded before September 2026.

Date Description
Firmware rollout Firmware enabling compatibility with both connectivity endpoints became available since April 2026
End of September 2026 Deadline for automated firmware upgrades
MQTT Broker URL The current URL will remain available until 10th October 2026. Please migrate to the new URL before this date.
McLib Two versions of McLib are available.
The current version: V4.4, can be used with the existing mindsphere.io URL.
The new version: V4.5, must be used once the tenant is migrated to the new siemens.app URL.
Note: To avoid any service interruptions, ensure that McLib is migrated to V4.5 by September 2026.

After September 2026

After September 2026:

  • Automated firmware upgrades are no longer available.
  • You have to manually download and install firmware on affected devices.
  • Devices running outdated firmware cannot ingest data into the platform.

Customer Action Summary

Ensure the following requirements are fulfilled:

  1. Firmware updates are approved if automatic approval is disabled.
  2. Required connectivity domains are accessible from the device network.
  3. Devices remain connected to the network whenever possible during the migration period.
  4. All devices are upgraded before the scheduled migration date to avoid service interruption.

MindConnect Library

Overview

For migrating MCLIB agents using MindConnect Library or MindConnect APIs, you have to start using api.eu1.siemens.app gateway URL instead of the current southgate.eu1.mindsphere.io to enable a seamless transition.

To support a seamless transition, Siemens provides MindConnect Library version 4.5.0 before migration begins.

Preparation Phase

Before the scheduled migration date, you have to create and deploy updated custom-built firmware using MindConnect Library version 4.5.0.

The following changes have to be incorporated into custom-built devices:

  • Update the Insights Hub gateway URL to use the Siemens Xcelerator Gateway endpoint.
  • Add support for the DigiCert TLS RSA4096 Root G.5 certificate (for future use), in addition to DigiCert Global Root G2.
  • Upgrade the OpenSSL version to 3.5.2 or later using OpenSSL as the security library.
  • Upgrade the libcurl version to 8.16.0 or later using libcurl as the HTTP client.
  • Upgrade the cJSON library to version 1.7.19.

Migration Execution

MCLIB agents need to save Registration Access Token (RAT) so that onboarded MCLIB agents continue to work with api.eu1.siemens.app gateway URL when they switch from southgate.eu1.mindsphere.io gateway URL.

If RAT is not available, then MCLIB agents need to be re-onboarded.

Info

Registration Access Token (RAT) does not expire.

The migration follows this sequence:

  1. Xcelerator Tenant ID is created for corresponding Insights Hub tenant.
  2. For Onboarded MCLIB agents, MCLIB agents start using api.eu1.siemens.app gateway URL for communicating with Insights Hub.
  3. Get Agent Access Token using api.eu1.siemens.app gateway URL.
  4. If RAT needs to be refreshed, update the RAT using PUT/register/{client_id} using api.eu1.siemens.app gateway URL.

MQTT Broker

The MQTT broker is available under the new URL:

  • mqtt.ih.eu1.siemens.app

Applications consuming MQTT data have to be updated to use this broker URL.

Authentication and authorization mechanisms remain unchanged. Replacing the existing broker URL with the new URL is sufficient.

The existing URL remains operational until October 10, 2026:

  • mindconnectmqtt.eu1.mindsphere.io
Last update: May 29, 2026

Except where otherwise noted, content on this site is licensed under the Development License Agreement.