@John Kline,I have also read the documentation and have come to exactly the same conclusion as you so that is what should be used. I am a current WOW user and intend to continue with the new service. https://claydonsweather.org.uk The the change @Tom made should be rolled back. On Wed, 24 Sept 2025 at 13:10, 'John Kline' via weewx-user < [email protected]> wrote: > no idea why @John Kilne had a different outcome
I’m not uploading to WOW-BE, but I can read documentation. I was responding to the following request from Tom:
Could someone check the WOW-BE API and see exactly what they need. That should be what we do, rather than make stations "better" or "worse". There was 3 of us getting wrong results before switching to absbaromin, the WOW-BE site was showing over 1100hPa, no idea why @John Kilne had a different outcome. I'm having a hard time following. I know the last commit fixed David's station. John: I gather it made yours worse?
Could someone check the WOW-BE API and see exactly what they need. That should be what we do, rather than make stations "better" or "worse".
-tk
For me using absbaromin, pressure readings for my station being reported by WOW-BE were consistently looking very wrong. They were approximately +10hPa higher than they should have been. Presumable the MSLP (barometer) being reported were then being (incorrectly) adjusted by WOW-BE to take into consideration the altitude of my weather station (around 105m). As soon as I changed to baromin instead, things looked much better. So far the WOW-BE barometric pressures for my station have been stable with no anomalous readings.
-- David On Sunday, September 21, 2025 at 11:40:08 AM UTC+9:30 John Smith wrote:
hPa even...
Not using absbaromin things go wonky, my station was reporting over 1100kPa at one stage...
Just a query with regards to the updated restx.py file for sending data to WOW-BE. When reporting pressure using "barometer", shouldn't the respective WOW-BE field be "baromin" instead of "absbaromin"? According the the WOW-BE site: "baromin = relative pressure (i.e. pressure reduced to sea level) and absbaromin = absolute pressure (i.e. the raw pressure measurement at the station’s location)." So for reporting pressure: - weewx parameter "barometer" corresponds to the field "baromin" in WOW-BE - weewx parameter "pressure" corresponds to the field "absbaromin" in WOE-BE May be I'm wrong, but since I modified the code to report "barometer" as "baromin" the reported pressure now seems to be correct (before the change they were abnormally high). I have a Davis Vantage Pro 2 so it makes sense for me to report "barometer" pressure since this is what is provided by the weather station.On Tuesday, September 16, 2025 at 9:02:01 PM UTC+9:30 John Smith wrote:
I've submitted a pull request for restx.py to enable sending weather data to both wow.metoffice.gov.uk and wow.meteo.be, the code is slightly modified from the diff that glennmckechnie posted to issue #1013
You can download a copy of restx.py with the changes here: https://github.com/evilbunny2008/weewx/raw/refs/heads/master/src/weewx/restx.py
Just replace the existing restx.py which resides in /usr/share/weewx/weewx/restx.py when you install using the Debian package, I don't know exactly where it would be for other install methods.
The above file is from the current weeWX master branch and only tested in weeWX 5.1.0 on Debian Bookworm running a 6.12 kernel from backports.
I have limited python experience and would value suggestions to make the code more pythonic if needed.
--
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].
To view this discussion visit https://groups.google.com/d/msgid/weewx-user/2686b8d5-5b58-4d99-801b-82855793a969n%40googlegroups.com.
--
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].
To view this discussion visit https://groups.google.com/d/msgid/weewx-user/4aa290e2-2a50-4e2b-8e58-e81be5ac7897n%40googlegroups.com.
--
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].
To view this discussion visit https://groups.google.com/d/msgid/weewx-user/CAPq0zEDVYHnru_vhi11hhM%2BagsOCQE8BPMFrmDUg-aX9pMUYYw%40mail.gmail.com.
--
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].
To view this discussion visit https://groups.google.com/d/msgid/weewx-user/CAGTinV5LjmrPJGOQON%2BMf1Em6vdnZAJJhTCcRTuHfYuOBgWmtw%40mail.gmail.com.
--
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].
To view this discussion visit https://groups.google.com/d/msgid/weewx-user/744C3E5F-17F7-45CC-AA0A-E7AD5B72A8B2%40johnkline.com.
--
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].
To view this discussion visit https://groups.google.com/d/msgid/weewx-user/CAGTinV6gy9ttPnDjrv6TfqdzgP6tEpUpP8OFi3NHFVxrnUOTsg%40mail.gmail.com.
--
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].
To view this discussion visit https://groups.google.com/d/msgid/weewx-user/2F168EE7-5941-4AEB-9AAF-60EBCCBE5FC3%40btinternet.com.
|