I’ve been messing around with this for a few months. Initially, the
external weather offset
was always returning a scale of zero because of how it was pulling OWM
data, so I brought that
service inside the house and updated the OWM code to work better. I also
implemented the
same thing using DarkSky data and calculate the scale from both. The
external thing runs on
NodeJS, which was pain to get running on an RPi, so I’m rewriting the whole
mess in python.
What’s left is to get it working as a CGI server so the OS controller can
talk to it. In terms of weewx
data, all I’m pulling at the moment is the last ~2 days of rain using a
template to write a web
page the new code fetches. That gets added to the forecast calculations.
The scale numbers
between old way and new code track, but often don’t match because of the
math related to the
3 parameters (temp and humidity mostly), which vary slightly between OWM
and DS.
No idea if the OS guys every fixed the forecasting thing or not, but they
knew it was a problem.
I’d rather have all this inside my network anyway. The WU thing only works
when you have a key,
and WU quite giving them away, which is why the OS guys switched to the OWM
api.
Once I get this in a usable state I can share it. I hadn't thought of
serving it from the main
httpd I have in the house, but that might speed things up.
Chris
--
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.
