When starting up CMX it starts catching up the data from the Davis logger. Apparently it also tries to catch up data from the extra Ecowitt sensors. It then registers zero value for those extra sensors until reaching the time it has caught up and continues normal reading. I don't see how this comes about because the Ecowitt has no logger if I understand it well. Shouldn't the missed data just be skipped (now I get a dip in the chart, caused by my daily backup, when skipped I get a straight line between the last read and the first in normal reading).
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
Catching up on extra (Ecowitt) sensors
Moderator: mcrossley
- HansR
- Posts: 5958
- Joined: Sat 20 Oct 2012 6:53 am
- Weather Station: GW1100 (WS80/WH40)
- Operating System: Raspberry OS/Bookworm
- Location: Wagenborgen (NL)
- Contact:
Catching up on extra (Ecowitt) sensors
Situation with a Davis main station and an Ecowitt Extra Sensor.
When starting up CMX it starts catching up the data from the Davis logger. Apparently it also tries to catch up data from the extra Ecowitt sensors. It then registers zero value for those extra sensors until reaching the time it has caught up and continues normal reading. I don't see how this comes about because the Ecowitt has no logger if I understand it well. Shouldn't the missed data just be skipped (now I get a dip in the chart, caused by my daily backup, when skipped I get a straight line between the last read and the first in normal reading).
When starting up CMX it starts catching up the data from the Davis logger. Apparently it also tries to catch up data from the extra Ecowitt sensors. It then registers zero value for those extra sensors until reaching the time it has caught up and continues normal reading. I don't see how this comes about because the Ecowitt has no logger if I understand it well. Shouldn't the missed data just be skipped (now I get a dip in the chart, caused by my daily backup, when skipped I get a straight line between the last read and the first in normal reading).
You do not have the required permissions to view the files attached to this post.
Hans
https://meteo-wagenborgen.nl
CMX build 4017+ ● RPi 3B+ ● Raspbian Linux 6.1.21-v7+ armv7l ● dotnet 8.0.3
https://meteo-wagenborgen.nl
CMX build 4017+ ● RPi 3B+ ● Raspbian Linux 6.1.21-v7+ armv7l ● dotnet 8.0.3
- mcrossley
- Posts: 12756
- Joined: Thu 07 Jan 2010 9:44 pm
- Weather Station: Davis VP2/WLL
- Operating System: Bullseye Lite rPi
- Location: Wilmslow, Cheshire, UK
- Contact:
Re: Catching up on extra (Ecowitt) sensors
It is skipped, that is why you have the dips - MX has no concept of a "null" value, so missing values are zero. Not ideal I know, but not a lot else can be done.
- HansR
- Posts: 5958
- Joined: Sat 20 Oct 2012 6:53 am
- Weather Station: GW1100 (WS80/WH40)
- Operating System: Raspberry OS/Bookworm
- Location: Wagenborgen (NL)
- Contact:
Re: Catching up on extra (Ecowitt) sensors
With skipped I mean no data is being logged so I don't find any line on that time in the logfile.
This e.g. happens with the Davis: when the logger does not have the data to close the gap you just don't get the records.
This e.g. happens with the Davis: when the logger does not have the data to close the gap you just don't get the records.
Hans
https://meteo-wagenborgen.nl
CMX build 4017+ ● RPi 3B+ ● Raspbian Linux 6.1.21-v7+ armv7l ● dotnet 8.0.3
https://meteo-wagenborgen.nl
CMX build 4017+ ● RPi 3B+ ● Raspbian Linux 6.1.21-v7+ armv7l ● dotnet 8.0.3
- mcrossley
- Posts: 12756
- Joined: Thu 07 Jan 2010 9:44 pm
- Weather Station: Davis VP2/WLL
- Operating System: Bullseye Lite rPi
- Location: Wilmslow, Cheshire, UK
- Contact:
Re: Catching up on extra (Ecowitt) sensors
No, but MX does have a record for the main data, so when it constructs a set of values for that record it pulls in a zero value from the extra sensor. So unless you drop the main sensor data when there is no extra sensor data... Not something you would want to do I expect.
It is the same with any sensor value. If your temperature sensor went offline you would get zero values for that in your history too. During catch-up there is no data for the Ecowitt extra sensors, so it uses zero.
It is the same with any sensor value. If your temperature sensor went offline you would get zero values for that in your history too. During catch-up there is no data for the Ecowitt extra sensors, so it uses zero.
- HansR
- Posts: 5958
- Joined: Sat 20 Oct 2012 6:53 am
- Weather Station: GW1100 (WS80/WH40)
- Operating System: Raspberry OS/Bookworm
- Location: Wagenborgen (NL)
- Contact:
Re: Catching up on extra (Ecowitt) sensors
Ok, thanks.
I'll think about how to handle this or just leave it.
I'll think about how to handle this or just leave it.
Hans
https://meteo-wagenborgen.nl
CMX build 4017+ ● RPi 3B+ ● Raspbian Linux 6.1.21-v7+ armv7l ● dotnet 8.0.3
https://meteo-wagenborgen.nl
CMX build 4017+ ● RPi 3B+ ● Raspbian Linux 6.1.21-v7+ armv7l ● dotnet 8.0.3