Skip to content

Maps Examples

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

Home / Flows / Flow examples

Maps examples

Start with Google Maps setup. These examples use public locations and manual starts in Advanced Flow. Add a Maps device for the first and third examples. The fresh-estimate condition does not need one. Save each Flow before testing it. Avoid putting private routes or full error logs in public screenshots.

Look up a route once

Manual start connects to the one-off Maps action, then connects the travel time and distance to a notification

Illustration: both numbers in the message come from the action in this run.

  1. Add a Maps device if you don't already have one. Connect Start to its Calculate a one-off Google Maps route action. It ignores the saved trip.
  2. Set From to 52.3780, 4.9008 and To to 52.3600, 4.8852 (public coordinates in Amsterdam). Choose the typed entry for each. Set Mode to Foot.
  3. Connect the action's success path to a Homey notification action. In its message, insert Travel time (min) followed by min, and Distance (km) followed by km. Optionally add Open in Google Maps if you want to open directions.
  4. Connect the action's error path to a separate notification, such as Maps estimate failed; check the key and route. Save and run.

Expect a time and distance, not fixed numbers. If you get the error, try a public route with known access and check Maps troubleshooting. This action does not change devices or request an image.

Compare a fresh estimate

Fresh route condition sends distinct messages for estimates over 20 minutes, estimates at or below 20 minutes, and errors

Illustration: “not longer” and “could not calculate” are different outcomes.

  1. Add Google Services → A new route estimate takes longer than a limit (the app condition). Use the same coordinates and Foot mode as above. Set Minutes to 20. Connect a manual Start to the condition.
  2. Connect the true path to a notification with The walk is estimated to take more than 20 minutes. Connect the false path to The walk is estimated to take 20 minutes or less.
  3. Use the error path for Could not estimate the walk. Save and run. Expect one message for the path taken.

The condition compares the unrounded estimate and does not output the calculated minutes. Don't add this condition after the one-off action just to compare its result: that would request a second estimate. If you already have the action's Travel time (min) output, compare that token using a Homey Logic number condition instead.

Check a saved trip

Manual start goes to the saved-route refresh action; a separate refreshed trigger sends minutes to a notification

Illustration: the refresh action has no output tokens. The device trigger supplies the minutes.

  1. Add a Maps device. For a practice route, use the public coordinates above with Walking and leave Show route image off.
  2. In an Advanced Flow, connect a manual Start to the device's Refresh saved Google Maps route. For error handling, connect the action's error exit to a notification such as Saved trip refresh failed. Check the Maps device.
  3. In the same Advanced Flow, add the separate Saved route refreshed trigger on that device. Connect it to a notification action. In the message put Saved trip: , the trigger's Travel time (min) token and min. Save. Press the manual start or the device's Refresh route.
  4. Expect a new Last refreshed reading and a message with the current minutes, even on the first successful refresh. The trigger paths are independent: don't connect either trigger back to a refresh on the same device.

To notify only over a threshold, insert the device condition Travel time exceeds a limit between the refreshed trigger and the notification, set it to 20 and connect the true path. If testing outside the refreshed path, check Saved route results are available first and remember that a stored reading can be old.

To report changes rather than every result, use Travel time changed and put Previous travel time (min), Travel time (min) and Travel time change (min) into the message. It needs two different readings. To report errors from device-button refreshes too, use Saved route refresh failed → Error in a private notification instead of the action-only error message.

Once the manual test works, you can replace Start with one daily time trigger. Each scheduled refresh can count towards usage and billing; avoid frequent schedules or automatic retry loops.

Clone this wiki locally