Skip to content

Troubleshooting

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

Troubleshooting

Home · Getting started · Flows · Examples

Work through the checks in order. Card labels may vary slightly with your Homey language or Chronograph version.

Contents

A name is missing or the card says “New”

  1. Check that the name is used by a saved, enabled Flow for the same chronograph type.
  2. Confirm that the spelling and capitalization match. A stopwatch, timer and transition can share a name, but they are separate instances.
  3. If both Pick and Name are filled in, clear the picker or select the intended entry; the picker takes precedence.
  4. Save the Flow again and reopen the card's name picker.

The picker is a convenience, not a separate chronograph setup page. You can type a fixed name in the Name field. Avoid a wildcard or a changing token when you want a device or widget to refer to one specific chronograph.

The historical forum discussion about a transition name is an example of a name being shown as “New” while a Flow was being edited. Its Homey and app versions are older; use the checks above for the current picker behavior.

A timer does not restart when motion is detected again

  1. Check that the motion Flow runs on every detection, not only the first one.
  2. In that Flow, use Start or replace timer with the same fixed name and duration on every run.
  3. In a separate Flow, use Timer is finished for that exact name to switch off the light or fan.
  4. Test by triggering motion again before the countdown ends. The timer should restart from its full duration; the finish action should happen only after the last restart.

Use Start or resume timer when a paused timer should continue instead of starting a fresh countdown. If the sensor already provides a suitable “no activity for…” trigger, that may be simpler than a separate timer. See the community discussion about retriggering a timer for the original scenario and sensor-zone context.

A timer finishes immediately or at the wrong time

  1. Check the duration value and selected unit on Start or replace timer. The duration must evaluate to a positive number.
  2. Check any MathJS expression and Flow tokens in the duration field. Confirm the token is numeric and the selected unit is what you intended.
  3. Check that a later Flow is not replacing or adjusting the same timer.
  4. If you use Adjust timer, remember that it changes elapsed time: a positive adjustment makes the timer finish sooner; a negative adjustment gives it more time, up to the amount already elapsed.
  5. Test with a simple fixed duration, such as 2 minutes, and verify the finish trigger before adding expressions or other conditions.

A Flow action or condition reports that no chronograph exists

  1. Confirm a start Flow has run for the same type and exact name.
  2. Check whether the timer or transition has already finished, or another Flow has stopped it. Finished and stopped instances are removed.
  3. A paused instance still exists; use the matching resume action, not a new “resume existing” action on a finished timer.
  4. If you use a wildcard, check that it matches at least one current name. Wildcards are case-sensitive.

Conditions that inspect a duration need an active or paused instance. An already paused chronograph is not “running”; use the inverted running condition if you want to test for “not currently running.”

A transition runs but the light does not change

  1. Create and enable a Flow with Transition reached a step for the same transition name.
  2. Connect its Transitionvalue output to the target device's dim-level argument. The device may expect a different range; check its card and test a known value before running a long transition.
  3. Confirm the device action works on its own with a fixed value.
  4. Start the transition and check Homey's Flow timeline or a temporary diagnostic action to confirm the step Flow receives values.
  5. Save the threshold/step Flow before starting the chronograph. Short transitions may use fewer intermediate steps than requested; a busy Homey or a device integration may also delay visible changes.

Chronograph produces the values and runs the trigger; it does not operate a light by itself. A complete dimming example shows the exact token connection. A historical forum report about missing transition steps describes one user's older setup; it is not a guarantee that every step will be visible on every device.

A stopwatch, timer or transition device is unavailable

  1. Check the device type and name selected during pairing.
  2. Keep a saved Flow card that refers to that exact type and fixed name. The device becomes unavailable if no relevant saved start, start-or-resume or trigger card still refers to it.
  3. Save and enable the Flow, then check device availability again.

For a device's Start / Stop control to create a chronograph, first start it once with a Flow so the device has the last start values to reuse. See the device guide and the type-specific device pages.

A Flow does not run at the expected interval

  1. Set Every interval to a whole number of at least 1 and select seconds, minutes, hours or days.
  2. Check that the Flow is enabled and that its trigger arguments are valid.
  3. If the app or Homey was stopped when a deadline passed, expect one run after startup, not one run for every missed interval.
  4. Check Homey's Flow timeline and system load. A busy Homey can delay a scheduled run.

Flows with the same interval share a schedule. Intervals are measured from their schedule start; they are not aligned to the clock.

A widget shows no chronograph or a control is missing

  1. Select the correct type and name in the widget settings.
  2. Save an enabled Flow that uses that name if it is missing from the picker.
  3. Confirm that your Homey software is version 12.3.0 or later. These dashboard widgets are not supported on Homey Cloud.
  4. If a button or field is hidden, switch to the Default design and check the selected design's visibility rules for the current size and state.
  5. For a timer or transition start form, enter a valid duration; transitions also need numeric start/end values and at least two steps.

See Dashboard widgets for setup and Widget designer for visibility and layout.

A HomeyScript or app integration fails

  1. Confirm the app ID is nl.fellownet.chronograph and the caller has the required Homey permission.
  2. Use the current name-based endpoint and URL-encode the chronograph name.
  3. Check that the chronograph exists; it may finish between a list request and a later read or update.
  4. Use the current HomeyScript methods such as get({ path }) and post({ path, body }), not older apiGet or apiPost examples.

See the API reference for current requests and error behavior.

Clone this wiki locally