David Miller

You can send a keep-alive by using a codec. For example, place this file (`keep-alive-codec.js`) next to your `config.json` file: ```javascript // keep-alive-codec.js module.exports = { init: function( params )...

Yes. I tested it with this: ```json { "accessory": "mqttthing", "type": "lightbulb-HSV", "name": "Test espurna Light", "url": "http://192.168.10.35:1883", "topics": { "getHSV": "test/hsvlight2/hsv", "setHSV": "test/hsvlight2/hsv/set", "getOn": "test/hsvlight2/on", "setOn": "test/hsvlight2/on/set" }, "logMqtt":...

The only mention of certificates I can see at https://www.npmjs.com/package/mqtt#client is to disable rejection of self-signed server certificates. I'm not sure that MQTT supports client certificates.

Sorry, I take that back! TLS options are passed straight through to https://nodejs.org/api/tls.html#tls_tls_connect_options_callback. Looking at https://github.com/mqttjs/MQTT.js/issues/1077 I'll need to add a way for you to specify filenames that mqttthing loads.

The latest release (v1.1.19) now allows certificate files to be loaded for MQTT. See https://github.com/arachnetech/homebridge-mqttthing/blob/v1.1.19/docs/Configuration.md#mqtt-settings for details.

The same issue applies to `StatusFault`: ``` export class StatusFault extends Characteristic { public static readonly UUID: string = "00000077-0000-1000-8000-0026BB765291"; public static readonly NO_FAULT = 0; public static readonly GENERAL_FAULT...

Do you have sample messages that you want to publish and receive?

That's the default 'last will and testament' message (see https://www.hivemq.com/blog/mqtt-essentials-part-9-last-will-and-testament/) that MQTT-thing uses if you don't configure one explicitly. The 'will' message is sent automatically by the MQTT broker when...

I like that idea!

I've just added an alternative way to expose garage door opening/closing state. Instead of publishing to the `getCurrentDoorState` topic, you can now publish to `getDoorMoving` - publishing `true` if the...