Build and integrate
Integration guides for v0.15.0. These pages cover the parts of the release that go beyond a first read: serving objects, routing, shared endpoints, Network Port and Number controls, transports and BACnet/SC. Install the release from v0.15 installation, or try the local lab first.
Choose the owner for your application
Section titled “Choose the owner for your application”| Your task | Start here |
|---|---|
| Send requests to other devices | Standalone BACnetClient; choose a transport and use the API reference |
| Model a device with the full server’s service set | Serve objects from your application with a standalone BACnetServer |
| Join BACnet networks and reach devices behind a router | Route between networks with BACnetRouter |
| Request and respond as one device through one transport | Shared endpoints for B/IP, SC or MS/TP |
| Associate a B/IP socket with a Network Port object | Network Port registration |
| Learn and answer local network-number queries | Passive Number controls; no discovery command or startup announcement required |
| Connect through an SC hub | BACnet/SC setup, with explicit trust, credentials and durable device identity |
| Decide which peers may write to or control your server | Restrict who can change a device |
| Describe your device’s objects and services in a PICS | Generate a PICS for your device |
Shared endpoints deliberately have a narrower responder than the full server. Transport implementation, language binding and actual runtime evidence are separate choices; compare the transport matrix before selecting a path.
Working on the repository
Section titled “Working on the repository”For an unreleased change or a different feature set, build from source. The contributor guides cover checkout setup and documentation changes separately from release integration.
Use the reference for exact signatures
Section titled “Use the reference for exact signatures”The engineering documentation map links the canonical Rust API, Python API and CLI reference. These task guides summarize those contracts rather than duplicate every method.
Before 1.0, APIs may be removed or changed directly. Keep the source revision, feature selection and installed native artifact together in your integration record. Review upgrade guidance when moving an existing application.
Next steps
Section titled “Next steps”Release v0.15.0 ·Build and integrate. Pre-1.0 APIs; partial conformance.Support & limitations