Repository navigation
Troubleshooting
Home · Getting started · Flows · Examples
Work through the checks in order. Card labels may vary slightly with your Homey language or Chronograph version.
- A name is missing or the card says “New”
- A timer does not restart when motion is detected again
- A timer finishes immediately or at the wrong time
- A Flow action or condition reports that no chronograph exists
- A transition runs but the light does not change
- A device is unavailable
- A Flow does not run at the expected interval
- A widget shows no chronograph or a control is missing
- A HomeyScript or app integration fails
- Check that the name is used by a saved, enabled Flow for the same chronograph type.
- Confirm that the spelling and capitalization match. A stopwatch, timer and transition can share a name, but they are separate instances.
- If both Pick and Name are filled in, clear the picker or select the intended entry; the picker takes precedence.
- 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.
- Check that the motion Flow runs on every detection, not only the first one.
- In that Flow, use Start or replace timer with the same fixed name and duration on every run.
- In a separate Flow, use Timer is finished for that exact name to switch off the light or fan.
- 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.
- Check the duration value and selected unit on Start or replace timer. The duration must evaluate to a positive number.
- Check any MathJS expression and Flow tokens in the duration field. Confirm the token is numeric and the selected unit is what you intended.
- Check that a later Flow is not replacing or adjusting the same timer.
- 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.
- Test with a simple fixed duration, such as
2minutes, and verify the finish trigger before adding expressions or other conditions.
- Confirm a start Flow has run for the same type and exact name.
- Check whether the timer or transition has already finished, or another Flow has stopped it. Finished and stopped instances are removed.
- A paused instance still exists; use the matching resume action, not a new “resume existing” action on a finished timer.
- 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.”
- Create and enable a Flow with Transition reached a step for the same transition name.
- 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.
- Confirm the device action works on its own with a fixed value.
- Start the transition and check Homey's Flow timeline or a temporary diagnostic action to confirm the step Flow receives values.
- 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.
- Check the device type and name selected during pairing.
- 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.
- 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.
- Set Every interval to a whole number of at least
1and select seconds, minutes, hours or days. - Check that the Flow is enabled and that its trigger arguments are valid.
- If the app or Homey was stopped when a deadline passed, expect one run after startup, not one run for every missed interval.
- 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.
- Select the correct type and name in the widget settings.
- Save an enabled Flow that uses that name if it is missing from the picker.
- Confirm that your Homey software is version 12.3.0 or later. These dashboard widgets are not supported on Homey Cloud.
- 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.
- 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.
- Confirm the app ID is
nl.fellownet.chronographand the caller has the required Homey permission. - Use the current name-based endpoint and URL-encode the chronograph name.
- Check that the chronograph exists; it may finish between a list request and a later read or update.
- Use the current HomeyScript methods such as
get({ path })andpost({ path, body }), not olderapiGetorapiPostexamples.
See the API reference for current requests and error behavior.
Support development - If Chronograph is useful to you, you can support its
continued development through GitHub Sponsors,
Patreon,
PayPal, or
bunq.
Thank you!