The Kafka streaming feature from the MonsterMQ Core broker is now available directly in the MonsterMQ Edge broker… done with just some prompts!
The lightweight Edge version becomes a full-fledged enterprise broker, while still remaining a compact, single standalone executable.
👉 Learn more at MonsterMQ.com
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.
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? 😉
Deploy and run ML Models with WinCC OA 😎
Today I built an ONNX manager for WinCC OA that makes model integration simple:
The video shows the complete loop: changing live inputs, calculating an output, and controlling model execution directly from a WinCC OA panel.
We used a simple linear model to make the workflow easy to follow. The same approach opens the door to more complex models for industrial applications by using the ONNX standard.
AI also helped us build the integration and test panel — a practical example of using coding agents to bring new capabilities into an automation system.
The problem was: I always had a bunch of terminal sessions open with Claude Code, Codex, OpenCode and others running on headless Linux machines or locally in different directories/projects, and after a while I had no idea anymore which project was running in which terminal.
And every time I needed a new skill, an MCP server or one of the common coding tools, I had to look up how to install it again.
TermClaw provides:
With the MCP Server, you can connect Claude on your phone to it and handle your sessions with your voice. Saying “start a new project on my dev server” while having a walk…
MIT Open Source 👉 https://github.com/vogler75/termclaw
Not sure about the name, should we keep it?
Star it if you like it. 😉
We optimized MonsterMQ Edge: ⚡️ 1.9M v/s Pub&Sub 💪 on a MacBook Air M4, and it persisted all values in memory! 🧠
Can we trust those numbers? 🙈 It looks unbelievable! With 1.9M v/s the latency went up, but at 1.3M v/s we had a stable latency of about 1.3 ms P95.
The test program is fully AI-created: 3,000 leaf topics with a 5-level tree structure, where clients are concurrently producing and consuming. It runs for 370s, increases and adapts the load, and writes a detailed benchmark protocol. See pic below!
See MonsterMQ running directly as a WinCC Open Architecture manager, bringing MQTT, NATS, Redis, and Grafana connectivity to WinCC OA datapoints.
⚠️ Disclaimer: This integration is a proof of concept and is not available as a product.
I love having a Siemens SIMATIC WinCC Unified Comfort Panel running at home. It operates 24/7 without a single hiccup, consumes minimal energy, and having a dedicated, rugged industrial touch panel to check the real-time status of the house at a glance is simply awesome.
However, there has always been a catch: I am an IT guy.
I never enjoyed building UIs from scratch—and honestly, designing HMIs inside classic engineering environments like TIA Portal is not something I look forward to on the weekend.
So, I decided to solve this in true IT & Edge fashion.
MonsterMQ Edge already runs seamlessly as a Siemens Industrial Edge Application directly on SIMATIC WinCC Unified Comfort Panels, bridging panel runtime data and MQTT with ultra-low latency and minimal resource footprint.
Now, I’ve taken it one step further: MonsterMQ brokers can host simple, web-based HMI pages directly!
No heavy web server stack needed, no extra middleware—the broker itself serves your custom web interfaces.
By combining MonsterMQ’s web hosting capabilities with our brand-new MonsterMQ CLI and AI skills, the workflow becomes almost magical:
Here is what the newly generated web dashboard looks like running live on the WinCC Unified Comfort Panel touch screen:
Stay tuned for quick video walkthroughs and demo repositories showing the AI prompt-to-panel pipeline!
#Siemens #WinCCUnified #IndustrialEdge #MonsterMQ #MQTT #IIoT #EdgeComputing #GenerativeAI #SmartHome #Automation
Is your valuable machine data locked away and inaccessible?
If you are running a **Siemens SIMATIC WinCC Unified Comfort Panel**, you are in luck! You already have the power to unlock that data and stream it anywhere you need.
Here is how you can liberate your machine data in a few steps using **MonsterMQ Edge**:
### 1. Enable Industrial Edge
First, enable the **Industrial Edge** runtime on your WinCC Unified Comfort Panel (note: this typically requires a Siemens Industrial Edge license). This turns your HMI panel into an extensible edge device.
### 2. Deploy MonsterMQ Edge
Next, install the lightweight, single-binary **MonsterMQ Edge MQTT Broker** as an Industrial Edge app. As detailed in our [previous setup guide](https://www.rocworks.at/wordpress/?p=1717):
– Download `MonsterMQ-Edge.tar` from the [GitHub Releases](https://github.com/vogler75/monster-mq-edge/releases).
– Rename the file extension to `.app`.
– Upload and launch the app on your panel.
### 3. Connect to the Runtime
Once MonsterMQ Edge is running, configure it to connect to your panel’s runtime data. Use `/tmp/automation/HmiRuntime` as the Pipe Path to establish the data connection.
### 4. Stream to MQTT, Databases, & More!
With the connection established, MonsterMQ Edge exposes your machine tags via MQTT. But it doesn’t stop there:
– **Broker Forwarding**: MonsterMQ Edge can forward MQTT data directly to other cloud or enterprise-level MQTT brokers.
– **Database Integration**: It can write your runtime data immediately into databases for archiving and real-time analysis.
—
### 🌐 Scalable IoT Architecture
In a production deployment, you can run **MonsterMQ Edge** on multiple WinCC Unified Comfort Panels across the factory floor. Each edge instance forwards its tag data to a central **MonsterMQ Full** broker. The central broker then stores and forwards the aggregated stream directly into a database like **InfluxDB** for historical archiving and dashboarding.
Additionally, the central broker can host the MonsterMQ Dashboard to manage all brokers—including the ones running on the panels—providing a single, unified interface to manage your entire broker network.
Vacation day 🏝️ I have published the MonsterMQ Edge MQTT Broker as an Industrial Edge app, bringing a lightweight, single-binary MQTT broker directly to your SIMATIC WinCC Unified Comfort Panels with a data connection to the runtime data.
### ⚡ Quick 4-Step Setup:
1. Download: Grab MonsterMQ-Edge.tar from MonsterMQ-Edge GitHub Releases https://github.com/vogler75/monster-mq-edge/releases
2. Rename: Change the file extension from .tar to .app (MonsterMQ-Edge.app).
3. Upload & Start: Upload the .app file directly to your panel (with Industrial Edge enabled) and launch it.
4. Configure: Connect and manage the broker using the MonsterMQ Dashboard app, available under releases at MonsterMQ GitHub https://github.com/vogler75/monster-mq/releases
See how you can configure the HMI Tags to be exposed via MQTT
👉 https://youtu.be/C9KdrntWjec
⚠️ Use “/tmp/automation/HmiRuntime” as the Pipe Path!
#Siemens #WinCCUnified #IndustrialEdge #MQTT #MonsterMQ #IIoT #IndustrialAutomation #EdgeComputing
