Repository navigation
Integrations
Home › Integrations
- App-specific guides
- Storage and privacy
- HTTP and MQTT data
- FTP file lists
- Better Logic Library
- HomeyScript
- FTP Client: supply file lists for a collection loop.
- Device Capabilities: display the loop's images on an AVD.
- Better Logic Library: store JSON between runs.
- HomeyScript: pass a built JSON object into a script.
Build and Read operate on their supplied values and return Flow tokens. They do not automatically persist a JSON document, fetch a URL, write a file, or maintain a database. Loop bookkeeping and names are in memory; do not rely on them surviving an app restart. To keep a result, explicitly save the JSON text with a suitable variable or storage app; retrieve it again before the next update. Concurrent read-modify-write Flows can overwrite each other's changes, so serialize updates where possible.
The app logs action arguments and errors. Avoid secrets and personal information in JSON and diagnostic reports; never publish credentials.
First obtain the response body/message with a separate compatible HTTP or MQTT app or card. Connect its JSON text token to Existing JSON on Read. Check that the received body is complete, valid JSON and that the selected paths have the right types. JSON Handler does not perform the network request. A community MQTT example uses a received message before extracting fields; adapt paths and types to your own payload rather than copying assumptions about a sensor.
Install and configure FTP Client and verify a folder with known image files. Its Get files (JSON) output feeds the loop action's Collection. The loop trigger's Item as text goes to the image-token action's path input. For exact steps and a virtual-camera example, see FTP Client: process several images. The original developer example explains the same connection. Use only files you are authorized to access.
Store JSON text in a BLL text variable if you need it later. The list and JSON guide explains initialization, updates and concurrency; its pipe-splitting example shows how returned property names relate to Read paths. Keep JSON as data, not executable JavaScript.
Pass Build's JSON token as a script argument and parse it with
JSON.parse(args[0]); see the copyable example.
Do not confuse JSON Handler's Flow cards with HomeyScript API methods.
Support development - If JSON Handler is useful to you, you can support its
continued development through GitHub Sponsors,
Patreon,
PayPal, or
bunq.
Thank you!