Versions Compared

Old Version 3

changes.mady.by.user Gill Houghton

Saved on

compared with

New Version 4

changes.mady.by.user Gill Houghton

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

However, there are some instances where the migration from older MQTT Engine modules does not complete this process and it must be complete manually.

How do I configure the legacy state message?

The additional legacy STATE client is configured under the Advanced section for each of the configured MQTT servers in the MQTT Engine module configuration. 

To disable, you simply deselect the Enable Legacy STATE messages option. To fully remove the retained legacy STATE message at the server, you will need to restart any connected server.

Which clients will be created?

With Primary Host Disabled and Legacy Host Disabled

  • ME client created, connects and subscribes [[a/#][0], [spBv1.0/#][0]]

With Primary Host Enabled and Legacy Host Disabled

  • ME client created, connects and subscribes [[a/#][0], [spBv1.0/#][0], [spBv1.0/STATE/MyPrimaryHost][1]]

With Primary Host Disabled and Legacy Host Enabled

  • ME client created, connects and subscribes [[a/#][0], [spBv1.0/#][0]]
  • ME-LS client created but no connection made

With Primary Host Enabled and Legacy Host Enabled

  • ME client created, connects and subscribes [[a/#][0], [spBv1.0/#][0], [spBv1.0/STATE/MyPrimaryHost][1]]
  • ME-LS client created, connects and subscribes [[STATE/MyPrimaryHost][1]]


Warning

MQTT Engine will always attempt to publish/subscribe using the new STATE message format even when the Legacy Client is enabled and there is no means to disable this.

If you have restrictive Access Controls Lists configured at your broker you will need to allow access to the spBv1.0/STATE/ topic

...