Not to flog a dead horse, but any idea why WU is showing "Station reported
-199 seconds ago" and I've gone over every place where the clock could be
wrong, all my servers etc are sync'd, so it seems like I'm able to predict
the future with my setup.
On Saturday, 28 October 2017 09:56:23 UTC-4, Tom Keffer wrote:
>
> ​Could be. Things I've noticed about the WU servers through the years:
>
> 1. The WU servers are flaky.
> 2. Especially with RapidFire
> 3. Especially when all types are not included in the WU upload
> ("partial packets").
>
> The weewx WU uploader includes a cache to get around problem #3, but the
> other two still remain.
>
> Make sure the outgoing WU urls are what you're expecting. If it includes
> parameter baromin, then it's going out OK and the problem is on the WU
> end.
>
> -tk
>
>
> On Sat, Oct 28, 2017 at 6:23 AM, Robert Mantel <[email protected]
> <javascript:>> wrote:
>
>> So I managed to calculate barometer using pressure and outTemp, and then
>> publish that in my mqtt server, looks good on my SteelSeries gauges, but
>> will is still not picking it up regularly. Is this now a Wu problem?
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected] <javascript:>.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
