Repository navigation
Flow Examples
Examples · Flow cards · Supported apps
These community examples combine BLL variables with other apps. A companion
app's ability to send a tag to BLL does not mean all its text fields
support {[ ... ]} coding.
In this MQTT walkthrough, a JSON Handler card extracts several fields and BLL saves the numeric result tags:
Community Flow screenshot: selected JSON properties are saved into separate BLL number variables.
- Trigger the Flow when your MQTT app receives the relevant message.
- Pass the received JSON text to JSON Handler's reading action.
- Configure numeric paths such as
$.CO2,$.IAQand$.GASres. - Set the corresponding BLL number variables from the resulting number tags.
The original screenshot starts with a sample tag rather than a live MQTT trigger. For example, an adapted payload is:
{"CO2":913,"IAQ":84.54,"GASres":1937}The follow-up correction is important: use a card that reads/selects JSON properties, not one that sets properties inside a JSON document. The latter constructs JSON; it does not extract sensor values.
Verify actual payload names and types, handle missing/invalid readings, and test against a sample message first. Connect a receipt-timestamp action if you also want freshness checks.
This timer-status example combines JSON Handler's loop, Chronograph's running-state condition, a BLL text accumulator and Simple (Sys) LOG:
Community Flow screenshot: timer names are iterated, tested, and appended to one BLL text report.
The steps are:
- Clear a BLL text variable used for this report.
- Start a wait-until-complete loop over a JSON array of timer names.
- Within the loop, check whether the timer named by the current item is running.
- Append its name and
trueorfalseto the report, followed by a line break. - After the loop completes, send the accumulated report to the log.
The original uses Shift+Enter to insert line breaks after the state text. An adapted input list could be:
["HallTimer","KitchenTimer","GardenTimer"]Adding another name to the list does not require duplicating the check cards. Use sequential iteration when updating a shared accumulator, and prevent overlapping report runs from clearing or overwriting each other's text. Decide how to report a missing timer rather than silently treating an error as a valid stopped state.
A heating-controller question
requires values such as 24.50, including the trailing zero.
The confirmed advice
is to keep the formatted result as text, either in a text variable
or a temporary formatted tag.
- Read the numeric input.
- Format it with two decimals and the separators expected by the recipient.
- Pass the text result to the HTTP card without converting it back to a number.
See fixed decimals and spreadsheet separators for expressions and the No Grouping option. The transport app only needs to accept the resulting text; it need not decode BLL coding.
Use a harmless test endpoint first and keep credentials out of shared
examples. For a JSON request, "24.50" and 24.50 have different types:
match the recipient's schema rather than forcing everything to text.
Support development - If Better Logic Library is useful to you, you can support its
continued development through GitHub Sponsors,
Patreon,
PayPal, or
bunq.
Thank you!

