Mostly an important bug fix release, but some nice OD noise reductions, too!
We recommend being on version 25.1.21 or later before updating.
Download the release here25.3.5
Enhancements
- New faster ADC firmware with less noise
- Upgraded ADC firmware improves signal processing speed and reduces measurement noise, leading to more reliable readings for all sensors.
led_intensityis now registered in our database- This means that running
pio kill --all-jobs(and relatedpio killcommands) will now also turn off all LEDs, ensuring a complete shutdown of active processes.
- This means that running
- New option in
pio workers addto specify an IPv4 address- When adding a new worker, you can now explicitly provide an IPv4 address instead of relying on the default
hostname.local. This is useful in networks where mDNS resolution is unreliable or unavailable. Ex:pio workers add <name> -a 192.168.0.3
- When adding a new worker, you can now explicitly provide an IPv4 address instead of relying on the default
- New time option on the Overview page: “Now” for only real-time data
- The UI now has a “Now” option that filters out historical data, displaying only real-time sensor readings and status updates.
- Logs for experiment profiles now include an action step number
- Each log entry related to an experiment profile now contains a step number, making it easier to track progress and diagnose issues in multi-step workflows.
- Improved outlier detection in nOD and growth rates
- Our outlier detection algorithms for normal optical density (nOD) and growth rates have been refined, reducing false positives and improving tracking accuracy during experiments.
- Changing OD readings interval programmatically
- OD Reading job now exposes
intervalas a editable published_setting. For example, you can PATCH tohttp://pioreactor.local/api/workers/<pioreactor_unit>/jobs/update/job_name/od_reading/experiments/<experiment>with body:
to change OD readings interval to 10s.{ "settings": { "interval": 10 }, }
- OD Reading job now exposes
Breaking Changes
id→job_idinpio_metadata_settingstable- Database schema update: The primary identifier column in
pio_metadata_settingshas been renamed tojob_id.
- Database schema update: The primary identifier column in
- Changed the scaling of
smoothing_penalizer- The
smoothing_penalizerparameter now operates on a scale that is ~100x lower than before.
- The
- Deprecation of
/unit_api/jobs/stop/...endpoint- The
/unit_api/jobs/stop/...API endpoint is being deprecated in favor of using query parameters:- Instead of
/unit_api/jobs/stop/job_name, use/unit_api/jobs/stop/?job_name=.... - The special case
/unit_api/jobs/stop/allremains valid and unchanged.
- Instead of
- The
- Timestamp precision change: From
xxxxxmilliseconds →xxxmilliseconds- All timestamps will now be stored with three-digit millisecond precision instead of five. This change optimizes storage efficiency and speeds up queries while maintaining sufficient accuracy for most use cases.
Bug Fixes
- Fix for “More” button in the Logs UI page
- Previously, clicking “More” in the Logs UI would default to “Standard” log level instead of retaining the selected filter. Now, it correctly uses the log level chosen by the user.
- Multiple experiment profiles no longer overwrite each other in MQTT
- Previously, running multiple experiment profiles could cause MQTT messages to overwrite each other. This is now fixed, but note that the new MQTT topic format introduces
job_id, deviating from our usual topic structure.
- Previously, running multiple experiment profiles could cause MQTT messages to overwrite each other. This is now fixed, but note that the new MQTT topic format introduces
- Fix for API returning incorrect responses for Huey-related tasks
- API responses related to background tasks (e.g., adding a new Pioreactor, syncing configs, updating firmware) were sometimes incorrect or missing details. This has been fixed.
- Correction to
od_reading.config’ssmoothing_penalizerscaling error- A miscalculated scaling factor in
od_reading.configcaused the smoothing factor to be larger than intended. This has been corrected, and yourconfig.inifile has been automatically updated to reflect the new values.
- A miscalculated scaling factor in
- Fix for missing log events in Event Logs after worker unassignment
- Some log events (such as clean-up and assignment events) were missing when they occurred after a worker was unassigned. These now appear correctly. Additionally, some unrelated log entries that were mistakenly displayed have been removed.
- Scaling bug fix in the extended Kalman filter affecting nOD detection
- A bug in the extended Kalman filter was causing outlier detections too frequently. In extreme cases, these detections could compound, driving nOD values negative and corrupting the filter’s internal state. This issue has been fixed with a new, more stable filtering algorithm that significantly improves robustness.