Deployed 03e9214 with MkDocs version: 1.6.1

Parameters/index.html

@@ -697,9 +697,9 @@
 </a>
 </li>
 <li class="md-nav__item">
-<a class="md-nav__link" href="#parameter-numbersallownegativerates">1.5.4 
+<a class="md-nav__link" href="#parameter-allownegativerates_1">1.5.4 
 <span class="md-ellipsis">
-      Parameter &lt;NUMBERS&gt;.AllowNegativeRates
+      Parameter AllowNegativeRates
     </span>
 </a>
 </li>
@@ -2045,9 +2045,9 @@
 </a>
 </li>
 <li class="md-nav__item">
-<a class="md-nav__link" href="#parameter-numbersallownegativerates">1.5.4 
+<a class="md-nav__link" href="#parameter-allownegativerates_1">1.5.4 
 <span class="md-ellipsis">
-      Parameter &lt;NUMBERS&gt;.AllowNegativeRates
+      Parameter AllowNegativeRates
     </span>
 </a>
 </li>
@@ -3512,7 +3512,7 @@ It especially improves the zero crossing check between digits.</p>
 In an error case, the last valid number will be used for the various transmission protocols (MQTT, InfluxDB, REST, ...).</p>
 <hr style="border:2px solid"/>
 <p><a id="PostProcessing-NUMBER.AllowNegativeRates"></a></p>
-<h3 id="parameter-numbersallownegativerates"><span class="enumerate-headings-plugin enumerate-heading-plugin">1.5.4</span> Parameter <code>&lt;NUMBERS&gt;.AllowNegativeRates</code></h3>
+<h3 id="parameter-allownegativerates_1"><span class="enumerate-headings-plugin enumerate-heading-plugin">1.5.4</span> Parameter <code>AllowNegativeRates</code></h3>
 <p>Section: <a href="#section-postprocessing">1.5 PostProcessing</a></p>
 <p>Default Value: <code>false</code></p>
 <p>Allow a meter to count backwards (decreasing values).</p>
@@ -3520,6 +3520,10 @@ In an error case, the last valid number will be used for the various transmissio
 <p class="admonition-title">Note</p>
 <p>This is unusual (it means there is a negative rate) and not wanted in most cases!</p>
 </div>
+<div class="admonition note">
+<p class="admonition-title">Note</p>
+<p>This parameter must be prefixed with <code>&lt;NUMBER&gt;</code> followed by a dot (eg. <code>main.AllowNegativeRates</code>). <code>&lt;NUMBER&gt;</code> is the name of the number sequence  defined in the ROI's.</p>
+</div>
 <hr style="border:2px solid"/>
 <p><a id="PostProcessing-NUMBER.AnalogToDigitTransitionStart"></a></p>
 <h3 id="parameter-analogtodigittransitionstart"><span class="enumerate-headings-plugin enumerate-heading-plugin">1.5.5</span> Parameter <code>AnalogToDigitTransitionStart</code></h3>

Watermeter-specific-analog---digit-transition/index.html

@@ -740,7 +740,7 @@
 <p>The models for image recognition are good, but have inaccuracies in the range +/- 0.2. In order to obtain as many correct results as possible, a treatment is carried out in the post process in the range of 9.8-0.2 for the analogue pointer, which must start differently depending on the type of counter.</p>
 <h2 id="how-to-configure-for-my-meter-type"><span class="enumerate-headings-plugin enumerate-heading-plugin">1.4</span> How to configure for my meter type</h2>
 <p>If you have a devices with "normal" transition you should not have any issues. On devices with "early" transition, you can set the option <code>AnalogToDigitTransitionStart</code> to a value between 6 and 8.
-See the <a href="../Parameters/#parameter-numberanalogtodigittransitionstart">parameter documentation</a> for details.</p>
+See the <a href="../Parameters/#parameter-analogtodigittransitionstart">parameter documentation</a> for details.</p>
 </article>
 </div>
 <script>var target=document.getElementById(location.hash.slice(1));target&&target.name&&(target.checked=target.name.startsWith("__tabbed_"))</script>