From b5bedc9080433ba3dc172f172de63c724ed95159 Mon Sep 17 00:00:00 2001 From: John Date: Sat, 1 Oct 2022 13:39:05 +0200 Subject: [PATCH] better documentation --- contrib/etc/ebusd/knx.cfg | 32 ++++++++++++++++++++------------ 1 file changed, 20 insertions(+), 12 deletions(-) diff --git a/contrib/etc/ebusd/knx.cfg b/contrib/etc/ebusd/knx.cfg index c112a7e9..47929f94 100644 --- a/contrib/etc/ebusd/knx.cfg +++ b/contrib/etc/ebusd/knx.cfg @@ -1,21 +1,30 @@ -# Configuration file for ebusd KNX integration with KNXnet/IP and/or [knxd](https://github.com/knxd/knxd). +# Configuration file for ebusd KNX integration with KNXnet/IP or [knxd](https://github.com/knxd/knxd). # Use this file with ebusd to establish a bridge between KNX and eBUS for a set of messages. -# The commandline options to ebusd need to include "--knxurl=..." in order to activate KNX support. +# The commandline options to ebusd need to include "--knxurl=..." in order to activate KNX handling. + +# Setting the group associations and the individual address via ETS is not (yet) possible. +# This is done in here and/or via "--knxvar=" arguments to ebusd. + + +# ## INDIVIDUAL ADDRESS + +# Depending on the connection to KNX, the individual address either has to be set here for KNXnet/IP mode as stated +# below, or in knxd mode depends on how knxd is configured and as such might change each time ebusd and/or knxd is +# restarted when a range of possible addresses were configured on knxd side (which is recommended when there is more +# than one client using knxd). + +# the own individual address (only necessary and relevant when running in KNXnet/IP mode) +# address = 1.1.1 + + +# ## GROUP ASSOCIATIONS # Currently only reading from and writing to group addresses as defined here is supported. -# Setting the addresses via ETS is not (yet) possible as well as setting the physical address. -# All entries are set to group address flags as follows: +# All entries below are set to group address flags as follows: # - for read and passive write messages: "Read", "Transmit" # - for active write messages: "Write", "Read" (only answered when value was written before via KNX or eBUS), no "Update" -# The physical address depends on how knxd is configured and might change each time ebusd and/or knxd is restarted when -# a range of possible client addresses were configured on knxd side (which is recommended when there is more than one -# client using knxd). - -# the own individual address (only relevant when running in KNXnet/IP mode) -# address = 1.1.1 - # the global value group assignments for running, version, signal, uptime, updatecheck, and scan. # running: 1 bit, 1=running, DPT 1.002 global/running = 9/0 @@ -30,7 +39,6 @@ global/updatecheck = 9/4 # scan: 1 bit, 1=running, DPT 1.002 global/scan = 9/5 - # the message field value group assignments by circuit/message/field name. # the value coding depends on the field data type and currently only numeric data types are supported. # the mapping is as follows: