Gets the container's communication manager.
Gets the container object of this controller.
Gets the controller's options as specified in the configuration options.
Gets the registered name of this controller.
The registered name is either defined by the corresponding key in the
Components.controllers object in the container configuration, or by
invoking Container.registerController method with this name.
Gets the container's Runtime object.
Whenever one of the controller's log methods (e.g. logDebug, logInfo,
logWarning, logError, logFatal) is called by application code, the
controller creates a Log object with appropriate property values and
passes it to this method before advertising it.
You can override this method to additionally set certain properties (such
as LogHost.hostname or Log.logLabels). Ensure that
super.extendLogObject is called in your override. The base method does
nothing.
log object to be extended before being advertised
Advertise a Log object for debugging purposes.
a debug message
any number of log tags
Advertise a Log object for an error.
an error (object)
additional error message
any number of log tags
Advertise a Log object for an error with stacktrace information.
an error (object)
additional error message
any number of log tags
Advertise a Log object for a fatal error.
an error (object)
additional error message
any number of log tags
Advertise an informational Log object.
an informational message
any number of log tags
Advertise a Log object for a warning.
a warning message
any number of log tags
Overwrite this method to define how internal OPC UA errors within this controller should be traced.
By default, OPC UA errors are logged on the console.
Do not call this method in your application code, it is called by this controller internally.
an OPC UA error
Generated using TypeDoc
Connect to OPC UA server and map OPC UA variables to raw (non-Coaty) MQTT messages.
Each value of a monitored OPC UA data source is published on its associated MQTT topic with the data value as its payload. Topic mappings are configured on a controller option named
opcuaMqttOptionswhich must implement theOpcuaMqttOptionsinterface.By default, OPC UA data values are serialized as UTF-8 encoded JSON message payloads. You can implement a specific data value coercion (e.g. as a binary payload) by defining a
coerceValuefunction in the associatedOpcuaDataSource.This controller only runs in a Node.js runtime, not in a browser.