Back to TOC
Back to chapter 1

2. BSB-LAN: The Software

In the following chapters the installation and the configuration of the BSB-LAN software is described. A description of the web interface, however, can be found in chap. 4, a description of the query and control options in chap. 5 and a description of the special functions in chap. 6.

2.1 Installation

The BSB-LAN software must be flashed to the used microcontroller (Arduino Due or ESP32) for installation. This can be done e.g. with the “Arduino IDE”, but of course other programs like “PlatformIO” or “Visual Studio Code” can be used as well.

Note
In this manual it is assumed that the Arduino IDE is used. All descriptions and terms therefore refer to the Arduino IDE.
If you are a beginner and not yet familiar with the Arduino IDE, you will find a description of how to install and configure the Arduino IDE in chap. 12.

Depending on the used platform (Arduino Due or ESP32) the necessary settings of the Arduino IDE differ. Thus the appropriate board types must be installed and selected, the settings must be adapted platform-specifically etc. These settings will be mentioned in the following. It is assumed that the necessary libraries for the respective platform are already installed. If this is not the case, then you find information for this in chap. 12.
Beyond that there are still further things to consider with the installation on the ESP32, which are likewise treated in the appropriate chapter.

2.1.1 Installation onto the Due

The following describes the installation of the BSB-LAN software on an Arduino Due. The description refers to the use of the Arduino IDE. With the default settings of the BSB-LAN software DHCP is used for the IP address assignment. If you don’t want this and want to assign a fixed IP, please read chap. 2.2.2 and adapt the file BSB_LAN_config.h before flashing!

Note
If you are using Windows, an additional driver installation may be necessary. See the page https://www.arduino.cc/en/Guide/ArduinoDue for further informations.

It is advisable to proceed with the following steps:

  1. Connect the Arduino setup with a USB cable to your computer. Use the ‘Programming Port’ of the Due, which is the USB port in the ‘middle’, placed next to the power supply socket. Both the LAN shield and the BSB-LAN adapter should already be plugged onto the Due beforehand, but this is not mandatory.

    Setup

    *The complete setup (Arduino Due + LAN-Shield + BSB-LPB-LAN-Adapter v3) including the corresponding cables.

  2. Download the current BSB-LAN version and unzip the downloaded file BSB-LAN-master.zip.

  3. Enter the folder “BSB-LAN-master”/”BSB_LAN” and rename the file BSB_LAN_custom_defs.h.default to BSB_LAN_custom_defs.h and BSB_LAN_config.h.default to BSB_LAN_config.h!

  4. Open the BSB_LAN sketch by double clicking on the file BSB_LAN.ino in the BSB_LAN folder. The corresponding files BSB_LAN_config.h, BSB_LAN_custom_defs.h and BSB_LAN_defs.h are loaded automatically.

  5. Select “Arduino Due (Programming Port)” under “Tools/Board”.

    Note
    If the board is not listed, you have to add the Atmel SAM Core. Information about this can be found in chap. 12.

  6. Select the correct serial port where the Due is connected to the computer under “Tools/Port”.

    Settings Due

    The settings for the Due in the Arduino IDE.

  7. If you want to configure BSB-LAN by customizing the file BSB_LAN_config.h (see chap. 2.2.2), please do so now.

  8. Start the flash process and upload the sketch to the Arduino Due by clicking on “Sketch/Upload”.

  9. After finishing the flash process start the serial monitor of the Arduino IDE and watch the outputs which are generated when starting the Arduino Due. Among other things, the IP that is assigned to the setup when using DHCP will be diplayed there.

Congratulations - you have installed BSB-LAN!
Now proceed with configuring the BSB-LAN software and the connection and startup of the setup.

Important Note
In order to gain access to all of the parameters your controller offers, a controller specific file BSB_LAN_custom_defs.h must be created. Afterwards BSB-LAN must be reinstalled with this new file. Therefore please read the chap. 3.3 and perform the steps mentioned there!

2.1.2 Installation onto the ESP32

