Skip to content

Commit 6d8ea80

Browse files
authored
Update Berry.md
Formatting
1 parent 8518229 commit 6d8ea80

File tree

1 file changed

+6
-5
lines changed

1 file changed

+6
-5
lines changed

docs/Berry.md

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -594,11 +594,12 @@ Since v11.1.0.1, there is an easier way than registering a driver, and listening
594594
The function you attach to a topic pattern received **only** the matching MQTT messages, not all messages unlike `mqtt_data()` would.
595595

596596
The function takes the same parameters as `mqtt_data()`:
597-
- `topic`: full topic received from the broker
598-
- `idx`: not used
599-
- `payload_s`: payload as string, usually converted to JSON with `import json json.load(payloas_s)`
600-
- `payload_b`: payload as a binary payload, bytes() array
601-
- the function should return `true` if the event was parsed or if the event should not trigger a Tasmota command. If you return `nil` or nothing, it is considered as `true` which is the usual behavior you want (i.e. not trigger a Tasmota command from random MQTT messages).
597+
* `topic`: full topic received from the broker
598+
* `idx`: not used
599+
* `payload_s`: payload as string, usually converted to JSON with `import json json.load(payloas_s)`
600+
* `payload_b`: payload as a binary payload, bytes() array
601+
602+
the function should return `true` if the event was parsed or if the event should not trigger a Tasmota command. If you return `nil` or nothing, it is considered as `true` which is the usual behavior you want (i.e. not trigger a Tasmota command from random MQTT messages).
602603

603604
Tasmota Function|Parameters and details
604605
:---|:---

0 commit comments

Comments
 (0)