Pausing data upload when sensor contact lost (Fine Offset)

[TedM]

Hello,
I recently got a Fine Offset WS2083 (badged as Aercus) and set it up running Cumulus MX on a Raspberry Pi. All was well for several days, then I started getting 'Sensor contact lost' errors. I have read lots of reports in the forum from other FO owners with the same problem, so I will follow up their suggestions about transmitter/console location, batteries, shielded leads etc. In the meantime, is there a way of preventing bad data being uploaded to the MetOffice WOW website? It appears that when sensor contact is lost, Cumulus recognises this by setting a flag, but continues to upload the last valid data, even though it may be hours old. I'd prefer to have missing data rather than errors.

Ted

[steve]

There's a request in the enhancement request section for Cumulus to stop uploading and logging when sensor contact is lost. I'll get around to it one day, hopefully!

[TedM]

Thanks Steve, it's good to know that I'm not alone with the problem, and I fully understand the constraints on your time. Although I raised it as a Fine Offset problem, there could be other instances and equipment when data that appears plausible is actually incorrect, so rather than stopping uploading and logging maybe a simpler solution would be for Cumulus to routinely output a 'valid data' flag and then leave it up to the import routine in the target system to check this. My particular interest is the MetOffice WOW site, but I don't know enough about this yet to know whether it performs any screening of input data. Just thinking aloud really...

Ted