Vince Skahan <[email protected]> writes: >> when you talk about influxdb, do you mean still using weewx to >> >> get data from station >> put into influxdb >> >> get from influxdb and make graphs, as in skins >> >> ? > > I use influxdb to do data aggregation and comparison locally on the LAN, > comparing a lot of sensors from multiple vendors. > > In doing that, weewx does the talking to the Davis console hardware since I > have a serial datalogger. If I had a tcp/ip enabled datalogger or > equivalent, I wouldn't need weewx for that for most things, although > weewx's automatic catchup feature to read the datalogger menu is super > slick and very useful if we have power issues or the like. > > Influxdb is just a time-series database. It requires something else to do > graphs+dashboards. I use 'grafana' for that. Other options exist.
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. 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. > Not 'as a driver' perhaps. More like 'using the appropriate hardware to > talk to the VP2 console for me'. That's what I meant. > 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. > Examples: That's very cool stuff! > If I tried to all this via weewx only, it is technically possible, but I'd > pull my few remaining hairs out battling mapping stuff to available fields > in the weewx v4 extended schema. I'd then need to battle writing a custom > cheetah skin to display it. And I mean battle. Cheetah is kinda brutal if > you try to do to much in it. Makes sense to me, even though I've done very little in skins. > Hope this helps explain. Yes - thanks for taking the time to explain. I hope others appreciated it too. -- 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/rmipnbe3q0n.fsf%40s1.lexort.com.
