Deployed 7e8919f with MkDocs version: 1.6.0

CHANGELOG.html

@@ -399,6 +399,8 @@ <h2 id="current-master">Current Master</h2>
 <li><strong>ATTENTION: BREAKING CHANGE</strong> The acknowledgement message sent by BSB-LAN to the <code>MQTT</code> topic has been removed. Instead, QoS for publishing messages has been set to level 1.</li>
 <li><strong>ATTENTION: BREAKING CHANGE:</strong> Log configuration values have changed. However, only users that have logged to UDP are affected and will have to adjust their settings.</li>
 <li><strong>ATTENTION:</strong> <code>/JK=ALL</code> now lists all categories of all devices in LPB systems with more than one device. Use <code>dev_fam</code> (device family), <code>dev_var</code> (device variant), <code>dev_id</code> (destination device ID) and <code>dev_name</code> (device model) elements to sort and identify which category applies to the current destination device. </li>
+<li>Added new URL command /QDB - this queries the heating system for device-specific parameters and activates these until reboot. Categories do not apply, you have know the parameter numbers you want to query and access them directy (e.g. /0-9999).<br />
+This is not a replacement for generating a proper device-specific parameter list as it only contains few parameter types which we know for certain how they work and no harm can be done (mostly read-only status temperatures). However, these can be helpful for heating technicians which want to monitor on the spot the behavior of a random heating system without the need to create a device-specific parameter list. </li>
 <li>Added setting to only publish log parameters to MQTT. Forcing MQTT updates via /poll topic are still possible.</li>
 <li>Added state_class for non cumulative sensors in MQTT auto-discovery</li>
 <li>Updated the room unit emulation in <code>custom_functions</code> to work with version 4.x.</li>
@@ -422,9 +424,9 @@ <h2 id="version-41">Version 4.1</h2>
 <h2 id="version-40">Version 4.0</h2>
 <p><strong>01.11.2024</strong>  </p>
 <ul>
-<li><strong>ATTENTION: BREAKING CHANGE!</strong> Room temperature parameter 10000, 10001 and 10002 must now have the additional flag <code>FL_SPECIAL_INF</code>, otherwise setting temperature will not work!</li>
+<li><strong>ATTENTION: BREAKING CHANGE!</strong> Room temperature parameter 10000, 10001 and 10002 must now have the additional flag <code>FL_SPECIAL_INF</code>, otherwise setting temperature will not work! See <code>BSB_LAN_custom_defs.h.default</code> and search for <code>FL_SPECIAL_INF</code>to find the right line and use that as an example.</li>
 <li><strong>ATTENTION: BREAKING CHANGE!</strong> Outside temperature simulation parameter 10017 must have <code>FL_SPECIAL_INF</code> flag removed, otherwise setting temperature will not work!</li>
-<li><strong>ATTENTION: BREAKING CHANGE!</strong> Room temperature parameter 10000, 10001 and 10002 for Weishaupt heaters (device families 49, 50, 51 and 59) must now have <code>FL_SPECIAL_INF</code> flag removd, otherwise setting temperature will not work!</li>
+<li><strong>ATTENTION: BREAKING CHANGE!</strong> Room temperature parameter 10000, 10001 and 10002 for Weishaupt heaters (device families 49, 50, 51 and 59) must now have <code>FL_SPECIAL_INF</code> flag removed, otherwise setting temperature will not work!</li>
 <li><strong>ATTENTION: BREAKING CHANGE!</strong> URL commands <code>/U</code> (dislpay user-defined variables) and <code>/X</code> (display MAX! values) have been removed as these values can now be accessed via parameters 20000++</li>
 <li><strong>ATTENTION: BREAKING CHANGE!</strong> PPS time program parameters (15050-15091) have been streamlined with BSB/LPB time program parameters, resulting in only one parameter per day (instead of six), covering three switch points (start and end) per parameter.</li>
 <li><strong>ATTENTION:</strong> For ESP32, BSB-LAN requires ESP32 framework version 3.0.x - please look out for errors or strange behaviour (1-Wire sensors are still not tested) as well as any other kind of strange behaviour/crashes.</li>

