Version 2.4.0.2

Fixed Device.xml dynamic loading where the file has not changed. It was causing a crash when a current was run.

Version 2.4.0.1

Adds the following features

• Added json schem for configuration files
• Fixed documentation for the configuration in the readme.
• Added xpath to the Mqtt2Service to subselect what components and data items will be published.

Full Changelog: v2.3.0.16...v2.4.0.1

Version v2.3.0.16

Features

• Added MqttRetain and MqttQOS options for the MqttSink2. See docs.

Bug Fixes

• Fixed URL parsing for Mqtt adapters
• Added period and rate filters to the agent adapter

Version v2.3.0.15

New Features

• MqttRetain and MqttQOS are now settable options in the configuration of Mqtt 2 Service (the latest).
  • MqttQOS options are: at_least_once, at_most_once, and exactly_once. The default is at_least_once
  • MqttRetain can be true or false.

Bug Fixes

• UUID device changes were not being pushed through to the Mqtt Service and were not reposting. This required redoing the UUID and device changed handling to better support changes in pub/sub services other than REST.

Version v2.3.0.14

Bug fix release

• Fixed issues with MQTT disconnect and options passing to the pipeline
• Fixed MQTT Host and Port in the URL

Version 2.3.0.11

Bug fix release

• Fixed bug where observations were not set to unavailable when MQTT Source would disconnect from broker
• Fixed bug with topics being incorrectly set when parsing the path

Version 2.3.0.10

This is a bug fix release.

• Fixes some unhandled exceptions relation to numeric conversions in the pipeline.
• Fixes Windows Services with a configuration file other than agent.cfg

Version 2.5.0.0 Release Candidate 4

Merges change from 2.3.0.9

Version 2.3.0.9

Tjisi is a bug fix release and addresses the following issues:

• The MQTT2 Sink now includes the MTConnectAssets and Header when publishing assets
• The MTCpmmect REST API correctly honors pretty parameter when publishing assets.
• MQTT2 Sink now publishes an empty Sample topic before data has come in to have the topic present for subscription.

Version 2.5.0.0 Release Candidate 2

• Added websockets interface
• Removed legacy mqtt sink

For websockets you need to connect to the server and then send requests:

{
  "id": "ABC",
  "request": "probe"
}

The id and request are required.

I have added a few other properties to support the response document,format and pretty. format can have a value of xml or json. The default format is xml.

{
  "id": "ABC",
  "request": "probe",
  "format": "json"
}

All the properties except request and id are the same as the properties you get from the swagger interface. Make a request to /swagger from the agent to find all the possible properties.

   http://localhost:5000/swagger

When an interval is given for sample or current, they will publish. A request of cancel will stop a request.

Some examples:

{"id": 1,"request": "probe", "format": "json"}
{"id": 2,"request": "current"}
{"id": 3, "request": "sample", "interval": 1000, "format": "json"}
{"id": 4, "request": "current", "interval": 5000 }
{"id": 3, "request": "cancel"}

There is no additional protocol level header. The results are chunked per the websockets spec as individual messages.