v2.2.7

Manual Notes

1. Use Units from the Profile Store Instead of the Top-Level Units
2. Time Zone Support for Profile Data Based on Looper's Time Zone

Details for 1:

• The units used within the profile's store (store.units) can differ from the units specified at the main level (profileData.units) when using Loop.
• Since the units are primarily used for interpreting profile data (e.g., basal rates, carb ratios), it makes sense to prioritize the units specified within the profile store.
• This change modifies the code to use the units from the profile's default store (store.units) when loading profile data.

Details for 2:

The person running the LoopFollow app can be in a different time zone than the person running the app which is being followed.

• When the looper is in a different time zone than the LoopFollow user, it's important to use the looper's time zone for accurate schedule-based setting displays (e.g., carb ratio, target range, basal rates).
• This change updates the code to use the time zone specified in the profile (store.timezone) when determining the current profile data.

Thanks to Odd Stoltenberg for reporting these two issues.

What's Changed

• Unit and timezone handling by @bjorkert in #330

Full Changelog: v2.2.6...v2.2.7