Nightscout 15.0.7 "Blueberry Muffin"

Nightscout 15.0.7 "Blueberry Muffin" is one of those updates you should install now instead of putting it off for "later"

15.0.7 - this release clearly strengthens security, compatibility with newer MongoDB versions, and API stability, which matters for both regular users and those using automation (Loop, AAPS, and other AID).

What’s new in Nightscout 15.0.7

Improved handling of UUIDs/identifiers for AID systems (Loop, Trio, and similar), reducing the risk of duplicate entries and data consistency issues.
A new environment variable UUID_HANDLING (default "true") controls how entries with UUIDs are stored, giving some flexibility for more advanced setups.
Stronger safeguards against accidentally using a production database in tests (hard requirement for NODE_ENV=test and entry count checks).
Updated MongoDB driver (5.x series) and fixes for MongoDB 8, so Nightscout handles newer database versions better and is less prone to _id-related errors.
The API once again accepts arrays of objects in POST (entries, treatments, devicestatus, profile, activity, food) with proper _id validation and returns 400 on errors.
Restored compatibility with historical data where UUID was stored in _id, so such entries can still be found.
Fixed mmol/L value display in OpenAPS suggestions, which matters for users working in units other than mg/dL.
Small but practical improvements in the websocket layer and profile saving that reduce the risk of errors during simultaneous operations (e.g., profile saves).

Why this version makes sense for regular users

Looking at the change list, 15.0.7 isn’t a big revolutionary release, but a solid refinement of the 15.x series, focused on things you don’t immediately see in the interface but that save you at the worst possible moment.

From a patient’s and parent’s perspective, three aspects stand out:

Greater resistance to errors and duplicates - if you use a closed loop or multiple AID apps, entry consistency (treatments, overrides) is critical; 15.0.7 clearly pushes toward cleaning up that mess.
A safer environment - protection against accidentally running tests on a production database isn’t a marketing feature; in practice, it can save days of data recovery.
Better compatibility with newer MongoDB versions - if your hosting (or your own server) upgraded Mongo, older Nightscout releases can behave unpredictably; 15.0.7 reduces that gap.

I don’t see anything here that justifies stubbornly sticking to old versions out of fear that "if it works, don’t touch it". With how fast cloud services change, clinging to outdated setups does more harm than good.

Importance for AID and integration users

If you use Loop, AAPS, Trio, or other solutions that rely heavily on the Nightscout API, this version is basically a must.

Key points from an integration perspective:

Normalization of UUID-based entries and the ability to control this behavior via UUID_HANDLING.
Support for arrays in POST for entries/treatments/devicestatus/activity/food/profile, with proper 400 errors for malformed _id.
Improved profile saves (replaceOne with upsert) and websocket deduplication by startDate, reducing weird cases where a profile seems saved but actually went sideways

In our User Panel version 15.0.7 is already available - you can update your Nightscout instance

You can also read about: