Changelog

• Add [[relative_effort]] as an additional statistic. Only available for Strava subscribers.

• Fix bug in creating goals where the fractional separator (e.g. 1.6km) was ignored and caused a 10x increase in the saved value (16km)

• Add support for swim intensities in [[wkt_steps]]
• Add new [[wkt_notes]] field to insert workout notes into description or private notes. This feature is experimental and may not work properly.

• Fix bug where using a countup/countdown counter in an equation used a value of 0 for the counter instead of the correct value.

• Add elapsed time as a match condition for upload rules

• Add new statistic [[gap]] to provide the average GAP for running activities

• Add additional counter increment option: lap_count

• Fix bug where double quotes in gear name would make you unable to select the gear for update or comparison

• Fix bug in expression parsing where the new number formatting feature causes expressions to be evaluated incorrectly

• Add [[activity_profile]] stat which has the name of the activity profile used to record the activity (requires Garmin/wahoo connection)

• Fix bug in workout parser ([[wkt_steps]]) where "until lap press" was repeated twice

• Added new settings to customize number formatting. You can now specify the thousands and decimal separator so numbers are displayed appropriately for your locale.
• Fixed a bug in [[wkt_steps]] where distance-based steps would display an incorrect distance.

• Display a warning about test rule not working as expected for any fields requiring data from a FIT file

• Fix a bug in the activity processing logic which could cause some activities to not be processed with the error "Not processed. Too many activities in 15 minutes."

• Fix issue where location may be set incorrectly after clicking a new location on the map
• Fix issue where you would have to click a second time to open the location picker again after saving a location

• Attempted fix for missing dropdowns on the add rule page in rare cases

• Fix cases where using rounding functions in certain stats could cause data to show up as missing (appears as a -). All cases are ones where additional data (power, temperature) need to be retrieved for an activity.
• Fix issues found when editing rules with certain special characters where the rule data would not populate correctly.

• Fix [[photo_count]] statistic to use the correct number of photos

• Add support for goal streaks to be used in expressions

• Added battery status comparison and statistic which can be used to display or compare against the battery status of your saved ANT+ sensors. A FIT file (Garmin/Wahoo connection) is required for this feature. The new statistic is [[battery_status:<Sensor>]] where <Sensor> is one of your saved sensor names. Battery status is one of New, Good, Ok, Low, Critical. You can also use the statistic [[battery_status:<Sensor>:emoji]] to insert battery status as an emoji (🟢 = New/Good, 🟡 = Ok, 🔴 = Low, Critical).
  • Note 1: Not all sensors provide battery status. Support for this feature depends on your device(s)
  • Note 2: For SRAM AXS only a single battery status is reported. It is unclear exactly which value it is (Front/Rear Derailleur, Shifters, Dropper) or whether it is always the lowest or just the status of one of the components.

• Fix bug in experimental [[wkt_steps]] statistic where some values weren't converted correctly.
• Update speed/pace display in [[wkt_steps]] to take activity type into account and show target pace as either a speed for cycling or pace for running/swimming.
• Remove leading 00: in the hours field for displaying average pace.

