Skip to main content
net10.0net8.0net9.0

MQTT protocol executor for OPC UA WoT Connectivity binding forms

Published
Oct 12, 2026
10d ago
Total Downloads
391
391

Install

dotnet add package OPCFoundation.NetStandard.Opc.Ua.WotCon.Bindings.Mqtt --version 2.0.1-preview.200
ProductVersions
.NET
net10.0net8.0net9.0

README

OPC UA WoT Connectivity — MQTT Executor

OPCFoundation.NetStandard.Opc.Ua.WotCon.Bindings.Mqtt executes MQTT WoT Connectivity binding forms compiled by the MQTT planner in Opc.Ua.WotCon.Bindings.

It uses the repository's MQTTnet infrastructure (kept out of the core model assembly) to implement publish / subscribe / RPC patterns per the pinned MQTT binding, with bounded QoS, topic, payload sizes and timeouts. The MQTT client factory is injectable.

Transport security

  • An mqtts:// href always enables TLS and defaults to port 8883; an mqtt:// href stays explicit plaintext (port 1883). There is no silent plaintext downgrade.
  • Username / password credentials, the TLS client certificate and the TLS trust anchors are resolved through the registered IWotCredentialProvider. A form that declares a security scheme fails closed (the connection is refused) when the provider resolves no credential.
  • Username / password credentials are refused over a plaintext mqtt:// connection unless MqttWotBindingOptions.AllowCredentialsOverPlaintext is set for an explicitly accepted plaintext deployment. ValidateServerCertificate controls broker-certificate validation for mqtts://.

Register it with builder.AddMqttWotBinding(...).

The package targets net8.0, net9.0, and net10.0. The MQTT planner and common binding contracts are supplied by OPCFoundation.NetStandard.Opc.Ua.WotCon.Bindings.

See the WoT protocol bindings guide.

Changes from Previous Version

No structural changes between v2.0.0-preview.200 and v2.0.1-preview.200.

Adoption Assessment

A verified publisher signal is available. Assess fit from the package's supported frameworks, license and dependency graph rather than popularity alone.

This version is marked prerelease. Validate its API and upgrade path before production use.No SPDX license expression is published. Review the license text and your organisation's policy before redistribution.Compatibility metadata lists 3 target frameworks; confirm the exact target used by your application.The published metadata declares 60 direct dependency entries across framework groups. Inspect the resolved dependency graph for your target framework.

Related Guides & Workflows

Learn how to evaluate, integrate, or audit this package in your .NET project.