michielvdvelde / novus-component Goto Github PK

When the component disconnects from the MQTT broker, even if this is involuntary (e.g. no end packet sent), the reference to MQTT.js is removed, thus not allowing reconnect logic. The MQTT.js package does seem to support it, so it might be prudent to rewrite the start() logic to take advantage of this.

Also, check to see how unclean sessions are handled, and if anything needs to be changed for (better) session support.

The component's get() and set() methods allow one to store configuration variables in a configurable store. Yet this still requires manually setting up one or more routes (if the config values are stored in MQTT retained messages, as they are in my case). It would be a nice addition if the amount of work to do this could be lowered.

A simple example:

component.setConfig([
  'some/config/topic',
  'another/config/topic',
  'a/longer/topic/#key'
]);

I'd love to hear some input on this.

Example:

component.route({
  route: [ 'topic/one', 'topic/two', 'topic/three' ],
  // ...

This can be used for different topics that need to call the same handler for processing.