Hello,
I'm implementing a driver for the Columbia Weather Systems MicroServer that
supports a variety of their weather stations including the Pulsar 600.
However, I'm still not clear on how the rain field is to be mapped. Right
now, I only have rainRate mapped but I've not been able to find how
Hmmm... how about a little more information?
1. Can you give the context of the error? More of the log would help.
2. I don't know why wxservices would be trying to calculate dayRain. Do
you have it listed under [StdWXCalculate]?
3. Where is dayRain used? Is it used in your skins?
I d
If anybody has a Davis WeatherLink Live device and would like to test my
driver that pulls data periodically via JSON, please email me and I'll set
you up.
This one would be ideal if you can spin up a VM or a pi with a throwaway
weewx db for some testing. The driver tests and runs in the fore
Busy here on packaging issues, but I just wanted to add that all releases
are tagged. So, if you want v3.9.0 for some reason,
git checkout tags/v3.9.0
would do it. But, maybe you already knew that, in which case, my apologies.
On Fri, Mar 6, 2020 at 11:07 AM Vince Skahan wrote:
> On Friday, Ma
On Friday, March 6, 2020 at 10:56:20 AM UTC-8, Greg Troxel wrote:
>
> Vince Skahan > writes:
>
> >> So basically what's missing is a branch ref stable-3-9 which started
> out
> >> pointing to master as soon as it became v3.9 time, is advanced along
> >> commits on master intended for v3.9.next,
Vince Skahan writes:
>> So basically what's missing is a branch ref stable-3-9 which started out
>> pointing to master as soon as it became v3.9 time, is advanced along
>> commits on master intended for v3.9.next, and now points to 0ecd4fed.
>>
> Totally lost. There 'is' no stable N-1 branch.
On Friday, March 6, 2020 at 10:07:29 AM UTC-8, Greg Troxel wrote:
>
> Vince Skahan > writes:
> > Greg - still missing what you're looking for that you can't already do.
> >- git pull
> >- git checkout -b v3.8.2 (create a local branch off a release
> tag)
>
> That creates a branch o
Vince Skahan writes:
> Greg - still missing what you're looking for that you can't already do.
>
>- git pull
>- git checkout -b v3.8.2 (create a local branch off a release tag)
Sorry, I misread that the first time, so my previous-message comments
about that didn't make sense.
That c
Greg - still missing what you're looking for that you can't already do.
- git pull
- git checkout -b v3.8.2 (create a local branch off a release tag)
- go wild
If you want to install a particular release, you could alternately download
the tarball from old_releases in the web page
Thomas Keffer writes:
> The merge was intended (and usually is) done just before release. It was
> our intention to do an immediate release, but we had some delays.
>
> WeeWX may be a bit different from other software you are used to. We
> *never* support old releases. Either you upgrade, or you
First, thanks to you and Thomas for replying; I was delaying on purpose
to see if anyone else commented happened and think about it.
Vince Skahan writes:
> Interesting post. Sounds like you want some kind of semi git-flow kind of
> thing except with long-lived minor-release extra level of int
Tom,
For several months I runned succesful weewx version 4.0.0a4 with raspbian
stretch on a raspberry Pi 2B.
Today I installed from scratch raspbian buster lite (2020-02-13) and weewx
version 4.0.0b14.
With each loop message I now get a debug message:
DEBUG weewx.wxservices: Unknown extensible
12 matches
Mail list logo
