MQTT Engine - Can't bind server set to a custom namespace, and no tag created

Ignition 8.3 Early Access
, ,
1

Hello,

Here my configuration.

  • I have a Raspberry Pi 5 with Docker compose with
    • Ignition 8.3
    • PostgreSQL database
    • Mosquitto (MQTT broker)

I’m able to connect the gateway to the server

{B9248DAA-FDE8-4193-AFCD-D130A4FB3B01}

I use the default server set.

The default namespaces are disabled (Elecsys, SparkplugA, SparkplugB and Xirgo), and a custom namespace “aircon” is created.

{5DC89B43-1F0A-439A-8DA0-DFFAA9FFD2E3}
{5DC89B43-1F0A-439A-8DA0-DFFAA9FFD2E3}418×792 25.6 KB

But here I’m not able to link the custom namespace to the server set.

{D7AC1280-1C84-43F6-A45C-6940F2A6E20C}
{D7AC1280-1C84-43F6-A45C-6940F2A6E20C}998×331 9.02 KB

Someone has the same issue ? It is a configuration error ? Or just a bug ?

I can wait the official release, it’s just annoying :neutral_face:

Thank you !

2

Hey,

I’m running into the same error, was about to post, but came across this post while looking if there’s a solution/duplicate.
I’m leaning more towards it being a bug, as I am getting tags using the same configuration on 8.1.42

3

The server set was linked after a reboot of the gateway.

I can see the tag “Messages per second” change when I send a message, but no tags are created. I’m on the right topic “aircon/test”.

I tried to remove the wildcard on the namespace for just “aircon”. But the gateway seems to not change the subscription. So I restarted again the gateway, and the subcription was right. But same result, I can see the tag “Messages per second” change, but no tag was created.

4

I’ve created a support request on cirrus website. I will post their answer here

1 Like
5

Answer :

Steven,

There were some bugs in the Custom Namespace handler at Engine and should be fixed in beta4 when our modules become available. They may be ready later today. I assume you were subscribing to MQTT Topic messages, not Sparkplug?

In order to run our latest modules you will also need to upgrade (or freshly load) Ignition v8.3.0-beta4.

As these Ignition beta versions change so too will our modules. I would not expect differing versions of beta software to be cross compatible. This is the nature of beta software development & testing.

Regards,

Daniel

6

Updated to MQTT Engine 5.0.0-Beta2 and Ignition 8.3-Beta4, and still the same issue.

Waiting the cirrus support