In the following the installation of the BSB-LAN software on an ESP32 is described. The description refers to the use of the Arduino IDE. With the default settings of the BSB-LAN software DHCP is used for the IP address assignment. If you don’t want this and want to assign a fixed IP, please read chap. 2.2.2 and adapt the file BSB_LAN_config.h before flashing!

Note
If the ESP32 board is not recognized by your operating system, you may need to install an additional driver for the USB chip used by the board.

It is advisable to proceed with the following steps:

  1. Connect your ESP32 board with a USB cable to your computer. You may have already plugged the BSB-LAN adapter on or under your ESP32 board, but this is not mandatory.

  2. Download the current BSB-LAN version and unpack the downloaded file BSB-LAN-master.zip.

  3. Enter the folder “BSB-LAN-master”/”BSB_LAN” and rename the files BSB_LAN_custom_defs.h.default to BSB_LAN_custom_defs.h and BSB_LAN_config.h.default to BSB_LAN_config.h!

  4. Open the BSB_LAN sketch by double clicking on the file BSB_LAN.ino in the BSB_LAN folder. The corresponding files BSB_LAN_config.h, BSB_LAN_custom_defs.h and BSB_LAN_defs.h are loaded automatically.

  5. Select the corresponding ESP32 board type under “Tools/Board”:

    • For the Joy-It ESP32-NodeMCU (or identical clones with an “ESP32-WROOM” chip) recommended in this manual the appropriate board type is “ESP32 Dev Module”.

    • For the recommended Olimex ESP32-EVB & ESP32-PoE please select the entry with the same name from the list.

    Notes
    If the ESP32 framework is already installed and you see the different ESP32 board variants, please check in the “Board Manager” under “Tools/Boards” that version 2.0.2 (or higher, if available) is installed.
    If the board is not listed, the ESP32 platform must be added in the Arduino IDE. Information about this can be found in Chapter 12.1.2.

  6. Select the correct serial port, where the ESP32 board is connected to the computer, under “Tools/Port”.

  7. Set the transfer speed/baudrate to 115200 (Attention: In the Arduino IDE usually 921600 is preset for ESP32 boards!)

  8. “Partition Scheme”: depending on the type of board, you need to choose the specific partition scheme.

    • For the recommended ESP32-NodeMCU please choose “Default 4MB with spiffs (1.2BM APP/1.5MB SPIFFS)”.
      The following screenshot shows the configuration for the ESP32-NodeMCU.

      Settings ESP32

      The settings for the ESP32 NodeMCU in the Arduino IDE.

    • For the recommended Olimex boards select the variant “Minimal SPIFFS (Large APPS with OTA)”.

  9. Now click on the tab for the file BSB_LAN_config.h and adjust necessarily the following settings:

    • Activate the definition #define WIFI in the file BSB_LAN_config.h if you want to use WiFi. If you are using an Olimex board and want to use LAN, please leave the definement deactivated: //#define WIFI.

    • If you want to use WiFi, enter the access data for your WiFi network at the entries
      char wifi_ssid[32] = "YourWiFiNetwork"; and
      char wifi_pass[64] = "YourWiFiPassword";.

  10. If you want to configure BSB-LAN by adapting the file BSB_LAN_config.h (see chap. 2.2.2), please do this now.

  11. Start the flash process and upload the sketch to the Arduino Due by clicking on “Sketch/Upload”.

After finishing the flash process, start the serial monitor of the Arduino IDE and observe the outputs that occur when the ESP32 is started. Among other things, the IP that is assigned to the setup when using DHCP will be displayed there.

Notes
If the ESP32 cannot connect to the configured WLAN, it will set up its own access point “BSB-LAN” with the password “BSB-LPB-PPS-LAN” for 30 minutes. After that, it will reboot and try again to connect to the configured WLAN network.
Although the logging feature also works with the ESP32, it is not recommended to overuse this feature due to wear and tear of the flash memory. If the Olimex board is to be used, a microSD card can be used instead of the SPIFF flash memory. The usage has to be activated in the file BSB_LAN_config.h.

Congratulations - you have installed BSB-LAN!
Now proceed with configuring the BSB-LAN software and the connection and startup of the setup.

