forked from blakadder/templates
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathD06
124 lines (96 loc) · 5.51 KB
/
D06
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
---
date_added: 2020-09-20
title: D06
model: D06
image: /assets/images/D06.jpg
template: '{"NAME":"D06 Door Sensor","GPIO":[0,148,0,149,21,0,0,0,0,0,0,0,0],"FLAG":0,"BASE":18}'
mlink:
link: https://www.aliexpress.com/item/10000093278617.html
link2:
flash: serial
category: sensor
type: Contact Sensor
standard: global
---
<div style="float:right; margin:10px; text-align: center;"><img style="width:50px" src="/assets/images/blakapproved.png"> <br><b> by <a href="https://blakadder.com">blakadder</a></b></div>
This is a Tuya battery powered contact sensor. Runs on two AAA batteries (not supplied with the device).
This sensor can be found for around 6$ on AliExpress!
## Flashing
To have best results with this type of device I strongly recommend compiling a stripped down binary. There's an [unofficial tasmota-battery.bin binary](https://github.com/tasmota/binaries), compiled from current development release. Flash at your own risk.
### Serial
Easily disassembled by removing the back plate, then prying away the plastic with the battery holder and pcb.
The PCB has no visible serial number or other marking on it but the MCU is marked D06. It powers on the [TYWE3S](https://tasmota.github.io/docs/Pinouts/#tywe3s) module on probe contact on "Reset" button press for a short amount of time sufficient to send alerts.
To flash the device solder directly to [TYWE3S](https://tasmota.github.io/docs/devices/TYWE3S/) TX, RX, VCC and GND pins (optional: solder GPIO0 to GND but you only need to connect it to GND during boot). You also need to temporarily remove the marked resistor to prevent the MCU from interfering with the flashing process. Resolder it back or bridge the connection once flashing is complete.
## Configuration
_If you're using battery power you will have to periodically wake up the sensor with the reset button or by shorting the GND and KEY pads on the PCB_.
In this case we will not use the TuyaMCU base but will instead capture raw serial traffic and emulate a Tuya module with a couple of rules executed on system boot.
Disable multipress button options to prevent an accidental device reset, disable Power Cycle recovery, disable bootloop recovery and enable power retain to keep the power state in your broker.
```console
Backlog SetOption1 1; SetOption65 1; SetOption36 0; PowerRetain 1
```
Add rule
```console
rule1
on system#init do baudrate 9600 endon
on system#boot do backlog serialsend5 55AA000800010008; delay 5; serialsend5 55AA000200010406 endon
```
Don't forget to turn on the rule: `Rule1 1`
```console
rule2
on serialreceived#data=55AA0008000C00020202020202010100010123 do power 1 endon
on serialreceived#data=55AA0008000C00020202020202010100010022 do power 0 endon
on serialreceived#data=55AA0008000C00010101010101030400010223 do publish2 stat/%topic%/BATTERY high endon
on serialreceived#data=55AA0008000C00010101010101030400010122 do publish2 stat/%topic%/BATTERY medium endon
on serialreceived#data=55AA0008000C00010101010101030400010021 do publish2 stat/%topic%/BATTERY low endon
```
Turn on the rule: `Rule2 1`
The relay in the template is a dummy relay used to keep power states with rule2.
You can adapt the publish topics and payloads to work with your system, these are formed to work in my environment. Battery messages are sent on every boot but we're still publishing those messages with the retained flag so the battery state will always be reachable.
Remember that the reset button on the back will trigger the sensor which is useful to test the device periodically and refresh battery status so you don't run out accidentally.
## Home Assistant Integration
Since autodiscovery won't work on this type of device and configuration.yaml is so 2019 we will create a manual autodiscovery message and end up with a Device in HA with two entities. You need Tasmota 8.5+ to do this.
The payload is presented in yaml form for easier editing. To get a valid payload, take the yaml block and convert it to JSON. I recommend using [onlineyamltools](https://onlineyamltools.com/convert-yaml-to-json). If you have changed topics and payloads in the rule you need to change them here too.
Set your device `Topic` to something meaningful because it will be used as part of the device name in HA.
#### Contact Sensor
{% highlight yaml %}
{% raw %}name: %topic% Contact Sensor
state_topic: stat/%topic%/RESULT
value_template: '{{value_json.POWER}}'
payload_off: 'OFF'
payload_on: 'ON'
device_class: opening
unique_id: '%deviceid%_contact'
device:
identifiers:
- '%deviceid%'
name: %topic%
manufacturer: Tasmota
platform: mqtt{% endraw %}
{% endhighlight %}
Paste the converted json payload in the rule instead of `<json_payload>`
```console
rule3 on system#boot do publish2 homeassistant/binary_sensor/%deviceid%_contact/config <json_payload> endon
```
#### Battery Sensor
{% highlight yaml %}
{% raw %}name: '%topic% Battery'
state_topic: stat/%topic%/BATTERY
value_template: '{{ value }}'
icon: 'mdi:battery'
unique_id: '%deviceid%_battery'
device:
identifiers:
- '%deviceid%'
name: %topic%
manufacturer: Tasmota
{% endraw %}
{% endhighlight %}
Paste the converted json payload in the rule instead of `<json_payload>`
```console
rule3 + on system#boot do publish2 homeassistant/sensor/%deviceid%_battery/config <json_payload> endon
```
This will append a new line to the existing rule3.
Don't forget to enable the rule with `Rule3 1`
When the sensor boots again it will send the two autodiscovery messages and your device will appear in HA devices list.
