Skip to content

pvyleta/ebusd-brink-hru

Repository files navigation

ebusd-brink-hru

Collection of Brink HRU configuration files for ebusd

The configuration files were created by parsing the Brink Service Tool decompiled through JetBrains DotPeak. The decompiled source code is not distributed in this repo for it likely being a violation of the license agreement, though decompiling SW with the intention of interfacing to it can be considered legal. This is also a reason why parsing the code through independent python script was used, rather than re-using portions of the decompiled source code in a new C# binary.

For few parameters, other sources than the decompiled Brink Service Tool was used, such as datasheets, random internet forums etc. This is always noted in the source code, or even in the produced files.

Supported devices

Currently, the ebusd-configuration for these heat recovery units is present:

  • Brink CWLF250
  • Brink CWLF350
  • Brink CWLTower300
  • Brink ConstantRPM400
  • Brink DecentralAir70
  • Brink Elan10
  • Brink Elan4
  • Brink Renovent Excellent180
  • Brink Renovent Excellent300
  • Brink Renovent Excellent400
  • Brink Renovent Excellent450
  • Brink Flair200
  • Brink Flair225
  • Brink Flair300
  • Brink Flair325
  • Brink Flair400
  • Brink Flair450
  • Brink Flair600
  • Brink MultiRoomCtrlT01
  • Brink Nather300
  • Brink RenoventElan300
  • Brink Renovent Sky150
  • Brink Renovent Sky200
  • Brink Renovent Sky300
  • Brink ValveT01
  • Viessmann Vitovent200W
  • Viessmann Vitovent300C
  • Viessmann Vitovent300W300
  • Viessmann Vitovent300W400
  • Viessmann Vitovent300WH32SA225
  • Viessmann Vitovent300WH32SA600
  • Viessmann Vitovent300WH32SC400
  • Viessmann Vitovent300WH32SC325

Note, that Brink devices are re-branded as Viessmann, Wolf, VisionAIR, Ubbink and maybe others, os these configuration files are (mostly) applicable for those as well.

repo structure

ebusd-configuration-known-slave-address

If you find your device in this folder, you may consider yourself lucky - there can be used verbatim in ebusd. The files contain parameters for the latest SW version, for the 'Plus' variant of the HRU unit, so not all parameters might be applicable for your device. If you want a .csv file that matches your device perfectly, you need to look into ebusd-configuration-unknown-slave-address

All files are provided with language mutations for English, German, French, Italian, Spanish, Dutch and Polish in the respective subdirectories.

ebusd-configuration-unknown-slave-address

This folder contains all known Brink devices in all known SW versions and basic/plus variants of HW.

All files are provided with language mutations for English, German, French, Italian, Spanish, Dutch and Polish in the respective subdirectories.

The naming format is [device].[first_sw_version].[last_sw_version].[plus].csv (Files for basic devices, or for devices that does not even have a 'plus' variant have no 'plus' suffix)

The use is simple:

  1. Find out your device type and SW version (e.g. from the wall controller) and pick the appropriate file.
  2. Figure out the slave address of your device (can be easily found from ebusd logs - Brink devices respond as manufacturer ENCON to the 0704 id scan message, which might help you to find it)
  3. Rename the file to that address (in hexa, e.g. 3c.csv)
  4. In the file, replace [fill_your_slave_address_here] with slave address of your device, (e.g. '3c')
  5. Now you can use the file in ebusd

ebusd-mqtt

Contains useful adaptation of the mqtt-hassio.cfg file from the ebus repo, that is suitable for controlling Brink HRUs. The original is aimed mostly at water heaters and not ventilation units, so it was extended.

ebusd-scan

This is work-in-progress. The hope is, that we would be able to automate the selection of right file in ebusd through properly scanning various fields in this file, however, after several tries, this looks like way more difficult thing to achieve, than originally thought.

src

Contains the python scripts used to parse the decompiled Brink Service Tool. They are not exactly pretty, but they do the jobs and they contain reasonable number of sanity checks. The scripts are expected to be run from the root repo directory, i.e. python .\src\main.py

BCSServiceTool

This folder is expected to be filled in with the decompiled binary.

The version of tool used and tested with the parsing scripts is 'S1_04_11_0002'

dump

Contains dump of the parsed data in fairly re-usable JSON and CSV formats. if you plan to integrate Brink HRUs in other software than ebusd, this is the place to go.

Future work

  • structure config files better with using !include instructions and conditions
  • find out slave IDs for more Brink HRUs

About

Collection of Brink HRU configuration files for ebusd

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages