Versioning Policy

WEDA Core and WEDA Node are versioned separately. This page explains which version combinations provide full feature support, how automatic updates work, and how to check WEDA Node after an update.

---

Matching WEDA Core and WEDA Node versions

Match the first two version numbers, major.minor, for full feature support. For WEDA Core v1.2.x, use WEDA Node v1.2.x to support the v1.2 feature set. Patch and build numbers do not need to match. Consult the release notes for the fixes included in a particular release or build.

	WEDA Core	WEDA Node
Version format	v1.2.x-<build>	v1.2.x_<build>
Match for full feature support	1.2	1.2
Can differ between products	Patch and build numbers	Patch and build numbers

Here, x represents a patch number and <build> represents a build identifier. With different major.minor versions, feature availability is limited by what both versions support. Use a matching pair when you need the full feature set.

WEDA Core	WEDA Node	Result
v1.2.x	v1.2.x	Full v1.2 feature support
v1.2.x	v1.1.x	Features that require WEDA Node v1.2 are unavailable
v1.1.x	v1.2.x	Features that require WEDA Core v1.2 are unavailable

WEDA Node automatic upgrades

WEDA Node automatically detects and installs available service updates, including the upgrade from v1.1 to v1.2.

WEDA Node v1.2 has no supported setting to disable automatic updates or schedule a maintenance window.

When upgrades happen

WEDA Node checks for updates every 5 minutes. If an updated image is found and can be downloaded, replacement can start at any time of day.

What happens on the device

The updated image is downloaded before the affected service stops. WEDA Node then stops and recreates the affected service. Communication resumes as the restarted services reconnect. Expect a service interruption during restart and reconnection. Recovery time depends on the device and its connection to WEDA Core.

Checking the installed version

Run this on the device using an account with permission to access Docker:

/opt/Advantech/show-weda-versions.sh

The script lists the image metadata for dmagent, system-agent, and watchtower, including Version and Created. These components have separate version numbers; they do not need to match each other. A value of n/a means the script could not read that metadata.

Confirming an upgrade succeeded

Check the version, local services, and cloud connection together:

1. Run the version script above and compare the component versions with the intended update.

2. Check the local service state:

   docker ps -a

   Confirm that dmagent, system-agent, and watchtower are present and show Up. A missing service or a status such as Restarting or Exited means the service has not recovered.

3. Check recovery from WEDA Core:

   • Use List devices by Organization to find the WEDA Node. Check that connectivity.state is Connected and that connectivity.updatedAt shows a heartbeat received after the restart.
   • Use Get device hardware capabilities to inspect the reported software version in swVersion after the next capability report. This is reported device information and can lag behind a local change.

A device lifecycle status of Activated alone does not confirm that WEDA Node has reconnected or is running the intended version.

---

Release notes

Release notes for each product line are listed under this section, one page per release.