Skip to content

Flow Examples

Arie J. Godschalk edited this page Nov 15, 2026 · 4 revisions

Multi-app workflows

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.

Extract MQTT sensor readings into BLL variables

In this MQTT walkthrough, a JSON Handler card extracts several fields and BLL saves the numeric result tags:

JSON Handler extracting CO2, IAQ and GASres into three BLL number variables

Community Flow screenshot: selected JSON properties are saved into separate BLL number variables.

  1. Trigger the Flow when your MQTT app receives the relevant message.
  2. Pass the received JSON text to JSON Handler's reading action.
  3. Configure numeric paths such as $.CO2, $.IAQ and $.GASres.
  4. 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.

Log the running state of many Chronograph timers

This timer-status example combines JSON Handler's loop, Chronograph's running-state condition, a BLL text accumulator and Simple (Sys) LOG:

Looping over timer names and collecting running states in a BLL text variable

Community Flow screenshot: timer names are iterated, tested, and appended to one BLL text report.

The steps are:

  1. Clear a BLL text variable used for this report.
  2. Start a wait-until-complete loop over a JSON array of timer names.
  3. Within the loop, check whether the timer named by the current item is running.
  4. Append its name and true or false to the report, followed by a line break.
  5. 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.

Keep a formatted decimal intact in an HTTP request

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.

  1. Read the numeric input.
  2. Format it with two decimals and the separators expected by the recipient.
  3. 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.

Clone this wiki locally