Pool Math App issue

[Leebo]

Last year you tracked Salt so there's still several "records" of a salt level thus the reasoning your CSI Screen keeps showing salt. Keep in mind the CSI screen is mostly just a "what if" where you can play around to see what would occur.

On the Summary page however I'm perplexed why you're showing -0.11.......I'm wondering if you could "pull to refresh" that result as maybe you've deleted some stuff and it just needs smacked up side the head?? On the Summary page it's now using the default 1000 for Salt since you've disabled it (I do kinda agree it could maybe use the last record, but that's another discussion) and I am also getting -0.07 as Marty is?

 

[Leebo]

Was able to work with Jon today to get an internal App updated that allowed me to really see info that's allowed me to slightly pinpoint some issues you're having. After I updated my personal device to iOS 15 Beta the internal App hasn't worked right but Jon was able to get things sorted out today and got me back up and running.

So looking at things two things struck me as odd, first was how you were seeing -.11 on your screenshot while both Marty and I were getting -.07 doing the same math. The second item was how you were seeing a change in your CSI on your logs even though the data used to calculate things were the same. As an example here, on Aug 1st you saw a CSI result of 0.21 with a pH of 7.9 while two days later you saw a CSI result of 0.22 when also using a pH result of 7.9. I couldn't figure this out until I was able to dig a bit deeper into things today. Long story short, there's a tiny bit of unexpected behavior here, but it's avoided in the HUGE majority of the users.

Both of the issues above have been caused by you entering your results to the hundredths while the HUGE majority of our users enter results to the tenths place. I suspect this is something you're doing as you use a digital pH meter of some sort. This is causing the results to be displayed as one number (rounded) when in fact the actual number is being used for the calculations. I can see where this maybe causing some confusion to a small amount of users and I've been talking to Jon about options to make this cleaner. In the mean time I would greatly suggest just entering your pH to the tenths place. Things don't have to be that exact as it's just water.........

 

[sbcpool]

Pentair IntelliChlor Salt Replacement Cell | IC60 | EC-521105

or, if you do not have Pentair automation, don't mind a non-Pentair cell, and can wait a bit,

APX PERFORMANCE P60 Aftermarket Replacement Salt Cell fits Pentair IC60

Discount Salt Pool has the APX PERFORMANCE P60 aftermarket replacement salt cell that fits a Pentair IC-60 cell (521105). Get the best price with this salt cell alternative.

www.discountsaltpool.com

This is in stock -- IC40 generic

APX PERFORMANCE P40 Aftermarket Replacement Salt Cell fits Pentair IC40

Discount Salt Pool has the APX PERFORMANCE P40 aftermarket replacement salt cell that fits a Pentair IC-40 cell (520555). Get the best price with this salt cell alternative.

www.discountsaltpool.com

Thank you for the links. After my past experience with the CircuPool RJ60+ that's made for Discount Salt Pool, I'm not confident in the performance claims attached to their products. I do appreciate the help, though. That 50% premium on the IC60 is a bit rich for my blood. I don't like to buy from scalpers. Although it's certainly their right and their prerogative to charge what they wish, I don't want to encourage price inflation. I can wait at this point.

 

[sbcpool]

Both of the issues above have been caused by you entering your results to the hundredths while the HUGE majority of our users enter results to the tenths place. I suspect this is something you're doing as you use a digital pH meter of some sort. This is causing the results to be displayed as one number (rounded) when in fact the actual number is being used for the calculations. I can see where this maybe causing some confusion to a small amount of users and I've been talking to Jon about options to make this cleaner. In the mean time I would greatly suggest just entering your pH to the tenths place. Things don't have to be that exact as it's just water.........

Thank you for looking into it. The salt levels are still where they were last left and maybe a little higher because of LC additions, so I need that value to be included if it does indeed affect CSI. When I went in and changed the pH logs to tenths it still didn't fix the problem. I had to go in and re-save the temperature log entry that came after the last pH entry. That fixed it.

That clued me in a little bit on the internal workings of the app. It seems that the CSI tile on the summary screen displays the CSI value from the last log entry where CSI was calculated rather than actively calculating the CSI based on the currently logged conditions. Re-saving the last log entry with a CSI calculation forced the CSI to be re-calculated.

I hadn't expected that behavior because as a DB admin I tend to shun storage of derived attributes, so I just kind of operate from that assumption.