Skip to content

Troubleshooting

Arie J. Godschalk edited this page Nov 15, 2026 · 1 revision

Troubleshooting

Home · Getting started · Flows · Variables · Devices

Start with the exact Flow card, variable type, and app version. Change one thing at a time and test with a harmless variable before applying a fix to a production Flow.

A Flow does not start

  1. Confirm the Flow is enabled and its trigger event actually occurs.
  2. Check that the selected variable still exists and has the expected type.
  3. For A variable changed, confirm the value actually changed; use A variable is set when same-value writes matter.
  4. For A number variable changed, check direction and minimum amount against old/new values.
  5. For a sustained trigger, confirm the condition stays true for the entire duration; writes can restart the timer.
  6. For global/debug triggers, use a selected-variable trigger as a control test. Current source registers a false-returning listener on the global trigger cards, so verify their behavior on your installed version.

A condition is always false

  1. Check that the variable type matches the condition.
  2. For text conditions, check spaces and case. Comparisons are case-insensitive, but spaces remain significant.
  3. For number cards, greater-than and less-than are strict; equality is exact.
  4. Confirm the syntax: Math.js uses $VariableName$; BLL expressions do not use {[ ]}; embedded text coding does.
  5. Test the expression in BLL settings and check that it returns a boolean.

A variable disappears or a device breaks

Variables created through a Flow selector may be removed when no longer referenced by the relevant saved cards. Device and free-text references do not necessarily keep them alive. Create important variables manually in settings, then check type and name before pairing or editing a device.

A device does not follow its variable

  • BitFlip: verify the variable is boolean.
  • NumSlide: verify it is number and within the selected slider range. The driver writes values directly and does not clamp other Flow/API updates.
  • Trigger: verify it is still type Trigger.

If the variable is correct, open device settings and re-pair if needed.

A formatted tag is blank or unexpected

Check the output token type and the receiving card’s argument type. A formatted date, number, or duration is text. Base64 is encoded, not encrypted. CSV Base64 has a result-property mismatch in the 4.2.3 development source; use ordinary CSV or test your installed version.

A file download fails

A file-server link is temporary and can expire after the configured availability time. Generate a fresh link, verify the server is running, and keep the link private. Do not expose the server to the public internet.

More help

Clone this wiki locally