Storage and Logging

Data is currently handled across both the EEPROM and device classes. Choose a single storage approach and rename classes to reflect clear ownership. Implement a centralized logging system (Serial or alternatives) and apply it consistently across device actions.

Related articles

• https://www.instructables.com/Data-Logging-With-Raspberry-Pi-Pico/
• https://rc2014.co.uk/modules/pi-pico-vga-terminal/pi-pico-sd-card-backpack/

For exmaple set highpoint cali in pH probe

def set_highpoint_calibration(self, highpoint):
        """
        Set the highpoint calibration value for the pH probe.
        """
        self.slope_is_out_of_range = False
        self.eeprom.set_ignore_bad_ph_slope(False)
        self._highpoint_calibration = highpoint
        buffer = f"Cal,High,{int(highpoint)}.{int(highpoint * 1000 + 0.5) % 1000}\r"
        print(buffer)  # Simulate sending the string to the Atlas Scientific product
        print(
            f"PHProbe::setHighpointCalibration({int(highpoint)}.{int(highpoint * 1000) % 1000})"
        ) 

vs cpp
serial(F("PHProbe::setHighpointCalibration(%i.%03i)"), (int)highpoint, (int)(highpoint * 1000) % 1000);

Start by tracing ownership between the EEPROM and device classes, using set_highpoint_calibration as the concrete entry point and reviewing the Serial or print logging examples in the issue. Done means storage has one clear owner, classes reflect that ownership, and device actions use one centralized logging approach consistently.