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

Updated Configuration Procedure for New Devices (markdown)

blakadder 2019-04-10 10:01:06 +02:00
parent f94fddbbff
commit 16a43d2594
1 changed files with 14 additions and 20 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

34
Configuration-Procedure-for-New-Devices.md

@ -1,35 +1,29 @@
[**Digiblur DIY Tutorial**](https://youtu.be/5Oa27pCHtYo)
If your device is similar to the existing module it is best to use that as a starting point. When you're not sure which module is suitable for your device, use module Generic (18). Once you have selected the module type and saved the configuration, return to the module type configuration dialog.
If your device is not a built-in module listed in the module configuration menu, a [user contributed device template](User-created-templates) ([explanation](Templates)) may be available. Otherwise, follow this procedure for configuring your device.
1. Set every GPIO (excluding, at first, "dedicated" GPIO's such as Tx, Rx, GPIO0, GPIO2, etc.) to one of the available `Relay<x>` relays.
If your device is similar to the existing module it is best to use that as a starting point. When you're not sure which module is suitable for your device, use Generic module (18). Once you have selected the module type and saved the configuration, return the the module type configuration dialog.
_a._ Save the configuration. Once the device reboots, use the web UI to find which of the buttons assigned to GPIO actually control relays and LED's on the device.
1. Set every GPIO (excluding, at first, "dedicated" GPIO such as Tx/Rx & GPIO0/GPIO2, etc.) each assigned to one of the available `RelayX` relays.
- If you are unable to control some of the relays or LED's on the device, they may be attached to one of the "dedicated" GPIO's. Set those to an unused `Relay<x>` and repeat step _1a_.
_a._ Save the configuration. Once the device reboots, use the web GUI virtual buttons to find which of the buttons assigned to GPIO actually control relays and LEDs on the device.
_b._ Once you have found which GPIO controls which relay and LED, set these "active" GPIO's to associate them with the corresponding `Relay<x>` or `LED<x>`. If they behave opposite of expected change them to inverted (`Relay<x>i`/`LED<x>i`).
- If you are unable to control some of the relays or LEDs on the device, they may be attached to the "dedicated" GPIO. Set those GPIO to an unused `RelayX` and repeat step _1a_.
2. Set every remaining GPIO (excluding, once again, remaining "dedicated" ones like Tx/Rx & GPIO0/GPIO2, etc.) to `Switch<x>` switches.
_b._ Once you have found which GPIO control which relays and LEDs, set these "active" GPIO to associate them with the corresponding `RelayX` or `LEDX`. Proper operation may dictate the use regular or inverted (`RelayXi`/`LEDXi`) settings.
_a._ Save the configuration. Once the device reboots, use the web UI Console to run `Status 8` (sensors) command. This will display the current state of each GPIO.
2. Now, set every remaining GPIO (excluding, once again, remaining "dedicated" like Tx/Rx & GPIO0/GPIO2, etc.) to `Switch`es.
_b._ While pressing each button, display `Status 8` again. Whichever GPIO changes state from what was shown in step _2a_ is the GPIO tied to the button.
_a._ Save the configuration. Once the device reboots, use the web GUI Console to run the<br>`Status 8` (sensors) command. This will display the current state of each GPIO.
- If none of the GPIO's change state, then configure the "dedicated" GPIO and retry.
_b._ Then, while pressing each button, display `Status 8` again. Whichever GPIO changes state from what was shown in step _2a_ is the GPIO tied to the button.
_c._ Once you have found which GPIO's are connected to each button, change the GPIO setting in the configuration to `Button<x>`. You may need to determine whether the internal pull-up is used or not. If so, select `Button<x>n`. *`n` indicates no pull-up or normally-closed.*
- If none of the GPIO change state, then configure the "dedicated" GPIO and retry.
> See [Using a physical pushbutton with single press, double press, and hold](https://github.com/arendst/Sonoff-Tasmota/wiki/Rules#16-using-an-external-button-with-single-press---double-press-and-hold) to control multiple devices with one button.
_c._ Once you have found which GPIO are connected to each button, change the GPIO setting in the configuration to a `ButtonX`. You may need to determine whether the internal pull-up is used or not. If so, select `ButtonX`_**n**_. _**n**_ indicates no pull-up or normally-closed.
- See [Using a physical pushbutton with single press, double press, and hold](https://github.com/arendst/Sonoff-Tasmota/wiki/Rules#16-using-an-external-button-with-single-press---double-press-and-hold) to control multiple devices with one button.
3. Once you have determined which GPIO your device uses, set any remaining GPIO to `None`.
- Save the configuration.
3. Once you have determined which GPIO's your device uses, set any remaining GPIO's to `None` and **Save** the configuration.
4. Once the device reboots, your device hardware is configured for use.
5. Since you have now configured a device not previously known to the TASMOTA user base, you may want to [export the template](https://github.com/arendst/Sonoff-Tasmota/wiki/Templates#exporting-your-template) and contribute it to the [templates database](https://blakadder.github.io/templates/).
5. Since you have configured a previously unknown device, you may want to [export the template](https://github.com/arendst/Sonoff-Tasmota/wiki/Templates#exporting-your-template) and contribute it to the [templates repository](https://blakadder.github.io/templates/).
For an example check out [**Digiblur DIY Video Tutorial**](https://youtu.be/5Oa27pCHtYo) on which this article is based.