I have a VP2. It’s been hooked up to WeeWX via the usb logger for about 2 years. I spent some time before that struggling to get a robust set up (hw, not WeeWX) and life got in the way, etc. I’ve been lurking on the groups during those years. Currently everything is not public. But I have been experimenting with a rest Api to a .net core server in Azure. Also played some with D3 to graph it.
I did hack together something to import my archive datainto InfluxDB Needs a lot of work, but maybe I can start out on that issue you have opened. I also got Istanbul running, to help me get a handle on the current tests. Again, a bit of a hack... -rich On Sun, Apr 22, 2018 at 9:04 AM Thomas Keffer <[email protected]> wrote: > Right you are! Good sleuthing! > > Fixed in commit a0045078cc > <https://github.com/tkeffer/weert-js/commit/a0045078cc2887355373eac381df8da357c30df4> > . > > I also have limited experience with Node, React, etc., but it has been a > great learning experience playing with them. > > What kind of weather station do you have WeeRT running on? > > -tk > > On Sat, Apr 21, 2018 at 2:43 PM, <[email protected]> wrote: > >> I continue to be impressed by all things Weewx. After finally upgrading >> WeeWX (easy) and struggling with upgrading node, I was able to get this up >> and running. I have limited experience with the technology being used, but >> have experimented with node some. I’m currently working on understand >> InfluxDB, but hope to be able to help some. >> As an aside, I think on aggregation, a NEW_AGGREGATE event is created and >> the test expects a a NEW_AGGREGATION event. >> - rich >> > >