de/CHANGELOG.html

@@ -399,6 +399,8 @@ <h2 id="current-master">Current Master</h2>
 <li><strong>ATTENTION: BREAKING CHANGE</strong> The acknowledgement message sent by BSB-LAN to the <code>MQTT</code> topic has been removed. Instead, QoS for publishing messages has been set to level 1.</li>
 <li><strong>ATTENTION: BREAKING CHANGE:</strong> Log configuration values have changed. However, only users that have logged to UDP are affected and will have to adjust their settings.</li>
 <li><strong>ATTENTION:</strong> <code>/JK=ALL</code> now lists all categories of all devices in LPB systems with more than one device. Use <code>dev_fam</code> (device family), <code>dev_var</code> (device variant), <code>dev_id</code> (destination device ID) and <code>dev_name</code> (device model) elements to sort and identify which category applies to the current destination device. </li>
+<li>Added new URL command /QDB - this queries the heating system for device-specific parameters and activates these until reboot. Categories do not apply, you have know the parameter numbers you want to query and access them directy (e.g. /0-9999).<br />
+This is not a replacement for generating a proper device-specific parameter list as it only contains few parameter types which we know for certain how they work and no harm can be done (mostly read-only status temperatures). However, these can be helpful for heating technicians which want to monitor on the spot the behavior of a random heating system without the need to create a device-specific parameter list. </li>
 <li>Added setting to only publish log parameters to MQTT. Forcing MQTT updates via /poll topic are still possible.</li>
 <li>Added state_class for non cumulative sensors in MQTT auto-discovery</li>
 <li>Updated the room unit emulation in <code>custom_functions</code> to work with version 4.x.</li>
@@ -422,9 +424,9 @@ <h2 id="version-41">Version 4.1</h2>
 <h2 id="version-40">Version 4.0</h2>
 <p><strong>01.11.2024</strong>  </p>
 <ul>
-<li><strong>ATTENTION: BREAKING CHANGE!</strong> Room temperature parameter 10000, 10001 and 10002 must now have the additional flag <code>FL_SPECIAL_INF</code>, otherwise setting temperature will not work!</li>
+<li><strong>ATTENTION: BREAKING CHANGE!</strong> Room temperature parameter 10000, 10001 and 10002 must now have the additional flag <code>FL_SPECIAL_INF</code>, otherwise setting temperature will not work! See <code>BSB_LAN_custom_defs.h.default</code> and search for <code>FL_SPECIAL_INF</code>to find the right line and use that as an example.</li>
 <li><strong>ATTENTION: BREAKING CHANGE!</strong> Outside temperature simulation parameter 10017 must have <code>FL_SPECIAL_INF</code> flag removed, otherwise setting temperature will not work!</li>
-<li><strong>ATTENTION: BREAKING CHANGE!</strong> Room temperature parameter 10000, 10001 and 10002 for Weishaupt heaters (device families 49, 50, 51 and 59) must now have <code>FL_SPECIAL_INF</code> flag removd, otherwise setting temperature will not work!</li>
+<li><strong>ATTENTION: BREAKING CHANGE!</strong> Room temperature parameter 10000, 10001 and 10002 for Weishaupt heaters (device families 49, 50, 51 and 59) must now have <code>FL_SPECIAL_INF</code> flag removed, otherwise setting temperature will not work!</li>
 <li><strong>ATTENTION: BREAKING CHANGE!</strong> URL commands <code>/U</code> (dislpay user-defined variables) and <code>/X</code> (display MAX! values) have been removed as these values can now be accessed via parameters 20000++</li>
 <li><strong>ATTENTION: BREAKING CHANGE!</strong> PPS time program parameters (15050-15091) have been streamlined with BSB/LPB time program parameters, resulting in only one parameter per day (instead of six), covering three switch points (start and end) per parameter.</li>
 <li><strong>ATTENTION:</strong> For ESP32, BSB-LAN requires ESP32 framework version 3.0.x - please look out for errors or strange behaviour (1-Wire sensors are still not tested) as well as any other kind of strange behaviour/crashes.</li>

de/using.html

