Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "BaSyx / Documentation / Components / AAS Server / Features / Simple MQTT"

m (Adds LambdaProperty disclaimer)
 
Line 10: Line 10:
  
 
If the hierarchical topics presented in [[BaSyx_/_Documentation_/_Components_/_AAS_Server_/_Features_/_Hierarchical_MQTT | Hierarchical MQTT Eventing]] are too complicated, this feature will support event-driven use cases.
 
If the hierarchical topics presented in [[BaSyx_/_Documentation_/_Components_/_AAS_Server_/_Features_/_Hierarchical_MQTT | Hierarchical MQTT Eventing]] are too complicated, this feature will support event-driven use cases.
 +
 +
 +
Please note, that this feature can not be combined with lambda properties due to them being only updated on query.
 +
 
== Feature Overview ==
 
== Feature Overview ==
  

Latest revision as of 04:20, 23 May 2023

Simple MQTT Eventing

User Story & Use Case

As AAS Components user

I want simple MQTT topics in the AAS Server Component

so that I can receive MQTT events without having to worry about subscribing to detailed topics


If the hierarchical topics presented in Hierarchical MQTT Eventing are too complicated, this feature will support event-driven use cases.


Please note, that this feature can not be combined with lambda properties due to them being only updated on query.

Feature Overview

Information about what events will be published can be found in the eventing extension.


Feature Configuration

Eventing via MQTT is disabled by default. It can be enabled in the aas.properties file as well. This will publish events for every action to a separately specified server:

aas.events=MQTT

The MQTT broker endpoint can be configured via mqtt.properties file

Back to the top