When viewing the alert threshold configuration for a VWC sensor, if I switch back to the chart view for the sensor, then back to the alert settings, some of the values will be gone, wrong, or set to wild numbers (-30). If I pull down to refresh, the expected numbers load. I will try to attach a screencast to demo.
This appears to be purely visual, as I get alerts at the expected thresholds.
Switch back to data tab, then back to Alerts and they have changed again:
Hello.
Thank you for posting your issue.
I don’t have a lot of information to work with here, but my guess is that you are typing the values into the inputs?
These selector controls have a minimum / maximum limit.
Usually they are fairly intuitive and are not exceeded.
If the limit is exceeded the input value will not be considered valid and may not be saved.
When a save is successful the app will show a “Threshold Saved” messaged at the lower part of the screen.
It is also worth noting that the system saves the last changed threshold.
So in theory if you are changing them at a bizarre speed - it may only save the last one.
You should be getting a separate “Threshold Saved” message for every changed threshold.
So unless you got this message - the threshold was not updated.
How to resolve your issue?
Option 1 - use the ± buttons. They will not go above the supported ranges.
Option 2 - please share a video of you changing the thresholds to get this issue. I will be able to trace your actions and help. (you can send it to gregory@pulsegrow.com)
The issue is I set sane values for alert thresholds like 17c - 22c. Then I change views in the app and go back and the values are crazy like subzero values. This is true in the app and web. I emailed you a screencast from my phone.
[Update for anyone reading, this is apparently an issue specific to my lucky account, so you probably have nothing to fear 
and also just to clarify, this never actually affected the alerts I received it was only a visual glitch]
This issue should be resolved now. (make sure you clear browser cache if it’s still there)
It wasn’t specific to your account as i initially assumed, but only happened on some thresholds of some sensors.
Once again, thank you for posting this.
Please let us know if there’s anything else.
Amazed you were able to ship a fix so quick. Thanks for your work tracking down the root cause. I can confirm it’s all good here, too.
