After a restart, graphs do not display data prior to the restart time. The Y axis starts from the restart time. I expected the data to be reloaded from the logs and then the graphs would display the last 24 hours or whatever is configured. This happens in both the uploaded graphs and the user interface.
MXdiag after restart is attached.
Welcome to the Cumulus Support forum.
Latest Cumulus MX V4 release 4.4.2 (build 4085) - 12 March 2025
Latest Cumulus MX V3 release 3.28.6 (build 3283) - 21 March 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
If you are posting a new Topic about an error or if you need help PLEASE read this first viewtopic.php?p=164080#p164080
Latest Cumulus MX V4 release 4.4.2 (build 4085) - 12 March 2025
Latest Cumulus MX V3 release 3.28.6 (build 3283) - 21 March 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
If you are posting a new Topic about an error or if you need help PLEASE read this first viewtopic.php?p=164080#p164080
Graph start time after restart of CumulusMX
Moderator: mcrossley
-
daveh
- Posts: 10
- Joined: Mon 30 Nov 2015 1:39 pm
- Weather Station: Home built
- Operating System: Linux
- Location: Peterborough, UK
Graph start time after restart of CumulusMX
You do not have the required permissions to view the files attached to this post.
-
steve
- Cumulus Author
- Posts: 26672
- Joined: Mon 02 Jun 2008 6:49 pm
- Weather Station: None
- Operating System: None
- Location: Vienne, France
- Contact:
Re: Graph start time after restart of CumulusMX
I have to take special actions for the 'Easyweather.dat' input type for things that would normally be done after connecting to the station. It looks like I have missed out loading up the recent data from the logs in MX - I'll check and fix in the next build if that's the case.
Steve