Skip to content

tedge-dot 0.0.16

Choose a tag to compare

View all tags
@reubenmiller reubenmiller released this 12 Oct 15:55
0.0.16
f1dbf9f
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Two interchangeable packages, one binary: tedge-dot-rs (Rust, the default) and
tedge-dot-c (C, for small or old devices: glibc 2.17 floor, adds PROFIBUS-DP). Install one
of them from the thin-edge.io community repository:

sudo apt-get install -y tedge-dot-rs    # or tedge-dot-c

Install & upgrade guide
· README
· Changelog
· SHA256SUMS covers every asset below.

This release also delivers 0.0.15, which was tagged but never published.

Highlights

OPC UA method calls

A point can now be an OPC UA method: access = "call_method" with
address = { object_id, method_id, inputs = [...] }. The new call-method command takes
arguments and returns the method's outputs. Both packages support it, with identical failure
reasons.

[[device.point]]
id      = "multiply"
access  = "call_method"
address = { object_id = "ns=2;s=Machine", method_id = "ns=2;s=Machine.Multiply", inputs = ["int32", "int32"] }
  • ot-registration announces a device's methods as the retained ot_call_method command
    capability, and ot-command-forward routes an ot_call_method command to the connector. The
    outputs come back on the command.
  • A method call is never retried. A call that times out may still have run on the server.
  • Method ids follow the device's namespace table (below).
  • Breaking, tedge-dot-rs only: a write-only point (access = "write") is no longer polled and so no longer
    publishes samples, as the contract always required (tedge-dot-c already behaved this way).
    Declare it read_write to keep its samples.
  • See doc/connectors/opcua-connector-spec.md §3.10 and contract §6.6.

OPC UA namespace tables

An OPC UA node id such as ns=3;i=1234 names its namespace by position in the server's
namespace array. A firmware update, or another instance of the same device type, can number the
namespaces differently, and the id then reads a different node, or none. A device
(protocol_address.namespaces) or a point library ([library] namespaces) can now record the
array its ids were written against. On every connect the connector maps each index through
that table to the server's current one, and logs a namespace that moved.

  • Node ids stay numeric, as copied from UaExpert. Without a table nothing changes.
  • A namespace the server does not list fails only its own points (namespace not found: <uri>)
    and is tried again, so one the server adds later is picked up.
  • Both packages support it. An older package ignores a device's table and reads the configured
    index. It rejects a library that carries one.
  • See doc/connectors/opcua-connector-spec.md §3.9.

0.0.16 (2026-10-12)

Bug Fixes

0.0.15 (2026-10-12)

Features

  • opcua: call OPC UA methods (opcua-method-calls) (#71) (39c205f)
  • opcua: namespace tables for numeric node ids (opcua-namespace-table) (#69) (fed70e7)
Assets 26
Loading