Backing up heating system parameters

Attention: This is method may corrupt your heating system, please read these instructions carefully!

BSB-LAN provides the URL-command /JB with which you can download a complete JSON structure of all the writeable parameters of your heating system (it doesn't make sense to dump read-only parameters because you can't write them back. Use URL-command /0-11000 if you want an overview of all parameters in your system).
Therefore, in order to store all parameters, you may use curl to download and store your system's status in a file named backup.json:
curl 'http://bsb-lan.local/JB' --output backup.json

To restore these settings at any point, you can then use BSB-LAN's /JS URL-command to set parameters based on a JSON structure (the same that /JB sends you). Again, we use curl for that purpose and store the return status in the file restore.json:
curl -X POST -d @backup.json 'http://bsb-lan.local/JS' --output restore.json

You can then check the result in restore.json. A status of 1 means that the parameter was successfully written, 0 means that there was an error. This doesn't necessarily have to be a problem and sometimes happens with "disabled" parameters (with a ---). But it's worth checking the parameters in question.

If you have more than one device in your heating system (for example in an LPB setup), you can download the backup for each device by calling /JB!<x> where <x> is the device ID of the device you want to download from. So /JB!1 would download the backup from device ID 1 (LPB address 00:02). The device ID is stored in the JSON structure, so in order to restore the backup, you can always use the same command as stated above.

Attention: The parameters are restored in numerical order. However, some parameters are only becoming active if another parameter has been set accordingly. If these parameters are not in the required numerical order, this might result in undefined or even unintended configurations. It is therefore advisable to check if all parameters have been set correctly. This can be done by downloading another backup via /JB and compare it with the first one and then investigate any differences.
In any case, you are doing this on your own risk!