@@ -489,8 +489,12 @@ <h3 id="verschiedenes">Verschiedenes</h3>
 <td style="text-align: left;">Löschen des EEPROM und Neustarten des Mikrocontrollers. Alle Konfigurationseinstellungen werden anschließend aus der Konfigurationsdatei gelesen, bis sie in der Web-Oberfläche gesetzt und erneut gespeichert werden, um sie in das EEPROM zu schreiben.</td>
 </tr>
 <tr>
-<td style="text-align: left;"><code>/QD</code></td>
-<td style="text-align: left;">Ausgeben der Parameterstruktur des Heizungssystems</td>
+<td style="text-align: left;"><code>/Q</code></td>
+<td style="text-align: left;">Download der gerätespezifischen Parameterliste des Heizungssystems</td>
+</tr>
+<tr>
+<td style="text-align: left;"><code>/QDB</code></td>
+<td style="text-align: left;">Ruft eine gerätespezifische Parameterliste von der Heizung ab und aktiviert diese bis zum Neustart. Kategorien gelten nicht, Du musst die Bedeutung der Parameternummern kennen, die Du abfragen möchtest, und kannst dann direkt darauf zugreifen (z. B. /0-9999). Dies ist kein Ersatz für die Generierung einer richtigen gerätespezifischen Parameterliste, da diese nur wenige Parametertypen enthält, von denen wir sicher wissen, wie sie funktionieren und die keinen Schaden anrichten können (meistens schreibgeschützte Statustemperaturen). Diese können jedoch für Heizungstechniker hilfreich sein, die das Verhalten eines beliebigen Heizsystems vor Ort überwachen möchten, ohne eine gerätespezifische Parameterliste erstellen und hochladen zu müssen.</td>
 </tr>
 <tr>
 <td style="text-align: left;"><code>/W</code></td>

fr/CHANGELOG.html

@@ -399,6 +399,8 @@ <h2 id="current-master">Current Master</h2>
 <li><strong>ATTENTION: BREAKING CHANGE</strong> The acknowledgement message sent by BSB-LAN to the <code>MQTT</code> topic has been removed. Instead, QoS for publishing messages has been set to level 1.</li>
 <li><strong>ATTENTION: BREAKING CHANGE:</strong> Log configuration values have changed. However, only users that have logged to UDP are affected and will have to adjust their settings.</li>
 <li><strong>ATTENTION:</strong> <code>/JK=ALL</code> now lists all categories of all devices in LPB systems with more than one device. Use <code>dev_fam</code> (device family), <code>dev_var</code> (device variant), <code>dev_id</code> (destination device ID) and <code>dev_name</code> (device model) elements to sort and identify which category applies to the current destination device. </li>
+<li>Added new URL command /QDB - this queries the heating system for device-specific parameters and activates these until reboot. Categories do not apply, you have know the parameter numbers you want to query and access them directy (e.g. /0-9999).<br />
+This is not a replacement for generating a proper device-specific parameter list as it only contains few parameter types which we know for certain how they work and no harm can be done (mostly read-only status temperatures). However, these can be helpful for heating technicians which want to monitor on the spot the behavior of a random heating system without the need to create a device-specific parameter list. </li>
 <li>Added setting to only publish log parameters to MQTT. Forcing MQTT updates via /poll topic are still possible.</li>
 <li>Added state_class for non cumulative sensors in MQTT auto-discovery</li>
 <li>Updated the room unit emulation in <code>custom_functions</code> to work with version 4.x.</li>
@@ -422,9 +424,9 @@ <h2 id="version-41">Version 4.1</h2>
 <h2 id="version-40">Version 4.0</h2>
 <p><strong>01.11.2024</strong>  </p>
 <ul>
-<li><strong>ATTENTION: BREAKING CHANGE!</strong> Room temperature parameter 10000, 10001 and 10002 must now have the additional flag <code>FL_SPECIAL_INF</code>, otherwise setting temperature will not work!</li>
+<li><strong>ATTENTION: BREAKING CHANGE!</strong> Room temperature parameter 10000, 10001 and 10002 must now have the additional flag <code>FL_SPECIAL_INF</code>, otherwise setting temperature will not work! See <code>BSB_LAN_custom_defs.h.default</code> and search for <code>FL_SPECIAL_INF</code>to find the right line and use that as an example.</li>
 <li><strong>ATTENTION: BREAKING CHANGE!</strong> Outside temperature simulation parameter 10017 must have <code>FL_SPECIAL_INF</code> flag removed, otherwise setting temperature will not work!</li>
