Welcome to the Cumulus Support forum.
Latest Cumulus MX V3 release 3.28.6 (build 3283) - 21 March 2024
Cumulus MX V4 beta test release 4.0.0 (build 4019) - 03 April 2024
Legacy Cumulus 1 release 1.9.4 (build 1099) - 28 November 2014
(a patch is available for 1.9.4 build 1099 that extends the date range of drop-down menus to 2030)
Download the Software (Cumulus MX / Cumulus 1 and other related items) from the Wiki
Latest Cumulus MX V3 release 3.28.6 (build 3283) - 21 March 2024
Cumulus MX V4 beta test release 4.0.0 (build 4019) - 03 April 2024
Legacy Cumulus 1 release 1.9.4 (build 1099) - 28 November 2014
(a patch is available for 1.9.4 build 1099 that extends the date range of drop-down menus to 2030)
Download the Software (Cumulus MX / Cumulus 1 and other related items) from the Wiki
Yearly Rainfall resetting to zero
-
pasl123
- Posts: 1
- Joined: Sat 26 Jan 2019 12:14 pm
- Weather Station: Watson 8681 Pro
- Operating System: Windows 10
Yearly Rainfall resetting to zero
I have a standalone Watson 8681 Pro and have noticed that in 2019 the Yearly Rainfall total keeps resetting to zero. I have had the machine since December 2017 and this did not happen in 2018. The base data is there and the Monthly Rainfall total seems to be working fine. I have switched off and on with no result. I am reluctant to use reset in case I lose data. I would appreciate any help.
-
AllyCat
- Posts: 1124
- Joined: Sat 26 Feb 2011 1:58 pm
- Weather Station: Fine Offset 1080/1 & 3080
- Operating System: Windows XP SP3
- Location: SE London
Re: Yearly Rainfall resetting to zero
Hi,
As the 8681 Pro is not a compatible /supported station with the Cumulus software, we may not be able to help much.
Where are you seeing this behaviour, on the Console or in a Web interface? Generally, the first port of call for such a problem is to back up all the data as best you can, and then Reset the offending device.
Cheers, Alan.
As the 8681 Pro is not a compatible /supported station with the Cumulus software, we may not be able to help much.
Where are you seeing this behaviour, on the Console or in a Web interface? Generally, the first port of call for such a problem is to back up all the data as best you can, and then Reset the offending device.
Cheers, Alan.