MQTT Connector

Bug fix

Added delay option to MQTT connection info

Fix for #19

Reworked handling of End term in topic component match

Fix bug introduced in 2022.0.1

Fixes device/variable publication bugs

Python3!

Fix for #17 Explicit disconnect from broker before destroying the broker object.

Fix for UTF-8 encoded payloads, issue #16

Implemented issue #15.

Bug fix - state labels now correct

Fixed device publishing to multiple broker devices

More capability changes in device template.

More info in device template dict

Added more fields to top level. Added actual values to capabilities.

0.4.3 was never released

Added device capability keys to the dictionary available for publishing templates. The dict now looks something like this: { 'name': u'Example Sensor', 'deviceId': 1379277130, 'address': u'123456', 'model': u'Example On/Off Sensor Module', 'states': [ {'name': u'backlightBrightness', 'value': 0}, {'name': u'sensorValue', 'value': 82.4}, {'name': u'sensorValue.ui', 'value': u'82.4 \xb0F'} ], 'supportsAllLightsOnOff': True, 'supportsAllOff': True, 'supportsOnState': True, 'supportsSensorValue': True, 'supportsStatusRequest': True, }

The "supportsXXX" keys are new. All device attributes starting with "supports" are added to the list. The actual keys present will be different for different devices. Only "True" keys will be included.

Fix bug in publishMessageAction

retain flag not processed properly

The release implements MQTT topic commands to set variables or command devices.

Added topic aggregation Device. Changed payload templates to double quotes. Fixed topic subscription actions.

Added termination term to topic match

So that topic matching can terminate at a specific term.

Fixed indentation problem

This is the first test release implementing support for the AWS IoT MQTT broker. There's a new option when configuring a Broker device to select this type of broker. Requires an AWS account and IoT instance configured. Documentation on that will be in the Wiki, eventually.

See https://github.com/FlyingDiver/Indigo-MQTT/issues/6

One change for existing users - the files paths for the DXL Broker Device configuration are now relative to the Indigo base directory, rather than absolute paths.

Catch error if DXL Library not installed. Prevent creating DXL Broker if no DXL Library.

Now supports OpenDXL Brokers. DXL is a off-shoot of MQTT.

https://www.opendxl.com

OpenDXL is an initiative to create adaptive systems of interconnected services that communicate and share information for real-time, accurate security decisions and actions.

Addresses issue #4, will automatically reconnect if MQTT Broker connection is lost.

Actually fixed exclusion method.

Also, blocks updates on broker devices

Release 0.1.0 - First plugin store release