Publishing Config

Publishing a configuration pushes the current set of edge device profiles and device configurations to the desired state of a deployment's device shadow. The edge gateway then picks up the changes on its next poll cycle.

When to publish

You need to publish a configuration whenever you want changes to take effect on the edge gateway. Changes that require publishing include:

• Creating, updating, or deleting variable bindings
• Attaching or detaching connectors from assets
• Modifying connector configuration (endpoint, security settings)

If auto-publish is enabled, the platform publishes automatically when these changes occur. If auto-publish is disabled, you must publish manually.

Publishing for a single deployment

To publish a configuration for a single deployment:

1. Navigate to the site and open the Edge Gateway tab
2. Select the deployment
3. In the Config Sync Status card, click Publish Config

The platform generates the edge configuration from the current bindings and connectors, updates the desired state in the shadow, and increments the config version.

Publishing for all deployments at a site

To publish configurations to all deployments at a site at once:

1. Navigate to the site
2. Open the Configuration tab
3. Click Publish Config to All Deployments

This triggers a bulk publish that processes each deployment at the site. The result summary shows:

What happens during publish

When you publish a configuration, the platform:

1. Collects bindings — gathers all variable bindings for the site's assets
2. Groups by connector — organizes bindings by their connector
3. Generates profiles — creates one edge device profile per connector, with a device resource for each bound variable
4. Generates devices — creates one edge device configuration per connector, with protocol settings and auto-event schedules
5. Computes hash — calculates a SHA-256 hash of the generated configuration
6. Compares with current — if the hash matches the existing desired config hash, the publish is skipped
7. Updates shadow — stores the new configuration in the desired state and increments the config version
8. Sets sync status — changes the sync status to Pending (if it was previously In Sync or Error)

After publishing

Once published, the configuration is available for the edge gateway to pick up:

1. The config agent polls the shadow API every 30 seconds
2. When it detects that delta.hasChanges is true, it downloads the configuration bundle
3. The agent applies the profiles and devices to the local Fleetera Edge instance
4. The agent reports the result back to the cloud
5. The sync status updates to In Sync (on success) or Error (on failure)

You can monitor the progress in the Config Sync Status card on the deployment detail page, which auto-refreshes every 30 seconds.

Naming conventions

The platform uses consistent naming when generating edge configurations:

When multiple connectors use the same protocol, each receives a unique instance number (for example, device-opc-ua-1, device-opc-ua-2).