🌳 Views / Virtual Topic Trees in MonsterMQ Edge!

One thing has always bothered me about MQTT in practice: devices publish where they want to, for example: tasmota/devices/14835A/...

The device ID is in there, fine. But every time I want to query or subscribe to that sensor, I first have to look up what device 14835A actually is. Is it my living room or is it the kitchen? Is it a temp sensor? Or is it a power meter?

With virtual topics, you can now define views on top of real topics. The sensor above can also be made available as: austria/vogler/office/temperature/..

Same data, two (or more) names. No republishing, no copying, no duplicated messages.

  • 👉 Map a single topic, or mount a whole subtree
  • 👉 Wildcard subscriptions work on the virtual tree
  • 👉 Each node is read-only or read-write

That way you can have a location view, an asset view, or an ISA-95 style view of the same devices, all at the same time.

Now my question to you: is this useful, or should I drop it again? How do you deal with this today? Republishing in Node-RED, a strict UNS naming convention from day one, or just an Excel sheet? 😉

1793791980848

WinCC OA & Node-Red Integration

It is very easy to get data from WinCC Open Architecture to NodeRed.

Add a new user to WinCC OA – System Management / Permission / User Administation.

We will use “node” as username.

Add Config Entry

[wssServer]
httpsPort = 8449
resourceName = "/websocket"

Start Control Manager “wss.ctl -user <username>:” Note the trailing “:” !!

wss.ctl -user node:

Node-Red: Install Palette “node-red-contrib-winccoa”

You can now add a Node. In that example we will use the dpQuery node and use “SELECT ‘_online.._value’ FROM ‘Meter_Input_WattAct.'” as query. So we just query the online value of one tag.

You have to configure the Server by clicking on the pencil button. This points to the before started Websocket Control Manager and you have to set the username and password we have added in one of the previous steps.