Skip to content

Latest commit

 

History

History
102 lines (64 loc) · 5.34 KB

README.md

File metadata and controls

102 lines (64 loc) · 5.34 KB
Raw

ebusd-configuration

This repository serves vendor specific configuration files for ebusd.

WARNING: There is absolutely no warranty at all for using any of the files provided here and you should definitely know what you're doing.

If you mess up these files or even just a single line in one of them, you might force your heating to weird behaviour or at the worst even damage it.

If you don't know what you're doing: better keep your hands off!!!

IMPORTANT NOTICE

The old web service at cfg.ebusd.eu (https and http) is at its end of life and will be shutdown soon (likely end of 2024).

If you want to continue using web based configuration files, you need to

  • move to ebusd version >= 24.1, or
  • use local CSV files from here (old frozen version kept for convenience), or
  • use local CSV files from the new CDN repository (can also be cloned for local use, see below)

Usage with ebusd

For many years, the CSV file based definitions served a great purpose, the last published version of which are still kept for convenience in the ebusd-2.1.x folder.

However, the CSV files are hard to read and understand and as such, there is a new approach of working with eBUS message defintions.

That's why the CSV files were relieved by TypeSpec files that reside in the src folder.

These files are way easier to maintain and understand, especially when it comes to applying corrections or enhancements.

See the guidelines for further reading.

Using the CDN

For use with ebusd, the TypeSpec files are converted back to CSV by using the eBUS TypeSpec library which was developed explicitly for this purpose.

The CSV output is made available via github CDN on https://ebus.github.io/ and this is used as the default definition source since ebusd version 24.1.

The CDN repository can also be cloned for local use by using the "--configpath" option to point to the desired language folder.

Using the TypeSpec sources locally

When working on message definitions, the easiest way is to use the eBUS TypeSpec library for conversion, or even better the VS Code extension "ebus notebook".

Scan mechanism

As a central heating system usually consist of several components, there is a dedicated file for each of those and maybe even for different hardware/software versions of it.

This is reflected by the file name as well as conditional messages within a file.

For each seen device on the bus, ebusd will pick the best suiting file from the manufacturer subdirectory after reading the device's identification. See also the ebusd scan documentation for details.

The file is then picked like this:

  • manufacturer subdirectory
  • target address: two hex digits prefix of the CSV file name
  • ID part: converted to lower case, trimmed (leading/trailing spaces removed as well as up to two trailing "0" digits), remaining spaces replaced by underscore
  • optional component type suffix, see below
  • optional software and/or hardware version suffix (e.g. ".HWvvvv" or ".SWvvvv").
  • extension: .csv

So, e.g. for the scan result
08;Vaillant;EHP00;0327;7201
which is

  • target address: 0x08
  • manufacturer 0xB5: "Vaillant"
  • device id: "EHP00"
  • software version: "03.27"
  • hardware version "72.01"

ebusd will load the file src/vaillant/08.ehp.tsp indirectly using e.g. the english variant converted CSV from the CDN repository served from https://ebus.github.io/en/vaillant/08.ehp.csv.

Some devices share the same prefix (e.g. "ehp.*"). This is due to the fact that the same physical unit can contain several logical circuits.

Component type names

In the configuration files, some of the following component type names (circuits) are used frequently:

  • bc: burner circuit
  • hc: heating circuit
  • mc: mixer circuit
  • hwc: hot water circuit
  • cc: circulation circuit
  • sc: solar circuit

These are sometimes also used as suffix in filenames (e.g. 23.ehp.cc.tsp) in order to note the component type as replacement for the device identifier not revealing the type in the first place.

For a single heating installation, a component type may be present in several instances (e.g. two mixers). In case these share the exact same message definitions (besides a different target address), this is reflected here as symbolic link to the main definition file.

Mixers and room controllers usually are available for more than one heating circuit. If so, these files are available multiple times with the heating circuit number appended, e.g. "mc2.4.tsp" for heating circuit 4. For the primary heating circuit the number is not appended, though.

Contact

The author can be contacted at ebusd@ebusd.eu .