Skip to content

Commit 3ab0eca

Browse files
committed
link added
1 parent 5224353 commit 3ab0eca

File tree

2 files changed

+5
-3
lines changed

2 files changed

+5
-3
lines changed

content/components/remote_transmitter.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -235,7 +235,8 @@ on_...:
235235
- All other options from [Remote Transmitter Actions](#remote_transmitter-transmit_action).
236236

237237
{{< note >}}
238-
The brennenstuhl devices use rolling codes, i.e. each button of the remote generates 4 different codes in a pseudo random manner. The four codes of the button are stored in a vector. The vector is looped to provide the **transmit_brennenstuhl** function with codes that differ from the previous ones. See remote-setting-up-rolling-codes for details and a YAML example.
238+
The brennenstuhl devices use rolling codes, i.e. each button of the remote generates 4 different codes in a pseudo random manner. The four codes of the button are stored in a vector. The vector is looped to provide the **transmit_brennenstuhl** function with codes that differ from the previous ones. See
239+
[Rolling Codes](#remote-setting-up-rolling-codes) and [Setting up RF Devices](#remote-setting-up-rf) for details and a YAML example.
239240

240241
{{< /note >}}
241242

content/guides/setting_up_rmt_devices.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -188,10 +188,11 @@ You can adjust the `repeat:` settings accordingly.
188188

189189
{{< /note >}}
190190

191-
192191
## Rolling Codes
193192

194-
Some devices are using rolling codes, i.e. instead of **one unique** code, the buttons generate **n different** codes in a random manner. Good-natured receivers have a simple logic: the current code must differ from the previous one. In such a case, the n codes can be recorded by pressing each button several times and stored in a vector. The *brennenstuhl* remote for example uses four rolling codes for each button.The YAML below shows the transmitter for three buttons:
193+
{{< anchor "remote-setting-up-rolling-codes" >}}
194+
195+
Some devices are using rolling codes, i.e. instead of **one unique** code, the buttons generate **n different** codes in a random manner. Good-natured receivers have a simple logic: the current code must differ from the previous one. In such a case, the n codes can be recorded by pressing each button several times and stored in a vector. The brennenstuhl remote for example uses four rolling codes for each button.The YAML below shows the transmitter for three buttons:
195196

196197
```yaml
197198

0 commit comments

Comments
 (0)