On Friday, May 8, 2020 at 5:34:18 PM UTC-7, Greg Troxel wrote:
>
> Vince Skahan <[email protected] <javascript:>> writes: 
>
> Thanks.  That all makes complete sense.  What I was getting at is that 
> weewx has as I see it 4 different things (being a bit hand wavy): 
>
>   1) talk to hardware to get data 
>   2) put that data in a weewx database 
>   3) send data to CWOP etc. 
>   4) generate web pages and publish them 
>
> and it sounds like you are using weewx to do (1), and maybe a bit of (2) 
> is happening, and you have (3) publish data to influxdb, either like 
> people send to CWOP, or like people publish loop packets to mqtt. 
>
>
I do 1,2,3,4 in my weewx setup for the VP2 'plus' publishing to MQTT via 
that extension.

I do 1,2,4 in my weewx setup for the WeatherFlow Smart Weather station

In both cases I use the core 'rsync' uploader to also upload my Internet 
website.
 

> Hence you are really only using (1) and some sort of [put into influxdb] 
> part of weewx, and not using the rest.  Which all makes sense to me, for 
> what you are doing. 
>
>
For the WF Tempest I don't even use weewx quite yet, but I'll do 1,2,4 
there too once we're allowed to have public data visible with that 
currently-beta gear.
 

> > I use weewx to connect to the VP2 console in order to get the data the 
> > hardware emits in LOOP packets.  I then jump through some hoops to get 
> that 
> > data into influxdb so I can cook up an integrated dashboard. 
>
> Would be nice if that were standard, included code. 
>
>
Many things are nice, and Tom always likes to see a PR :-)

I don't sweat the influxdb part much as my convoluted way is good enough 
for me.  If it bothered me then I'd add the influxdb extension, which 
'does' exist and 'would' simplify things a lot.  I just never had a reason 
to spend the time switching to it here.  As I said, the MQTT => influxdb 
(via telegraf) thing was something I was interested in as a learning 
experience, as was using grafana as a dashboard rather than going to the 
whole TICK stack (which I looked at, but decided to not go all the way 
thattaway)

Here's a couple comparison charts from grafana

First one is solar radiation.  The green dots are maxSolarRad as calculated 
by weewx. The other lines are three different WeatherFlow sensor suites.   
As you can tell, they're still tuned a little high in value.   The 
bounciness is clouds etc. but you can even tell when each device went into 
the shade as the sun went down this evening.   It is a little funny seeing 
a drop in solar when the pole on my basketball hoop blocks the sun for a 
few minutes every afternoon.

Second graph is temperature comparison.  Green dots that are infrequent are 
the VP2 from weewx.  The others are the WeatherFlow sensors that emit data 
much more frequently, and the blue line is my arduino with a DS18b20 sensor 
on it, located inside.  Don't sweat minor differences in the outside gear, 
it all makes sense based on where they're located in the yard.  The air is 
in a fake Stephenson screen (actually, a birdhouse with lots of holes 
drilled in it) so it shows very smooth curves.  The Tempest is out in the 
air next to the VP2 so it will show bouncier fractions of a degree 
temperatures since it was gusty today with wind coming off the very cold 
water in Puget Sound a mile or so away, but if you check at 17:00 when they 
both went out of direct sunlight, they was basically identical to small 
fractions of a degF.  Good enough :-)

You 'can' do similar integrated dashboards in weewx if you map the data 
correctly and cook up custom skins.   I've seen lots of examples using only 
weewx.


-- 
You received this message because you are subscribed to the Google Groups 
"weewx-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-development/892559e5-325e-4b8d-8fdb-2a73e4987d66%40googlegroups.com.

Reply via email to