Important Note
In order to gain access to all of the parameters your controller offers, a controller specific file BSB_LAN_custom_defs.h must be created. Afterwards BSB-LAN must be reinstalled with this new file. Therefore please read the chap. 3.3 and perform the steps mentioned there!

2.1.3 Updates

Updating the BSB-LAN software is done by the usual flashing of the new version (download as ZIP file, via git or similar), as described in the previous installation chapters. Please pay attention to the following notes!

For ESP32 based boards (Olimex, NodeMCU) an OTA update (“OverTheAir” update) can be done alternatively (this function is NOT usable with the Arduino DUE!). For this, the corresponding OTA function must be activated in the web config or the file BSB_LAN_config.h. The belonging firmware file BSB_LAN_ino.bin can be created in the Arduino IDE under “Sketch / Export compiled binary file…”. The file has to be uploaded via browser to port 8080 of the BSB-LAN IP (http://<BSB-LAN-IP>:8080 or http://bsb-lan:8080 with activated MDNS).

Notes
When updating to v3.x please do not use any existing files - please install BSB-LAN completely new!
Also note the necessary creation of a controller specific BSB_LAN_custom_defs.h - the procedure is described in chap. 3.3.
If you have made certain changes in the file BSB_LAN_config.h for the new version to be flashed, e.g. the access data for your WLAN or a fixed IP, which were apparently not accepted after flashing, this is usually due to the fact that the old settings were read from the EEPROM.
To make the new settings effective, set the setting “Read configuration from EEPROM” in the Web configuration once to “Off”, save the change and flash again.
After that the new settings should have become effective, because BSB-LAN has now read them from the file BSB_LAN_config.h and not from the EEPROM.
After successful check set “Read configuration from EEPROM” again to “On”.
The existing and (if necessary) adapted file BSB_LAN_config.h can usually be taken over when updating to a newer version, but it is advisable to use the current file BSB_LAN_config.h.default instead of the existing file BSB_LAN_config.h. To do this, the file BSB_LAN_config.h.default must be renamed as before and, if necessary, adapted to the previous settings. This way you can be sure that you have made a complete update of the BSB-LAN software.
If the adapter is connected to the bus of the heating controller, it can remain connected if the Due/ESP32 is to be flashed again. There is no need to disconnect the adapter from the controller when updating BSB-LAN.
If you enable the function “check for updates” within the config, newer versions of BSB-LAN will be mentioned at the start page of the webinterface. This includes development versions also though (and not only ‘stable’ releases) - so if you only want to use a ‘stable’ release, you have to check for that manually at the project page.

2.2 Configuration

The BSB-LAN software can be configured according to individual requirements. The configuration can be done in two ways: by adapting the BSB_LAN_config.h file and via the web interface. The configuration options are explained in more detail below. The descriptions in chapter 2.2.2 are generally more detailed, so it makes sense to study both chapters in detail.

2.2.1 Configuration via Webinterface

The settings overview or the web configuration interface is in principle self-explanatory, nevertheless the individual points are listed here again with a short explanation.
For a more detailed explanation of the individual functions, please refer to chap. 2.2.2.

The overview of the web configuration is divided into three columns:

Webconfig

Important
To apply changed settings, you must finally click on the button “Save parameter” at the bottom!

In the following, the tabular overview of the functions with the (default) settings and the corresponding explanations (unfortunately, the naming of the left column “Category” must be omitted here for reasons of space and presentation):

Function (default) Setting Explanation
Display extended configuration Off Displays the advanced settings of BSB-LAN (Off/On). For accessing all setting options of BSB-LAN “On” must be selected (and then click on “Save parameters” below).
Read config from EEPROM On Reads the stored configuration from the EEPROM when starting the Due (Off/On).
These settings can deviate from the default settings, which were made in the file BSB_lan_config.h.
If the settings stored in the EEPROM should be overwritten, e.g. during an update, set to “Off” and save the setting before flashing!
If the setting is “Off”, changes will only remain active until the Due is restarted.
Write access (level) Off Write access of the adapter to the heating controller (Off/Standard/Complete).
If write access to the heating controller should be granted, it is recommended to select the ‘Standard’ setting, in which case almost all available parameters can be written. In contrast to ‘Complete’, however, some function-critical parameters cannot be changed, as they are protected again inside the controller.
The setting ‘Complete’ should therefore only be selected in exceptional cases and with caution and a very good knowledge of the controller functionality!
Check for updates Off Automatically check for updates of BSB-LAN (Off/On)
OTA Update Off OTA update function (OTA = Over The Air) deactivated (Off) / activated (On).
For the further procedure for OTA updates please read chap. 2.1.3 Updates.
RX pin number 0 0 = autoselect. If another pin than the preset RX pin (see file BSB_LAN_config.h) is used, it must be entered here.
TX pin number 0 0 = autoselect. If another pin than the preset TX pin (see file BSB_LAN_config.h) is used, it must be entered here.
Type BSB Used bustype (BSB/LPB/PPS)
Own address 66 Own address of the adapter
Destination address 0 Destination address for queries
PPS: PPS mode passive PPS only: Users who use the adapter on the PPS interface must make two settings: First, the mode in which the bus is to be accessed (passive/as room unit) must be selected. When using a QAA room device, “passive” must be selected here. Then only the values that go via the bus are displayed in the web interface, writing of values is then not possible.
If “as room unit” is selected here, values can also be sent to the heating system via the web interface. The type of the room device to be emulated must then still be selected (see below). There should then be no other room device on the bus, otherwise both transmitters send their own values to the heater, so that no consistent operation is possible.
PPS: QAA model QAA70 PPS only: Type of the room unit that should be imitated (QAA50/QAA70).
Device family 0 0 = automatic controller recognition active (recommended setting). In case of a faulty detection, the device family (output of /6225) of the connected controller can be set here.
Device variant 0 0 = automatic controller recognition active (recommended setting). In case of a faulty detection, the device variant (output of /6226) of the connected controller can be set here.
URL Passkey -no default setting- Optional security function: “URL Passkey”
HTTP authentification -no default setting- Optional security function: “User-Pass” (Basic HTTP Auth). Syntax: Username:Password
DHCP usage On DHCP usage (= automatic allocation of the IP address by the router) (Off/On)
IP address (fixed) 192.168.178.88 Manual network configuration: fixed IP address
Subnet 255.255.255.0 Manual network configuration: Subnet
Gateway 192.168.178.1 Manual network configuration: IP address of the gateway
DNS Server 192.168.178.1 Manual network configuration: IP address of the DNS server
TCP Port 80 TCP port of the setup
MAC address 00:80:41:19:69:90 (Preset) MAC address of the LAN shield or MAC address of the ESP
Trusted IP address 0.0.0.0 Optional security function: “Trusted IP”, access is only possible from this IP
Trusted IP address 0.0.0.0 Optional security function: “Trusted IP”, access is only possible from this IP
WLAN SSID -no default setting- SSID of the WLAN when using the WiFi-ESP-solution
WLAN password -no default setting- Password of the WLAN when using the WiFi-ESP-solution
mDNS Hostname BSB-LAN Hostname
Logging mode -no default setting- Different options for the logging mode (multiple options possible): Write to SD card / Calculate 24h averages / Send to MQTT broker / Send to UDP
Interval (seconds) 3600 Loginterval in seconds
Parameters 8700,8743,8314 Parameters to be logged
Bus telegrams Off Logging of bus telegrams activated (Off/-various options-), the desired setting is to be made according to the respective option description.
Parameter 8700,8326 Parameters for the 24h average calculation
Usage Plain Text Plain Text / JSON / Rich JSON
IP address broker 192.168.178.20 IP-Adresse des MQTT-Brokers
Username User MQTT: Username when using username/password
Password Pass MQTT: Passwort when using username/password
Device ID BSB-LAN Device name (header in JSON payload)
Topic prefix BSB-LAN Topic prefix of the MQTT messages
Pins 0 Used pin(s) for OneWire sensors (DS18B20) (0 = deactivated)
Pins 0 Used pin(s) for DHT22 sensors (0 = deactivated)
Sensoren 0 Amount of connected BME280 sensors
DHW push button: pin 0 Room unit emulation: used pin for the DHW push
RU1 temperature sensor parameter -no default setting- Room unit 1 emulation: enter the specific parameter number(s) for the optional room temperature sensor(s) here. Up to five sensors are possible, parameter numbers must be separated only with a comma. If more than one sensor is used, an automatic average will be calculated.
RU1 presence button: pin 0 Room unit 1 emulation: used pin for the presence button for HC1
RU2 temperature sensor parameter -no default setting- Room unit 2 emulation: enter the specific parameter number(s) for the optional room temperature sensor(s) here. Up to five sensors are possible, parameter numbers must be separated only with a comma. If more than one sensor is used, an automatic average will be calculated.
RU2 presence button: pin 0 Room unit 2 emulation: used pin for the presence button for HC2
RU3 temperature sensor parameter -no default setting- Room unit 3 emulation: enter the specific parameter number(s) for the optional room temperature sensor(s) here. Up to five sensors are possible, parameter numbers must be separated only with a comma. If more than one sensor is used, an automatic average will be calculated.
RU3 presence button: pin 0 Room unit 3 emulation: used pin for the presence button for HC3
Usage Off Use MAX! devices (Off/On)
IP address cube 192.168.178.5 IP address of the CUNO/CUNX/modified MAX!Cube
Devices KEQ0502326,KEQ0505080 Serial numbers of the MAX! devices to be used
Usage Off Use IPWE extension (URL/ipwe.cgi) (Off/On)
Parameters 8700,8743,8314 Parameters that should be displayed within the IPWE extension
Usage Serial Use debug function (Off/Serial/Telnet)
Verbosity mode On Verbosity mode activated (Off/On)
Monitor mode Off Monitor mode activated (Off/On)
Display unknown parameters On Displays unknown / not supportet parameters (“error 7 - parameter not supportet”)-(On/Off).

2.2.2 Configuration by Adjusting the Settings Within BSB_LAN_config.h

The BSB-LAN software can be configured by adjusting the settings in the file BSB_LAN_config.h. All settings are listed below in the same way as they are listed and preset in the file. It is therefore advisable to work through the settings point by point with this manual at hand.

Note
To ‘activate’ or a definement you have to delete the two slashes in front of the hashtag, to ‘deactivate’ a definement you have to add two slashes in front of the hashtag. E.g.:
A deactivated definement: //#define XYZ
An activated definement: #define XYZ

Network settings:

Note
By default, the usage of DHCP is activated, so you don’t have to change any network settings. If you want to use a fixed IP though, deactivate DHCP and set the IP and the addresses of the Gateway and the Subnet accordingly.

Security functions:

There are several options to control and protect access to your heating system. However, keep in mind, that even activating all three options are no guarantee that a versatile intruder with access to your (W)LAN won’t be able to gain access. In any case, no encryption of data streams is provided by the Arduino itself. Use VPN or a SSL proxy if that is a must for you and connect the Arduino wired to the VPN server or SSL proxy.
The following three security options are available within BSB-LAN:

Settings for optional sensors:

Settings of the bus pins and bus type:

2.3 Adding Parameters Manually From v2.2

Compared to previous versions of BSB-LAN, you may notice that some parameters now no longer appear in the device-specific parameter list, even if they seemed to work fine in previous versions.
However, it is still possible to include selected parameters from the parameter list of version 2.2 in the current version.

Note
We strongly recommend to add these parameters, which are not officially supported by the controller manufacturer, only after a thorough check, especially if these values should also be written!
As a safe number range in which parameters can be added as described below, we recommend 10600 and warm up.

The first step is to download the Release version 2.2 at https://github.com/fredlcore/BSB-LAN/releases.
After unpacking the file, you will find the file BSB_LAN_custom_defs.h.default in the subdirectory BSB_LAN. Open this file with a text editor like Notepad under Windows or TextEdit under MacOS.
In parallel you also open the file BSB_LAN_custom_defs.h from the current BSB-LAN version you want to use in the Arduino IDE.
When both files are open, look for the parameter number of the parameter you want to add in the BSB_LAN_custom_defs.h.default of version 2.2.

The further steps are explained using the example of the former parameter 701 “Presence button (temporary absence)”. This parameter is now included by default in the device-specific BSB_LAN_custom_defs.h file; it is only missing in the first files created (during the conversion phase to BSB LAN version 3.x at that time).

Searching for “701” first results in this entry:
const char STR701[] PROGMEM = STR701_TEXT;
Copy this line to the clipboard.
In the file BSB_LAN_custom.defs.h of the current BSB-LAN version you now search for the text const char S and find a number of such entries. There you insert the above selected line at any position.

If no entry starting with const char is found for a parameter, but an entry corresponding to the pattern #define STR<searched parameter number> STR<referenced parameter number>, two steps are necessary:
First you copy the line #define STR... into the current BSB_LAN_custom_defs.h file and then you search in the BSB_LAN_custom_defs.h.default for the referenced parameter number until you find the line for this number that starts with const char S.
Using the parameter number 702 as an example, this line would therefore be found first: #define STR702 STR701.
Then you search again for the referenced parameter number (in this case 701), so when you search again for this parameter number you would then find the line const char STR701[] PROGMEM = STR701_TEXT; which you would then copy as well.
It is important that the #define line must be below the const char S... line!
So the result would look like this for parameter 702:

const char STR701[] PROGMEM = STR701_TEXT;
#define STR702 STR701

All other entries where the parameter number is possibly in the position of the referenced parameter in #define lines (like #define STR1301 STR701) can be ignored - unless you want to add the parameter number 1301 as well in this case.

Since the parameter 701 is a parameter with selection options, there are also lines starting with #define ENUM701_.... These lines must also be copied into the current BSB_LAN_custom_defs.h.
In this context another entry appears, which starts with const char ENUM701[]. This and the following lines must also be copied to the current BSB_LAN_custom_defs.h up to the closing curly bracket:

const char ENUM701[] PROGMEM_LATEST = {
"\x00 " ENUM701_00_TEXT "\0"
"\x01 " ENUM701_01_TEXT "\0"
"\x02 " ENUM701_02_TEXT
};

For purely numeric parameters, which have no selection menu, but e.g. only display a temperature value, this step is omitted, because there is then no const char ENUM... entry for this.

Finally, we find the actual table entry for parameter 701, which looks like this:
{0x2D3D0572, VT_ENUM, 701, STR701, sizeof(ENUM701), ENUM701, DEFAULT_FLAG+FL_WONLY, DEV_ALL},.
The corresponding table can be found in the current BSB_LAN_custom_defs.h file at the end of the file. In the third column you always see the parameter number. Now you go up in this file so far that the parameter is inserted at the correct place. In our example this would be after the line for parameter 700.

Attention
It is absolutely important to make sure that the parameter is inserted at the right place (and not e.g. before the line for parameter 700 or somewhere after), because otherwise the parameters will not be listed completely in the category overview!

For some controllers, however, parameter 701 will already be occupied by another function. Newer LMS controllers have stored there e.g. the function for “temporarily warmer/cooler”. However, relocating the new parameter to be added is simple: Select a free parameter number (apart from the “presence button” function mentioned here, we recommend parameter numbers 10600 and upwards for this purpose) and add the line
{0x2D3D0572, VT_ENUM, 701, STR701, sizeof(ENUM701), ENUM701, DEFAULT_FLAG+FL_WONLY, DEV_ALL},
at the appropriate place in the file. Then you only need to change the parameter number in the third column, e.g. to 10600. The parameter numbers entered for STR... or ENUM... can, however, remain as they are, since they were chosen in such a way that they do not collide with the new parameters.
The new, final line would then look like this:
{0x2D3D0572, VT_ENUM, 10110, STR701, sizeof(ENUM701), ENUM701, DEFAULT_FLAG+FL_WONLY, DEV_ALL},

Summarized once again the lines that would have to be copied for the function “Presence key (temporary absence)” to be inserted in the current version as parameter number 10600:.

const char STR701[] PROGMEM = STR701_TEXT;
const char ENUM701[] PROGMEM_LATEST = {.
"\x00 " ENUM701_00_TEXT "\0"
"\x01 " ENUM701_01_TEXT "\0"
"\x02 " ENUM701_02_TEXT
};

And the following line at the correct place:
{0x2D3D0572, VT_ENUM, 10110, STR701, sizeof(ENUM701), ENUM701, DEFAULT_FLAG+FL_WONLY, DEV_ALL},

After that BSB-LAN can be flashed to the microcontroller again and the new command is ready for use.

If you want to change the somewhat unspecific parameter name “presence button (temporary absence)” to e.g. the more appropriate name “Time program (temporary)”, you can do this in the same step. To do this, you would simply change the line
const char STR701[] PROGMEM = STR701_TEXT;
to
const char STR701[] PROGMEM = "Time program (temporary)";
and then flash again. Since all these changes are made in BSB_LAN_custom_defs.h, they are retained even if the BSB LAN software is updated.

If you also want to add the presence button for HC2 (which was 1001 in the v.2.2) as parameter 10111, then the belonging lines would look like this:
#define STR1001 STR701
and this line at the correct place of the cmdtbl-structure:
{0x2E3E0572, VT_ENUM, 10111, STR1001, sizeof(ENUM701), ENUM701, DEFAULT_FLAG+FL_WONLY, DEV_ALL}, // [-] - Heizkreis 2 - Präsenztaste (Absenkmodus bis zum nächsten BA-Wechsel laut Zeitplan) ***(virtuelle Zeile)***

Parameters that might be of interest and the lines to copy for them
1602 – DHW State
const char STR1602[] PROGMEM = STR1602_TEXT;
const char ENUM1602[] PROGMEM_LATEST = {
"\x00\x02 " ENUM1602_00_02_TEXT "\0"
"\x02\x02 " ENUM1602_02_02_TEXT "\0"
"\x00\x04 " ENUM1602_00_04_TEXT "\0"
"\x04\x04 " ENUM1602_04_04_TEXT "\0"
"\x00\x08 " ENUM1602_00_08_TEXT "\0"
"\x08\x08 " ENUM1602_08_08_TEXT <br> };
And this line at the correct place of the cmdtbl-structure:
{0x31000212, VT_BIT, 1602, STR1602, sizeof(ENUM1602), ENUM1602, DEFAULT_FLAG, DEV_ALL}, // Status Trinkwasserbereitung
10100 – Burnerstate
#define ENUM10100_01_TEXT ENUM_CAT_34_TEXT
const char ENUM10100[] PROGMEM_LATEST = {
"\x00" // index for payload byte
"\x01\x01 " ENUM10100_01_TEXT "\0"
"\x02\x02 " ENUM10100_02_TEXT "\0"
"\x04\x04 " ENUM10100_04_TEXT "\0"
"\x08\x08 " ENUM10100_08_TEXT "\0"
"\x10\x10 " ENUM10100_10_TEXT "\0"
"\x20\x20 " ENUM10100_20_TEXT "\0"
"\x40\x40 " ENUM10100_40_TEXT "\0"
"\x80\x80 " ENUM10100_80_TEXT
};
And this line at the correct place of the cmdtbl-structure:
{0x053D0213, VT_CUSTOM_BIT, 10100, STR10100, sizeof(ENUM10100), ENUM10100, FL_RONLY, DEV_ALL}, // INFO Brenner
10102 – Info HC1
{0x2D000211, VT_UNKNOWN, 10102, STR10102, 0, NULL, DEFAULT_FLAG, DEV_ALL}, // INFO HK1
10103 – Info HC2
{0x2E000211, VT_UNKNOWN, 10103, STR10103, 0, NULL, DEFAULT_FLAG, DEV_ALL}, // INFO HK2
10104 – Info HC3/P
{0x2F000211, VT_UNKNOWN, 10104, STR10104, 0, NULL, DEFAULT_FLAG, DEV_ALL}, // INFO HK3/P

ko-fi

Further on to chapter 3
Back to TOC