Repository navigation
Bricklogger 0.2.0
The first public release of Bricklogger.
Install with
curl -fsSL https://github.com/CX1-ApS/bricklogger/releases/latest/download/install.sh | sudo sh
or run the image ghcr.io/cx1-aps/bricklogger:0.2.0. The documentation is at
https://cx1-aps.github.io/bricklogger/.
Upgrading from 0.1 with an iBOS source
The iBOS source is no longer built in: it is a plugin of its own,
bricklogger-ibos. While sources.yaml names type: ibos and the plugin is not
installed, the daemon does not start: it reports the unknown source type
'ibos'. Add the plugin right after the upgrade and start the daemon again:
bricklogger plugins add bricklogger-ibos
sudo systemctl restart bricklogger
The configuration, the type name, the vocabulary and the collected history are
unchanged, and collection resumes from the latest observation of every point;
the stretch the daemon was down is fetched from the cloud.
Changes
- Bricklogger is published on PyPI, and the install script is a release
asset; the image is built for released versions only, without anedge
tag. - The plugin SDK grows:
bricklogger.sdk.bacnet(BACnet's object types and
the map from its engineering units to QUDT),expandandUnknownPrefix
for prefixed names, andDURATION_HELP,parse_durationand
format_duration. A plugin built for 0.1 pinsbricklogger<0.2and is
released again for 0.2. - The model explorer keeps systems, collections and zones out of the tree:
they stand in a band of their own under class headings, and a grouping opens
to what it gathers.bricklogger model tree --root <grouping>does the same.
Fixes
- A destination whose write fails — after the database restarted, say — is
stopped and started again before the write is retried, so it reconnects
instead of retrying on a dead connection forever. plugins addandplugins removeno longer miss a plugin installed within
the same instant as their previous look at the environment.