-<li><strong>ATTENTION: BREAKING CHANGE!</strong> Room temperature parameter 10000, 10001 and 10002 for Weishaupt heaters (device families 49, 50, 51 and 59) must now have <code>FL_SPECIAL_INF</code> flag removd, otherwise setting temperature will not work!</li>
+<li><strong>ATTENTION: BREAKING CHANGE!</strong> Room temperature parameter 10000, 10001 and 10002 for Weishaupt heaters (device families 49, 50, 51 and 59) must now have <code>FL_SPECIAL_INF</code> flag removed, otherwise setting temperature will not work!</li>
 <li><strong>ATTENTION: BREAKING CHANGE!</strong> URL commands <code>/U</code> (dislpay user-defined variables) and <code>/X</code> (display MAX! values) have been removed as these values can now be accessed via parameters 20000++</li>
 <li><strong>ATTENTION: BREAKING CHANGE!</strong> PPS time program parameters (15050-15091) have been streamlined with BSB/LPB time program parameters, resulting in only one parameter per day (instead of six), covering three switch points (start and end) per parameter.</li>
 <li><strong>ATTENTION:</strong> For ESP32, BSB-LAN requires ESP32 framework version 3.0.x - please look out for errors or strange behaviour (1-Wire sensors are still not tested) as well as any other kind of strange behaviour/crashes.</li>

fr/using.html

@@ -502,10 +502,14 @@ <h3 id="divers">Divers</h3>
 <td style="text-align: left;">Effacer l'EEPROM et redémarrer le microcontrôleur. Tous les paramètres de configuration seront ensuite lus à partir du fichier de configuration jusqu'à ce qu'ils soient définis et enregistrés à nouveau dans l'interface web pour être écrits dans l'EEPROM.</td>
 </tr>
 <tr>
-<td style="text-align: left;"><code>/QD</code></td>
+<td style="text-align: left;"><code>/Q</code></td>
 <td style="text-align: left;">Afficher la structure des paramètres du système de chauffage</td>
 </tr>
 <tr>
+<td style="text-align: left;"><code>/QDB</code></td>
+<td style="text-align: left;">Récupère une liste de paramètres spécifiques à l'appareil du radiateur et l'active jusqu'au redémarrage. Les catégories ne s'appliquent pas, il faut que connaître la signification des numéros de paramètres que tu souhaites interroger et tu peut ensuite y accéder directement (par exemple /0-9999). Il ne s’agit pas d’un substitut à la génération d’une liste de paramètres spécifique à l’appareil, car elle ne contient que quelques types de paramètres dont nous savons avec certitude comment ils fonctionnent et qui ne peuvent pas causer de dommages (principalement des températures d’état en lecture seule). Cependant, ils peuvent être utiles aux chauffagistes qui souhaitent surveiller le comportement de n'importe quel système de chauffage sur site sans avoir à créer et téléverser une liste de paramètres spécifique à l'appareil.</td>
+</tr>
+<tr>
 <td style="text-align: left;"><code>/W</code></td>
 <td style="text-align: left;">Avec <code>/W</code> précédant les commandes URL <code>C</code>, <code>S</code> et <code>Q</code>, les données sont renvoyées sans en-tête et pied de page HTML (par exemple : <code>/WC</code> ou <code>/WS&lt;x&gt;=&lt;y!z&gt;</code>).</td>
 </tr>

index.html

@@ -277,5 +277,5 @@ <h4 class="modal-title" id="keyboardModalLabel">Keyboard Shortcuts</h4>
 
 <!--
 MkDocs version : 1.6.0
-Build Date UTC : 2024-12-19 16:51:41.473820+00:00
+Build Date UTC : 2024-12-23 18:18:08.985991+00:00
 -->