Metadata-Version: 2.4
Name: moat-link-ow
Version: 0.1.1
Summary: 1-Wire (OWFS) connector for MoaT-Link
Author-email: Matthias Urlichs <matthias@urlichs.de>
Project-URL: homepage, https://m-o-a-t.org
Project-URL: repository, https://github.com/M-o-a-T/moat
Keywords: MoaT
Classifier: Intended Audience :: Developers
Classifier: Programming Language :: Python :: 3
Classifier: Framework :: AsyncIO
Classifier: Framework :: Trio
Classifier: Framework :: AnyIO
Classifier: Development Status :: 4 - Beta
Requires-Python: >=3.13
Description-Content-Type: text/markdown
License-File: LICENSE.txt
Requires-Dist: anyio~=4.2
Requires-Dist: asyncclick~=8.3
Requires-Dist: asyncowfs~=0.15
Requires-Dist: attrs
Requires-Dist: moat-util~=0.63.0
Requires-Dist: moat-link~=0.9.0
Requires-Dist: moat-lib-config~=0.2.0
Dynamic: license-file

# 1-Wire (OWFS) connector

% start synopsis
Connects MoaT-Link to 1-Wire buses via the asyncowfs library.
% end synopsis

% start main

This module bridges MoaT-Link values and 1-Wire device attributes, in
both directions, via the ``asyncowfs`` library.  It replaces the legacy
``moat-kv-ow`` package.

## Quick start

1. Configure an OWFS server (owserver):

   ```shell
   moat link ow mybus add -h 10.0.0.1
   ```

2. Map a device attribute to a MoaT-Link path:

   ```shell
   moat link ow mybus at 10.345678.90 temperature add -s dest .data.temp.room -s interval =5
   ```

3. Run the connector:

   ```shell
   moat link ow mybus monitor
   ```

## Deprecation

This package supersedes ``moat-kv-ow``.  The address tree now lives in
MoaT-Link under the ``ow.<NAME>`` prefix; device attributes are stored
below the server entry, keyed by family code, hardware code, and the
attribute path.

% end main
