bricklogger 0.2.0__tar.gz

bricklogger-0.2.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 CX1 ApS
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

bricklogger-0.2.0/PKG-INFO

@@ -0,0 +1,208 @@
+Metadata-Version: 2.4
+Name: bricklogger
+Version: 0.2.0
+Summary: Data bridge for building automation: collects data based on a Brick model and writes it to time-series databases
+Keywords: brick,bacnet,building-automation,timescaledb,data-logger
+Author: Michael Rosenlund
+Author-email: Michael Rosenlund <michael.rosenlund@cx1.dk>
+License-Expression: MIT
+License-File: LICENSE
+Classifier: Development Status :: 2 - Pre-Alpha
+Classifier: Environment :: Console
+Classifier: Environment :: Web Environment
+Classifier: Intended Audience :: Developers
+Classifier: Intended Audience :: System Administrators
+Classifier: Operating System :: POSIX :: Linux
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Home Automation
+Classifier: Topic :: Scientific/Engineering
+Requires-Dist: pydantic>=2.7
+Requires-Dist: pyyaml>=6.0
+Requires-Dist: typer>=0.12
+Requires-Dist: httpx>=0.27
+Requires-Dist: fastapi>=0.110
+Requires-Dist: uvicorn>=0.29
+Requires-Dist: jinja2>=3.1
+Requires-Dist: python-multipart>=0.0.9
+Requires-Dist: itsdangerous>=2.1
+Requires-Dist: rdflib>=7.0
+Requires-Dist: pyshacl>=0.30
+Requires-Dist: reasonable>=0.4
+Requires-Dist: pyoxigraph>=0.4
+Requires-Dist: bacpypes3>=0.0.90
+Requires-Dist: psycopg[binary]>=3.1
+Requires-Dist: mcp>=2.2.0
+Requires-Dist: packaging>=24
+Requires-Python: >=3.11
+Project-URL: Homepage, https://github.com/CX1-ApS/bricklogger
+Project-URL: Documentation, https://cx1-aps.github.io/bricklogger/
+Project-URL: Source, https://github.com/CX1-ApS/bricklogger
+Project-URL: Issues, https://github.com/CX1-ApS/bricklogger/issues
+Description-Content-Type: text/markdown
+
+# Bricklogger
+
+Bricklogger is a data bridge for building automation. It reads a
+[Brick](https://brickschema.org/) model of a building, collects the values of
+the points the model describes from the building's automation systems, and
+writes them to a time-series database. The model decides what is collected:
+upload a new model, and the logger follows it.
+
+- **Sources:** BACnet/IP on the local network is built in; other systems are
+  added as plugins, such as the [iBOS source](https://github.com/CX1-ApS/bricklogger-ibos)
+  for the iBOS Data API in the cloud.
+- **Destination:** TimescaleDB, with every observation timestamped by its
+  source and a spool that holds them while the database is away.
+- **Interfaces:** a command-line interface first, a web interface with the same
+  abilities beside it — including a model explorer — an HTTP API, and an MCP
+  server so an AI assistant can configure the logger for you.
+- **Read only:** Bricklogger never writes to a building automation system.
+
+The full documentation is at **<https://cx1-aps.github.io/bricklogger/>**. This
+page is the short version.
+
+## What you need
+
+- A Linux machine, amd64 or arm64, that can reach the building's network —
+  for BACnet/IP, on the same subnet as the devices or with a route to them.
+- A Brick model of the building as Turtle (`.ttl`), with the points' external
+  references (BACnet device and object, for instance).
+- A TimescaleDB database Bricklogger may create tables in.
+
+## Install
+
+```bash
+curl -fsSL https://github.com/CX1-ApS/bricklogger/releases/latest/download/install.sh | sudo sh
+```
+
+The script brings its own Python, so the machine needs only `curl`. With
+`sudo` it installs a service: the program under `/opt/bricklogger`, the
+configuration in `/etc/bricklogger`, the data in `/var/lib/bricklogger` and
+three systemd units, left stopped. Without `sudo` everything stays in your home
+directory. `--version 0.2.0` installs a given version; options come after
+`--` when the script is piped: `… | sudo sh -s -- --version 0.2.0`.
+
+**As a container** the same program is `ghcr.io/cx1-aps/bricklogger`, with a
+compose file for the daemon, the web interface and the MCP server; see
+[Docker](https://cx1-aps.github.io/bricklogger/docker/).
+
+## Prepare the database
+
+```sql
+CREATE DATABASE brick;
+\c brick
+CREATE EXTENSION IF NOT EXISTS timescaledb;
+CREATE ROLE bricklogger LOGIN PASSWORD '...';
+GRANT ALL ON SCHEMA public TO bricklogger;
+```
+
+Bricklogger creates and migrates its own tables at the first start.
+
+## First setup
+
+```bash
+bricklogger init                        # guided: sources, destinations, secrets
+bricklogger validate                    # after any edit by hand
+bricklogger daemon start                # or: sudo systemctl enable --now bricklogger
+bricklogger model upload building.ttl   # validate, infer, activate
+bricklogger status
+bricklogger points --outcome active     # the last value of every point
+```
+
+`init` asks for the settings of each source and destination and writes four
+files: `sources.yaml`, `destinations.yaml`, `rules.yaml` and `daemon.yaml`.
+Secrets, such as the database password, go into an `env` file beside them and
+are referred to as `${NAME}`. The first rule set accepts every point in the
+model every five minutes; [rules](https://cx1-aps.github.io/bricklogger/features/configuration/)
+narrow that down by class, location, equipment or any SPARQL pattern.
+
+## The web interface and an assistant
+
+```bash
+bricklogger serve        # http://127.0.0.1:8421
+```
+
+Everything the CLI does can be done there, and the model explorer shows the
+building as a tree and a graph, with every point's outcome and value.
+
+To let an AI assistant that speaks MCP set up sources, destinations and rules,
+register the MCP server with it — for Claude Code on the same machine:
+
+```bash
+claude mcp add --transport stdio bricklogger -- bricklogger mcp serve
+```
+
+The assistant reads the plugins' schemas and this documentation, validates
+before it writes, and never takes a secret's value. See
+[MCP](https://cx1-aps.github.io/bricklogger/features/mcp/) for remote use.
+
+## Plugins
+
+```bash
+bricklogger plugins                          # what is installed
+bricklogger plugins add bricklogger-ibos     # add a plugin from PyPI
+bricklogger plugins remove ibos              # remove one by its type
+sudo systemctl restart bricklogger           # the daemon reads plugins at start
+```
+
+A plugin is a Python package that provides a source or a destination type. A
+plugin that cannot load stops nothing: its instances show as failed and the
+rest keep running. Writing one is described under
+[plugins](https://cx1-aps.github.io/bricklogger/features/plugins/).
+
+## Mail notifications
+
+Bricklogger can mail an administrator when something goes wrong, when it is
+put right, and once a day as proof that it is alive. Put the mail server and
+recipients under `notifications` in `daemon.yaml`, then:
+
+```bash
+bricklogger notify test
+```
+
+See [notifications](https://cx1-aps.github.io/bricklogger/features/notifications/).
+
+## Upgrade
+
+Run the install script again; it leaves the plugins, the configuration and the
+data where they are. Then restart the daemon. A container pulls the new image
+instead:
+
+```bash
+curl -fsSL https://github.com/CX1-ApS/bricklogger/releases/latest/download/install.sh | sudo sh
+sudo systemctl restart bricklogger
+```
+
+After an upgrade to a new minor version, `bricklogger plugins` shows whether
+every plugin still loads.
+
+**Upgrading from 0.1 with an iBOS source:** iBOS is no longer built in. The
+`ibos` instance shows as failed until the plugin is added with
+`bricklogger plugins add bricklogger-ibos` and the daemon is restarted; the
+configuration and the collected history stay as they were.
+
+## If nothing arrives
+
+- `bricklogger status warnings` lists what stands in the way, one line per
+  cause — points no source claims, points without a reference, read errors.
+- `bricklogger sources bacnet_main discover` shows the BACnet devices that
+  answer. If none does, the address in `sources.yaml` or the network is the
+  problem, not the model.
+- `bricklogger sources bacnet_main resolve <point>` shows how one point's
+  reference resolves, and reads it.
+- `bricklogger destinations status` shows whether the database takes writes.
+  While it does not, observations wait in the spool.
+
+## Reporting a problem
+
+Bugs and questions go in the
+[issues](https://github.com/CX1-ApS/bricklogger/issues). A security
+vulnerability is reported privately, as [SECURITY.md](https://github.com/CX1-ApS/bricklogger/blob/main/SECURITY.md) describes.
+
+## License
+
+[MIT](https://github.com/CX1-ApS/bricklogger/blob/main/LICENSE). Bricklogger bundles Brick's ontology and a few web libraries
+and fonts under their own licenses, listed with them in the package.

bricklogger-0.2.0/README.md

@@ -0,0 +1,163 @@
+# Bricklogger
+
+Bricklogger is a data bridge for building automation. It reads a
+[Brick](https://brickschema.org/) model of a building, collects the values of
+the points the model describes from the building's automation systems, and
+writes them to a time-series database. The model decides what is collected:
+upload a new model, and the logger follows it.
+
+- **Sources:** BACnet/IP on the local network is built in; other systems are
+  added as plugins, such as the [iBOS source](https://github.com/CX1-ApS/bricklogger-ibos)
+  for the iBOS Data API in the cloud.
+- **Destination:** TimescaleDB, with every observation timestamped by its
+  source and a spool that holds them while the database is away.
+- **Interfaces:** a command-line interface first, a web interface with the same
+  abilities beside it — including a model explorer — an HTTP API, and an MCP
+  server so an AI assistant can configure the logger for you.
+- **Read only:** Bricklogger never writes to a building automation system.
+
+The full documentation is at **<https://cx1-aps.github.io/bricklogger/>**. This
+page is the short version.
+
+## What you need
+
+- A Linux machine, amd64 or arm64, that can reach the building's network —
+  for BACnet/IP, on the same subnet as the devices or with a route to them.
+- A Brick model of the building as Turtle (`.ttl`), with the points' external
+  references (BACnet device and object, for instance).
+- A TimescaleDB database Bricklogger may create tables in.
+
+## Install
+
+```bash
+curl -fsSL https://github.com/CX1-ApS/bricklogger/releases/latest/download/install.sh | sudo sh
+```
+
+The script brings its own Python, so the machine needs only `curl`. With
+`sudo` it installs a service: the program under `/opt/bricklogger`, the
+configuration in `/etc/bricklogger`, the data in `/var/lib/bricklogger` and
+three systemd units, left stopped. Without `sudo` everything stays in your home
+directory. `--version 0.2.0` installs a given version; options come after
+`--` when the script is piped: `… | sudo sh -s -- --version 0.2.0`.
+
+**As a container** the same program is `ghcr.io/cx1-aps/bricklogger`, with a
+compose file for the daemon, the web interface and the MCP server; see
+[Docker](https://cx1-aps.github.io/bricklogger/docker/).
+
+## Prepare the database
+
+```sql
+CREATE DATABASE brick;
+\c brick
+CREATE EXTENSION IF NOT EXISTS timescaledb;
+CREATE ROLE bricklogger LOGIN PASSWORD '...';
+GRANT ALL ON SCHEMA public TO bricklogger;
+```
+
+Bricklogger creates and migrates its own tables at the first start.
+
+## First setup
+
+```bash
+bricklogger init                        # guided: sources, destinations, secrets
+bricklogger validate                    # after any edit by hand
+bricklogger daemon start                # or: sudo systemctl enable --now bricklogger
+bricklogger model upload building.ttl   # validate, infer, activate
+bricklogger status
+bricklogger points --outcome active     # the last value of every point
+```
+
+`init` asks for the settings of each source and destination and writes four
+files: `sources.yaml`, `destinations.yaml`, `rules.yaml` and `daemon.yaml`.
+Secrets, such as the database password, go into an `env` file beside them and
+are referred to as `${NAME}`. The first rule set accepts every point in the
+model every five minutes; [rules](https://cx1-aps.github.io/bricklogger/features/configuration/)
+narrow that down by class, location, equipment or any SPARQL pattern.
+
+## The web interface and an assistant
+
+```bash
+bricklogger serve        # http://127.0.0.1:8421
+```
+
+Everything the CLI does can be done there, and the model explorer shows the
+building as a tree and a graph, with every point's outcome and value.
+
+To let an AI assistant that speaks MCP set up sources, destinations and rules,
+register the MCP server with it — for Claude Code on the same machine:
+
+```bash
+claude mcp add --transport stdio bricklogger -- bricklogger mcp serve
+```
+
+The assistant reads the plugins' schemas and this documentation, validates
+before it writes, and never takes a secret's value. See
+[MCP](https://cx1-aps.github.io/bricklogger/features/mcp/) for remote use.
+
+## Plugins
+
+```bash
+bricklogger plugins                          # what is installed
+bricklogger plugins add bricklogger-ibos     # add a plugin from PyPI
+bricklogger plugins remove ibos              # remove one by its type
+sudo systemctl restart bricklogger           # the daemon reads plugins at start
+```
+
+A plugin is a Python package that provides a source or a destination type. A
+plugin that cannot load stops nothing: its instances show as failed and the
+rest keep running. Writing one is described under
+[plugins](https://cx1-aps.github.io/bricklogger/features/plugins/).
+
+## Mail notifications
+
+Bricklogger can mail an administrator when something goes wrong, when it is
+put right, and once a day as proof that it is alive. Put the mail server and
+recipients under `notifications` in `daemon.yaml`, then:
+
+```bash
+bricklogger notify test
+```
+
+See [notifications](https://cx1-aps.github.io/bricklogger/features/notifications/).
+
+## Upgrade
+
+Run the install script again; it leaves the plugins, the configuration and the
+data where they are. Then restart the daemon. A container pulls the new image
+instead:
+
+```bash
+curl -fsSL https://github.com/CX1-ApS/bricklogger/releases/latest/download/install.sh | sudo sh
+sudo systemctl restart bricklogger
+```
+
+After an upgrade to a new minor version, `bricklogger plugins` shows whether
+every plugin still loads.
+
+**Upgrading from 0.1 with an iBOS source:** iBOS is no longer built in. The
+`ibos` instance shows as failed until the plugin is added with
+`bricklogger plugins add bricklogger-ibos` and the daemon is restarted; the
+configuration and the collected history stay as they were.
+
+## If nothing arrives
+
+- `bricklogger status warnings` lists what stands in the way, one line per
+  cause — points no source claims, points without a reference, read errors.
+- `bricklogger sources bacnet_main discover` shows the BACnet devices that
+  answer. If none does, the address in `sources.yaml` or the network is the
+  problem, not the model.
+- `bricklogger sources bacnet_main resolve <point>` shows how one point's
+  reference resolves, and reads it.
+- `bricklogger destinations status` shows whether the database takes writes.
+  While it does not, observations wait in the spool.
+
+## Reporting a problem
+
+Bugs and questions go in the
+[issues](https://github.com/CX1-ApS/bricklogger/issues). A security
+vulnerability is reported privately, as [SECURITY.md](https://github.com/CX1-ApS/bricklogger/blob/main/SECURITY.md) describes.
+
+## License
+
+[MIT](https://github.com/CX1-ApS/bricklogger/blob/main/LICENSE). Bricklogger bundles Brick's ontology and a few web libraries
+and fonts under their own licenses, listed with them in the package.

bricklogger-0.2.0/pyproject.toml

@@ -0,0 +1,126 @@
+[project]
+name = "bricklogger"
+version = "0.2.0"
+description = "Data bridge for building automation: collects data based on a Brick model and writes it to time-series databases"
+readme = "README.md"
+license = "MIT"
+license-files = ["LICENSE"]
+requires-python = ">=3.11"
+keywords = [
+    "brick",
+    "bacnet",
+    "building-automation",
+    "timescaledb",
+    "data-logger",
+]
+classifiers = [
+    "Development Status :: 2 - Pre-Alpha",
+    "Environment :: Console",
+    "Environment :: Web Environment",
+    "Intended Audience :: Developers",
+    "Intended Audience :: System Administrators",
+    "Operating System :: POSIX :: Linux",
+    "Programming Language :: Python :: 3",
+    "Programming Language :: Python :: 3.11",
+    "Programming Language :: Python :: 3.12",
+    "Programming Language :: Python :: 3.13",
+    "Topic :: Home Automation",
+    "Topic :: Scientific/Engineering",
+]
+dependencies = [
+    "pydantic>=2.7",
+    "pyyaml>=6.0",
+    "typer>=0.12",
+    "httpx>=0.27",
+    "fastapi>=0.110",
+    "uvicorn>=0.29",
+    "jinja2>=3.1",
+    "python-multipart>=0.0.9",
+    "itsdangerous>=2.1",
+    "rdflib>=7.0",
+    "pyshacl>=0.30",
+    "reasonable>=0.4",
+    "pyoxigraph>=0.4",
+    "bacpypes3>=0.0.90",
+    "psycopg[binary]>=3.1",
+    "mcp>=2.2.0",
+    "packaging>=24",
+]
+
+[[project.authors]]
+name = "Michael Rosenlund"
+email = "michael.rosenlund@cx1.dk"
+
+[project.urls]
+Homepage = "https://github.com/CX1-ApS/bricklogger"
+Documentation = "https://cx1-aps.github.io/bricklogger/"
+Source = "https://github.com/CX1-ApS/bricklogger"
+Issues = "https://github.com/CX1-ApS/bricklogger/issues"
+
+[project.scripts]
+bricklogger = "bricklogger.cli:main"
+
+[project.entry-points."bricklogger.sources"]
+bacnet-ip = "bricklogger.plugins.bacnet_ip.declaration:SOURCE"
+
+[project.entry-points."bricklogger.destinations"]
+timescaledb = "bricklogger.plugins.timescaledb.declaration:DESTINATION"
+
+[dependency-groups]
+dev = [
+    "pytest>=8.0",
+    "ruff>=0.5",
+    "mypy>=1.10",
+    "types-PyYAML>=6.0",
+    "mkdocs-material>=9.7.6",
+]
+
+[build-system]
+requires = ["uv_build>=0.8,<0.13"]
+build-backend = "uv_build"
+
+[tool.uv.build-backend]
+module-name = "bricklogger"
+module-root = "src"
+
+[tool.ruff]
+line-length = 88
+target-version = "py311"
+src = [
+    "src",
+    "tests",
+]
+
+[tool.ruff.lint]
+select = [
+    "E",
+    "F",
+    "W",
+    "I",
+    "UP",
+    "B",
+    "SIM",
+    "RUF",
+]
+
+[tool.mypy]
+python_version = "3.11"
+strict = true
+plugins = ["pydantic.mypy"]
+files = [
+    "src",
+    "tests",
+]
+
+[[tool.mypy.overrides]]
+module = [
+    "bacpypes3.*",
+    "rdflib.*",
+    "pyshacl.*",
+    "reasonable.*",
+]
+ignore_missing_imports = true
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]
+addopts = "-q"

bricklogger-0.2.0/pyproject.toml.orig

@@ -0,0 +1,103 @@
+[project]
+name = "bricklogger"
+version = "0.2.0"
+description = "Data bridge for building automation: collects data based on a Brick model and writes it to time-series databases"
+readme = "README.md"
+license = "MIT"
+license-files = ["LICENSE"]
+authors = [{ name = "Michael Rosenlund", email = "michael.rosenlund@cx1.dk" }]
+requires-python = ">=3.11"
+keywords = ["brick", "bacnet", "building-automation", "timescaledb", "data-logger"]
+classifiers = [
+    "Development Status :: 2 - Pre-Alpha",
+    "Environment :: Console",
+    "Environment :: Web Environment",
+    "Intended Audience :: Developers",
+    "Intended Audience :: System Administrators",
+    "Operating System :: POSIX :: Linux",
+    "Programming Language :: Python :: 3",
+    "Programming Language :: Python :: 3.11",
+    "Programming Language :: Python :: 3.12",
+    "Programming Language :: Python :: 3.13",
+    "Topic :: Home Automation",
+    "Topic :: Scientific/Engineering",
+]
+dependencies = [
+    # core
+    "pydantic>=2.7",
+    "pyyaml>=6.0",
+    # CLI
+    "typer>=0.12",
+    "httpx>=0.27",
+    # API and web interface
+    "fastapi>=0.110",
+    "uvicorn>=0.29",
+    "jinja2>=3.1",
+    "python-multipart>=0.0.9",
+    "itsdangerous>=2.1",
+    # Brick model and working graph
+    "rdflib>=7.0",
+    "pyshacl>=0.30",
+    "reasonable>=0.4",
+    "pyoxigraph>=0.4",
+    # plugins
+    "bacpypes3>=0.0.90",
+    "psycopg[binary]>=3.1",
+    "mcp>=2.2.0",
+    # plugin management: the requirements and markers read at `plugins remove`
+    "packaging>=24",
+]
+
+[project.urls]
+Homepage = "https://github.com/CX1-ApS/bricklogger"
+Documentation = "https://cx1-aps.github.io/bricklogger/"
+Source = "https://github.com/CX1-ApS/bricklogger"
+Issues = "https://github.com/CX1-ApS/bricklogger/issues"
+
+[project.scripts]
+bricklogger = "bricklogger.cli:main"
+
+[project.entry-points."bricklogger.sources"]
+bacnet-ip = "bricklogger.plugins.bacnet_ip.declaration:SOURCE"
+
+[project.entry-points."bricklogger.destinations"]
+timescaledb = "bricklogger.plugins.timescaledb.declaration:DESTINATION"
+
+[dependency-groups]
+dev = [
+    "pytest>=8.0",
+    "ruff>=0.5",
+    "mypy>=1.10",
+    "types-PyYAML>=6.0",
+    "mkdocs-material>=9.7.6",
+]
+
+[build-system]
+requires = ["uv_build>=0.8,<0.13"]
+build-backend = "uv_build"
+
+[tool.uv.build-backend]
+module-name = "bricklogger"
+module-root = "src"
+
+[tool.ruff]
+line-length = 88
+target-version = "py311"
+src = ["src", "tests"]
+
+[tool.ruff.lint]
+select = ["E", "F", "W", "I", "UP", "B", "SIM", "RUF"]
+
+[tool.mypy]
+python_version = "3.11"
+strict = true
+plugins = ["pydantic.mypy"]
+files = ["src", "tests"]
+
+[[tool.mypy.overrides]]
+module = ["bacpypes3.*", "rdflib.*", "pyshacl.*", "reasonable.*"]
+ignore_missing_imports = true
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]
+addopts = "-q"

bricklogger-0.2.0/src/bricklogger/__init__.py

@@ -0,0 +1,17 @@
+"""Bricklogger: a data bridge for building automation, driven by a Brick model.
+
+The package is laid out after the architecture in ``docs/architecture.md``:
+
+- ``bricklogger.daemon`` — the long-running core that collects and writes,
+- ``bricklogger.cli`` — the ``bricklogger`` command, the control plane,
+- ``bricklogger.web`` — the web interface served by ``bricklogger serve``,
+- ``bricklogger.mcp`` — the MCP server served by ``bricklogger mcp serve``, for
+  an AI assistant,
+- ``bricklogger.ops`` — the operations the CLI and the MCP server share,
+- ``bricklogger.sdk`` — the contract and the helpers plugins are built on,
+- ``bricklogger.plugins`` — the built-in source (BACnet/IP) and
+  destination (TimescaleDB), registered through the same entry points as
+  external plugins.
+"""
+
+__version__ = "0.2.0"

bricklogger-0.2.0/src/bricklogger/__main__.py

@@ -0,0 +1,6 @@
+"""``python -m bricklogger``: the same as the ``bricklogger`` command."""
+
+from bricklogger.cli import main
+
+if __name__ == "__main__":
+    main()