Release 14 Liquorice

(Note this is currently a silent release - please do not post massive announce threads anywhere. The dev team will do this once we confirm everything is working as expected.)

Nightscout documentation is now hosted at nightscout.github.io.

Major changes in this release

• The release fixes issues found with MongoDB Atlas. Notably, the database load is hugely improved with release 14, compared to previous releases. It's highly recommended all users who have migrated to Atlas update to this release.
• Related to above, release 14 is unlikely to work if you’re uploading data directly to MongoDB. If you’re using an uploader that connects directly to MongoDB instead of using the REST API, please migrate to REST API as part of updating to this release. Instructions on how to do this should be either in the uploader settings or the uploader documentation.
• Nightscout now integrates the split view that allows you to view 2-8 Nightscout graphs in one browser window. See the Readme for details
• We now have a configurable Clock view! After updating, press the +.button next to clock view links in the Nightscout site, create your view and bookmark clock page you just made
• This release fixes a security issue with remote service integrations. We do not know of any exploits using this vulnerability and exploiting the issue requires access to your Nightscout, so it’s unlikely any users are in danger. However, if you use Loop Overrides, Dexcom Share Bridge or the Medtronic Guardian service, it’s highly recommended you immediately upgrade to this release
• Multiple issues with Dexcom Share and Medronic cloud services have been fixed

Other changes

• Stale data alarms were still broken on some users, depending on how they synched data to Nightscout. The alarms should now work again for all users
• Nightscout now shows the size of the database as a pill (enabled by default)
• Client side caching now uses a service worker instead of appcache. After updating the site, please clear the browser cache to ensure you get the latest client side version.
• Improved translations for many languages
• Google Home and Alexa improvements
• Reporting pages updated styling, fixing some issues on mobile browsers
• Graph rendering has been fixed for situations where data was missing
• Glucose distribution report headline now shows dates
• Day to Day reporting now supports Loop overrides
• Default mg/dl setting value changed from “mgdl” to “mg/dl” (should not affect any users)
• DBsize plugin now works with Atlas
• The flow that pushed users to the profile editor on startup has been improved
• Layout fixes for small screens

Known issues

• The current Loop implementation stores a large amount of profile data into Nightscout and can cause issues after migrating to MongoDB Atlas, especially with reporting. The current fix is to simply go to Atlas and delete the profile collection data. We’re working with Loop developers to fix this in the future releases of Loop/Nightscout.

Developer notes

• Direct to Mongo data injection is now fully unsupported. This is a permanent change and even if the current release might work with direct to Mongo data injection, the upcoming releases are guaranteed to break this functionality. For read-only use cases, the V1 API offers performant data reads and if you want to save data into Nightscout and/or synchronise the Nightscout data with a local database, please use the V3 API, as we’re likely to make V1 API read only in the future.
• The V1 API now uses a caching layer to improve the performance of the API and reduce Mongo load very significantly. The cache is refreshed on every data change, but there is a few second gap between data being inserted and updated, during which you will be served stale data that doesn't include the latest insertion. If this is a problem for data synchronisation with a local database, please migrate over to using the V3 API. If you're implementing an app that only reads data, please keep using V1. To ensure the requests hit the cache to load recent data, avoid using date parameters in the queries and just request latest n entries from the database. Also please be mindful of how frequently you request data and don't ask for more entries than what the application actually needs.
• The site caching has been migrated to use a service worker