mirrors
/
Tasmota
mirror of https://github.com/arendst/Tasmota.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

added docker-tasmota and some lectoring

blakadder 2019-11-16 14:43:38 +01:00
parent 20a69bda85
commit e083c2c1c5
2 changed files with 10 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
Commands.md

@ -430,11 +430,12 @@ SetOption80<a id="SetOption80"></a>|[Blinds and shutters](blinds-and-shutters) s
SetOption81<a id="SetOption81"></a>|Set PCF8574 component behavior for all ports&emsp; »6.6.0.14<BR>`0` = set as regular state *(default)*<BR>`1` = set as inverted state
### Serial Bridge
Both Hardware and Software Serial Bridge are supported.
Both hardware and software Serial Bridge are supported.
Hardware Serial Bridge uses GPIO1 (Tx) and GPIO3 (Rx) or GPIO13 (Tx) and GPIO15 (Rx) pins of your device. Software Serial Bridge can use any other GPIO to be configured as components `Serial Tx` and `Serial Rx`or `SerBr Tx` and `SerBr Rx`. If TX or Rx components are not explicitly assigned in the Template or Module, GPIO1 and GPIO3 will be used. You must disable serial logging (`SerialLog 0`).
Hardware Serial Bridge uses `GPIO1 (Tx)` and `GPIO3 (Rx)` or `GPIO13 (Tx)` and `GPIO15 (Rx)` pins of your device.
Software Serial Bridge can use any other GPIO to be configured as components `Serial Tx` and `Serial Rx` (or `SerBr Tx` and `SerBr Rx`). If `Tx` and `Rx` components are not assigned in the Template or Module `GPIO1` and `GPIO3` will be used. You must disable serial logging ([`SerialLog`](#seriallog) 0) when using Software Serial Bridge.
Information received by Tasmota over the serial bridge is captured automatically. Before data will be received, a properly formatted [`SerialSend<x>` or `SSerialSend<x>`](#SerialSend) command must executed. This must be done any time the device restarts (e.g., via a `System#Boot` triggered rule). This command is required in order to set how the expected serial data will be formatted and interpreted (i.e., which \<x> option). A `{"SSerialReceived":{"Data":"<string>"}}` message will be posted. You can use [a rule](Rule-Cookbook#switch-relays-via-serial-interface) to process the string which will be contained in `SSerialReceived#Data`.
Information received by Tasmota over the serial bridge is captured automatically. Before data will be received, a properly formatted [`SerialSend<x>` or `SSerialSend<x>`](#SerialSend) command must be executed. This must be done any time the device restarts (e.g., via a `System#Boot` triggered rule). This command is required in order to set how the expected serial data will be formatted and interpreted (i.e., which \<x> option). A `{"SSerialReceived":{"Data":"<string>"}}` message will be posted. You can use [a rule](Rule-Cookbook#switch-relays-via-serial-interface) to process the string which will be contained in `SSerialReceived#Data`.
Expect possible communication errors when additional sensors are configured.

10
Flashing.md

@ -113,14 +113,16 @@ Unplug your serial programming adapter or your device and plug it back in or con
# Flashing and compiling from source
Tutorials for setting up development environments if you want to modify the code or default settings and [compile your own binaries](compile-your-build).
- [**PlatformIO**](PlatformIO) - setup and configure [PlatformIO](https://platformio.org) for Tasmota compilation and upload
- [**PlatformIO CLI**](PlatformIO-CLI) - how to flash Tasmota using the PlatformIO command line interface on Linux
- [**PlatformIO**](PlatformIO) - setup and configure [PlatformIO](https://platformio.org) for compilation and upload
- [**PlatformIO CLI**](PlatformIO-CLI) - use the PlatformIO command line interface on Linux for compilation and upload
- [**PlatformIO-Core**](Create-your-own-Firmware-Build-without-IDE) - automate firmware builds using PlatformIO-Core and flash with esptool
- [**Visual Studio Code**](Visual-Studio-Code) - setup and configure [Visual Studio Code](https://code.visualstudio.com) with PlatformIO for Tasmota
- [**Atom**](Beginner-Guide---Create-your-own-Firmware-Build) - beginner guide building Tasmota firmware using [Atom](https://atom.io/) with PlatformIO plugin
- [**Arduino IDE**](Arduino-IDE) - setup and configure Arduino IDE for Tasmota compilation and upload
- [**Docker Tasmota**](https://github.com/tasmota/docker-tasmota) - compile from a Docker container using PlatformIO
If you use PlatformIO, to be sure that you have the latest build of the ESP Core, first delete the following folders in your current `.platformio` folder:
In PlatformIO, be sure that you always have the latest build of the ESP Core.
Delete the following in your `.platformio` folder (`%USERPROFILE%\.platformio` in Windows):
- Everything in `.platformio/platforms`
- All folders that begin with `framework...` in `.platformio/packages`
@ -131,7 +133,7 @@ _**Can only create a firmware binary.** Use one of the [tools](Prerequisites#fla
# OTA Flashing Tools
**Tasmota is NOT a developer of these tools. For help and troubleshooting you will need to _get support from those projects_.**
- [**Tuya OTA**](Tuya-OTA) - easy OTA flash for devices with Tuya chips, no disassembly required
- [**Tuya Convert**](Tuya-OTA) - easy OTA flash for devices with Tuya chips, no disassembly required
- [**Sonoff DIY**](Sonoff-DIY) - OTA flash for select Sonoff devices (some disassembly required)
- [**Node-RED OTA server and firmware manager**](https://flows.nodered.org/flow/888b4cd95250197eb429b2f40d188185) - [Node-RED](https://nodered.org/) flow for managing OTA updates
- [**OTA over SCP**](OTA-over-SCP) - setup and configure "OTA over SCP" upload for PlatformIO