Repository navigation
Variables
Home · Getting started · Flow cards
BLL stores named values that can be used in Flow cards and, for supported types, as Homey tags.
| Type | Use |
|---|---|
| String / text | Store text, such as a status. |
| Number | Store a count or measurement. |
| Boolean / yes-no | Store a true/false state. |
| Trigger | Represent an event that can be executed from a Flow or device. |
In app settings, Variables lets you add, search, inspect, edit and delete variables. The list includes the name, value, type, last-set time and whether the variable was automatically created. Number variables can have Insights.
The community settings guide illustrates adding a variable. This screenshot is from an earlier version:
Historical screenshot from the community guide: use the current Variables settings controls to add a name and choose its data type.
A variable created in settings is managed manually. In compatible typed Flow cards you can type a new name, select the create option and save the Flow; BLL creates it automatically. Save the Flow before looking for its tag.
Automatically created variables may be removed when no longer referenced by the relevant BLL Flow cards. A reference typed into an expression, an external app, or a device is not a substitute for a saved variable selector. For data that must persist independently, create the variable in settings.
Deleting a variable can break Flows and integrations that use it. Check dependencies and make an export before deleting variables or using Delete All.
Use Export and Import in Variables settings to copy variable data. Keep exports somewhere private: names and values may contain sensitive information. Test your recovery procedure before making destructive changes. Import can affect the existing variable collection; do not assume it is a safe merge. Export first and check your Flows and values afterwards. The Get all variables Flow action also supports export formats; see App settings.
Choose meaningful, distinct names and use the correct variable type for each card. When an existing variable is selected, keep its name and type consistent across Flows, devices and API calls. Changing or removing a variable does not automatically repair those references.
For lists, store JSON in a text variable rather than trying to create an array variable type; see lists and rolling history. Use timestamp and freshness examples when deciding whether a stored sensor reading is still suitable for a calculation.
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!
