Regarding the UMH core stack, I updated my 'starterkit' fully last week with some examples for ERP data, OPC-UA and included pgbouncer. Let me know if you have questions 👍

There is a project “UMH-factory-demo” by @DanielH which we use internally for testing. Will check yours out as well

ah, yes. https://github.com/united-manufacturing-hub/umh-factory-demo it is a fully automated script for setting up umh-core, timescale, nginx, pgbouncer, a machine simulator that generates upc-ua data, pre-generated flows, data-models, sql-functions/views. Not meant for production use. Works fine for playing around, testing functions etc.

Wow did not know about this one. Thanks

It is quite new. I have rewritten it a couple of times, but now it is stable. It is very quick to setup a demo and play around.

@DanielH as someone specialised in the sheet metal industry, I'm impressed with your accuracy of the demo setup! I would maybe adjust a few things regarding the laser data points, but got the fabrication demo up now. Super done!

@Luke van Enkhuizen Thanks. I have been in the industry for many years my self, so i have quite good understanding of different processes. 😀 I also did some research for the machine simulator to be as accurate as possible.

Hey @DanielH yes, for both the repo itself as well as some use cases i will create a few issues. I found some bugs with the stop detector, erp-receiver and some enhancement to stop reasons (e.g. have them in the simulator dashboard instead of grafana)

Nice. i am currently working with erp-receiver and stop-detector, so hopefully it will be fixed today. also pushed some minor changes in the machine simulator since it was causing deadlocks.

some could be my own creations, like #2 but on it 🙂

this is super helpful. I have also fixed some hypertable errors which should greatly improve the performance in grafana.

Yea, I see the challenge. I was trying to integrate a powdercoating line example like I integrated it myself for client. Quite tricky to not break other things

Issue #1: Stop-detector default state & null guard - else { 2 } default — acceptable design choice (assumes RUNNING on first boot; only creates a duplicate stop on restart if machine is already stopped). - Cache key fix confirmed: both GET/SET use meta("umh_topic") (not the broken json("asset_id")). - Cache SET value fix confirmed: uses content() (not the broken json("current_state").string()). - Added missing filter_no_asset guard — drops messages with null asset_id before determine_action, preventing the NOT NULL constraint error we saw on the VM. Issue #2: ERP-receiver lineId suffix stripping - Fixed: lineId now strips the -N suffix via rawLineId.replace(/-\d+$/, '') so automotive-welding-1 becomes automotive-welding. - The get_output_vs_planned LIKE fallback at line 1567 handles existing data with the old suffixed names.