EmonCMS¶
V2 has no EmonCMS integration, and none is planned.
This page described something else until 2026-08
It listed an EmonCMS integration for V2: server URL and API key in .env, a
fetch via php artisan emoncms:fetch, mapping feeds onto measurement
channels, thresholds warning during a calibration, a live dashboard and a
troubleshooting table for all of it. None of that exists in the code. The
name does not appear in laravel/ or frontend-v2/ at all; every hit sits
in httpdocs/, that is, in V1.
What existed and what exists¶
In V1 there is an EmonCMS dashboard widget. It displays sensor values, nothing more.
In V2 there is none, and there will not be one. Monitoring a laboratory is the job of a monitoring system, not of calibration software. A lab that needs a continuous record of environmental conditions — and an ISO/IEC 17025 lab does — runs that outside calServer and keeps the records there.
What calServer V2 does with environmental conditions¶
Two figures that have nothing to do with each other:
| Figure | Where it lives | What happens to it |
|---|---|---|
| Target range | Resources, field environment_resources in the format 21,0 ... 23,0 °C\|40 ... 60 % |
gets printed on the calibration certificate |
| Actual values | fields temperature, humidity, pressure on the calibration, captured in the test run preamble |
sit on the record and can be printed |
Printed, not checked
Nothing compares target against actual. There is no limit monitoring, no history and no alarm. The actual values are optional input on top of that. The completion check does pull environmental conditions into its plausibility section, but as a hint, not as a block.
For an ISO/IEC 17025 laboratory¶
The wiki template
wiki-iso-17025-calserver
states this as a named limit in QMH-05: the monitoring system, the form of the
records, their retention and the review interval are the lab's decision and
belong in the quality manual, not in an expectation of calServer.