Skip to content

Flow Examples

Arie J. Godschalk edited this page Nov 19, 2026 · 7 revisions

Multi-app workflows

Examples · Flow cards · Supported apps

This page includes a live BLL example and community workflows that 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.

Contents

Live BLL variables, devices, and Flow

This example was created and tested in English on HP2023 with BLL v4.3.0 Development. It demonstrates four variable types, the three BLL devices, and a regular Flow that updates a count and status when the Trigger device is pressed.

Create these variables in BLL app settings:

Name Type Initial value
Wiki Example Status String Watering complete
Wiki Example Count Number 3
Wiki Example Enabled Boolean true
Wiki Example Event Trigger No value; it represents an event

Pair the devices in the Wiki sub-zone under the Better Logic Library zone:

Device Linked variable Configuration
BitFlip Wiki Example Enabled The tile starts on (true).
NumSlide Wiki Example Count Minimum 0, maximum 10, step 1.
Trigger Wiki Example Event Pressing the device executes the trigger variable.

Three paired BLL example device tiles in the Wiki sub-zone: Wiki Example Count, Wiki Example Enabled, and Wiki Example Event

Live device tiles: BitFlip is on, alongside NumSlide and Trigger. The NumSlide range is configured from 0 to 10 in steps of 1.

Create and save a regular Flow in My Flows > Better Logic Library > Wiki:

  1. When: Better Logic Library — Wiki Example Event is set.
  2. Then: Increment Wiki Example Count by 1.
  3. Then: Set Wiki Example Status to The trigger button was pressed.
  4. Press the Trigger device in the Wiki zone.

Live BLL Flow canvas with the Wiki Example Event trigger, count increment, and status update actions

Live Flow: setting the trigger increments the number variable before setting the status variable.

After one press, the count changes from 3 to 4, the status changes to The trigger button was pressed, and the trigger variable's last-set time updates. Wiki Example Enabled remains true. To repeat the test, restore the count to 3 and the status to Watering complete, then press the device again. The app settings list and complete variable details are shown in Variables.

Extract MQTT sensor readings into BLL variables

Better Logic Library Flow card example: Extract and store a reading

Actual Homey card examples, saved but disabled. They have not been run; follow this page for the full setup and connections.

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

  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 linked forum example 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

Better Logic Library Flow card example: Log the running state of many Chronograph timers

Actual Homey card examples, saved but disabled. They have not been run; follow this page for the full setup and connections.

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

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

Better Logic Library Flow card example: Fixed decimals for HTTP and spreadsheets

Actual Homey card examples, saved but disabled. They have not been run; follow this page for the full setup and connections.

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