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

expanded on config procedure

blakadder 2019-10-30 21:08:13 +01:00
parent f7dddef4fc
commit 32e9739e34
1 changed files with 5 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
PIR-Motion-Sensors.md

@ -4,10 +4,10 @@ Most PIR's are single wire and they require connecting to VCC, GND and one GPIO.
### Tasmota Configuration
In _Configuration -> Configure Module_ menu change `GPIO15` to `Switch1`:
In _Configuration -> Configure Module_ menu change `GPIO15` to `Switch1`.
![Step 1](https://user-images.githubusercontent.com/5904370/67887920-7e814c80-fb4c-11e9-863d-7219894be506.png)
>If there already is a `Switch1` simply choose the next in line. This way you can even have more than 1 PIR on a single device.
If there already is a `Switch1` simply choose the next in line. Same applies if you're connecting more than 1 PIR on a single device.
A configured PIR will not appear in the web UI in any form. To make it report like a sensor we need a rule that will send movement triggers to an MQTT topic.
@ -17,7 +17,9 @@ SwitchTopic 0
Rule1 on switch1#state=1 do publish stat/%topic%/PIR1 ON endon on switch1#state=0 do publish stat/%topic%/PIR1 OFF endon
Rule1 1
```
You can change the topic (`PIR1`) and the message (`ON`/`OFF`) to whatever suits your needs.
You can change (`PIR1`) and the message (`ON`/`OFF`) to whatever suits your needs. `%topic%` is the configured device topic.
Look in console for motion detection messages ```[20:24:03] stat/%topic%/PIR1 ON``` to verify everything is working
optional:
>Before using rules configure any GPIO that doesn't have anything connected to it as `Relay1`.