Wacnet is an open-source BACnet web server built primarily on the BACnet4J library and written in Clojure. Its distinguishing engineering feature is a REPL page that allows operators or developers to define and use commands at runtime. The available evidence identifies both source and compiled distributions, but it does not provide the commands, prerequisites, supported BACnet services, or deployment requirements needed for a reproducible installation procedure.
Understand the Wacnet Architecture
Wacnet uses BACnet4J for most BACnet functionality while Clojure provides the application layer and interactive REPL. Some functions, including property-reading functions, were identified as possible candidates for a native Clojure rewrite; therefore, do not assume every subsystem has the same implementation or runtime behavior.
| Component | Confirmed role | Engineering implication |
|---|---|---|
| Wacnet | BACnet web server | Provides the web-facing application. |
| BACnet4J | Implements most BACnet functionality | Review BACnet behavior in the context of this underlying library. |
| Clojure | Application implementation language | Supports interactive command definition through the REPL page. |
| REPL page | Defines and runs commands on the fly | Treat entered commands as executable application behavior and validate them before operational use. |
Select a Source or Compiled Deployment
Two distribution paths are documented: source code and a compiled release. Use the source path when code inspection or modification is required; use the compiled path when the objective is to run the packaged application. Release 1.1.0 is explicitly identified, but the evidence does not establish its runtime dependencies, upgrade compatibility, configuration format, or changes from earlier versions.
Before deployment, obtain the release-specific instructions supplied with the selected distribution. Confirm the installed release, required runtime, BACnet network settings, web-service settings, and startup command from that documentation rather than inferring values.
Verify BACnet and REPL Operation
After startup, verify that the web interface loads and that the application can read the intended BACnet properties. Then test a non-disruptive REPL command and confirm its result against the corresponding BACnet object or property. The evidence does not define authentication, authorization, command isolation, or write safeguards, so evaluate those controls before exposing the web server or REPL beyond a controlled environment.
A successful web page load proves only that the web layer is reachable. Operational acceptance also requires confirmed BACnet communication and a validated REPL response; record the Wacnet release and the exact command used so the test can be repeated after changes.
FAQ
Is Wacnet built entirely in Java?
No. Wacnet is written in Clojure and uses BACnet4J for most of its BACnet functionality.
Can Wacnet commands be created at runtime?
Yes. Its REPL page supports defining and using commands on the fly; validate each command in a controlled environment before operational use.
What Wacnet version is confirmed by the available evidence?
Release 1.1.0 is confirmed. Consult its release-specific package instructions for dependencies, configuration, startup, and upgrade details because those values are not included in the evidence.