-
Notifications
You must be signed in to change notification settings - Fork 420
RF Bridge
Alex X edited this page May 8, 2022
·
4 revisions
Component will create Remote entity per RF Bridge - remote.sonoff_1000xxxxxx
.
You can receive signals from RF Buttons and RF Sensors through an event sonoff.remote
. And send signals using the service remote.send_command
.
Although the component supports training, it is recommended to train RF Buttons through the eWeLink application.
When a command is received, the event sonoff.remote
is generated with a button number and response time (in UTC, sends the device).
Example for receive all RF signal
automation:
- alias: Sonoff RF Receive
trigger:
platform: event
event_type: sonoff.remote # this is NOT entity_id, don't change it!
action:
service: persistent_notification.create
data_template:
title: Sonoff RF Receive
message: |-
Name: {{ trigger.event.data.name }}
Command: {{ trigger.event.data.command }}
Time: {{ trigger.event.data.ts }}
Example of reaction to the selected button
Instead of a name: Button1
, you can use command: 0
number of the button in the eWeLink application (starts from zero).
automation:
- alias: Receive Button1
trigger:
platform: event
event_type: sonoff.remote # this is NOT entity_id, don't change it!
event_data:
name: Button1 # button/sensor name in eWeLink application
action:
service: persistent_notification.create
data:
message: My Remote button pressed
Example for send RF signal
script:
send_button1:
alias: Send RF Button1
sequence:
- service: remote.send_command
data:
entity_id: remote.sonoff_1000abcdef
command: Button1 # button name in eWeLink application