Interesting. Reminds me of two other cases:Ok, so an update to this for anyone else that might be having this issue or for those who are yet to come lol. Well it kept giving me problems with dropping out and reboots and even the 3/300 was hit or miss. I'm am 100% ignorant on how the i2c bus works and talks, but there is some kind of a timing issue that causes the problem, guessing bus side. So I could look through the API "readings" and the drops were at specific intervals. At one point I changed it to 5m interval and looking through the log, it would drop every hour at the 9th minute, i.e 4:09, 5:09, 6:09. I tried to put the PH on i2c4, but could not get reef-pi to see it. Tried totally removing it from reef-pi and starting over. Now I need to recalibrate it lol. Guessing Reef-pi only searches on the primary bus, but @Ranjib could confirm that if that is the case. So I ended up putting it back on the primary bus, and disconnected my RTC. Verified the only thing on the bus was the PH and let it go. I added 2 statistic charts for testing purposes, one to show min, and other max. It is reporting as of 10:50pm last night (since it was alone on bus) the lowest report was 7.92 and highest 8.09. Today I will add the RTC to the second bus and get it set back up and hopefully everything will continue to be stable.
Ignore the temp dropouts, those were from the setup, testing, and troubleshooting (PH) of the entire build on my workbench.
-First where @bishoptf had kind of regular low-voltage warnings by the hour.
- Second where @bishoptf had kind of regular reboot messages in the log without a reboot.
Writing it like that I can now see a strange connection there ....