WESFIN LAB / GUIDES
Guides How to connect, validate and present energy equipment in Wesfin Lab
Start with the simulator tutorial. Recipes help with one task, the reference lets you check fields, explanations tell you why.
Tutorials
Go from nothing to a result in one sitting.
How-to guides
Short recipes for one specific task.
Connect a device over MQTT
Credentials, TLS, topics and the first telemetry.
Read → 10 minConnect Home Assistant
Entity mapping, validation and the local connector.
Read → 5 minImport and validate a profile
From an example or your own JSON to a validated version.
Read → 5 minRead a compatibility report
Verdict, blockers, the test matrix and what to do about them.
Read → 5 minIssue and revoke credentials
One-time secret, lifetime, rotation and revocation.
Read → 8 minA WebAssembly telemetry normalisation module
Turn a vendor's raw fields into canonical telemetry in an isolated, hashed Wasm module.
Read →Reference
Fields, topics, statuses and terms to check against.
Device profile fields
Every lab-device-profile-1 field, its limits and common errors.
Read → 6 minMQTT topics and messages
Telemetry, commands, acknowledgements and access rules.
Read → 4 minGlossary
What the words you see in the Lab mean.
Read → 6 minPower sign conventions: charge, discharge, import and export
The Wesfin canonical convention for batteries, loads and the grid connection point, and how to convert vendor signs.
Read →Explanations
Why the Lab works the way it does.
How a bounded command works
Limits, TTL, restore and five separate pieces of evidence.
Read → 4 minFrom the Lab to Wesfin Flex
Why the Lab never touches the real market and what comes next.
Read → 7 minWhat load flexibility is and how to prove it
A battery, water heater or other load as a flexibility resource: baseline, bounded command, measured response.
Read → 6 minTesting an integration on a device simulator
A deterministic BESS and load simulator, virtual time and fault injection without hardware.
Read →In a minute
- CommandThe Lab sends a power, a duration and a TTL within the profile's limits.
- AcknowledgedThe connector accepted the command.
- ExecutedThe device applied the new power.
- MeasuredAn independent measurement sees the change.
- RestoredAfter the duration the device returns to its baseline.
Each stage is separate evidence with its own source. An acknowledgement does not yet mean the power changed.
- SchemaEvery field is present, with the right types and limits.
- MeaningLimits agree with each other and the required telemetry is there.
- SafetyTTL is required, failure closes control, restore goes to baseline.
- TestsThe standard scenario pack on the deterministic simulator.
- ReportVerdict, blockers and hashes so the report can be checked.
If any stage fails, the report names the reason and the version stays unvalidated.
Every example runs in LAB. A Lab connection grants no production control and no energy market participation.