...

Starting from Firmware 16.XX the beroNet Gateways and Cards have a single XML File file for the functions:

• Backup
• Restore
• Provisioning

In older firmwares the backup constisted consisted of a .tar.gz package of several configuration files. These files are still the same, but encoded into a simple XML file. 

This method allows it to handle provsioning provisioning more easy, because a single request provides the whole gateway configuration. 

File Format

The File file is structured as follows:

<?xml version="1.0"?>
<beroNetProvisioning>
	<!-- Created on 2016-09-16T02:43:00-06:00 -->
	<Config>
		<Update>yes</Update>
		<File>
			<Name>$FILENAME-1$</Name>
			<Contents>
$FILECONTENT-1$
			</Contents>
		    <Config>
        <Update>[yes|no]</Update>
        <File>
            <Name>FILENAME</Name>
            <Contents>
FILE-CONTENTS
            </Contents>
        </File>
    </Config>
   ... <Firmware>
       <File>
			<Name>$FILENAME-N$</Name>
			<Contents>
$FILECONTENT-N$
			</Contents>
		</File>
	</Config>
</beroNetProvisioning>
 <Install>[yes|no]</Install>
        <Filename>FIRMWARE.[tar.gz|fw]</Filename>
		<Url>https://second-provisioning-server.url/ANOTHER-FIRMWARE.[tar.gz|fw]</Url>
    </Firmware>
</beroNetProvisioning>

As you can see the XML-Format is simply mostly a container for configuration files with a <name> and a <content> tag. There are some special tags:

• <update>  - defines if the file should be used in a device that receives it via provisioning.
• <Firmware> - defines a firmware that can be installed and if this firmware should be installed

Please Note:

The <Url> flag in the <Firmware> section is optional and only available since the 21.03 firmware. It offers the possibility to download the firmware to a second webserver using https://second-provisioning-server.url/ANOTHER-FIRMWARE.[tar.gz|fw] as Provisioning-URL. When set, it replaces the <Filename> flag. (HTTP of HTTPS protocol can be used).

All current config-files for the 16.XX firmware are: