Got a few things done on the 3.0 side.. ezo ph driver was ported to new HAL . And now I am running 3.0 development build on one of my ph monitor. Everything looks good, I am yet to test the ezo calibration bits on 3.0. But I wanted the ezo support to be there in 3.0 so that I can start comparing the ph board with ezo circuit side by side.
Unfortunately, due to 2.1 -> 3.o upgrade, I lost the usage data. But Adafruit.io was configured
During the process I also found a telemetry update API bug :-O , dont know how it went and who all have been impacted, I hope this was not part of 2.x series and it was only present in 3.0 development branch.. anyway.. its fixed now.
Telemetry bugfix: https://github.com/reef-pi/reef-pi/pull/762
EZO hal porting: https://github.com/reef-pi/reef-pi/pull/761
I'll start putting regular development update from now on. I feel like we have a decent community now, and there are enough folks who understand some parts of reef-pi, so if anyone curious how the code works, these changes with the context of whats being done might be useful. Software engineers could always use an extra pair of eyes for review
Unfortunately, due to 2.1 -> 3.o upgrade, I lost the usage data. But Adafruit.io was configured
During the process I also found a telemetry update API bug :-O , dont know how it went and who all have been impacted, I hope this was not part of 2.x series and it was only present in 3.0 development branch.. anyway.. its fixed now.
Telemetry bugfix: https://github.com/reef-pi/reef-pi/pull/762
EZO hal porting: https://github.com/reef-pi/reef-pi/pull/761
I'll start putting regular development update from now on. I feel like we have a decent community now, and there are enough folks who understand some parts of reef-pi, so if anyone curious how the code works, these changes with the context of whats being done might be useful. Software engineers could always use an extra pair of eyes for review