• Fixed a bug where some special characters in text comparisons (e.g. "X Contains <string>)" weren't loaded correctly when trying to edit the rule.

• Experimental Feature: Added new [[wkt_steps]] statistic which will insert a description of your workout in plain text. It currently only supports running and cycling activities, and a limited subset of the most common durations and targets. If you find any problems or unsupported workout features, or if you run workouts for other sports (swimming, weightlifting, etc...) and would like support added for them, please e-mail me (activityfix@gmail.com) a FIT file with the workout and a plain text description of what the workout should be. I'll do my best to support it.

• Add a setting to disable automatic adding of a space between multiple updates to description, title, or private notes. If enabled, you will need to write your rules to include a leading/trailing space as needed.
  Note: Default behavior is OFF so your rules should behave the same as before until you toggle the setting

• Fix bug introduced in v0.9.20240624.0 which broke other (non-temperature) unit conversions in stat comparisons.

• Add support for Strava's new hide start time option. As part of the change, "Hide Stats" has been changed to "Hide Details" to match Strava.

• Minor tweaks to manually entering rule order number to fix issues with iPhone auto zoom on input
• Fix bug where temperature comparisons were being done in mixed units (F/C) for users with temperature in Fahrenheit, resulting in invalid comparisons

• Allow rules to reordered by entering a number directly instead of dragging. To use, click on the order number on the My Rules page and enter the desired new order, then click the button

• Add time formatting options for counters using moving time and elapsed time. These are the same as the time format options for moving and elapsed time in stats.

• Minor bug fixes for displaying stat comparisons on the activity processing history page
• Bug fix where equations using counters weren't being evaluated correctly
• Added rounding support to equations using round(value, precision)

• Added a new type of counter increment -- "proximity" -- which will increment the counter by the number of times you enter the circle for the first Route Proximity condition in a rule. The most likely use case would be for counting repeats without relying on the lap button. For example if you want to track the number of times you've climbed a certain hill, create a counter which increments by proximity. Create a rule using that counter with a match condition of "Route proximity within 500m (or feet) of <top of the hill>." Every time you enter the location radius, the count will increment by 1.
• Added support for [[date z]] to the update preview on the add rule page

• Added [[wkt_name]] statistic to insert the name of the workout from the FIT file
• Added the ability to do arbitrary math as both a match condition and in updates to text fields (title, description, private notes).
• As a match condition: Select "Expression" as the match condition and enter a valid math expression with a comparison (<, >, ==, !=). Values in the expression can be any statistic or counter along with hardcoded values.
  Important: The counter values will be the CURRENT counter value (before it is updated by any rules). Meaning if the current counter value is 5 and one of your rules will match this activity and update the counter to 6, the value used in the expression will be 5.
• As an update to a text field, surround the expression with [= and =], i.e. [=EXPRESSION GOES HERE=]. As with the match condition, the expression can use any statistic, counter, or hardcoded value. Using a counter in an expression does not update its value.
  Important: Counter values here will be much more confusing. The counter value will be either the current value OR the updated value, depending on rule order. Updates are processed in order, so the counter value used will be whatever the counter's value is at the time the expression is evaluated. Some examples:
  • If rule #1 updates the counter and rule #2 has an expression using that counter, the expression will use the new (updated) value.
  • If rule #2 uses the counter in an expression and rule #3 updates it, the expression will use the current (old) value.
  • If a rule updates the counter AND uses it in an expression, the value will depend on if the expression is before or after the counter update. For example, if you had a counter with current value of 5 and had a rule which updates the description to
        "Counter value {{counter}}, 10x counter = [=10 * {{counter}}=], Counter second increment = {{counter}}, 10x counter = [=10 * {{counter}}=]"
    First the counter would be incremented from 5 -> 6 on the first use of {{counter}}, then the expression would be evaluated using the current value of 6, then the second use of {{counter}} would update the counter from 6 -> 7, then the second expression would be evaluted using the current value of 7. So the final update would be
        Counter value 6, 10x counter = 60, Counter second increment = 7, 10x counter = 70

• Released new upload rules feature. Please let me know if you run in to any problems, and my apologies in advance for any issues you run in to. I've been testing it for the past 2 weeks and haven't seen any issues, but I everyone has different ways of using things and different devices, apps, etc... so there may be issues I didn't find in testing.
• Fixed a bug with countdown counters where the date used for calculation was the current date instead of the activity date. This would only be a problem if activity upload was delayed by > 1 day.

Feature Preview - Upload Rules

• Additional backend changes for upcoming feature. Details and a demo video will be released within the next week after some additional testing.

• Fix a bug where if a person has multiple rules which hide stats, only the stats from first matching rule would be hidden.

• Minor bug fixes from the previous release:
  • Fix issue where changing a toggle from the My Rules page would occasionally fail
  • Fix bug in FIT processor where Garmin BCM3 sensor wasn't detected properly
  • Fix database error when adding a new rule to the database
• FIT processor updates

• Backend changes to support an upcoming feature. If you notice any issues with your rules or the website please let me know (activityfix@gmail.com)

• Fix a bug where toggling a slider on the My Rules page would occasionally cause an error and fail

• Add new statistics: [[avg_cadence_spm]], [[photo_count]], [[lap_count]]
• Add [[end_date FORMAT]] to insert the activity end date into title/description/private notes

• Added [[perceived_exertion]] as an additional statistic and match field
• Added rounding options (:r, :ru, :rd) for counters. These are the same rounding options that already exist for stats. E.g. {{counter_name:ru}}. :r will do standard rounding to the nearest whole number, :rd will always round down (floor), :ru will always round up (ceiling).

• Fix bug where using [[weight]] with the weight source as FIT file would still use the weight from Strava
• Added a series of tutorial videos for ActivityFix. Check out the playlist!

• Fix bug where editing a counter without advanced options visible would cause errors in max increments

• Add additional counter reset option for number of days, and change max increments/day to be max increments/X days
• Hide advanced counter options by default to attempt to reduce confusion on counters

• Fixed issue with [[fit_name]] not working after previous update

• (Hopefully) fixed issues with the new FIT file processor. Please let me know if you see any issues with processing your rules

• Added option to specify weight source as Strava or FIT file
• Added support for Stryd CP (FTP) and Weight. If you have your preference for FTP or Weight set to FIT file, the value from Stryd will be used instead of the Garmin/Wahoo value
• Full rewrite of the FIT file parser. If you notice any difference in behavior for your rules using data from FIT files please let me know (activityfix@gmail.com)

• Fixed bug where certain special characters in goal names could cause the add rule page to load incorrectly

• Fixed [[date]] statistic to use the activity's timezone instead of UTC

• Added option to limit the number of increments per day on counters. The counter can still be used normally but will only increment up to the specified number of times per day. Any additional rule matches will show the current value but will not increment it.
• Added additional "m:s" option to display durations in minutes:seconds format when using stats with time (e.g. pace, moving time, ...)
• Update Garmin and Wahoo activity matching to be more accurate (hopefully)
• Fix bug where editing a rule using gear in a match condition wouldn't pre-populate the rule data correctly

• Added elapsed_time as an additional counter option
• Fixed display of reset frequency on my counters page
• Fix bug where "/" in a rule name caused the add rule page to load incorrectly

• Added special case for Starting/Ending Location match conditions to detect a loop or point-to-point route. You can enter "Start" or "End" as the location to match. For example:
  • "Starting Location within 1000 meters of End" will match if your activity starts and ends in approximately the same location (i.e. a loop).
  • "Starting Location not within 1000 meters of End" will match if your activity starts and ends in in different locations (i.e. a point-to-point route).

• Added new match condition "Previous Rule" which will allow you to create a dependency on another previously run rule.
• Added a warning dialog when testing a rule to say it won't work properly if the rule requires a FIT file.
• Add support for semi-custom number formatting in counters and stats. Any numeric stat or counter use can be followed by ":%<format>" to provide a specific number format using a limited set of flags from sprintf. E.g. to print a 3 digit counter with leading 0s you would use [[counter_name:%03d]].
• Fixed backend issue which would occasionally cause processing of old activities to get stuck.

• Fix issue where the wrong units were used for some statistics comparisons

• Added match condition for # of laps

• Fixed a bug where "is not" comparisons on combined activities wouldn't match correctly

• Changed all dropdowns in the Add Rule page to be searchable to make rule creation easier
• Added combined activity types to the activity type match. These should make it easier to match against multiple activities of the same type, or to create a rule which applies to all activities. The combined activity types match the ones used by Strava (and ActivityFix) for goals.
  • Any Activity - Matches against any activity
  • All Ride - Matches Ride, Virtual Ride, Mountain Bike Ride, Gravel Ride, and Handcycle
  • All Run - Matches Run, Virtual Run, Trail Run, Wheelchair
  • All E-Ride - E-Bike Ride, E-Mountain Bike Ride

• Fixed a bug where some match options were unavailable if they were also used as updates
• Fixed an issue where an empty value in title/description prevented some rules from running

• Fixed a bug in FIT file parser which would only allow Garmin profile names of 16 characters
• Released new goals feature! Check out the video below for a short overview

• Major code cleanup and refactoring. If you see any unexpected behavior or problems with the site or your rules, please let me know (activityfix@gmail.com)
• Added support for an upcoming new feature: Goals
  • The goals feature will allow you to define daily, weekly, monthly, and yearly goals
  • Goals can be any combination of distance, elevation, moving time, calories, and number of activities
  • Each goal condition can be associated with one or more activities
  • Goal streaks can be used as a counter value in your rules
  • Goals will (hopefully) be released next week

• Added select all/none checkboxes to the process old activities page

• Fix bug where geolocation data (e.g. [[start_city]]) was not being found due to missing data from Strava
• Fix bug where occasionally timezones were not handled correctly

• Fix bug where comparisons and updates using new Strava activity types would occasionally fail

• Added new Strava activity types: Badminton, HIIT, Pickleball, Pilates, Racquetball, Squash, Table Tennis, Tennis, Virtual Row

• Changed the process old activities page to only show processing details for the most recent request. This change was made to avoid a memory issue for users who submit a large number of requests or process a lot of activities.
• Fixed a bug where estimated time to start processing a history request was incorrect.

• Fixed several instances where some special characters would not display correctly
• Fix bug where no rules would be shown on the my rules page if they are all disabled
• Added [[description]] and [[title]] to allow pre-filled activity fields (e.g. from Peloton) to be moved around. These will use the original value of the title and description from whatever device/software uploaded the activity
• Lots of backend updates and cleanup. If you see any unexpected behavior let me know, I've tested as thoroughly as possible but it's likely I missed something. A pre-emptive sorry for any inconvenience.

• Updates to handle separate run and cycle FTP for Garmin devices
• Backend fixes for processing old activities.
  • There was a backlog of requests due to an error which caused the processing task to stop unexpectedly. I apologize to anyone who was waiting for a pending request to complete. They should all be done now.

• Fix bug where rules using "route proximity not within" would not match correctly

• Added new statistics and match conditions for temperature: min_temp, max_temp, avg_temp. These use the temperature recorded by your device and will only work if your device provides temperature (generally everything except smartphones)
• Added additional setting to select your preferred temperature units. The default will match your Strava default measurement preference
• Fixed a bug where negative values weren't allowed for some comparisons where they should be

• Add new heatmap map type
• Fix bug with comparisons of duration-based statistics (avg_pace, moving_time, elapsed_time)
• Fix bug where durations entered could be off by 1s due to a rounding error (e.g. 5:08 could be incorrectly compared to 5:07)

• Add ability to match activities on any of the activity stats fields ([[stat_name]])
• Fix a bug where certain special characters in gear names would prevent rule creation and editing
• Fix a bug where trying to replace newlines in text didn't work

• Add option to delay activity processing for up to 15 minutes. Click on "Setings" from the menu to change your preference (default is 10 seconds).
• Add option to select FTP source as either Strava or the FTP from your device (Garmin/Wahoo)
• Fixed an issue where weight and FTP were not updated on every new activity causing incorrect calculations of weight and power-based data
• Added [[weight]] as an additional statistic
• Fixed a bug in Chrome where highlighting text in a popup would sometimes cause the popup to close

• Add new Vive le Tour map option

• Fix a bug where new activity types were not matching rules
• Fix a bug which was causing process old activity requests to hang and never be processed. Note: There is a backlog of activities due to this issue so it will take some time to get through them all
• Added new 3D map style as an option.

• Added suport for Strava's new activity types: Mountain Bike Ride, E-Mountain Bike Ride, Gravel Ride, Trail Run
• Allow replace text to be used more than once in a rule

• Fixed a bug with counters resetting twice if multiple activities were recorded on the same day the counter reset

• Fixed a bug where editing/copying a rule with a boolean expression wouldn't show letters next to each match condition
• Update trainer match condition to be trainer/treadmill and fix display of it on My Rules page
• Added the ability to share rules. The My Rules page now has a share button which will generate a unique link to your rule which you can share with friends.
  Important: The shared rule link copies your rule exactly so please consider any privacy concerns before sharing a rule, for example GPS coordinates for rules which use your start or end location.
  • The link goes to the Add Rule page with all of the fields pre-populated (like editing/copying a rule). The person you shared the link with can make any changes they want and click "Save Rule" to save a copy of your rule to their account.
  • If your shared rule uses counters, they will be automatically created for anyone using the share link.

• Added temporary fix for issue where Strava API sends empty ending location data.

• Added update option to hide stats (Idea #60, 62, 120)
• Fix bug where power stats were missing for some activities
• Fix bug where some FIT files couldn't be loaded to save new sensors

• Added ability to round/truncate numbers in stats (Idea #26). You can add one of the following 3 options to any numeric statistic:
  • [[stat_name:r]] - Will round to the nearest whole number
  • [[stat_name:ru]] - Will always round up (ceiling)
  • [[stat_name:rd]] - Will always round down (floor)
• Added formatting options for time and duration based stats (Idea #155). You can add one of the following 3 options to elapsed_time, moving_time, and average_pace:
  • [[stat_name:h:m]] - Display duration as H:MM (e.g 1:02)
  • [[stat_name:hm]] - Display duration as Hh Mm (e.g. 1h 2m)
  • [[stat_name:hms]] - Display duration as Hh Mm Ss (e.g. 1h 2m 3s)
• Added ability for force disconnect for Wahoo

• Added "disconnect" button to connected services page.
• Backend improvements and code cleanup. Hopefully no new issues introduced :)

• Fix issue where replace text rules were not working and could not be edited
• Add Support Ukraine as a map option

• Fix issue where rules using has power data or is trainer ride could not be saved or edited
• Add Strava Metro as a map option (Idea #148)
• Increase maximum number of match conditions (Idea #149)

• Fix issue where distance and elevation counters were being incremented by meters instead of an appropriate unit conversion (to yards/miles/kilometers). I apologize for anyone whose counters got messed up in the last ~24 hours because of this.

• Add replace text as an update option (Idea #76)
• Add distance_swim as a counter increment to allow counting distance in meters/yards instead of kilometers/miles (Idea #141)

• Fix bug where some users were unable to add a new rule after yesterday's update.

• Added option to set or clear commute and trainer/treadmill instead of only setting them (Idea #91)
• Added additional match fields for gear, calories, commute (Ideas #56, #129, #134)
• Save setting of disable drag to reorder on the My Rules page so it is applied next time you visit the page. The setting is saved per-browser, so you can have a different setting across devices (Idea #115)

• Added [[dist_swim]] as a statistic which will display the distance in meters or yards
• Added match condition for whether GPS data is present or not (Idea #93, Idea #125)
• Added "Waiting for User Input" as a status on features to let requester know more information is needed
• Fixed activity processing to only handle one activity per user at a time. This should prevent a rare issue where multiple simultaneous uploads can process out of order and mess up counters.

• Fix bug where using [[fit_name]] would occasionally not retrieve data from Garmin

• Fix bug where power-related stats which rely on weight (e.g. W/kg) were not being calculated correctly
• Add options to set and prepend private notes (Idea #113)
• Add generic date formatting option [[date FORMAT]]. This will format the start date of your activity any way you specify in FORMAT. See DateTime.format for available options.

• Fix counter reset dates to always use midnight instead of counter creation time

• Calculate real normalized power instead of Strava's weighted average power (Idea #23)
• Added power-based metrics/stats: TSS, IF, VI, NP, WAP, W/kg
• Added counter options for calories and moving time (Ideas #108, #110)
• Added average heart rate as a match condition (Ideas #107, #109)

• Add option to enable/disable drag to order on the My Rules page to help users with touchscreen devices.
• Minor bug fix for handling boolean expressions.

• Added an (optional) advanced option to create a rule with a boolean expression instead of always using AND for the conditions (Idea #78). If you don't enter an expression the previous behaviour of all AND will be used.
• Allow "not within" as an option for location-based match conditions (Idea #104)
• Fix a bug where testing a rule on an activity with no gear would cause testing to fail

• Fixed an issue where the same sensor was not being detected on two different recording devices due to how Garmin saves the sensor data.
• Fixed matching rule display on activity processing history to correctly show all matching rules
• Processing old activities is now available to everyone

• Added the ability to run your rules on old activities (Idea #22)
• Lots of backend changes to support processing old activities
• Change default counter reset value to 0 instead of 1

• Added Average Pace as a match condition (Idea #52)
• Added "is" and "is not" to comparisons of activity type (was previously always "is") (Idea #90)
• When using a counter, you can add a "?" prefix to display the counter without incrementing it. For example, current value {{?counter_name}} will display the counter's current value without changing it (Idea #92)
• Fixed issue where an extra space was added after a newline \n (Idea #94)
• Added Yes/No text to sliders to make it clearer when an option is enabled or disabled
• Fix bug where the same rule name appears multiple times as a match in activity processing history

• Fix issue where decimal values were not allowed for initial or reset value on counters (Idea #86)
• Add [[day]] and [[monthnum]] so dates can be entered in Y/M/D or other formats (Idea #83)

• Fix issue where comparisons on activity moving time were using an incorrect value
• Fix issue where updates with an apostrophe weren't working correctly (Idea #71)
• Fix issue where editing a rule with certain characters (e.g. <, >) would load incorrect values
• Major changes to counters
  • Added accumulators/decumulators which can increment by either distance or elevation (Idea #34)
  • Add countdown functionality to count days to a specific date (Idea #28)
  • Add ability to increment (or decrement) counters by any value instead of only +1
  • Change counters to use an initial value instead of 'next value'

• Fix issue where editing a rule with private notes has empty data (Idea #66)
• Add a user settings dialog with options for different distance and elevation units (Idea #31)
• Add ability to change map type (Idea #33)
• Add [[fit_name]] to allow insertion of activity/workout name from Garmin or Wahoo (Idea #43)
• Add support for (some) BLE sensors. This functionality is still not fully working so it may not find all of your BLE sensors.

• Add ability to update workout type (Idea #48)
• Add variables to add starting and ending location data to title or description (Idea #27). There are 4 new variables available for each. The start location ones are shown below, there is an equivalent version for 'end_' instead of 'start_'. Since the specifics vary with each location around the world, I recommend using the 'Test Rule' button on the add rule page to see what the value of each is for your region.
  • [[start_city]] - The name of the nearest city or town
  • [[start_admin1]] - This will vary by where in the world you live but is generally going to be state/province/territory/etc
  • [[start_admin2]] - As with admin1, this will vary by where in the world you live, generally it will be county/department/municipality/etc
  • [[start_country]] - The two letter country abbreviation (e.g. US, UK, AU, FR, DE, IT, etc)
• Add option to match ANT+ sensors on "No sensors found" (Idea #53)
• Update "Mark as Trainer" to include "Treadmill" for runners
• Fix an issue where max speed was not being shown correctly for users with metric units as their preference
• Fix an issue where rules based on activity start time weren't able to be saved
• Fix an issue where the wrong Garmin profile would be detected

• Add match condition on Garmin activity profile (Idea #29)
• Added variables for time: [[year]], [[month]], [[dayofweek]], [[weeknum]] (Idea #39)

• Add ability to set private notes as an update (Idea #35)

• Fix an issue where starting a title or description with '.' would cause the server to reject the save rule request
• Add moving time (duration) as a match condition (Idea #36)

• Added a feature request page where you can suggest a new feature and view, vote, and comment on other's suggestions.
  • I tried to add all of the requests I have received so far but may have missed some. If you have previously e-mailed me and don't see your suggestion please add it.
• Fix issue where user data wasn't cleared when logging out

• Allow updating gear to 'none'
• Fix bug where editing a rule with a decimal value in a match field would cause the value to disappear
• Fix bug where clicking set location in the location picker would not update the address/gps coordinates correctly
• Add sensor support for older Garmin devices (e.g. 500/510/800/810)
• Scroll to the top of My Rules and Add Rule if an error occurs so the error display is visible on small screens
• Fix issue where editing a rule then adding a new one could leave the add rule page in the edit state and cause false errors
• Add 'remember me' functionality so you don't have to keep authorizing through Strava. You will now stay logged in for a week

• Fix issue on touchscreen devices (iPad, some phones) preventing rules from being reordered
• Remove autocomplete in location picker and fix bug where GPS coordinates were not being entered correctly
• Update FAQ with instructions on unlinking Garmin Connect

• Reduce minimum location radius for location matches to 10m (~30ft)
• Allow entry of GPS coordinates into the address entry area of the location picker

• Added detection of DI2/DFly for ANT+ files
• Added notification for Stages devices that ANT+ ID is unreliable but it's ok
• Reduce width of My Rules table to allow easier scrolling on touchscreen devices
• Improve matching of manually uploaded activities against Garmin/Wahoo activities

• Added updates to prepend and append to title and description as requested by several users.

• Fixed a bug where special characters such as < would be removed from rules.
• When editing/cloning a rule with a radius around a location, the map will now show the correct radius.

• Added a fix for missing sensor data on some Wahoo and Garmin activities. The fix is still unconfirmed but was successful in my local testing.

• Add new rule update to mute matching activities (https://www.strava.com/clubs/231407/posts/18304386)
• Fix ANT+ ID display when adding sensors - There is a variation in how the ANT+ ID is provided among manufacturers. When known, the correct one will be shown. Otherwise there is a possibility that 2 IDs will be displayed (only one will be correct). The display is only to help you identify your sensor, multiple IDs has no impact on matching the sensor in a rule.
• Add notification about known issue with Wahoo and sensor matching

• Fixed issued where editing a rule which changes the activity type would fail if the activity type contains a space or hyphen

• Added option to match activities by title
• Added extra stats for distance, elapsed time, and moving time
• Add warning to log out of Garmin connect for Chrome users before linking account

• For activities which aren't ride or run, hide the equipment display in the preview
• Hide the preview when Test or Save rule buttons are clicked

• Change "Set bike ridden" to "Set gear used" to make it more applicable to non-cycling sports

• Fix bug where spaces in a fit file name would fail to upload and parse correctly on the add sensors page

• Show activity update preview using actual data when testing a rule.
• Make instructions on add rule and counters pages more helpful and add orange highlight for keywords.
• Reduce activity history saved to 2 weeks (from 30 days).

• Added a preview to show what activity updates will look like in Strava to help test your rule updates ahead of time. Note: Numbers for counters and stats are randomly generated.

• Added autocomplete for inserting ride stats
• When adding multiple match conditions the word "AND" is now shown between each

• Fixed an issue where removing a match condition which uses location would prevent removing any other match conditions.
• Stop adding an extra space after auto-completing a counter or stat

• Changed "Stop processing on match" to "Process next rule on match" to make things more clear. All existing rules will still work
• Made the main page more informative about what ActivityFix does

• Added help pages on rule creation, counters, and sensors
• Change rule processing to match if the rule compares against activity type and a previous rule changed it. E.g. Rule1 changes Activity Type to Run and Rule2 matches on Run -- both rules will now match (previously only Rule1 would match).

• Fixed a bug which was causing the Test Rule button to not work properly
• Remove leading and trailing spaces from title and description updates
• Fixed a bug where the map picker could show the wrong radius around the selected location

This release adds Garmin and Wahoo integration so you can create rules which match ANT+ sensors connected during your activities. To set it up, click on the Connected Services button in the menu and select the service you would like to authorize with ActivityFix.

Once you have done connected a service, you will have access to the My Saved Sensors page where you can view and save the ANT+ sensors from your activities. After saving the sensors you are interested in, you can create rules which compare the sensors used in your activities against the ones you have saved.

• Garmin and Wahoo integration to allow rules which use ANT+ sensors - see above paragraphs for details
• Added ability to edit counters
• Added shortcuts to insert activity data into title and/or description updates. See the Add Rule page for details on available data and how to insert it
• Added activity processing retry when there is a Strava server error. Processing will be retried after 5 minutes if the first attempt failed

• Fixed an issue with displaying activity history for activities with processing errors
• Fixed a bug where newly added counters cannot be edited or deleted

• Display activity title correctly in processing history if a rule changed it
• Properly display newlines when editing a rule
• Fixed a bug where the My Rules page wouldn't say you have no rules if they were all deleted

This release has a big change in how rules are processed. Instead of stopping on the first match, every rule will now be processed. When creating a rule there is a new option to stop processing additional rules if it matches. By default this is set to true for all existing rules to preserve the previous behavior.

If multiple rules match and update the same thing, only the first matching rule will change that setting -- this means that rule order is important, as later rules will not overwrite updates from earlier ones. The exception to this is "add to title" and "add to description" which will just keep adding on.

As an example to make it more clear, assume you have an activity which should match the three rules below. Rule #1 will match and all three updates will be done. Rule #2 will also match -- since the title has already been set, it will not be overwritten, but the description will have 'Garfield hates Mondays' added to it (since it is not overwriting but just adding). Rule #2 has stop processing on match set, so Rule #3 will not be processed at all. The final update will be to set title to "My Commute", set description to "Home to work Garfield hates Mondays", and mark it as a commute.

• Rule #1 - Set title to "My Commute", Set description to "Home to work", mark as commute. Stop processing on match = No.
• Rule #2 - Set title to "Monday morning ride", Add to description "Garfield hates Mondays". Stop processing on match = Yes.
• Rule #3 - Set bike to "road bike". Stop processing on match = No.

• Allow multiple rules to match an activity - see above paragraphs for details/explanation.

• Fixed a bug where editing/copying a rule which updates the activity type would not correctly set the update on the add rule page.

• Added counters which can be used in updates to an activity title or description. Use the My counters page to manage your counters. When creating a rule, you can reference a counter by entering {{counter_name}}. If the rule matches, the current counter value will be inserted and the counter incremented for the next use.
• Added a confirmation/warning when deleting rules.
• Show a clear indication of a processing error on the activity history page

• Added a small delay to rule processing to allow other Strava Apps (e.g. Klimat) to complete their processing, since they may overwrite updates made by ActivityFix

• Added a match option to check if your route passes near a specific location

• Emojis used in ride titles will now show up correctly. I don't have a good way to fix old activities but all new ones should show up correctly in your activity history.
• Fixed a bug where certain errors in rule creation weren't being reported to users correctly

There is now a page where you can view and submit feature requests and report bugs. Even if you don't have any features to request, you can vote for other people's suggestions and add your own comments to help me determine what features are most important to you!

• Added feature request and bug reporting page
• Added "is" and "is not" matches for day of week, and added shortcuts for Weekdays and Weekends
• Added elevation/distance as a match field - this can be used to determine how hilly a ride is

This is a minor release to fix two UI bugs. No new features have been added.

• Fixed missing edit/copy/delete buttons on the My Rules page in Firefox
• Fixed an issue on the Add Rules page where a bike name with a single quote in it (') would cause the page to not load correctly.

The latest release includes a few requested features and several minor bug fixes. The biggest change is the addition of edit and copy buttons on the My Rules page. As is probably obvious, these buttons will let you edit or copy an existing rule instead of having to delete and re-create it

• Added the ability to edit and copy existing rules
• Added elevation as another match option for rules

• When deleting a rule, renumber all existing rules so the order is contiguous
• In the rule editor, fix a bug where a match condition for location could not be deleted if the location picker had not yet been opened.
• On the test rule dialog, display tested value in the correct units instead of always showing metric

Welcome to ActivityFix! I spend a lot of time outdoors -- riding, skiing, kayaking, and hiking -- and like to track how much time and distance I put in to each activity and my equipment. I often forget to update my activities and thought that there must be a better way. After talking with many of my active friends this seems to be a common problem.

ActivityFix started out as a simple project but quickly turned in to something much larger. I hope that you find it as useful as I have. The major features are all in place but I do have some plans for the future to make things even better. If you have any suggestions or ideas for the site (or if you find bugs) please let me know. You can e-mail me at support@activityfix.com. I do have a full-time job so I may take a day or two to get back to you.

This site is a personal project and I intend to keep it free forever. I don't collect any of your personal data aside from:

• A token Strava provides to let ActivityFix access information about your activities. You can revoke this at any time from Strava's settings page
• Your e-mail address (which is recommended, but completely optional)
• Any rules you create which may include GPS coordinates or other identifying information
• The last 30 days of your Strava activity history -- only titles and any values from the activity which were tested against your rules

I will never sell your information. You can view the full and official privacy policy if you want the legal version of the above.