Files

znetsixe 59ff4d230e examples: replace stale flows with single integrated e2e example

Drop the pre-refactor flows (edge.flow.json, integration.flow.json,
monster-dashboard.flow.json, monster-api-dashboard.flow.json) and ship
one canonical 02-integrated-e2e.json instead.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-05-12 14:51:25 +02:00

02-integrated-e2e.json

examples: replace stale flows with single integrated e2e example

2026-05-12 14:51:25 +02:00

basic.flow.json

before functional changes by codex

2026-02-19 17:37:09 +01:00

README.md

before functional changes by codex

2026-02-19 17:37:09 +01:00

README.md

Monster Example Flows

Import-ready Node-RED examples for monster.

Files

basic.flow.json
- Purpose: quick-start flow with dashboard charts for key monster outputs.
integration.flow.json
- Purpose: lightweight integration contract example (registerChild path).
edge.flow.json
- Purpose: unknown-topic/edge handling smoke example.
monster-dashboard.flow.json
- Purpose: richer dashboard-focused visualization of process output.
- Includes:
  - manual flow input
  - manual start trigger
  - seeded rain_data and monsternametijden
  - parsed report fields (m3Total, m3PerPuls, pulse, running)
monster-api-dashboard.flow.json
- Purpose: full orchestration template around monster with API paths and dashboard output.
- Includes:
  - Open-Meteo weather fetch -> rain_data
  - Aquon SFTP CSV fetch -> monsternametijden
  - Z-Info token + import payload builder for m3Total/m3PerPuls
  - dashboard API publish template (Grafana)
  - placeholder-only credentials/hosts (__SET_*__)

Notes

basic.flow.json and monster-dashboard.flow.json are intentionally API-free.
monster-api-dashboard.flow.json is the full API template variant and must be hardened with environment-backed secrets before production use.
ui-chart uses series by msg.topic (category: "topic", categoryType: "msg").