Merge branch 'development' into influxdb_period

barbudor · barbudor · commit e102872a12d6 · 2021-11-28T15:58:56.000+01:00
diff --git a/docs/Commands.md b/docs/Commands.md
@@ -104,7 +104,7 @@ A `Backlog` command without an argument clears an possible existing `Backlog` qu
 
 !!! warning
     If you're using Tasmota versions earlier current release some of the commands might not work.
-    Availability of some features and their associated commands depend on the firmware build. Please consult the [builds](Builds) table for a reference of which features are available for each firmware variant.
+    Availability of some features and their associated commands depend on the firmware build. Please consult the [builds](Firmware-Builds) table for a reference of which features are available for each firmware variant.
 
 !!! note
     Almost all settings using string parameters (except `Rule` and `MqttFingerprint`) share a common area with max 698 chars, i.e. the total length of all these parameters is limited to this size (you will be noted if this limit is exceeded).
@@ -157,7 +157,7 @@ Gpios<a class="cmnd" id="gpios"></a>|Show list of available [components](Compone
 Gpio<a class="cmnd" id="gpio"></a>|Show current [component](Components#gpio-conversion) assignments of the Module's configurable GPIO<BR>`255` / `All` Show [component](Components#gpio-conversion) assignments for all the devices available GPIO<BR>
 Gpio<x\><a class="cmnd" id="gpiox"></a>|`<component>` = assign a [component](Components) to `Gpio<x>`
 I2Cscan<a class="cmnd" id="i2cscan"></a>|Scan I<sup>2</sup>C bus and show addresses for found devices
-I2CDriver<a class="cmnd" id="i2cdriver"></a>|Enable / Disable I<sup>2</sup>C sensor drivers. [Read more...](I2CDevices)<BR>
+I2CDriver<a class="cmnd" id="i2cdriver"></a>|Enable / Disable I<sup>2</sup>C sensor drivers. [Read more...](I2CDEVICES)<BR>
 LogHost<a class="cmnd" id="loghost"></a>|`1` = reset [syslog](https://www.sigmdel.ca/michel/ha/rpi/syslog_en.html) host to firmware default (`SYS_LOG_HOST`)<BR>`<value>` = set syslog host
 LogPort<a class="cmnd" id="logport"></a>|`1` = reset [syslog](https://www.sigmdel.ca/michel/ha/rpi/syslog_en.html) port to firmware default (`SYS_LOG_PORT`)<BR>`2..32766` = set syslog port
 Modules<a class="cmnd" id="modules"></a>|Show available modules by name and index
diff --git a/docs/FAQ.md b/docs/FAQ.md
@@ -206,7 +206,7 @@ In case you're using a template you created yourself or found in our Templates R
 
 ### Sensors do not show values
 Make sure your sensor is properly wired and the GPIOs assigned. 
-Your vanilla `tasmota.bin` doesn't have complete sensor support. Make sure you've installed tasmota-sensors.bin that support the largest number of sensors. Some sensors require enabling in the code and compiling your own binary. See [Builds](Builds) for a comprehensive list of supported components.
+Your vanilla `tasmota.bin` doesn't have complete sensor support. Make sure you've installed tasmota-sensors.bin that support the largest number of sensors. Some sensors require enabling in the code and compiling your own binary. See [Builds](Firmware-Builds) for a comprehensive list of supported components.
 
 ### Timers trigger at the wrong time
 Tasmota devices must have a their time of day set properly in order for **any** timers to work properly. Check the log in the web UI Console to see if the device's time is set correctly. There are two elements to setting the time: 1. obtaining the UTC time, and, 2. local Daylight Saving Time policies.  
diff --git a/docs/Getting-Started.md b/docs/Getting-Started.md
@@ -47,7 +47,7 @@ Tasmota installed from a precompiled binary needs to be configured to work with
 
 ### Needed Software
 #### Tasmota Firmware Binary
-Download a Tasmota firmware binary file (.bin). If you're not sure which binary is the right one for you just start with `tasmota.bin` or consult the [builds table](Builds) to see which features you need. 
+Download a Tasmota firmware binary file (.bin). If you're not sure which binary is the right one for you just start with `tasmota.bin` or consult the [builds table](Firmware-Builds) to see which features you need. 
 
 Official release binaries can be downloaded from [firmware server](http://ota.tasmota.com/tasmota/release/). 
 
diff --git a/docs/Gitpod.md b/docs/Gitpod.md
@@ -39,7 +39,7 @@ To modify the stock configuration:
 
 1. Select the `/tasmota` folder in the Explorer (1) pane
 2. Create a new file called `user_config_override.h`
-3. In the Editor (2) pane, add, change, or remove anything you need in your configuration file to define your own settings. Refer to the `user_config_override_sample.h` file as well as `my_user_config.h` for `#define` options ([sample](https://pastebin.com/M5KPPWAJ)). You can find a list of Tasmota features and settings listed [here](Builds). Define the features you require in your configuration file.
+3. In the Editor (2) pane, add, change, or remove anything you need in your configuration file to define your own settings. Refer to the `user_config_override_sample.h` file as well as `my_user_config.h` for `#define` options ([sample](https://pastebin.com/M5KPPWAJ)). You can find a list of Tasmota features and settings listed in the [builds table](Firmware-Builds). Define the features you require in your configuration file.
 4. Click 'File' on the menu bar and 'Save' your edits.
 
 ### Prepare the IDE for Compilation
diff --git a/docs/Peripherals.md b/docs/Peripherals.md
@@ -24,7 +24,7 @@ Assign a [component](Components) to a GPIO.
    
 - `GPIO14 2` configures sensor AM2301 to GPIO14_    
 - `Backlog GPIO14 5; GPIO4 6` sets I<sup>2</sup>C SCL to GPIO14 and I<sup>2</sup>C SDA to GPIO4
-   Tasmota will auto-detect all connected and supported I<sup>2</sup>C devices. If you have conflicting I<sup>2</sup>C addresses see [I2CDevices](I2CDevices)
+   Tasmota will auto-detect all connected and supported I<sup>2</sup>C devices. If you have conflicting I<sup>2</sup>C addresses see [I2CDevices](I2CDEVICES)
 
 _[`GPIOs All`](Commands.md#gpios) shows list of all available components by name and index_
 
diff --git a/docs/PlatformIO-CLI.md b/docs/PlatformIO-CLI.md
@@ -14,7 +14,7 @@ Either download the latest Tasmota Source code from https://github.com/arendst/T
 `git clone https://github.com/arendst/Tasmota.git`
 
 ## Select the environment
-The default environment configuration can be used to easily generate Tasmota firmware variants (tasmota, sensors, display, etc.). If you're not sure which binary is the right one for you, consult the [builds table](Builds) or just start with `tasmota.bin`. To build and/or flash exactly one of these, use the `-e` command line argument (e.g., `-e tasmota-sensors`). 
+The default environment configuration can be used to easily generate Tasmota firmware variants (tasmota, sensors, display, etc.). If you're not sure which binary is the right one for you, consult the [builds table](Firmware-Builds) or just start with `tasmota.bin`. To build and/or flash exactly one of these, use the `-e` command line argument (e.g., `-e tasmota-sensors`). 
 
 # Compile and upload
 Once all the prerequisites are in place, compiling and uploading is one simple command. Execute this from within the `Tasmota` source code directory:  
diff --git a/docs/Rules.md b/docs/Rules.md
@@ -5,7 +5,7 @@ Tasmota provides a Rule feature heavily inspired by the _ESPEasy_ implementation
 Rules perform actions based on triggers (e.g., switch state change, temperature threshold, events like system boot, a defined timer elapsing, custom defined events, etc.) They are stored in flash and therefore will survive a reboot.
 
 !!! note
-    Most pre-compiled [builds](Builds) have the Rules feature enabled. *If you are >compiling your own firmware, in order to use rules, include `#define USE_RULES` in `user_config_override.h`.*
+    Most pre-compiled [builds](Firmware-Builds) have the Rules feature enabled. *If you are >compiling your own firmware, in order to use rules, include `#define USE_RULES` in `user_config_override.h`.*
 
 **List of [Rules Commands](Commands.md#rules)**  
 
diff --git a/docs/SPS30.md b/docs/SPS30.md
@@ -1,6 +1,6 @@
 # SPS30 Particulate sensor
 
-!!! info "This feature is **not** included in any prebuilt Tasmota variant (check [BUILDS.md](https://github.com/arendst/Tasmota/blob/development/BUILDS.md))"
+!!! info "This feature is **not** included in any prebuilt Tasmota variant (check [builds](Firmware-Builds))"
 
 You must [compile your build](Compile-your-build). Add the following to `user_config_override.h`:
 ```cpp
diff --git a/docs/Upgrading.md b/docs/Upgrading.md
@@ -9,7 +9,7 @@ In other words, ensure that there is a good reason to mess with a working instal
 !!! tip "Backup before upgrading"
     Any time you upgrade it is highly recommended to [back up your device settings](#backing-up-settings). That is easily done from the webUI using **Configuration - Backup Config**.
 
-If you wish to switch to a different [build](Builds) or use development branch you need to download a binary file (gzipped or regular) or change the ***OTA Url*** link.
+If you wish to switch to a different [build](Firmware-Builds) or use development branch you need to download a binary file (gzipped or regular) or change the ***OTA Url*** link.
 
 Download binaries from:
 
diff --git a/docs/devices/Sonoff-RF-Bridge-433.md b/docs/devices/Sonoff-RF-Bridge-433.md
@@ -39,7 +39,7 @@ The RF upgrade requires wiring the bridge and then flashing the firmware via the
 <img src="https://github.com/arendst/arendst.github.io/raw/master/media/sonoff_bridge_rffw_upgrade.png" width="300">
 
 #### Flashing RF Firmware
-1. Make sure you have previously flashed a Tasmota binary built with `RF_FLASH`. Refer to the [builds table](https://github.com/arendst/Tasmota/blob/development/BUILDS.md) for pre-compiled binaries which include this feature. Otherwise the "Magic byte is not 0xE9" error will occur.
+1. Make sure you have previously flashed a Tasmota binary built with `RF_FLASH`. Refer to the [builds table](../Firmware-Builds) for pre-compiled binaries which include this feature. Otherwise the "Magic byte is not 0xE9" error will occur.
 2. Set the module type to `Sonoff Bridge (25)`
 3. Connect two wires (this will be different depending on the `Sonoff RF Bridge 433` hardware version):
     - For `R1`: Connect `GPIO4 to C2Ck` and `GPIO5 to C2D`.
diff --git a/mkdocs.yml b/mkdocs.yml
@@ -74,6 +74,10 @@ extra:
       link: 'https://t.me/tasmota'
     - icon: fontawesome/brands/github-alt
       link: 'https://github.com/tasmota'
+  analytics:
+    provider: google
+    property: G-8J08F8X90S
+
 markdown_extensions:
   - admonition
   - toc:
@@ -91,14 +95,11 @@ markdown_extensions:
   - pymdownx.keys
   - pymdownx.mark
   - pymdownx.superfences
-  - pymdownx.snipp  ets
+  - pymdownx.snippets
   - pymdownx.tilde
   - meta
   - def_list
 
-google_analytics:
-  - 'UA-140681905-2'
-  - 'auto'
 
 extra_css:
   - 'assets/css/anchor-fix.css'
@@ -130,7 +131,7 @@ nav:
     - Device-Groups.md
     - Displays.md
     - Dynamic-Sleep.md
-    - I2C Devices: I2CDevices.md
+    - I2C Devices: I2CDEVICES.md
     - IR Communication: Tasmota-IR.md
     - LCD/DLP Projector Control: Projector.md
     - Lights.md
