Of course the drivers of the weather software should be robust enough not to get stuck if anything strange happens and it should be able to repair or ignore any faulty data. This unfortunately does not happen in WeeWx.
The result is strange behaviour of the WeeWx interface.
That's great with Cumulus and that is why I'm using cumulus with my production system up to now.
Nevertheless this faults do not occur very often and it might be the easier solution to program a WeatherDuino data integrity check.
Im thinking of a sketch you can upload if there are any issues walking through the data like the eraser and sorting out any date-time combinations that as simply not possible.
Due to the bug i had the 35th of Oktober written on the Display for example. I don't know which timestamp is saved here, but it can not be good
.
Moreover I'm thinking of the possibility to specify a time range where the data should be kept and the other stuff should be deleted.
Until now I do not know how the logger works or how it knows where its data is stored, but I will have a closer look at it the next days.
@Werk There is no need to do anything. I will try to make a sketch to change the logged data in a way WeeWx can handle it and does not get stuck. I think this is the easiest way to get rid of this WeeWx bug in that seldom cases.
Best regards,
engolling
The result is strange behaviour of the WeeWx interface.
That's great with Cumulus and that is why I'm using cumulus with my production system up to now.
Nevertheless this faults do not occur very often and it might be the easier solution to program a WeatherDuino data integrity check.
Im thinking of a sketch you can upload if there are any issues walking through the data like the eraser and sorting out any date-time combinations that as simply not possible.
Due to the bug i had the 35th of Oktober written on the Display for example. I don't know which timestamp is saved here, but it can not be good
.Moreover I'm thinking of the possibility to specify a time range where the data should be kept and the other stuff should be deleted.
Until now I do not know how the logger works or how it knows where its data is stored, but I will have a closer look at it the next days.
@Werk There is no need to do anything. I will try to make a sketch to change the logged data in a way WeeWx can handle it and does not get stuck. I think this is the easiest way to get rid of this WeeWx bug in that seldom cases.
Best regards,
engolling