Skip to content

Troubleshooting

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

Troubleshooting

Home › Troubleshooting

Contents

The JSON card reports a parse error

Check the token is the response body, not a URL, blank value or error page. Ensure straight double quotes, commas and matching brackets; no comments or trailing comma. Paste a small valid example from JSON basics into the same card. If that works, inspect the original source and its network response. Build allows a blank existing value; Read does not.

A token is invalid or has the wrong type

Check each path points to an existing value and the text, number or yes/no slot matches its JSON type. A numeric string is not a number and an object is not text. For an optional property, a valid path with no match can produce undefined and Homey may reject the token. Test optional fields in a separate card and handle its error. Blank paths instead use defaults; see defaults.

I get zero, false or a blank value unexpectedly

Check the path was entered in the correct numbered field, spelled with matching case, and that array indexes start at zero. Try an explicit bracket path for unusual names. Defaults may also represent an invalid path, so test against a known nonzero or true value before trusting it. See read paths.

A nested Build result appears in the wrong place

Build's dot writer does not descend into an existing truthy parent. Inspect the JSON output; use a JSON-value card to insert the complete nested object, or a suitable JSON-aware tool. See Build paths.

The loop does not run, repeats too often or times out

Save and enable the trigger Flow first. Select the same name on both cards; if using the Tag field, leave the selected name empty. Verify the collection is a JSON array or object, not a quoted JSON string. Start with two items and check the matching typed item token and zero-based index. Reduce collection size and slow actions when Homey reports limits or a timeout. Check success/error connections and avoid retrying actions that have already changed external devices.

A stored value disappears or updates conflict

The JSON token is not persistent storage. Explicitly save it and read it back; use a text variable or another suitable storage system. Avoid simultaneous read-modify-write runs, which can overwrite each other. See storage.

If a small reproducible test still fails, consult the community topic or open an issue. Include app version, Homey version, sanitized example JSON, card paths, expected and actual results; remove personal data and secrets.

Clone this wiki locally