Use the first three channels as RGB channels. This will also enable the color picker in the web UI. Will only work if the device has at least 3 dimmable channels.<br>Reload the page to update the web interface.
Use the first three channels as RGB channels. This will also enable the color picker in the web UI. Will only work if the device has at least 3 dimmable channels.
Use a dimmable channel as warm white light and another dimmable channel as cold white light.<br>On devices with two dimmable channels the first use used for warm white light and the second for cold white light.<br>On color lights the fifth use used for warm white light and the fourth for cold white light.<br>Will only work if the device has exactly 2 dimmable channels or at least 5 dimmable channels and "white channel" above is also ON.<br>Enabling this will render useless the "Channel 5" slider in the status page.<br>Reload the page to update the web interface.
Use a dimmable channel as warm white light and another dimmable channel as cold white light.<br>On devices with two dimmable channels the first use used for warm white light and the second for cold white light.<br>On color lights the fifth use used for warm white light and the fourth for cold white light.<br>Will only work if the device has exactly 2 dimmable channels or at least 5 dimmable channels and "white channel" above is also ON.<br>Enabling this will render useless the "Channel 5" slider in the status page.
Sync channel values between multiple devices. Notice that every device that is subscribed to the topic <strong>should</strong> be configured to use the same brightness.
When specified, ESPurna will use these values in place of the hostname (see <strong>GENERAL</strong> panel) as SSID and device password (see <strong>ADMIN</strong> panel) as passphrase.
When left empty, the firmware will generate a client ID based on the MAC address of the chip. The following placeholders are also supported: {hostname}, {mac}
When left blank, the firmware will generate a Client ID based on the MAC address of the chip. The following placeholders are also supported: {hostname}, {mac}
This is the root topic for this device. The following placeholders can be used: {hostname} and {mac} to dynamically set the value to the device hostname and MAC address respectively.<br>
- <strong><root>/relay/#/set</strong> Send a 0 or a 1 as a payload to this topic to switch it on or off. You can also send a 2 to toggle its current state. Replace # with the switch ID (starting from 0). If the board has only one switch it will be 0.<br>
<spanclass="module module-relay">- <strong><root>/relay/#/set</strong> Send a 0 or a 1 as a payload to this topic to switch it on or off. You can also send a 2 to toggle its current state. Replace # with the switch ID (starting from 0). If the board has only one switch it will be 0.<br></span>
<spanclass="module module-relay">- <strong><root>/pulse/#/set</strong> Toggles the switch # and toggles it back after the specified time. Time is expected as <code>TIME[<UNIT>].</code> Without the unit, time is interpreted as a number of seconds (floating point). Unit can either be <code>h</code> for hours, <code>m</code> for seconds and <code>s</code> for seconds. Multiple time and unit pairs are allowed, for example <code>5h4m3s</code>.<br></span>
<spanclass="module module-cmd">- <strong><root>/cmd/set</strong> Send a command-line string to be executed. Multiple commands can be separated with <code>\r\n</code></span>
<!-- removeIf(!curtain) -->
- <strong><root>/curtain/set</strong> Set the curtain opening value (0-100), 0 means closed, 100 opened. "on", "off", "pause" pilots buttons.<br>
<spanclass="module module-curtain">- <strong><root>/curtain/set</strong> Set the curtain opening value (0-100), 0 means closed, 100 opened. "on", "off", "pause" pilots buttons.<br></span>
<!-- endRemoveIf(!curtain) -->
<!-- removeIf(!light) -->
<spanclass="module module-color">- <strong><root>/rgb/set</strong> Set the color using this topic, your can either send an "#RRGGBB" value or "RRR,GGG,BBB" (0-255 each).<br></span>
<spanclass="module module-color">- <strong><root>/hsv/set</strong> Set the color using hue (0-360), saturation (0-100) and value (0-100) values, comma separated.<br></span>
<spanclass="module module-color">- <strong><root>/brightness/set</strong> Set the brighness (0-255).<br></span>
<spanclass="module module-color">- <strong><root>/channel/#/set</strong> Set the value for a single color channel (0-255). Replace # with the channel ID (starting from 0 and up to 4 for RGBWC lights).<br></span>
<spanclass="module module-color">- <strong><root>/mired/set</strong> Set the temperature color in mired.<br></span>
<spanclass="module module-light">- <strong><root>/rgb/set</strong> Set the color using this topic, your can either send an "#RRGGBB" value or "RRR,GGG,BBB" (0-255 each).<br></span>
<spanclass="module module-light">- <strong><root>/hsv/set</strong> Set the color using hue (0-360), saturation (0-100) and value (0-100) values, comma separated.<br></span>
<spanclass="module module-light">- <strong><root>/brightness/set</strong> Set the brighness (0-255).<br></span>
<spanclass="module module-light">- <strong><root>/channel/#/set</strong> Set the value for a single color channel (0-255). Replace # with the channel ID (starting from 0 and up to 4 for RGBWC lights).<br></span>
<spanclass="module module-light">- <strong><root>/mired/set</strong> Set the temperature color in mired.<br></span>
<!-- endRemoveIf(!light) -->
- <strong><root>/status</strong> The device will report a 1 to this topic every few minutes. When MQTT broker detects that we disconnected, it will be set to 0.<br>
- Other values reported depend on the build options or the heartbeat settings (for example, <strong>firmware</strong>, <strong>version</strong>, <strong>hostname</strong>, <strong>IP</strong>, <strong>MAC</strong>, signal strenth (<strong>RSSI</strong>), <strong>uptime</strong> (in seconds), <strong>free heap</strong> and etc.)
@ -1158,16 +1163,48 @@
</div>
<divclass="pure-control-group">
<label>Use JSON payload</label>
<label>Default QoS</label>
<selectclass="pure-input-2-3"name="mqttQoS">
<optionvalue="0">0: At most once</option>
<optionvalue="1">1: At least once</option>
<optionvalue="2">2: Exactly once</option>
</select>
<spanclass="pure-form-message">
Level of assurance for delivery of the outgoing messages. Notice that messages are not (currently) cached on the device, QoS levels >0 only guarantee delivery <strong>after</strong> the broker receives the message.
Store the last published message (including the device <strong>status</strong>) on the server, so it can be delivered to any future subscribers that match the message topic.
All messages (except the device status) will be included in a JSON payload along with the timestamp and hostname
and sent under the <strong><root>/data</strong> topic.<br>
Messages will be queued and sent after 100ms, so different messages could be merged into a single payload.<br>
Subscriptions will still be done to single topics.
Causes all single <strong><topic></strong> messages published by the device, except the device status, to be sent in a JSON payload. For example:<br>
All messages will be queued and sent with a delay (100ms by default). Notice that all nested <strong><topic>: <message></strong> are published as-is, only the heartbeat payload will include all of topics at once.
</span>
</div>
<divclass="pure-control-group">
<label>Topic name</label>
<inputtype="text"name="mqttJson">
<spanclass="pure-form-message">
JSON message will be sent to <strong><root>/<name></strong> topic (<strong>data</strong> by default).
Sonoff 433 RF Bridge & RF Link Configuration<br><br>
This page allows you to configure the RF codes for the Sonoff RFBridge 433 and also for a basic RF receiver.<br><br>
<h1>RF BRIDGE</h1>
</div>
<divclass="page">
<details>
<summary>
Configuration
</summary>
Configure RF code associations for a basic 433 RF recevier, or the device like Sonoff RFBridge 433.<br><br>
To learn a new code click <strong>LEARN</strong> (the Sonoff RFBridge will beep) then press a button on the remote, the new code should show up (and the RFBridge will double beep). If the device double beeps but the code does not update it has not been properly learnt. Keep trying.<br><br>
Modify or create new codes manually and then click <strong>SAVE</strong> to store them in the device memory. If your controlled device uses the same code to switch ON and OFF, learn the code with the ON button and copy paste it to the OFF input box, then click SAVE on the last one to store the value.<br><br>
Delete any code clicking the <strong>FORGET</strong> button.
<br><br>You can also specify any RAW code. For reference see <aclass="external"href="https://github.com/Portisch/RF-Bridge-EFM8BB1/wiki/Commands">possible commands for Sonoff RF Bridge EFM8BB1</a> (original firmware supports codes from <strong>0xA0</strong> to <strong>0xA5</strong>).
Maxim Prokhorov
2 years ago